Recalculate driver compliance
Understand how required evidence produces pending, action-required or compliant results.
Exact navigationAdmin Area → Courier & Logistics → Drivers → Open driver → Compliance
What this guide covers
Understand how required evidence produces pending, action-required or compliant results. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Exact step-by-step process
- Review the required document list configured by the module.
- Confirm each required item is approved and not expired.
- Review licence and right-to-work dates.
- Trigger or save the action that recalculates compliance.
- Confirm progress and final status.
Fields, choices and supported possibilities
compliantAll required evidence is approved and unexpired.
action_requiredSome evidence exists but the set is incomplete, rejected or requires attention.
pendingNo qualifying required evidence has completed review.
expiredA driving licence expiry condition forces an expired result.
Code-backed validations and workflow rules
- Progress is calculated from qualifying required documents and retains the module’s onboarding floor.
- An approved document that is expired does not qualify.
Expected result and verification
- The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action.
Security, audit and operational checks
- Use the exact record and least-privilege role before changing any state.
- Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed.
- Use protected document and image routes rather than exposing server filesystem paths.
- Keep customer, driver, provider, financial and credential data within the authorised workflow.
- For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process.
Do not bypass the code flowDo not force database values, invent a status, mark a job completed without signed POD evidence, or expose encrypted credentials to make a screen appear successful.