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.
- Port & Terminal Management
- Features
- Review and receipts
Review and receipts
Keep submitted revisions, human decisions and operation outcomes traceable.
OverviewMove Decision History×
Port & Terminal Management · Review and receipts
New
Move Decision History
Review decisions
| Parent | Source revision | Decision | Decided at | Reviewer | Reason | |
|---|---|---|---|---|---|---|
| LDS-35931 | 950 | Approve | 27 Oct | Approve rd-541 | ||
| LDS-79025 | 850 | Return | 06 Oct | Reject rd-685 | ||
| LDS-50703 | 180 | Approve | 20 Oct | Return rd-129 | ||
| LDS-27300 | 440 | Return | 11 Oct | Approve rd-105 | ||
| LDS-18076 | 900 | Approve | 25 Oct | Reject rd-399 |
6 of 6 records
Approve rd-541Review decisions · RD-80569
ApproveParentLDS-35931
Source revision950
Decided at27 Oct
What you can do
Make the decision about a specific revision
The Dispatcher submits a terminal container move for independent review. The Transport Supervisor examines the submitted details and records a decision against a source revision. The decision includes the reviewer, time and reason, and belongs to the parent load. Approval, rejection and return are distinct decisions. The revision matters because a decision on one set of details should not silently follow a changed container number, weight or yard slot.
Record attachments hold supporting files on the load. Each attachment has a title, evidence type, uploader, upload time and visibility. The supervisor can compare the submitted move with that evidence before deciding. The Operations Overview places authorized load, terminal move and review activity in the same operating context.
How the work is organized
The Dispatcher submits and supplies evidence. The Transport Supervisor makes the independent decision. The Auditor reads the resulting trail.
- Review record. Each decision keeps a revision, reviewer, time and reason.
- Supporting file. Attachments connect evidence to the load under review.
- Operation receipt. A stable key and expected revision tie an action to its outcome.
What to agree during setup
Agree which evidence is required for each container move type and how a reviewer checks it. Decide when a supervisor returns a move for correction rather than rejecting it. Define which attachments can be shared and who may upload them. The team should rehearse what happens when the submitted revision changes while the supervisor is reviewing it: the decision must remain tied to the version examined.
Operation receipts have a result state, action, time, external reference, effect references and failure reason. Decide how the team investigates a failed or uncertain outcome and which external reference will be recorded when a connected system confirms an event. A receipt marked needs review is a prompt to reconcile the effect before anyone retries the action.
Check the handoff on an actual case
A Dispatcher submits a move for a container scheduled to leave the yard. The load has an attachment showing the observed container details. The Transport Supervisor compares the move’s revision, completed time, weight and slot against the file. If they agree and the required custody and customs checks are available, the supervisor records approval with a reason. If the number differs, the supervisor rejects or returns the revision and leaves an explicit reason.
After the guarded action, the supervisor checks its operation receipt. A completed receipt gives the key and references for the recorded effect. A failed or uncertain receipt stays visible in Operation Outcomes so the team can investigate before repeating the action. The auditor can follow the decision and receipt back to the same parent load.
What your team sees
- Submitted Container Moves — The independent review queue for submitted work.
- Move Decision History — Reviewer, decision, reason and source revision.
- Operation Outcomes — Completed, failed and review-needed guarded actions.
Follow the work through
What it keeps track of
Data model- Container moves
- Terminal container move extensions confirmed through independent review before gate release.
- Review decisions
- Independent reviewer decisions recorded against a load revision.
- Record attachments
- Supporting documents and evidence files attached to a load.
- Operation receipts
- Durable receipts for guarded operations, keyed for idempotent retries.
- Loads
- Freight and terminal loads moving through plan, dispatch, transit and delivery.
- Team members
- Named staff members with an authenticated platform identity and role scope.
Who uses it
Permissions- Dispatcher
- , Transport Supervisor and Auditor.
- The Transport Supervisor is the deciding reviewer.
Set up Port & Terminal Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.