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.
- Warehouse + Fleet + Delivery
- Features
- Review and evidence
Review and evidence
Trace decisions, attachments and operation results when work needs review.
OverviewUnresolved operation receipts×
Warehouse + Fleet + Delivery · Review and evidence
New
Unresolved operation receipts
Operation receipts
| Parent | Operation key | Action | Expected revision | Result state | Failure reason | |
|---|---|---|---|---|---|---|
| LDS-52902 | OK-994 | ACT-271 | 480 | Failed | Cut to length | |
| LDS-96900 | OK-924 | ACT-397 | 200 | Needs review | Weld frame | |
| LDS-62776 | OK-786 | ACT-643 | 930 | Failed | Drill and tap | |
| LDS-68051 | OK-386 | ACT-384 | 340 | Needs review | Deburr | |
| LDS-25400 | OK-459 | ACT-802 | 670 | Failed | Assemble |
6 of 6 records
OK-994Operation receipts · OR-32554
FailedParentLDS-52902
ActionACT-271
Expected revision480
Failure reasonCut to length
What you can do
Keep the action and its evidence together
A review decision is an independent answer about a load’s source revision. It records the reviewer, decision time, reason and operation key. An operation receipt records an attempted action under a stable key, the expected revision, its result and any failure reason or external effect references. An attachment adds a titled file or evidence reference to the load, with an evidence type, visibility and uploader. Together, these records let the Operations Manager follow what was decided, what was attempted and what actually completed.
Operations Overview is the triage point for active loads, pending decisions and failed operations. A reviewer can move from the load to the relevant decision and receipt. That is especially useful after a shift change, when the person resolving a failed action did not prepare the original handoff or dispatch.
How the work is organized
- Decide. Independent Reviewer records approve, reject or return on the current source revision and gives a reason.
- Execute. Dispatcher or Warehouse Lead uses a stable operation key for the authorized action and checks its durable result.
- Reconcile. Operations Manager checks failed receipts against linked local effects and the authoritative source before clearing the issue.
The receipt can be pending, completed, failed or needing review. A failed result is not a direction to repeat external work immediately. The reconciliation sweep is read first: it checks what already happened, records the discrepancy and moves unresolved work into review. Correction and cancellation retain original evidence and use a compensating receipt. The team can therefore see the first attempt and its authorized follow-up.
What to agree during setup
Define who may review a custody transfer or an excepted load. Keep that person independent from the preparer. Decide which attachments may be shared and which remain internal. Agree what external reference should be stored when a carrier or fleet system supplies the authoritative outcome, and who can resolve a mismatch between the local receipt and that system.
Set a stable key policy for each operation scope. The same requested action on the same source revision should resolve to its existing receipt on retry. Agree how an authorized correction refers to the earlier action and who may cancel unexecuted scope. External effects need explicit reconciliation with their owner; a local status change alone does not reverse them.
Check the handoff on an actual case
Submit a custody handoff and have the Independent Reviewer record a decision against the submitted revision. Complete the transfer and inspect the operation receipt. Repeat the request using the same key; confirm that the team sees one durable result. Attach a load evidence file marked internal, then check who can view it.
Next, simulate a failed completion receipt with an effect reference. The Operations Manager checks the linked load, decision and effect before marking it for review. If a correction is authorized, keep the first receipt and evidence, then add the compensating action. The case is complete when a new shift can explain the outcome from the records without recreating the external work.
What your team sees
- Unresolved operation receipts — Failed and needs-review actions with their reason and expected revision.
- Review decisions — The reviewer, decision and reason attached to a load revision.
- Delivery evidence — Attachments grouped by load and visibility.
Follow the work through
See exception review and custody review.
What it keeps track of
Data model- Review decisions
- Independent approval, rejection or return decisions on a source revision
- Operation receipts
- Idempotent operation receipts recording executed or failed actions with stable keys
- Record attachments
- Evidence files attached to loads with visibility and evidence type
- Loads
- Freight loads from pickup to delivery with promised windows, freight value and lifecycle
- Loading handoffs
- Warehouse-to-driver custody handoff extensions with review and completion state
- Team members
- Staff membership linking platform users to organizations with operational roles
Who uses it
Permissions- Independent Reviewer
- Makes custody and exception decisions.
- Operations Manager
- Reconciles failed effects.
- Dispatcher
- And Warehouse Lead supply action and physical evidence.
Set up Warehouse + Fleet + Delivery your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.