Evidence

A stock request is the common parent for hazard checks, review decisions, attachments, movements and operation receipts. That structure gives the team a place to inspect the complete case. A reviewer decision includes the source revision, decision, reason, time, operation key and reviewer. An attachment includes its title, file, evidence type, visibility, upload time and uploader.

An operation receipt records what the operation produced: Pending, Completed, Failed or needs review. The result matters because an approved request does not by itself prove stock moved. The reviewer can read the decision, the operator can read the posted effect, and the coordinator can read the receipt before reporting the case complete.

• Keep decisions attributable. Record the reviewer and the exact revision being decided.
• Keep files attached. Add inspection documents or photos to the parent request with an evidence type and visibility.
• Read the effect. Compare the receipt with linked movements before treating an operation as complete.

Agree which documents a review requires and whether each attachment is Internal or Shared. Define who may change visibility and who can read the file after the request closes. Decide what a useful decision reason must contain, particularly for Reject or Return. The record should tell a later reviewer what changed and why the work stopped or resumed.

Set an owner for Pending, Failed and needs review receipts. The owner should compare expected revision and effect references with the local request and movements before any repeat action. If an external system is connected, its reference needs the same comparison. A missing or uncertain external response is a reason to investigate, not a reason to create another stock effect blindly.

Choose a request with an approved hazard check and attached SDS file. Confirm the decision shows the reviewer, source revision and reason. Post a movement and check its receipt, linked effect references and parent request. Then simulate a needs review receipt: have the coordinator compare revision, quantity and linked movement before marking an outcome. Finally, return a revised request to the reviewer and confirm the prior decision remains visible rather than being overwritten by the new one.

• Receipts needing attention — Operations whose result calls for reconciliation.
• Review decision history — The recorded Approve, Reject and Return calls with reviewer and reason.
• Requests awaiting review — Parent requests whose current scope needs a decision.

See inspection and approval and outcome review.