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.
- Last-mile Delivery Platform
- Features
- Review and evidence
Review and evidence
Connect human decisions, attached files and operation outcomes to the load revision.
OverviewReview Decisions Default List×
Last-mile Delivery Platform · Review and evidence
New
Review Decisions Default List
Review decisions
| Parent | Source revision | Decision | Decided at | Reason | Reviewer | |
|---|---|---|---|---|---|---|
| LDS-30447 | 20 | Approve | 07 Oct | Approve rd-806 | ||
| LDS-41811 | 420 | Return | 23 Oct | Reject rd-294 | ||
| LDS-73933 | 760 | Approve | 26 Oct | Return rd-819 | ||
| LDS-83116 | 290 | Return | 26 Oct | Approve rd-582 | ||
| LDS-28572 | 560 | Approve | 17 Oct | Reject rd-476 |
6 of 6 records
Approve rd-806Review decisions · RD-77146
ApproveParentLDS-30447
Source revision20
Decided at07 Oct
What you can do
Make the decision traceable
A review decision belongs to a load and a reviewer. It records the source revision, an approve, reject or return decision, decision time, reason and operation key. This lets Operations Reviewer distinguish the case that was decided from a later edit to the same load. A return decision on an exception keeps the load available for further handling; it is not an automatic cancellation.
Operation receipts attach to loads and record a stable key, action, expected revision, result state and occurrence time. They can hold references to an external action or local effects and a failure reason. A receipt marked Failed or needs review draws attention to work that must be reconciled before anyone assumes the external or local effect happened. Record attachments keep evidence files, their type, uploader, upload time and Internal or Shared visibility with the parent load.
How the work is organized
- Decide. Record who reviewed the source revision and why they approved, rejected or returned it.
- Retain. Keep evidence files and their visibility beside the load they support.
- Reconcile. Inspect failed action receipts against linked effects before resolving a discrepancy.
What to agree during setup
Agree which decisions require an Operations Reviewer and which belong to the Warehouse Handoff Reviewer. Define when a reviewer should return work to the dispatcher rather than reject it. Decide who can change an evidence file’s visibility and who may read Internal material. The reason field should tell the next person what to correct, not merely repeat the decision label.
Set an escalation window for Failed and needs review receipts. If an operation has an external reference, identify the external authority the reviewer must consult. An apparent retry must use the stable operation key and expected revision so the team does not duplicate the effect. Reconciling a receipt is a read-first investigation; it is not permission to perform the external action again.
Check the handoff on an actual case
A load enters Exception after a delivery problem. Operations Reviewer opens the load, checks its owner, stops and evidence, then records a Return decision for the current revision with a reason. Dispatcher can correct the operational issue while the original decision remains linked to the revision reviewed. If a receipt for the same load is Failed, the reviewer compares its effect references with the local records and the authoritative external source before deciding whether it needs further review.
Try a later edit to the load after the decision. The source revision in the decision shows that the earlier approval was for a different state. Try a duplicate operation key and check that it is treated as the same attempted action rather than a new authorized delivery. Keep attached proof with its intended visibility throughout the investigation.
What your team sees
- Review Decisions Default List — Decisions with their source revisions, reasons and reviewers.
- Operation Receipts Default List — Failed and needs-review operations for reconciliation.
- Evidence Attachments — Load files with evidence type, uploader and visibility.
Follow the work through
Read delivery to review and stop to proof. The roles page supports access 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
- Delivery stops
- Delivery stop records supporting the complete-a-delivery-stop operation with proof and recipient exception evidence
- Team members
- Staff membership linking platform users to organizations with operational roles
Who uses it
Permissions- Operations Reviewer
- Owns exception decisions and reconciliation.
- Dispatcher
- Corrects the load.
- Warehouse Handoff Reviewer
- Decides submitted custody.
- Admin
- Manages access.
Set up Last-mile Delivery Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.