1. Driver Safety & Training
  2. Features
  3. Assignment Readiness
Feature · Assignment Readiness

Assignment Readiness

Read driver and vehicle commitments together with the readiness and repair evidence needed for a feasible load plan.

OverviewDriver Eligibility Due
Driver Safety & Training · Assignment Readiness

Driver Eligibility Due

Drivers

New
Driver codeNameEligibility untilExternal authorityActive
DC-324Driver 89409 OctEA-806Yes
DC-685Driver 48914 OctEA-860No
DC-258Driver 28010 OctEA-876Yes
DC-857Driver 40703 OctEA-308No
DC-194Driver 32410 OctEA-940Yes
6 of 6 records
DC-324Drivers · DRV-86821
Yes
NameDriver 894
Eligibility until09 Oct
External authorityEA-806
Example screen with sample data

What you can do

Put the planned commitment in view

A load assignment identifies the load, driver and vehicle over a start and end period. Those references let the supervisor examine whether the same driver or vehicle is already committed elsewhere. The assignment has its own Held, Confirmed, Dispatched, Completed or Cancelled state, which describes the commitment separately from the load’s delivery stage.

Vehicle records provide equipment class, capacity, readiness and an external fleet reference. Ready, Held and Maintenance describe the recorded readiness position. Vehicle defect records retain severity, repair evidence and a release date. Read the supporting context before deciding how the vehicle belongs in the plan; a coaching session’s outcome does not change that vehicle assessment.

How the work is organized

  • Assignment period. Record the intended start and end of the commitment and check the driver and vehicle against other active assignments. Keep the same time interpretation across the team. A period that looks clear in one time zone can be misunderstood when compared with another without an agreed convention.
  • Vehicle context. Check equipment class, active state and recorded readiness alongside the external fleet identity. Capacity provides planning context that the responsible team must interpret against the actual load requirements. Keep those requirements available during the feasibility discussion.
  • Repair and release evidence. Inspect the reported vehicle defect, severity and supporting repair reference with its recorded release date. The reviewer needs to understand which vehicle and event the evidence concerns. Retain that history when readiness is updated so a later review can explain the decision.

What to agree during setup

Agree how Held and Confirmed assignments affect availability and how the team handles adjacent commitment periods. Define the time zone and boundary convention before checking overlap. Confirm who can inspect assignment records and who submits the planning action, keeping the actual authorization for each operation clear.

Decide which fleet source supplies readiness and repair evidence and who verifies updates to it. Agree the evidence needed to plan a vehicle after a reported defect. Keep the external fleet reference aligned with the vehicle code used internally. Define the actual feasibility inputs used for the load so the planner can explain the choice of equipment and capacity.

Check the handoff on an actual case

Plan an illustrative load with a named driver, vehicle and commitment period. The supervisor checks another assignment for the same driver and finds that the periods overlap. Adjust the proposed commitment or choose an available resource through the planning process before treating the plan as feasible. Repeat the check for the vehicle, since a free driver does not establish vehicle availability.

Then inspect a vehicle recorded as Held with a reported defect and release evidence. Confirm the source and relevance of that evidence before the administrator updates its readiness. When the load is planned, keep the resulting assignment references available for the later coaching discussion. Rehearse cancellation of an unexecuted commitment separately from an already dispatched movement so the team preserves the evidence of work that occurred.

What your team sees

  • Assignment Schedule — Planned and active commitments with their driver, vehicle and start and end period.
  • Vehicle Readiness — Equipment, capacity and recorded readiness for authorized planning review.
  • Critical Vehicle Defects — Critical reports with their repair and release evidence for inspection.

Follow the work through

Use readiness and assignment planning, then follow load movement and evidence once the actual operation begins.

What it keeps track of

Data model
Load assignments
Nonoverlapping driver and vehicle commitments for a load.
Drivers
Driver eligibility and external authority records.
Vehicles
Fleet vehicles with capacity and readiness.
Vehicle defects
Reported vehicle defects with repair and release evidence.
Loads
Freight loads with lifecycle, promised delivery and freight amount.

Who uses it

Permissions
Dispatcher
Prepares the load plan through the eligible action.
Transport Supervisor
Reviews authorized assignment and readiness evidence.
App Administrator
Maintains driver and vehicle reference records.
Auditor
Reads authorized history.

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