> 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/workflows/inventory-standard-site-to-site-transfer-workflow-2-signatures-required.md).

# Inventory - Standard Site-to-Site Transfer Workflow (2 signatures required)

## Purpose

The Standard Site-to-Site Transfer workflow allows users to move inventory from one project site to another while maintaining full accountability, traceability, and a complete audit trail.

Both the sending site and the receiving site must sign to confirm ownership of the inventory.

This ensures clear responsibility for every movement between sites.

***

## Inventory Flow

Sending Site Signs to Release → Inventory In Transit → Receiving Site Signs to Accept

***

### 1. Start a Transfer

1. Open the **sending site**
2. Go to the **Transfers** tab
3. Click **Add (+)**
4. Select:
   * **Transfer From** = sending site
   * **Transfer To** = receiving site
5. Enter the transfer date
6. Add item quantities
7. Upload documents or photos if required
8. Click **Submit Transfer**

{% hint style="info" %}
[Quick Link: How to Perform a Site-to-Site Transfer](/inventory-management/transfers/standard-transfer-process.md)
{% endhint %}

***

### 2. Sending Site Sign-Off (Release Inventory)

1. Open the transfer in **Outbound Transfers**
2. Review listed items
3. Add **Name and Signature**
4. Click **Release Inventory**

**Outcome:**

* Items are deducted from the sending site
* Items move into **In Transit** status

***

### 3. Receiving Site Sign-Off (Accept Inventory)

1. Open the receiving site
2. Go to **Inbound Transfers**
3. Select the transfer
4. Review items
5. Add **Name and Signature**
6. Click **Receive Inventory**

**Outcome:**

* Items are added to the receiving site
* Transfer is fully completed and traceable

***

### Variances

If quantities are incorrect:

* Receiving site can submit a new return or transfer to correct differences
* Inventory Management Team can assist with balancing adjustments

***

### Roles

* **Sending Site User:** Creates and signs to release
* **Receiving Site User:** Signs to accept
* **Inventory Management Team:** Can view, monitor, and reconcile

***

> **Tips:**
>
> Double-check Transfer From and Transfer To site selection
>
> Use Reference Codes for PO numbers, job numbers, or internal identifiers
>
> Upload documents/photos for clarity and audit proof


---

# 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/workflows/inventory-standard-site-to-site-transfer-workflow-2-signatures-required.md?ask=<question>&goal=<endgoal>
```

`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.