# Field-service report: two-person QA checklist

**Use on the original work-order system, not on the generated draft alone.** A blank item blocks release or needs documented exception handling.

## Technician — field facts (first review)
- [ ] Correct work order, visit date, time zone, asset and site; no wrong-job mix-up.
- [ ] Requested complaint recorded separately from observations and diagnosis.
- [ ] Actual completed actions supported by notes and authorized scope; no unperformed procedure claimed.
- [ ] Parts quantities and identifiers matched to physical stock / inventory records, or explicitly NONE.
- [ ] Photos opened, correct job/asset, time/caption/stage understood, duplicates and personal data checked; IDs alone are not photographs.
- [ ] Tests/readings, if any, match approved instrument or work logs; no unsupported technical interpretation.
- [ ] Status COMPLETE/PARTIAL/OPEN consistent with outstanding items, not guessed from language.
- [ ] Safety-relevant concerns or unknowns escalated under existing procedure, not decided by AI/script.
- [ ] Missing evidence called out rather than invented; corrected fields linked to their original source.
- [ ] Review identity, date/time and exact report version recorded in approved system.

## Coordinator — office and customer handoff (second review)
- [ ] Work-order ID and site/asset match scheduling/dispatch record without copying schedule promises.
- [ ] Open items, unapproved scope, missing parts, and exceptions clearly assigned to a responsible human.
- [ ] Requested follow-up routed to office without auto-booking a visit or promising dates.
- [ ] Customer acknowledgment actually exists, with exact meaning; does not imply safety or work acceptance.
- [ ] Attachments are accessible to authorized recipients; restricted/private images removed or redacted.
- [ ] Costs, times, quotes, warranty and invoice data are taken only from approved source, if included at all.
- [ ] Privacy, least-privilege access, retention policy and export destination checked.
- [ ] Both human approvals explicitly recorded; if either is missing, mark HOLD / DO NOT SEND.
- [ ] Final version preserved, with correction/audit trail and authorized distribution path.

## Hold / return-to-technician conditions
Missing `source_ref`; missing actions or original evidence; COMPLETE with unresolved item; missing photo file when mandatory; missing acknowledgment proof when labeled recorded; unresolved item lacking owner; discrepancy between report and inventory. Do not silently repair; request a corrected source record.