Review and evidence

Inventory Reviewer records a decision against a particular request revision. The decision can approve, reject or return the work for correction. Its reason, date, reviewer and operation key travel with the request. This gives the next operator a clear answer when they ask why quantity was released or why a return stopped.

Record attachments hold the supporting files. Their evidence type explains what each file represents, while visibility distinguishes internal material from material shared more broadly. Uploaded time and uploader help the team see whether a file arrived before or after the review. For a disputed return, the original file and the decision should remain easy to find from the parent request.

• Collect. Inventory Coordinator adds files to the request and checks that the title and evidence type make sense to a reviewer.
• Decide. Inventory Reviewer reads the current revision and records the decision with a reason.
• Reconcile. Inventory Reviewer and Auditor follow operation receipts and stock effects after action.

Define the minimum evidence for a returned item. A damaged unit may need a photo and the receiving note; another case may need a lot label or a customer reference. Decide which files should be Internal and which may be Shared. Give reviewers a common rule for when to return a case for correction instead of rejecting it outright.

Agree how to handle an operation receipt marked Failed or needs review. The receipt has the attempted action, operation key, expected revision, time and failure reason. The team should inspect it alongside any movement or refurbishment effect before retrying the action. A repeated operation key should lead to reconciliation of the first attempt, because the receipt is intended to identify a guarded attempt uniquely.

Use a request with a receiving attachment and a changed requested quantity. Ask Inventory Reviewer to compare the attached evidence with the current revision. The reviewer records a return decision if the file supports the earlier quantity only. The coordinator corrects the request, adds the new supporting file and submits the updated revision. The final approval should retain its own reason and date.

Then inspect an operation receipt on the same request. If it says Completed, compare its effect references with the posted movement. If it says needs review, route it to the reviewer before another execution attempt. Auditor should be able to read the decision register and understand which revision was approved and which action produced the eventual stock effect.

• Review decision register — Decisions with source revision, reason, reviewer and date.
• Requests in review — The work package awaiting a decision.
• Operation exceptions — Failed and needs-review attempts needing reconciliation.

See request review and exception reconciliation.