Drivers and Eligibility

A driver record carries a driver code, name, active setting, eligibility date and external authority reference. App Administrator maintains those facts so the operational team can identify the person involved in an assignment or coaching discussion. The driver code helps distinguish people with similar names when a reviewer follows an incident back to the load.

Eligibility information has its own source and meaning. Review the recorded date and authority before relying on it for a planned assignment. A coaching score describes an assessment, while the driver’s eligibility record describes externally supported operating status. Completing a session leaves that separately maintained authority record to its own update process.

• Stable identity. Use the driver code consistently when reconciling names across dispatch, incident evidence and coaching. Transport Supervisor confirms the person on the load assignment before Dispatcher prepares the session. A similar name or an old contact detail should not decide which driver’s history receives attention.
• Eligibility context. Retain the external authority reference and the date through which the recorded eligibility applies. Review the date against the intended assignment period using the policy agreed during setup. Refer an uncertain record to the person responsible for its external source.
• Active records. Keep the active setting current for the driver records the team uses. Review changes before new assignment work begins. Preserve the earlier load and session evidence so an Auditor can still identify the driver associated with historical work.

Agree the authoritative source for driver identity and eligibility, the person who checks it and the process for recording an update. Define how an approaching or elapsed eligibility date is handled in the operational review. Keep the actual external reference available so the supervisor can resolve uncertainty without treating a local display as a new authority decision.

Choose how the driver is named in coaching sessions and how Transport Supervisor confirms the match with the assigned driver. Dispatcher records that confirmed identity using the agreed convention. Rehearse similar-name cases before using it across the team. Decide which staff can inspect driver records and which can maintain them, with access appropriate to their operating responsibilities.

Prepare an illustrative load whose driver has an eligibility date requiring review before the planned commitment ends. App Administrator checks the external authority and records the verified information. Transport Supervisor examines the intended assignment period and the recorded eligibility context before the plan proceeds. Dispatcher then uses the same driver’s identity when preparing an incident-related coaching session.

Repeat the exercise with similar driver names. Transport Supervisor starts from the assignment’s driver reference and confirms the driver code before accepting the session description. Then complete the coaching review and inspect the driver record again. Its eligibility date should still reflect the externally supported information, with any later update handled through the agreed administrative process. The session history remains useful evidence without changing the authority it refers to.

• Active Drivers — Current driver identities with eligibility dates and external authority references.
• Driver Eligibility Due — Driver records whose eligibility date is today or earlier and needs review in context.

Continue with readiness and assignment planning, then use the same identity checks in coaching review.