Reject a driver document

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Reject unusable or incorrect evidence without deleting the audit history.

What this guide helps you do

Reject unusable or incorrect evidence without deleting the audit history. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Follow these steps

1. Check the evidence.
2. Select Reject.
3. Record the operational reason using the available review process.
4. Request replacement evidence.
5. Upload and review the replacement as a new/updated document.

Fields and options

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

Rules and limits

• Rejected evidence does not count toward compliance.
• Use rejection rather than approval where holder, type, date or content cannot be verified.

Check 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.

Related guides