Job evidence and compliance capture on site

What does job evidence and compliance cover?

Two related jobs: proving what happened on a visit, and making sure the person on the visit is compliant to be there. Both fall apart when they depend on someone remembering to write things up, so the app captures them at the moment of work.

• Before-and-after photos. Captured through the device camera against the specific job, so the visual record is tied to the work rather than sitting in a phone’s camera roll.
• Signature capture. A customer signature is taken on the device and stored with the job, evidencing sign-off at the point of completion.
• Health and safety and disclaimer forms. Structured forms (risk assessments, disclaimers, checklists) are completed on site, so the paperwork a regulated job requires exists before the engineer leaves.
• A tamper-evident audit trail. Every capture is recorded with actor, timestamp, and, where permitted, location, on the platform’s append-only audit trail with field-level history, the same audit foundation used across the accelerator modules.
• Compliance documents with expiry. Certificates, insurance, and qualifications are held in the compliance document store proven in the Franchising module, with configurable expiry alerts and a network-wide view.

How it behaves at the edges

Evidence is only worth capturing if it survives a bad connection and stands up to challenge. These are the cases the design has to handle.

• Photos captured with no signal. Evidence is written to on-device storage and queued, then uploaded in the background on reconnect. A job is not marked fully synced until its evidence has landed, so completion and its proof travel together.
• A disputed signature or completion. Because each capture is timestamped and attributed on an append-only trail, a challenge is answered with the record rather than an argument. Nothing in the completed evidence is silently editable after the fact.
• A compliance certificate expiring mid-route. Expiry alerts fire ahead of the date and the network compliance view flags it, so an engineer is not dispatched to a job their certification no longer covers.
• A large upload on a weak connection. Photo uploads are chunked and retried in the background rather than blocking the engineer, and an interrupted upload resumes rather than starting over. The offline sync page explains the queue-and-forward design.

Integration points

Evidence capture reuses the platform’s document, audit, and compliance foundations.

• Document storage and versioning use the platform’s blob storage and versioned-document model, so evidence is retained with history rather than overwritten.
• Compliance tracking comes from the Franchising module, including expiry alerts and the network compliance view.
• The audit trail is the same append-only, actor-attributed record described in audit and accountability.

Why it matters

For regulated and insured work, evidence is not admin, it is the difference between a defensible job and an exposed one. Capturing it at the point of work, on a trail that cannot be quietly changed, means head office can trust what the field reports without chasing it. The companion guide below sets out how to test this against the system you run today.