Check engineer job notes against the closure code

Fields

• Job type (install, repair, meter exchange, survey)
• Closure code the engineer picked
• Engineer notes

Questions

1. What do the job notes say was the result of the visit? Choice

   Read the notes. Pick the result they describe for the job the engineer was sent to do, whatever closure code was picked. If the notes describe more than one result, pick the one for the reported fault.

   • Fixed The notes say the fault was found and put right on this visit, and the service was working when the engineer left.
   • Not fixed yet The notes say the fault is still there because parts, another trade or a return visit is needed.
   • No access The notes say the engineer could not get into the property or reach the equipment.
   • Fault on the customer side The notes say the fault is in the customer's own router, devices or wiring, not in the network.
   • No fault found The notes say everything was tested and nothing was wrong.
   • Customer declined The notes say the customer did not want the work done.
   • Stopped as unsafe The notes say work stopped because it was not safe to carry on.

2. Do the job notes support the closure code the engineer picked? Choice

   Read the closure code, its meaning in the context, and the notes. Judge whether what the notes describe fits that code. Pick one option.

   • Supported The notes describe what the code means, and nothing in them points to another code.
   • Contradicted The notes describe something that fits another code, such as a repair made under "No fault found", or work still needed under "Fixed".
   • Not enough detail The notes are too short or vague to tell whether the code fits, such as "all ok" or "no access" with nothing else.

3. Do the job notes say more work is needed that this visit did not do? Yes / No

   Read the notes. Count a part to order, another trade, a return visit, a check to book, or a job for someone else, whatever closure code was picked. Advice to the customer about their own equipment or property is not follow-on work. Yes: The notes say at least one more piece of work is needed. No: The notes say nothing is left to do, or mention no further work.

4. Do the job notes record a safety hazard at the property? Yes / No

   Read the notes. Count a hazard to people at the property or nearby, whoever owns the equipment: damaged or exposed wiring, a burning smell, a gas smell, asbestos, a damaged pole or chamber, a cable hanging low, water near electrics. Yes: The notes record at least one hazard of this kind. No: The notes record no hazard.

5. What do the job notes say the engineer did about any hazard they recorded? Choice

   Read the notes. If they record a hazard, pick what they say was done about it. If they record more than one, judge the one with the least action.

   • Made safe The engineer fixed, isolated, covered or otherwise made the hazard safe.
   • Warned or reported The hazard was left in place, and the notes say the occupant was warned or it was reported to the owner or another team.
   • No action recorded The notes record the hazard but say nothing about any action or warning.
   • No hazard recorded The notes record no hazard.

6. What evidence do the job notes give that the engineer tried to get access? Choice

   Read the notes and the standard for no-access notes in the context. Judge only a visit where the notes say the engineer could not get in or reach the equipment.

   • Evidence given The notes say what the engineer did to reach the customer, such as a card left, a call made, or how long they waited.
   • Claim only The notes say there was no access but give no detail of any attempt.
   • Not a no-access visit The engineer got in or reached the equipment.

7. Do the job notes explain why the fault was on the customer side or nothing was wrong? Choice

   Read the notes and the standard for chargeable codes in the context. Judge what the notes say, not the closure code: only notes that say the fault was in the customer's equipment or wiring, or that no fault was found, need a reason.

   • Explained The notes say what was tested and what showed the fault was on the customer side or that nothing was wrong.
   • Not explained The notes say the fault was on the customer side or that nothing was wrong, with no test or finding to back it.
   • Not claimed The notes do not say the fault was on the customer side or that nothing was wrong, for example because they describe a network repair.

8. Do the job notes say someone at higher risk lives in the home? Yes / No

   Read the notes and the list of people at higher risk in the context. Count what the engineer records about age, health, disability, a medical alarm or equipment, or having to explain things several times. Never infer it from a name. Yes: The notes say someone in the home is in one of these groups. No: The notes say nothing about anyone in the home being in one of these groups.

9. Could another engineer pick up this job from the notes alone? Scale

   Read the notes as an engineer who was not there. Judge whether what was found, what was done and what was left are all clear. Shorthand that engineers use is fine.

   • Too thin The notes say too little to act on, such as "done" or "no access".
   • Key facts missing The notes say some of what was found or done, but leave out what the fault was, what was fixed or what is left.
   • Clear What was found, what was done and what was left are all clear.

Lens columns

outcome, outcome_probability, code_supported, code_supported_probability, follow_on_work, follow_on_work_probability, hazard_found, hazard_found_probability, hazard_action, hazard_action_probability, no_access_evidence, no_access_evidence_probability, charge_evidence, charge_evidence_probability, vulnerable_occupant, vulnerable_occupant_probability, note_quality, note_quality_average