An incident happens on an HVAC job — a refrigerant leak, a burn, a fall from a ladder, a client's property gets damaged during a duct install. Someone writes it up. Weeks later, when the report actually matters — for a workers' comp claim, an insurance review, or an OSHA inquiry — it doesn't hold up.
Not because nobody documented it. Because what got written down wasn't built to survive scrutiny.
The most common mistake: writing what happened, not what's required
Most incident write-ups read like a text message to a friend. "Tech was checking refrigerant levels, got some on his hand, went to urgent care, back to work next day." That's a narrative. It's not a record.
A report that actually protects your company answers specific questions, in a specific order, every time — regardless of who's writing it or how rushed they are. If a report leaves out the time the incident occurred, whether a supervisor was notified, or what corrective action was taken, it's not going to hold up when someone with a reason to challenge it reads it six months later.
What an HVAC incident report actually needs
Every incident report — refrigerant exposure, burns, falls, electrical shock, equipment damage, property damage — needs to capture the same core structure:
Required Fields
- Exact date, time, and job site location
- Names of everyone directly involved and any witnesses
- What the crew was doing at the moment of the incident (the task, not just the job)
- What specifically happened — described in observable facts, not conclusions ("refrigerant contacted skin" not "tech was being careless")
- Immediate action taken on-site (first aid, equipment shutdown, area secured)
- Whether a supervisor or office was notified, and when
- Medical treatment sought, if any, and where
- Corrective action taken to prevent recurrence
- Signatures — the person reporting and a supervisor, both dated
Notice what's missing from that list: blame, opinions, and speculation about cause. "The tech should have double-checked the gauge" doesn't belong in an incident report — that's an internal safety conversation, not a documentation task. Keep the report to what happened and what was done about it.
Why generic templates fail HVAC-specific incidents
A generic incident form built for an office environment doesn't have a field for refrigerant type, EPA 608 exposure thresholds, or equipment lockout status — the details an HVAC-specific incident often turns on. If your report doesn't capture that a system was under pressure, or which refrigerant was involved, you've documented the injury but not the conditions that caused it — which is exactly what an inspector, an insurer, or a claims adjuster is going to ask about first.
This is the gap between a form you found online and a system built around how HVAC incidents actually happen.
The part almost every company skips: the follow-up
Writing the report is half the job. The other half is proving you did something about it. A near-miss log entry that never gets a corrective action attached to it looks, on paper, exactly like a company that noticed a hazard and ignored it — even if that's not what happened.
If your process ends at "report filed," it's incomplete. The record needs to show the loop closed: hazard identified, corrective action assigned, corrective action completed, verified by a supervisor.
Where this fits in your documentation
This is one document inside a larger system — your Incident & Risk documentation should include injury reports, near-miss logs, property damage forms, and corrective action tracking that all reference back to each other. A single incident report that isn't connected to a broader log is easy to lose and hard to prove was part of a consistent process.
That's the difference between having a form and having a system.
Get the HVAC Incident & Risk System
Injury reports, near-miss logs, and corrective action tracking — built specifically for HVAC compliance requirements.