These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Spare Parts SCM
- Features
- Review and evidence
Review and evidence
Retain the decision, supporting files and guarded operation result.
OverviewReview decision log×
Spare Parts SCM · Review and evidence
New
Review decision log
Review decisions
| Id | Decision | Source revision | Decided at | Reason | Reviewer | |
|---|---|---|---|---|---|---|
| IDD-913 | Approve | 920 | 13 Oct | Approve rd-581 | ||
| IDD-435 | Return | 240 | 08 Oct | Reject rd-360 | ||
| IDD-552 | Approve | 910 | 17 Oct | Return rd-231 | ||
| IDD-948 | Return | 270 | 11 Oct | Approve rd-479 | ||
| IDD-104 | Approve | 280 | 20 Oct | Reject rd-518 |
6 of 6 records
IDD-913Review decisions · RD-27702
ApproveSource revision920
Decided at13 Oct
ReasonApprove rd-581
ParentSR-67622
What you can do
Retain the decision, supporting files and guarded operation result
A review decision is a separate record linked to the parent stock request. It stores the source revision, decision, reviewer, reason, decision time and operation key. Approval, rejection and return remain distinct outcomes. For a critical-spare reorder, the workflow freezes the submitted revision and asks an independent Inventory Reviewer to decide. The decision history should explain why a case advanced or returned without overwriting the earlier review.
Attachments hold evidence for the request, with title, file, evidence type, uploader, time and its visibility setting. An operation receipt records the guarded command’s key, action, expected revision, time and result. The receipt result tells an administrator or reviewer whether the command completed or needs investigation. Together, the receipt and decision connect human authority with the operation outcome. The reviewer reads the source revision on the decision and the expected revision on the receipt. If they differ, the reviewer investigates the case before relying on the result.
How the work is organized
- Independent review. Keep the preparer and reviewer separate for the submitted revision.
- Visible evidence. Label attachments by type and sharing level before review.
- Operation trace. Use the receipt key and result to find repeated or failed commands.
What to agree during setup
Agree which evidence types are expected for a critical reorder and who may share a file. Decide how returned decisions are explained to the coordinator and who inspects failed or review-needed receipts. Rehearse the same operation key twice and a stale revision. A reviewer should see the decision and its related request before resolving an exception.
Check the handoff on an actual case
A coordinator submits a critical-spare reorder for a controller. The reviewer finds that the attached compatibility note covers an older model and returns the revision with a reason. The coordinator adds a new file, updates the critical-spare record and submits a later revision. A different reviewer approves it. The decision log shows both actions and their source revisions. The reviewer checks the attachment against the equipment model and requested units before acting. The administrator can use the receipt key to identify the same command on a later investigation. If the guarded operation needs review, the reviewer checks the receipt against the persisted decision before the team treats the command as complete.
What your team sees
- Review decision log — Approvals, rejections and returns with reasons.
- Operations needing attention — Failed and review-needed receipts for reconciliation.
Follow the work through
What it keeps track of
Data model- Review decisions
- Independent approve, reject and return decisions recorded against request revisions.
- Record attachments
- Evidence files attached to stock requests.
- Operation receipts
- Idempotent operation receipts for guarded workflow commands.
- Critical spares
- Critical-spare reorder extensions with criticality, minimum units and review state.
- Stock requests
- Stock requests that drive receive, move, reserve, consume and reorder operations.
- Team members
- Authenticated platform users acting as inventory coordinators, reviewers and administrators.
Who uses it
Permissions- Inventory Reviewer
- , Inventory Coordinator, Auditor, App Administrator.
- Reviewers decide; coordinators supply evidence; auditors and administrators inspect the history.
Set up Spare Parts SCM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.