A deficiency should stand on its own
The person reading the report may not have attended the inspection. A strong deficiency note should identify what was tested, where it is located, how it failed, and what correction is recommended. It should be understandable to the customer, estimator, service coordinator, and next technician.
Use an objective structure
A reliable format is: device or function + exact location + observed result + expected function + recommended correction. Example: “Addressable smoke detector SD-124 outside Electrical Room 2 failed to report alarm when tested with approved aerosol. Replace the detector and retest point operation and panel annunciation.”
Avoid unsupported conclusions
Do not state that wiring is damaged, a panel is defective, or a device is incompatible unless the inspection proved it. During an inspection, you may identify a failed function without completing full troubleshooting. Use language such as “did not operate,” “cause not determined during inspection,” or “requires service diagnosis.”
Describe the life-safety impact accurately
Explain which function is affected: local notification, initiating detection, monitoring transmission, supervisory indication, elevator recall, door release, or another interface. Avoid dramatic language that exceeds the finding. One failed strobe does not necessarily mean the entire fire alarm system is nonfunctional, but it does mean the affected area lacks the intended visible notification.
Separate deficiencies from recommendations
The deficiency is the observed nonconforming condition. The recommendation is the proposed correction. Keeping them distinct helps prevent a repair estimate from appearing to be the only possible technical solution before diagnosis is complete.
Include access limitations and untested items
Document devices that could not be accessed, areas not made available, functions not tested because of operational restrictions, and any customer-requested exclusions. Untested is not the same as passed. Clear limitations protect the accuracy of the report and help schedule a return visit.
Field checklist
- Device or function identification
- Exact building, floor, room, and position
- Observed test result
- Expected operation
- Affected protection or interface
- Recommended repair or further diagnosis
- Access limitation when applicable
- Retest requirement after correction
Important limitation
This guide is a field-oriented starting point, not a substitute for the adopted code, approved drawings, project specifications, manufacturer instructions, site safety procedures, or the authority having jurisdiction. Do not bypass a listed protection feature or leave a required system impaired without following the approved impairment process.