Use this with the person who wrote a maintenance record and someone who needs to use it. Choose one order and one practical change. Bring the original evidence, including what is still unknown.
This is a static discussion aid. Print it or copy the prompts into an approved organisational record. It sends and stores nothing. Keep actual records and personal information in the organisation's approved environment. The lead must check authority and obtain agreement before recording a commitment.
Worked example: WO-2104
Entirely fictional Northbank situation from the guide. Dates and decisions are invented, including the later review. This isn't an assessment of staff or a specification for operating equipment.
Record and question: WO-2104, motor M-410, reviewed 16 November 2026. “Bearing changed. Run OK.” The cause field says “Wear”. Ellis wants component, observations and check conditions to prepare questions for similar work. The cause is unestablished.
Writer's confirmed account, 17 November: Sam heard rough noise at the drive end, replaced the drive-end bearing and observed a 10-minute unloaded run. He didn't hear the noise during that check. No cause or normal-load result is established. The correction uses the accepted route, retaining the original and identifying “Wear” as unconfirmed.
Conditions to check: Sam describes waiting for a shared terminal near shift end, another job waiting and not knowing how to represent an unknown cause. Ruth checks rather than assuming every shift has the same problem.
People and authority: Sam checks work observations; Ellis checks planning usefulness; Ruth owns the review and trial support within delegated authority; Morgan agrees cover; Noor owns the separate technical evidence question. Technical/operating authorisations stay with the site's designated people and processes.
Agreed trial: Ellis co-drafts a short prompt with Sam and Noor by 18 November. Sam tries it 19–26 November with a protected opportunity after handover agreed with Ruth/Morgan around shift priorities. Ruth arranges/checks support. Ellis brings 4 selected comparable records, discussed with writers, on 27 November at 09:00. Noor's technical evidence question stays separate.
Returned evidence: Ellis brings the prompt and 4 records. All 4 identify equipment/component; 3 describe check conditions and could help Ellis draft preparation questions. One says “tested” without conditions. Sam identifies one shift without the agreed recording opportunity; Ruth checks with Morgan and keeps cover open. No later equipment history or accepted technical finding is supplied.
Accepted next step in the fiction: Ruth continues the small trial while addressing cover. Ellis follows up the unclear check with its writer. No site-wide quality judgement, individual score, prevented failure or reliability gain is established. Noor's technical question remains open.
Optional AI draft check: use only the identified pack/version; trace each claim to observations; leave cause/outcome unknown. Ruth checks the draft with the relevant people. Correct a circulated explanation for the same readers. A generated action still needs human agreement.
Blank conversation sheet
Review lead / date / next review time:
Order/equipment, source position and question: which original record/version is being reviewed? Who needs it and what decision or preparation question must it support?
Writer's observations and unknowns: what happened, what was checked and under what conditions? What hasn't been established? Who checked the account? Retain original/correction history through the accepted route.
Working conditions: ask the writer to show how/when they enter it. Check time, access, guidance, competing demands and ability to correct. What differs across shifts or roles?
Proposed change and needed support: who is affected, who agrees, what can be tried and within whose authority? What work/capacity does the support require?
Accepted task / owner / due time / evidence expected: record actual agreement. Include the leader's support task. Identify a route for difficulties before the due time. Keep technical/operating decisions with their owners.
Return: implementation and use: did the change happen? Ask the writer what it took. Ask the user to show how they used the result. Record source references, exceptions, limitations and corrective actions.
Return: operating outcome and acceptance: what separate equipment/operating evidence exists? What remains unknown? Which human accepts this limited conclusion? Avoid converting a small selection into a site result or staff score.
Next decision / accepted owner / due / open questions: continue, change, stop or refer to the authorised person. Tell contributors what happened with their input. Who will check the next evidence?
If AI helped: identify inputs/version, draft and corrections; confirm source checks and staff opportunity to challenge; identify the human who accepts the text/action. If a wrong explanation circulated, who receives the correction?
The blank fields are intentionally unfilled. A completed worksheet doesn't confer authority or establish an engineering result. Use local approved processes for records, decisions and work.