1. SCM with Container Tracking
  2. Features
  3. Review and evidence
Feature · Review and evidence

Review and evidence

Retain decisions, files and action outcomes with the load they concern.

OverviewDecision Register
SCM with Container Tracking · Review and evidence

Decision Register

Review decisions

New
DecisionDecided atReasonSource revisionReviewerParent
Approve11 OctApprove rd-816180LDS-43929
Return07 OctReject rd-639420LDS-25376
Approve03 OctReturn rd-267160LDS-48143
Return10 OctApprove rd-399860LDS-33045
Approve03 OctReject rd-195830LDS-11534
6 of 6 records
Approve rd-816Review decisions · RD-48365
Approve
Decided at11 Oct
Source revision180
ParentLDS-43929
Example screen with sample data

What you can do

Review and evidence

A review decision records a choice, reason, reviewer, source revision and time. An operation receipt records an action, operation key, expected revision, result state and time. Both link to the load, which gives a reviewer one place to inspect what was requested and what happened.

Attachments carry a title, file, upload date, visibility and evidence type. They can hold a document or photo supporting a stop, delivery or review. A receipt may also carry an external reference, effect references or failure reason, helping the team distinguish a completed action from a failed one.

How the work is organized

  • Record the decision. Keep reviewer, reason and source revision together on the load.
  • Read the receipt. Compare action, operation key and result before repeating work.
  • Keep the file. Attach the supporting document with its visibility and evidence type.

What to agree during setup

Agree what evidence must accompany a container review, pickup, delivery and correction. Decide which files may be shared and who can upload them. Keep review reasons specific enough that another supervisor can understand a rejection or return without relying on private conversations.

The Transport Supervisor checks a submitted booking revision independently and records the decision. If an action fails, the supervisor reads its receipt and linked evidence before marking it for further review. A repeated operation key should return the prior result rather than create a second effect.

Check the handoff on an actual case

For a booking submitted after an ETA change, the reviewer inspects the current revision and records a reason. The action receipt shows the operation key and result. If the result fails, the team keeps the failed receipt, reviews the linked load, and records the discrepancy rather than deleting the attempt.

Before the next shift treats the booking as approved, its Dispatcher checks the booking status as well as the supervisor decision. The decision action records evidence and a receipt, but does not itself change the booking or parent load. A failed receipt stays available for the Transport Supervisor to inspect.

For a returned review, read the reason and source revision before preparing another submission. Keep the earlier decision and receipt with the load, then use the current booking revision for the next review. That history lets an Auditor follow what was considered.

What your team sees

  • Decision Register — Trace reviewer, reason and source revision.
  • Receipt Register — Read action outcomes and failure reasons.
  • Failed operations — Focus reconciliation on results that need inspection.

Follow the work through

Read the operating process and the related handoff. Set up roles and rehearse the case in implementation.

What it keeps track of

Data model
Review decisions
Logs an approval or rejection made during a review, recording who decided what and why.
Operation receipts
Records the result of an action taken in the system, for audit and troubleshooting later.
Record attachments
Holds a file attached to a record, such as a photo or document, kept as supporting evidence.
Loads
Represents a freight shipment, tracking its pickup, delivery, and billing from start to finish.
Container bookings
Tracks a container booked on a vessel, following its shipment from booking through arrival.

Who uses it

Permissions
Transport Supervisor
Reviews and reconciles.
Dispatcher
Adds operating evidence.
Auditor
Reads the decision and receipt history.

Set up SCM with Container Tracking your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started