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.
- TMS for Trucking and Road Carriers
- Features
- Review and evidence
Review and evidence
Keep decisions and operational outcomes traceable while the team resolves exceptions.
OverviewReview decision history×
TMS for Trucking and Road Carriers · Review and evidence
New
Review decision history
Review decisions
| Record number | Source table | Source record | Source revision | Decision | Decided at | |
|---|---|---|---|---|---|---|
| RD-95436 | ST-888 | SR-981 | 760 | Approve | 21 Oct | |
| RD-59244 | ST-687 | SR-242 | 690 | Return | 07 Oct | |
| RD-46332 | ST-231 | SR-137 | 620 | Escalated | 13 Oct | |
| RD-65475 | ST-921 | SR-514 | 510 | Approve | 18 Oct | |
| RD-39801 | ST-444 | SR-289 | 790 | Return | 20 Oct |
6 of 6 records
ST-888Review decisions · RD-95436
ApproveSource recordSR-981
Source revision760
Decided at21 Oct
ReasonApprove rd-435
What you can do
Give an exception an owner and a history
Operations Overview brings a ranked exception queue across dispatch, fleet upkeep and evidence, with linked-record detail. Transport Manager can use it to start the shift conversation and identify the work that needs investigation. The supporting records retain decisions, operational outcomes and documents so the next person can follow the case without relying on a message thread.
A review decision describes a person’s judgment about a source record and revision. An operation receipt describes an action and its observed outcome. Keeping both available helps the team distinguish an approved plan from an action still awaiting verification. Attachments provide the bill of lading, photo, signature or other document behind the explanation.
How the work is organized
Transport Manager handles load-planning decisions, while Settlement Approver handles independent statement approval. Each reviewer identifies the source record and revision under review, records the decision and keeps a useful reason. Operational receipts carry the action, event and time, with an owner and external reference where relevant.
- Record the decision. Use Approve, Reject, Return or Escalated to explain the review result and the person responsible for it.
- Follow the outcome. Keep pending or failed receipts and those needing review visible until the responsible person reconciles the result.
- Attach useful evidence. Identify the related record and document type so another team member can find the supporting file or link.
What to agree during setup
Agree how reviewers identify a source table and record, and how the team recognizes the revision being decided. Define the reason expected for a return or rejection. Choose who owns uncertain external outcomes and how the dispatch and settlement teams hand those cases to each other.
Establish attachment naming and access rules for customer documents and signatures. A document title should help the reviewer find the right load or statement. Agree how long the organization keeps evidence and how it retains a useful reference when a connected system owns the original file. Test access using the actual staff accounts that will handle the work.
Check the handoff on an actual case
A settlement has an approval decision, but its operation receipt remains Pending after the external handoff. Settlement Clerk locates the external reference and asks the payment operator to confirm the result. Settlement Approver keeps the approved revision visible while the outcome is investigated.
If the provider confirms failure, the receipt remains Failed with follow-up assigned. If the provider confirms completion, the reviewer records the reconciled result and the clerk completes the statement with its settlement reference. During rehearsal, ask a colleague from the next shift to explain the decision and outcome separately. Repeat the exercise with a returned load plan so Transport Manager can demonstrate the same source-and-reason discipline for dispatch work.
What your team sees
- Operations follow-up — Pending or failed outcomes and receipts needing review, with owner and external reference.
- Review decision history — Decisions tied to their source record, revision and reviewer.
Follow the work through
Follow Plan and approve a load and Review and complete settlement. Agree the evidence checks in implementation.
What it keeps track of
Data model- Review decisions
- Approval, rejection and escalation decisions on records
- Operation receipts
- Recorded operational outcomes awaiting verification
- Record attachments
- Documents, photos and signature evidence attached to records
- Organizations
- Carrier, broker, shipper and operating companies using the platform
- Team members
- Dispatch, planning, safety and maintenance staff
Who uses it
Permissions- Transport Manager
- , Settlement Approver, Admin.
- Each reviewer owns decisions in their area; Admin maintains staff identity and organization access.
Set up TMS for Trucking and Road Carriers your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.