Fire Prevention Week lands the same way every year for Kitchen Exhaust Cleaning companies: your completed report gets handed to a kitchen leader who slides it into a binder that already holds four other fire-related records. An insurance certificate. A sprinkler inspection. A hood suppression service tag. Maybe an Ansul record. Your document is one of five, and the fire marshal reviewing that binder is not going to slow down for the one that makes him work.
That is the practical problem. The craft problem underneath it is that most KEC reports are built backward — organized around what was convenient to record in the field rather than what the reviewer needs to confirm compliance in sequence. Fixing that is not about design. It is about understanding what the record is actually for.
What the Record Is Doing in That Binder
A KEC job record serves two audiences on two different timelines. The kitchen leader needs it the day you hand it over, so they can file it and move on. The fire marshal needs it whenever an inspection happens, which could be tomorrow or eighteen months from now. Both audiences need to reach the same answer fast: was the system brought into compliance, and does the documentation prove it?
That means the record has to front-load the three things a reviewer reaches for first. Which system. When. And what condition it was left in. Everything else — the grease depth readings, the component-by-component notes, the crew credentials, the deficiency list — supports those three things. If the support material buries the headline, the record fails the binder test even if the work itself was perfect.
Grease Depth Is a Measurement, Not a Judgment Call
One of the most common ways a KEC report loses credibility on review is vague language around grease accumulation. "Heavy buildup" and "moderate accumulation" mean nothing to a fire marshal who has read a thousand of them. What matters is a number — specifically, a depth expressed in microns.
The standard that governs kitchen exhaust system inspection and cleaning establishes the thresholds in precise terms, expressed in microns. Fifty microns is the maximum acceptable residual after cleaning — the level a recently serviced system should read. Two thousand microns is the accumulation threshold on surfaces and devices, and 3,175 microns is the threshold in the fan housing. When your report records actual measured depths against those benchmarks, the reviewer does not have to interpret your language. The number either clears the threshold or it does not.
This also matters for your own protection. If a claim ever arises about the condition of a system after your visit, "we found moderate buildup and cleaned to standard" is not a defensible record. A depth reading before service and a depth reading after service is.
Inspection Interval Versus Cleaning Trigger — Keep Them Separate in Your Documentation
This distinction trips up reports constantly, and it trips up kitchen leaders who try to explain their compliance posture to a fire marshal without fully understanding what their documents say.
The standard sets inspection intervals based on cooking volume and fuel type — how often the system must be looked at. Cleaning is triggered by what the inspection actually measures. A high-volume fryer operation gets inspected more frequently because the accumulation rate is higher, but the cleaning is not on a calendar. It is on a gauge. Your report should reflect that logic. When you note the inspection interval that applies to a given system, and then separately note the measured condition that triggered or did not trigger cleaning, you are telling an accurate story. When you collapse those two things into one line — "monthly cleaning required" — you are telling a story that is partly wrong and partly misleading.
Deficiencies Belong in the Record, Clearly Labeled
There is a temptation to soften deficiency language in a report because you are handing it to a kitchen leader and you do not want to alarm them unnecessarily. Resist that. A deficiency that is documented clearly is a deficiency the kitchen leader can act on. A deficiency that is softened into a "recommendation" is a deficiency that may sit unaddressed until a fire marshal asks why it was not flagged.
Your report should distinguish between what was corrected during the service visit, what requires a follow-up trade (an electrician, a refrigeration tech, a sheet metal contractor), and what you flagged and left with the kitchen leader to schedule. Each category needs a different label and a different resolution path. If a component cannot be serviced because of a mechanical failure — a seized damper, a bearing that has seized in a fan motor — that goes in the record with the specific component named and the nature of the failure described.
Credentials on the Record, Correctly Stated
A fire marshal reviewing your report may check your crew's credentials. The record should make that easy. Cleaning Pros Plus, LLC, as an example of how this works in practice: the company is an IKECA member, the founder holds CECS #200452 personally, and crew members include PECT Designated Technicians. Each of those is a different credential held by a different party, and listing them accurately on the record is both honest and protective. Overstating credentials — claiming company-level certifications that belong to an individual, or implying accreditation that the membership does not confer — creates liability if it is ever checked.
The Readability Test
Before you hand over any report, run it through a single question: can someone who did not watch your crew work pick up this document and confirm the system's compliance status in sixty seconds?
If the answer requires them to read four pages of field notes before finding the summary, the answer is no. The summary — system identified, service date, pre-service condition, post-service condition, open deficiencies — belongs at the top. The supporting detail belongs underneath it, organized so a reviewer can drill down if they need to but does not have to in order to reach a conclusion.
Fire Prevention Week is a reasonable moment to audit your own report format against that standard. Not because a fire marshal is coming this week specifically, but because the binder test is always in effect. Five records, one minute, one reviewer. Make yours the one that does the work for them.
How HoodOps Structures the Record Coming Out of the Job
HoodOps is built around the idea that the documentation is part of the service, not an afterthought. Every job moves through a structured workflow — system identification, pre-service readings, component-by-component field notes, post-service readings, deficiency classification — and the output is a report organized the way a reviewer actually reads, not the way a technician works through a van checklist.
Depth readings are recorded in microns and referenced against established thresholds. Deficiencies are categorized by resolution path. Credentials are stated accurately by the party that holds them. The summary is at the top.
The record that comes out of HoodOps is the one that takes sixty seconds to read, because it was built in sixty structured steps that put the right information in the right place. That is not a feature. That is what the job record is supposed to be.
Reserve Your Free Trial: gethoodops.com
About the Author
Arthur Haggerty is the founder of Cleaning Pros Plus, LLC and its family of companies — HoodOps and Stovio Advisors. He holds the Certified Exhaust Cleaning Specialist credential (CECS #200452), and Cleaning Pros Plus, LLC is an IKECA member. He has served as an expert witness in an NFPA 96 commercial kitchen fire case. Before founding Cleaning Pros Plus, he spent 25 years in enterprise IT and cybersecurity consulting, including a decade in IT audit and compliance and a tenure as CIO at Madera Community Hospital, and holds an M.S. in Information Technology. He is a ten-year U.S. Air Force veteran.