Upload a driver compliance document
Add protected evidence to a driver record.
Exact navigationAdmin Area → Courier & Logistics → Drivers → Open driver → Documents → Upload
Before you begin
- Prepare the correct evidence and expiry details.
What this guide covers
Add protected evidence to a driver record. 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
- Open the driver.
- Choose the document type.
- Select the evidence file.
- Enter issue/expiry details where applicable.
- Upload.
- Confirm the document is pending review.
Fields, choices and supported possibilities
Allowed filesPDF, JPG, JPEG, PNG and WebP.
Maximum size8,192 KB.
StorageProtected module upload area rather than a public asset folder.
Code-backed validations and workflow rules
- Uploading evidence does not approve it.
- Use the download endpoint to review protected documents rather than guessing a filesystem URL.
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.