Review and evidence

A review decision binds a named reviewer, decision, reason and time to a particular stock request revision. Approve, Reject and Return give the reviewer distinct outcomes. Attachments preserve request evidence with an uploader and Internal or Shared visibility. Operation receipts hold a stable operation key, expected revision, action, outcome and any failure reason.

The reviewer records which request revision was examined, the decision, reason and time. Attachments stay with the parent request and show who uploaded them and whether they are Internal or Shared. An operation receipt records a separate action outcome; a Completed receipt does not by itself establish a posted stock effect.

• Check the revision. Inventory Reviewer compares the current request revision with the source revision on the decision.
• Keep the reason. Record Approve, Reject or Return with the reviewer, decision time and explanation.
• Trace the action. Read the operation key and result state, then match any posted movement and attachment to the parent request.

Agree who can review a coordinator request, what supporting file is needed, and when a receipt should be investigated. A reviewer checking a request for an urgent store transfer should compare the requested units, item, location and current revision with the attached evidence. The decision reason should explain the choice to someone reading the case later.

Inventory Reviewer owns the decision and exception check. Inventory Coordinator supplies request evidence and follows up on action results. Auditor reads the authorized trail. App Administrator maintains the people and locations involved.

When a guarded action fails or needs review, the coordinator and reviewer can inspect the receipt without treating it as a completed stock effect. Match any posted movement to the parent request and source effect key. Keep an independent decision record even when a proposal is later changed or cancelled.

Use a request whose required date is near and whose quantity changed during review. The reviewer checks the new revision before deciding, records a reason and keeps the attachment with the case. If a receipt says Failed or needs review, compare its expected revision and operation key with any posted movement. Preserve the receipt even when a later correction or retry succeeds.

• Review decisions by request — Reviewer, revision, outcome, reason and decision time for each parent case.
• Pending operation receipts — Pending, Failed and needs review action results for investigation.
• Requests awaiting review — Current requests whose decision is due.

See request review for the decision path and stock execution for the resulting stock effect. The data model shows the record links behind the screens.