> For the complete documentation index, see [llms.txt](https://docs.cloudscaff.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudscaff.com/site-management/returns-from-site.md).
# Returns from Site
## **Purpose**
A Return from Site allows teams to alert the yard that inventory is ready to be collected.
This ensures accurate stock control by recording:
* What items are being returned
* Any extra/over-returned items found on site
* Supporting notes and documents
***
## **How to Access**
Main menu → Sites → Select Site → Returns tab
***
## **How It Works (Summary)**
1. **Create Return**
* Open the Returns tab and click the plus button.
* Enter return date, notes, and reference if needed.
2. **Add Return Quantities**
* Enter the quantities being returned for items currently on site.
3. **Capture Over-Returned Items**
* Add any extra items found on site that were never issued.
4. **Upload Documents**
* Add photos, delivery notes, or supporting files.
5. **Submit Return**
* Return appears as "Pending" and notifies the inventory team.
***
## **Key Rules**
| Rule | Meaning |
| ---------------------------------------- | ----------------------------- |
| Only site users can submit a site return | Yard must process and approve |
| Over-returns must be logged separately | Ensures accurate audit trail |
***
## **What Happens Next**
* The inventory manager reviews the return.
* Driver details are added, and collection is scheduled.
* The site is notified when the return moves to Outbound.
* Yard receives, recounts, sorts, and approves the return.
* Stock levels update across the site and yard.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.cloudscaff.com/site-management/returns-from-site.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.