Reviews and evidence

A review decision records the source revision, decision, time, reason, operation key, parent request and named reviewer. The choices are Approve, Reject and Return. That record gives Inventory Reviewer a clear place to explain a decision, while Inventory Coordinator can see whether the request may proceed or needs correction. The decision concerns a specific revision, so a changed quantity or stock identity should be evaluated again.

Supporting attachments are linked to the request and carry a title, evidence type, upload time, visibility and uploader. Internal and Shared visibility let the team distinguish material intended for different audiences. The operating team should agree what to attach for a receipt, movement, reservation or consumption confirmation.

• Decision. The reviewer records an outcome and reason against the source revision.
• Attachment. The coordinator keeps the underlying file with its parent request and audience setting.
• Outcome. An operation receipt keeps the attempted action, expected revision and result state.

Define which requests require independent review and who can act as Inventory Reviewer for each organization. Agree how to avoid a person deciding their own prepared request. Review the attachment visibility rule with the people who may share records outside the operating team. A file marked Shared should be deliberately selected rather than inherited from a casual upload.

Agree how the team handles operation receipts in Pending, Failed or needs review. Each receipt has an operation key and can carry external and effect references or a failure reason. The reviewer needs a practical procedure for comparing that record with the resulting stock movement or usage record. A Completed result should correspond to the linked effect the team expected.

Take a request in Review with a particular revision. Attach the inspection or instruction file, enter the evidence type and choose its visibility. Ask a different team member acting as Inventory Reviewer to decide and explain why. Change the requested units in a second revision and confirm that the earlier decision is not used as the current answer. Keep both the request context and decision history available to Auditor.

Next, inspect an operation receipt for the same request. Follow its effect references and compare them with any posted movement. If the result is Failed or needs review, assign the exception for reconciliation before declaring the action complete. The Operations Overview and operation exceptions list give the team a place to start that review.

• Requests awaiting review — Request revisions ready for the reviewer’s decision.
• Operation exceptions — Failed and review-needed attempts with reason and parent request.
• Review outcomes — Decision history with source revision, reviewer and reason.

See request review and evidence reconciliation.