Handle right-to-work evidence

Maintain right-to-work dates and protected evidence.

What this guide covers

Maintain right-to-work dates and protected evidence. 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. Enter the verified right-to-work date information.
2. Upload supporting evidence using the protected document flow.
3. Review and approve it under the authorised process.
4. Recalculate compliance.

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

• Right-to-work information is part of onboarding/compliance; the organisation remains responsible for the legally required check.

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