Which workflow fits?
The deficiency feature helps a contractor document an observed condition without implying an engineering conclusion or completed repair. It keeps the note in the report and customer history instead of a separate text thread.
Keep deficiencies visible, specific, and separate from completed work.
A buried caption is easy to miss. Each finding gets its condition, location, photo, NFPA 96 section, and recommended action in one block.
- 3 reports or 3 days free
- No card
- No contract
Compliance Report1 finding
Rooftop grease containment is saturated and no longer holding runoff at the exhaust fan base.
High NFPA 96 §7.8.2.1
- Location
- Roof, exhaust fan base
- Action
- Replace or empty the containment system before the next cooking day.
The finding, beside the photograph it came from.
A deficiency is a location, a visible condition, a severity, the section it falls under, and the action you recommend. The photo record shows the reviewer what you saw; the Compliance Report says what it means.
Compliance Report1 finding
Rooftop grease containment is saturated and no longer holding runoff at the exhaust fan base.
High NFPA 96 §7.8.2.1
- Location
- Roof, exhaust fan base
- Action
- Replace or empty the containment system before the next cooking day.
Write facts the recipient can act on
Start with the location and observable condition. Then state the effect on scope, the recommended next step, and who needs to review it.
- Name the hood line, duct section, fan, or rooftop location
- Describe what was visible without guessing at a cause
- Attach a context photo and a useful close-up
- Record recommended action and an owner when known
Preserve the open-item history
A deficiency should remain discoverable after the PDF email disappears from the inbox.
- Keep the issue with the service date and job record
- Show whether it is open, acknowledged, or resolved
- Link follow-up evidence to the original observation
- Retain the customer-facing wording that was actually issued