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.
- ELD / Hours of Service
- Features
- Duty interval review
Duty interval review
Review driver activity against the correct load before completing a verified import.
OverviewDelivered Loads×
ELD / Hours of Service · Duty interval review
New
Delivered Loads
Loads
| Record number | Counterparty | Owner | Promised delivery at | Actual delivery at | Freight amount USD | |
|---|---|---|---|---|---|---|
| LDS-32176 | TP-1947 | 21 Oct | 23 Oct | 880 | ||
| LDS-54958 | TP-5733 | 19 Oct | 28 Oct | 710 | ||
| LDS-58431 | TP-8302 | 20 Oct | 22 Oct | 120 | ||
| LDS-29615 | TP-9001 | 27 Oct | 03 Nov | 230 | ||
| LDS-51528 | TP-4289 | 03 Oct | 06 Oct | 670 |
6 of 6 records
TP-1947Loads · LDS-32176
DeliveredPromised delivery at21 Oct
Actual delivery at23 Oct
Freight amount USD880
What you can do
Give each interval an accountable review
A driver activity record needs enough context for another person to check it. Dispatcher prepares the driver identity, duty state, start time and duration against the selected load. The operating organization stays attached to the interval so the review belongs to the same business scope as the movement.
Transport Supervisor checks the submitted revision independently. The decision records the reviewer, reason and source revision. Approval permits the import to proceed; the interval becomes Completed after its operation receipt has been saved. Dispatcher can distinguish work waiting for a decision from work whose import has actually finished.
How the work is organized
- Prepare the activity. Dispatcher compares the interval with the provider record and the load context. Driver text should identify the same person as the assignment being examined. Keep the source identity with the import evidence so another operator can trace the interval later.
- Review the submitted revision. Transport Supervisor checks the frozen submission against the matching load revision. Approve, Reject and Return express different decisions. The recorded reason explains what passed or what the preparer needs to resolve before asking for another review.
- Confirm the recorded outcome. Dispatcher follows the approved action through its operation receipt. A pending or failed receipt remains work to investigate. Repeating a request uses the same operation identity so the existing outcome can be recognized.
What to agree during setup
Agree how the logging provider identifies a driver and each activity record. Decide how duty state text and local timestamps will be interpreted before importing a live shift. App Administrator maintains the organization’s time zone; the team should rehearse a source timestamp that crosses the local date boundary.
Name the independent Transport Supervisor who handles the pilot queue and who covers that responsibility during absence. Agree the evidence required for a returned submission, how a corrected revision is presented, and where the provider identity appears in operation evidence. These decisions make a later review reproducible.
Check the handoff on an actual case
Use a rehearsal load called East Depot Transfer. Dispatcher enters a driving interval beginning at 08:10 with a duration of 95 minutes and submits it. Transport Supervisor finds that the attached source record names a different driver. The supervisor records Return and explains the discrepancy; the team preserves that decision while preparing corrected information.
On the corrected case, the supervisor checks the matching revision and records Approve. Interrupt the import before its receipt is confirmed. Dispatcher should still investigate the outcome before treating the interval as Completed. Resume using the same operation identity and inspect the saved receipt alongside the provider reference.
What your team sees
- Duty Review Inbox — Submitted intervals with their driver, duration and load context ready for independent review.
- Custody Board by Status — Activity grouped by its review and completion state.
- Loading Handoffs Default List — Interval details and decision dates for day-to-day follow-up.
Follow the work through
Use Duty interval import for the review sequence and Exception reconciliation when an outcome needs investigation.
What it keeps track of
Data model- Duty intervals
- Duty intervals supporting import of a verified duty interval against the selected Loads parent
- Loads
- Freight loads from pickup to delivery with promised windows, freight value and lifecycle
- Organizations
- Logistics operating organizations with time zone, currency and active scope
- 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
Who uses it
Permissions- Dispatcher
- Prepares and follows the import.
- Transport Supervisor
- Owns the independent decision.
- Auditor
- Reads authorized activity and decision evidence.
Set up ELD / Hours of Service your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.