Create a driver record
Onboard an employed or self-employed driver with contact, pay and compliance details. 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 → Add Driver
Before you start
- Have the driver’s verified identity, contact, right-to-work, driving-licence, pay and emergency information.
What you’ll accomplish
Onboard an employed or self-employed driver with contact, pay and compliance details. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Follow these steps
- Go to Drivers and select Add Driver.
- Enter identity and contact details.
- Select employed or self-employed.
- Set employment and availability states.
- Select a supported payment method and enter its matching rates.
- Add licence, right-to-work, bank and emergency details.
- Save the record.
- Go to the new driver and upload required evidence.
Fields and options to review
IdentityName, email, phone, address and identifying details.
Employmentdriver_type: employed or self_employed; employment_status: active, onboarding, suspended or left.
Availabilityavailable, busy, offline or unavailable.
Paymentfixed_job, percentage, per_mile, hourly, day_rate, hybrid or salary.
Sensitive valuesNational Insurance and bank details are encrypted before storage.
ComplianceDriving licence and right-to-work dates plus supporting documents.
Rules the system enforces
- New drivers receive a DRV code.
- The initial compliance state is pending and onboarding progress starts at 20%.
- Use a valid email when dispatch notifications are required.
How to confirm it worked
- The driver becomes available to the active list only when saved active and not deleted; dispatch still checks availability and compliance.
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.