Operational go-live checklist for Courier

Verify the complete module before accepting live jobs.

What this guide covers

Verify the complete module before accepting live jobs. 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

1. Confirm module activation/upgrade and schema ready.
2. Create least-privilege roles.
3. Configure general settings and operations email.
4. Onboard compliant drivers and available compliant vehicles.
5. Create/sync customers.
6. Test a draft job through dispatch, statuses, public POD, completion, invoice and journal.
7. Test provider feeds/webhook/POD if used.
8. Test BP fuel if used.
9. Run cron twice and verify duplicate controls.
10. Run instant reports and reconcile source records.

Fields, choices and supported possibilities

This action uses the values already stored on the selected source record. Review that record before continuing.

Code-backed validations and workflow rules

• Use test records/provider sandbox before live credentials and customer work.

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.

Related Courier guides