Guide

Vendor reports for multi-location roll-ups: one format across all sites

Updated 2026-10-08

Six stores, three vendors, and a folder of PDFs that do not match. One report has canopy photos only. Another buries the site address in a work-order number. A third skips the areas that were not cleaned. When the brand auditor or insurer asks for proof across the portfolio, you cannot roll those up. Fix the report format once, put it in every contract, and accept only that format.

Short answer Require every vendor to return the same field list and photo set for every kitchen, with the exact street address and tenant name on the first page and in the file name. ANSI/IKECA C10 expects service reports, certificates, and deficiency documentation after a clean; local AHJs often add electronic photo rules (one city’s public permit list calls out work-order ID, address, plenum, vertical riser up and down, access plates, and filter rails). Never reuse another site’s photos. Keep a one-row-per-visit spreadsheet at HQ so overdue sites and “areas not cleaned” show up in one glance.

Why single-site reports break at portfolio scale

Different vendors name fields differently (“location,” “job,” “WO #”) so you cannot sort by address
Photos without a work-order or address shot cannot prove which kitchen was cleaned
Missing “areas not cleaned” hides the vertical riser that never got a panel
Paper tags on the hood stay on site; the PDF that never reaches HQ is useless at renewal time
A rolled-up “all stores done” email with no per-site files is not documentation

The single-site checklist is in what a cleaning report should include. This page is the multi-site layer on top of that.

Required fields — same order on every report

Field	Why it has to match
Legal site name + full street address + city/state	Roll-up key; matches lease and insurance schedule
Tenant or brand unit ID (your internal code)	You assign this; put it in the RFP so every vendor uses it
Service date and time window	Cadence and after-hours proof
Company name, address, phone	Matches the hood tag
Technician name(s) and any claimed credential	AHJ and insurer questions
Components cleaned (hood, filters, plenum, ducts, fan, containment)	Scope comparison across vendors
Areas not cleaned + plain-English reason + priced fix if known	The clause most often missing; see public RFP practice in the RFP template
Before/after photo set (see below)	Proof the full path was opened
Next recommended due date	Portfolio calendar
File name: `YYYY-MM-DD_UnitID_City_Vendor.pdf`	So HQ can sort without opening every file

Minimum photo set (copy into the contract)

Clear shot of the work order or first page showing building address and tenant
Filter rails (top and bottom), plenum, front and rear of filters — before and after
Horizontal duct at an open access plate — before and after
Vertical riser looking up and looking down, when accessible
Rooftop fan interior / wheel area — before and after
Service label / tag on the hood after the job

That photo list tracks what one public AHJ (Edina, MN) publishes for electronic submittal after a permitted clean. Your city may want more or less; ask once, then write the stricter set into every regional contract so reports stay comparable. If a section was inaccessible, the report still needs a photo of the closed panel or blocked path plus the written reason — not silence.

HQ roll-up sheet (one row per visit)

Column	Example
Unit ID	TX-014
Address	1200 Main St, Houston, TX
Vendor	[name]
Service date	2026-10-08
Next due	2027-01-08
Full-system? (Y/N)	Y
Areas not cleaned	Vertical riser — no panel at 2nd floor
Open deficiency (Y/N)	Y
PDF link / path	shared drive path
Tag date matches report? (Y/N)	Y

Sort by next-due weekly. Any row with an open deficiency stays red until the access panel is installed or the section is cleaned. Pair with the site inventory CSV from the RFP template.

Contract language that forces the format

“Reports shall use the field list and photo set in Exhibit B. Reports that omit address, areas not cleaned, or the required photos are incomplete and are not accepted for payment.”
“Each PDF shall be named YYYY-MM-DD_UnitID_City_Vendor.pdf and uploaded to [portal] within [5] business days.”
“Photos from one location shall never be reused at another location.”
“Where the AHJ requires electronic filing (for example through The Compliance Engine), the vendor files and also delivers the same package to our portal.”

Who it’s for / not for

For: multi-unit operators, franchise field managers, and facilities leads who need one comparable package across cities and vendors
Not for: rewriting ANSI/IKECA C10 itself, or replacing an AHJ’s electronic filing rules. Confirm local photo and tag rules with each city’s fire prevention office.

Sources

IKECA: ANSI/IKECA standards overview (C10 cleaning methodology; reporting includes certificates, service reports, other documentation, deficiency reporting)
ANSI/IKECA C10-2021 (purchase page for the current cleaning standard)
City of Edina, MN: Commercial kitchen exhaust hood inspection and cleaning permit requirements (PDF) (example AHJ photo and electronic-report list: work order with address/tenant, vertical rise, access plates, filter rails, Compliance Engine filing)
Wayne State University kitchen hood cleaning RFP (PDF) (before/after photos with every report; system inventory by location)
University of Maine System hood cleaning RFB (PDF) (report fields: completion date, condition, equipment model/tag, filter style)

Next step

Export your last 30 days of vendor PDFs into one folder. If you cannot sort them by address without opening each file, put Exhibit B (field list + photo set + file-name rule) into the next renewal or RFP before you price another year.