Review and evidence

Review Decisions record a decision, reviewer, date, reason, operation key and source revision against a stock request. Inventory Reviewer is separate from the person who submits the work. This matters when a request is revised: a prior approval should remain evidence of what was considered then, while the changed request needs its own decision. An administrative account cannot stand in for the reviewer simply because it can maintain user access.

Record Attachments hold a title, evidence type, file, upload date, visibility and uploader on the parent request. The team can keep inspection material and other supporting evidence beside the decision rather than rely on an email thread. Visibility identifies whether an attachment is Internal or Shared. Reviewers and auditors should use their authorized view of these records when checking the history.

• Decision. The reviewer chooses Approve, Reject or Return and records a reason for the source revision.
• Supporting evidence. Attachments stay linked to the request, with uploader and visibility retained.
• Result. An operation receipt identifies the action, expected revision, outcome and any failure reason.

Agree what evidence is required for a receipt, movement, reservation and recall decision. Define who can mark an attachment Shared and who can see Internal material. The reviewer should check the current request revision and its item, lot and location context before recording a decision. Give each operation a stable key so a second attempt can be reconciled with the first receipt rather than mistaken for unrelated stock work.

Pilot one request that is approved and one that is returned. Compare the reason, revision and reviewer on each decision. Attach a small example of supporting material, then check whether an Auditor can read the authorized record without gaining permission to change it. If a later operation fails, the failure reason and linked request should make the next investigation clear.

A coordinator submits a request to receive inspected stock. The reviewer finds that the location needs clarification and records Return with a reason. The coordinator updates the request and submits the new revision. A later approval applies to that revised version. The operation receipt identifies the expected revision and result. A person reviewing the case next week can tell which decision applied to which revision and whether the stock effect was completed or needs attention.

• Review decision history — Decision, date, source revision, reason and reviewer on the request.
• Operation exceptions — Failed or needs review receipts with the action and failure reason.
• Requests in review — Current work awaiting an independent decision.

See stock request review for the human decision and exception review for a receipt that needs attention.