# Sign and stage a reviewed buy

Source: https://docs.tightly.io/help/commitments/act-sign-and-stage-a-reviewed-buy
Reviewed: 2026-10-29

## Review the buy

In **Buy plan**, the **Buy approval** section lists past reviews and has **Review buy**. It is closed, with the reason on hover, when you are read-only ("Read-only"), a saved submission needs recovering ("Recover the saved submission"), you have unsaved changes ("Unsaved changes") or no products have loaded ("No styles loaded"). **Add to Bench** opens the same review.

**Review buy** opens **Review buy cycle** (**Review next buy cycle** after a first one, **Review replacement buy** for a replacement). Pick the **Arrival** date, then press **Review physical need**. A tag beside the buttons says what is still missing, such as "Pick the first receipt date". The drawer reads the buy against stock and demand over the period it names, and shows each product's planned and required units. Changing the products, the commitments taking part, the supplier choices or a replacement cycle makes a different review. If demand, stock or the buy changed, the drawer says "Demand, stock or buy changed · review again before staging".

Where a reviewed count is available, **Preview with reviewed counts** reads the need again. It is marked "Reviewed count · Awaiting source confirmation" and "Preview only. The source has not confirmed stock or allocations; orders remain blocked." Such a preview cannot be submitted or staged. Clear it and review normally to go on.

## Submit the exact buy

Where approval applies, the drawer reads **Approval required**, **Awaiting approval** or **Approved**. Press **Submit reviewed buy**. Submission freezes the reviewed selection and its evidence as an approval request. It does not approve the request, stage anything or create a supplier order. If the answer is interrupted, **Recover approval submission** checks the saved request instead of sending another. Until you have reviewed and, where required, submitted, the drawer's tag says "Review this buy first", "Submit it for approval first" or "Awaiting approval".

## Approve or reject

Open a review from **Buy approval** to read **Reviewed buy**: its status, **Reviewed cost**, **Units**, **Delivery** and **Reviewed supply**. The organisation's approval policy decides who may decide, and a policy may require **Different approver required**. A pending review has **Decision note**, **Reject** (which needs a note) and **Approve reviewed buy**. Status is **Approved**, **Rejected** or **Changed since review**. A material change after approval makes the request stale: it keeps its approved history but needs a current review and approval before staging. Rejection keeps the request and its evidence and deletes no plan.

## Stage the signed buy

Once the buy is approved and still current, press **Create buy cycle** (**Create next buy cycle**, **Replace reviewed buy cycle** or **Create reviewed joint buy** as the case may be). It stages the purchases on the Bench. The drawer reads "Buy cycle created." with **Review Bench**, and links to any draft builds or transfers it created. An interrupted staging reads "Staging unconfirmed · retry the same request to recover the result." with **Retry staging**.

## Ask Tightly

Ask Tightly may propose the three steps separately: submitting a reviewed buy, deciding it, and staging it. Each waits for your **Yes** or **No**.

> Submit this exact dated buy and its material evidence for native approval. This records no order.

> Approve reviewed buy {number} against its frozen material snapshot. This records no order.

Reject reads the same, with "Reject". Submitting is not signing, and signing is not staging. Ask Tightly cannot invent an approver or treat a chat as a signature, and it offers a decision only when your seat may take it. Over MCP nothing here writes.

If the signed buy needs different quantities, dates or routes, review a replacement cycle and obtain the approval again; do not edit the Bench to get round the signed evidence.
