Build a brief
people can use.

Name the people at each end.

The office owner is responsible for the record being complete and current. The reviewer approves its release. The crew lead acknowledges receipt and raises discrepancies. The closeout owner checks the completion record and routes follow-up work. One person can hold several roles; make that explicit.

Define “ready for review”.

Choose the fields your work actually requires. A starting brief might include a job reference, source request, authorised contact, site address, scope and exclusions, timing, access arrangements, attachments and the responsible person.

Keep customer facts separate from inferred details. Write “not provided” where a source is missing. Link each draft to the original request and preserve the date or version. Site hazards and instructions must follow your existing safety process and competent review.

Put an approval gate before release.

Compare the draft with its sources. Check names, addresses, dates, scope and attachments. Confirm that any change in cost, timing or commitment has an authorised decision behind it. Mark the record approved only when required fields and checks are complete.

Give the crew a clear current version and a way to ask questions. Record the approver, time and version so an old draft cannot silently become the instruction.

Make “stop and ask” a normal route.

A conflicting address, missing access instruction, changed scope or failed integration should pause the affected step. Keep the original request, label the issue and notify the named owner. AI should not fill the gap with a plausible answer.

When the owner resolves the issue, record the decision and notify affected people. If the system is unavailable, use an agreed manual process and reconcile records before resuming automation.

Close the loop with evidence.

Capture the job reference, work completed, unresolved items, authorised evidence and the crew's completion time. Separate “crew marked complete” from “office reviewed”. Send variations, return visits and customer follow-ups to a named person.

Store only the information needed for the purpose. Decide who can view photos and notes, how long records are retained and how corrections are recorded.

Test a small sample, including awkward jobs.

Use fictional or de-identified examples first. Include a normal request, missing fields, contradictory instructions, a duplicate, a change after approval and a failed system connection. Ask both office and crew staff to walk through the records.

Agree acceptance criteria in advance: factual accuracy, required fields, correct routing, review effort and visible failures. Compare with the current process. If the review burden or error handling is unsuitable, change the design before expanding.