Recalculate driver compliance
This guide explains how required evidence produces pending, action-required or compliant results. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Courier & Logistics → Drivers → Open driver → Compliance
What you’ll accomplish
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.
Follow these steps
- Check the required document list configured by the module.
- Verify each required item is approved and not expired.
- Check licence and right-to-work dates.
- Trigger or save the action that recalculates compliance.
- Verify progress and final status.
Fields and options to review
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.
Rules the system enforces
- Progress is calculated from qualifying required documents and retains the module’s onboarding floor.
- An approved document that is expired does not qualify.
How to confirm it worked
- 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.