A technician may discover an incomplete job record only after leaving the site. The missing item might be a reading, a photograph or a customer acknowledgement, and finding it later can be awkward. A pre-departure evidence check can show the technician exactly what remains unresolved while keeping technical judgement and safe working decisions with the responsible person.
The proposed check is administrative. It does not prove that work is complete, equipment is safe or a customer accepted every outcome. It also does not instruct a technician to remain at a site or repeat a technical test regardless of circumstances. The practical output is a job-type evidence checklist with clear exception handling.
Build the required list from the accepted job type
Use a stable job identifier and the accepted job type, equipment identity and approved checklist version. A maintenance visit and a commissioning visit may require different records. Do not select a checklist merely because the customer's original fault description resembles a familiar task. The technician or authorised dispatcher must confirm the relevant job classification.
For every required item, define its purpose, acceptable evidence and reviewer. A label such as photo is too vague. It might mean an equipment identification image, a connection detail or a completed-work overview. The technical owner determines what is appropriate and whether a substitute is acceptable.
Distinguish mandatory, conditional and optional items. A conditional reading becomes required only when its accepted condition applies. Record that condition and who confirmed it. AI should not add technical requirements from general knowledge or mark a condition true just to make the checklist appear complete.
Compare evidence states rather than attachment counts
Use proposed states such as missing, received, unreadable, conflicting, awaiting review, accepted and authorised exception. Three uploaded images do not satisfy three photo requirements unless the technician or reviewer confirms their contents and associations. One image may support several items under an accepted rule, but the mapping must be explicit.
Source: Azure Document Intelligence overview describes text and layout extraction from documents. It can prepare candidate readings or form fields for review where the method fits the document. It does not establish that a technical measurement is valid or that an arbitrary site photograph proves completion.
Keep the original reading text, unit, equipment reference and source location. A missing unit is not a licence to assume the usual one. An unclear digit should remain unreadable until the technician resolves it. Customer acknowledgement should retain its scope: acknowledging attendance is different from accepting the quality or completeness of the work.
Reusable pre-departure evidence check
Use this proposed checklist record for the technician's final administrative review. The technical owner supplies the real item definitions and acceptance rules.
| Field | Required content | Check result |
|---|---|---|
| Job identity | Stable job ID, site and accepted equipment reference | Correct job matched |
| Checklist | Accepted job type, version and approving owner | Applicable requirements confirmed |
| Evidence item | Specific photo, reading, form or acknowledgement | Purpose and expected evidence are clear |
| Requirement condition | Mandatory, conditional or optional; accepted trigger | Item applies or is explicitly not applicable |
| Received record | Original source, receipt time and evidence ID | No count-only assumption |
| Quality state | Missing, unreadable, conflicting or available | Technician sees the actual problem |
| Review state | Awaiting review, accepted or authorised exception | Upload is not confused with acceptance |
| Technician action | Specific clarification or appropriate collection step | No improvised hazardous test |
| Exception | Reason, affected item and responsible reviewer | Unresolved item remains attributable |
| Administrative close | Reviewer decision and exact record version | Technical sign-off remains separate |
The technician-facing request should say: “For job [ID], [specific requirement] remains [state]. Please [approved appropriate action], or record why it cannot be supplied and send the exception to [reviewer]. Other accepted items do not need to be repeated.”
A completion check is that every applicable requirement has accepted evidence or an authorised, visible exception. This checks the evidence record under the agreed policy; it does not establish technical safety, work quality or customer satisfaction.
Show only the missing action and retain context
Source: OpenAI Structured Outputs describes responses constrained by a schema. A proposed response can list unresolved item IDs, evidence states and approved next actions. Correct response shape does not establish checklist applicability or the correctness of an extracted reading. Validate item references against the accepted checklist and permit an unresolved response.
Avoid a generic message demanding all documents again. If a label is unreadable, request the appropriate clarification rather than another full job pack. If a required customer acknowledgement was not obtainable, show its absence and route the exception; do not replace it with the technician's account of what the customer probably intended.
Offline or unavailable upload systems need a distinct pending-sync state. The technician may have captured the evidence even though the office has not received it. The workflow should not claim the evidence is absent without checking the local/queued record where the implemented system supports that check.
Work through normal, missing and duplicate evidence
Consider a hypothetical job type with three approved administrative requirements: an equipment-label photo, a recorded reading with its unit and an attendance acknowledgement. The technician uploads the label image and reading record, and the acknowledgement is available with the accepted scope. The check links those records to the requirements and marks them ready for review. It does not state that the equipment passed a test.
In another hypothetical case, the reading contains a value but no unit. The checklist shows that specific uncertainty and asks the technician to confirm the recorded unit through the approved procedure. It does not append a common unit from similar jobs. If collection is inappropriate or no longer possible, the technician records an exception for the technical owner.
A repeated upload with the same stable evidence ID should return the existing item state. Two different photographs named final.jpg must remain separate until their contents and job associations are checked. An image from an earlier job cannot silently satisfy the current job merely because the equipment looks similar.
Suppose the customer leaves before an acknowledgement is obtained. The workflow retains the missing acknowledgement and records the situation. It must not create a signature, infer acceptance or prompt the technician to claim the customer approved the work. The responsible reviewer decides the accepted administrative next step.
Keep exception decisions with the technical owner
Source: n8n human review documents approval or denial before selected agent tool actions. An implementation may use that mechanism for a record-close action. It does not define technical sign-off criteria or justify collecting evidence in unsafe conditions. The organisation's technical and operational owners establish those boundaries.
Evaluate the checklist with synthetic or appropriately permissioned jobs containing missing units, wrong equipment IDs, unreadable documents, duplicate uploads and unavailable synchronisation. Check false missing-item requests as well as missed requirements. A pilot should measure whether technicians and reviewers can resolve the record with less rework; it should not assume fewer return visits without observed evidence.
Questions about job evidence checks
Can an uploaded photo automatically mark the task complete?
Only under a verified, approved acceptance rule, and not merely because an attachment exists. Keep the photo linked to the correct job and requirement. The technical reviewer may still need to inspect its contents. Administrative completeness should not be presented as proof that the physical work is correct.
What happens when a required item cannot be collected?
Record the reason, affected requirement and responsible reviewer. An authorised person can decide whether an alternative or exception is appropriate. The system must not fabricate a value, acknowledgement or image to close the job. It also should not direct a technician to repeat work outside the approved technical process.
Should every job use the same checklist?
A common framework can help, but the actual requirements should match the accepted job type and equipment. Version the lists and identify conditional items. If the job changes during the visit, the authorised person confirms the revised checklist before the system asks for additional evidence.
If your business needs help defining this process, explore Workflow automation, the wider AI automation services, and our custom-agent workflow guide. The agents and automation comparison and custom AI agent glossary explain the terms. To discuss your records and approval rules, get in touch.