Troubleshoot a missing signature image

Check capture, protected file and token evidence in sequence. 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.

What you’ll accomplish

Check capture, protected file and token evidence in sequence. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Follow these steps

1. Verify the note is signed.
2. Verify a signature path and hash are retained.
3. Go to the controlled signature route.
4. Check deployment storage permissions if the route cannot read the protected capture.
5. Do not mark the job complete manually without valid evidence.

Fields and options to review

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

Rules the system enforces

• The completion rule requires signed POD and snapshot; evidence paths/hashes must remain intact.

How to confirm 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.

Continue with related guidance