Review and evidence

Keep decisions, attachments and operation outcomes attached to the request they concern. Keep the related request, decision and stock evidence together as the case moves between people.

• Record the operating identity. A review decision records a source revision, decision, reason, time and reviewer. The parent request identifies the operational case. An approval is meaningful only when the decision and the current request revision match. Return and Reject remain recorded outcomes that explain why work paused.
• Keep the control visible. A record attachment keeps a titled file, evidence type, upload time, visibility and uploader under the same request. Internal and Shared are the recorded visibility choices; agree who may use each before uploading. An attachment supplies context; the decision record still identifies who made the call.
• Make the decision traceable. An operation receipt identifies guarded attempts by operation key and action. Expected revision and result state help a reviewer distinguish a completed effect from a failure or a case needing review. Effect references can point the reader toward the stock movements that resulted.

Agree the minimum evidence to attach for each request type, who can share files, and how reviewers write reasons. Assign responsibility for reconciling failed and review-needed receipts with movements before treating a request as complete.

Use a real size-color SKU and storage location to rehearse the first case. App Administrator should confirm the entity and site codes; Inventory Coordinator and Inventory Reviewer should agree which revision is ready for a decision. Keep that convention available to Auditor when the movement is reconciled.

A coordinator submits an urgent location change and uploads the supporting file. The reviewer sees the current revision, checks the file and records Return because the destination is unclear. A corrected revision receives a new decision. Later, the operation receipt says needs review, so the reviewer traces the effect references and posted movements before resolving the case. The earlier return remains part of the audit trail.

At the handoff, compare the current request revision with the reviewer decision and any related lot, claim, receipt or posted movement. If a reference differs, give the case back to Inventory Coordinator with the mismatch named. Keep the earlier decision and effect visible to Auditor.

• Operations needing review — Guarded attempts that need reconciliation and a failure reason.
• Requests in review — Current cases waiting for a revision-specific decision.

Open the underlying record before making a decision that depends on revision, expiry, ownership or location. Inventory Reviewer should read the linked request and evidence before recording a reason; Auditor can follow the same references later.

See the operating handoff and the implementation sequence. Use the data model when mapping existing identifiers and references.