1. Driver Safety & Training
  2. Features
  3. Completion and Follow-up
Feature · Completion and Follow-up

Completion and Follow-up

Close verified coaching and review outstanding operation results while preserving executed evidence.

OverviewOutstanding Operations
Driver Safety & Training · Completion and Follow-up

Outstanding Operations

Operation receipts

New
ParentOperation keyActionExpected revisionResult stateOccurred at
LDS-68426OK-631ACT-213590Pending12 Oct
LDS-25945OK-318ACT-37440Failed18 Oct
LDS-42648OK-842ACT-431890Needs review03 Oct
LDS-34378OK-198ACT-599330Pending26 Oct
LDS-19435OK-712ACT-23040Failed27 Oct
6 of 6 records
OK-631Operation receipts · OR-25049
Pending
ParentLDS-68426
ActionACT-213
Expected revision590
Occurred at12 Oct
External referenceER-193
Example screen with sample data

What you can do

Check the outcome after the decision

An approved coaching session still needs the evidence that establishes its completion. Dispatcher follows the eligible closure action after Transport Supervisor’s review and retains the resulting operational context. The session’s Completed state describes that coaching outcome. The load’s delivery, driver eligibility and vehicle readiness retain their own meaning and update process.

Operation receipts help the team inspect what happened after an action was requested. They record an operation key, action, expected revision and result state, with references and a failure reason where relevant. Pending, Failed and results needing review remain part of the follow-up queue. Transport Supervisor reads the evidence before deciding how to reconcile the outstanding work.

How the work is organized

  • Verified closure. Confirm the exact session and the evidence required to complete it. Keep the supervisor’s decision and source revision traceable to that work. A session sharing a load with an approved session still needs its own outcome established before it can be treated as complete.
  • Outstanding actions. Read the action receipt alongside the source record and any external reference. Identify what was requested and what the retained evidence shows. The reconciliation process returns outstanding results for reviewer attention and starts by reading, rather than blindly repeating external execution.
  • Authorized correction. Explain the reason when canceling unexecuted draft scope. Preserve evidence of work that has already happened. An externally controlled effect follows the responsible system’s process; a local cancellation must not be treated as an automatic reversal of that effect.

What to agree during setup

Agree the evidence that supports coaching closure and the person responsible for following the result. Define how a session and action are identified when several coaching records share the same load. Retain the operation key during investigation so the supervisor can distinguish the intended request from other actions on the parent record.

Choose how the team handles pending or failed results and who checks an external confirmation. Establish what can be canceled while still unexecuted and how the team raises a correction involving executed work. The Auditor should be able to inspect the original evidence and subsequent explanation without changing either. Confirm these responsibilities before the operating process is released.

Check the handoff on an actual case

An illustrative coaching session has an approved independent review and the agreed assessment evidence. Dispatcher requests closure and checks the resulting session and action records. Transport Supervisor confirms that the retained evidence belongs to the intended session. The completion result should leave the original load proof and the driver’s external eligibility record unchanged.

Now rehearse an outstanding receipt with an external reference but an uncertain result. The supervisor reads the source and external evidence before taking another action. The reconciliation check should not repeat the external operation simply to see whether it works. Finally, cancel a separate unexecuted draft with a recorded reason, then inspect an already executed operation. Preserve its history and route any external correction through the responsible system rather than deleting evidence or assuming an automatic reversal.

What your team sees

  • Outstanding Operations — Pending, Failed and review-needed results with their action and source context.
  • Coaching History — Recorded review and completion states for checking the session outcome.
  • Returned Decisions — Review reasons that still require a response from the preparer.

Follow the work through

Follow closure and reconciliation, then use implementation to agree the first operating cycle’s acceptance checks.

What it keeps track of

Data model
Operation receipts
Stable operation keys and persisted result state for guarded actions.
Coaching sessions
Driver safety coaching sessions closed through verified review.
Review decisions
Independent reviewer decisions on a frozen source revision.
Loads
Freight loads with lifecycle, promised delivery and freight amount.
Record attachments
Uploaded evidence files linked to a load.

Who uses it

Permissions
Dispatcher
Follows eligible session actions and correction requests.
Transport Supervisor
Reconciles operational evidence.
Auditor
Inspects authorized history without changing the recorded outcome.

Set up Driver Safety & Training your way.

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

How to get started