Match the Seattle kitchen-hood inspection, testing and maintenance (ITM) report to the repair record for the same system and event. Start with the dated report already in the file. What happened to a finding from that test shows up in the matching repair record, beyond an installation approval or a later service invoice.
Identify which report answers the recurring-service question
Seattle Fire Department’s published Systems Testing information names Kitchen Hood Install and Kitchen Hood ITM separately. Its range-hood table lists acceptance, reacceptance and every-six-month reporting. These are distinct event categories; a particular property’s history comes from its own reports.
SFD describes electronic reporting through The Compliance Engine (TCE) and repair reports documenting completion of required work. That is a reporting route rather than an anonymous public archive. Read what a repair report covers instead of turning its presence into a claim of agency acceptance.
| Dated record or entry | Link to establish |
|---|---|
| Recurring test report | Which system, event date and report reference does it identify? |
| Finding or deficiency | Which item does the wording describe, and is it tied to that report? |
| Repair report | Does its reference and scope address the same item and system? |
| Later record | Does it explain the earlier finding, or describe a different service event? |
Preserve the actual outcome language. If a report lists several items, apply a repair reference only to the item it sits beside. The date a document was sent can also differ from the service date. Keep both when the file supplies them, and leave an unknown date unresolved.
A later report can add evidence without replacing the earlier document. Retain the original finding and the record that explains what followed. Deleting the earlier entry once new paperwork arrives can erase the very reference needed to understand the repair.
A fictional two-hood file exposes a false match
Imagine a fictional restaurant folder with a March 12 test report identifying Hood A and an unresolved item. A March 20 repair sheet says the work is complete, but its description names Hood B. Both documents carry the same street address. These labels are invented for the example.
The two systems share an address, and that is all the match shows. Ask for the report reference behind the repair sheet and compare it with the earlier finding. Hood B on the supplied sheet leaves Hood A’s status open; a missing attachment or inconsistent local label could explain the difference.
Suppose the service company supplies a revised sheet linking the work to the March 12 report. Keep both versions, the date of the clarification and the supplied explanation. Then check whether the revision addresses the particular unresolved item or only corrects the system name. An identity correction and a documented repair answer different questions.
A later recurring test in the same folder is another dated event. If it skips the March finding, its date belongs to that later test alone. Request the missing link if that earlier sequence matters to your research.
Recover the copy from the holder of the record
Start with the owner or service company when they hold the test and repair paperwork you need. Ask for the complete report and its referenced attachments, not just an invoice or a cropped outcome line. Each holder may keep a different set of historical versions.
Use a focused description:
- Identify the property address and the system name or location exactly as the existing document gives it.
- Preserve the test or service date, any report number and the finding you are trying to follow.
- Name the missing repair report, attachment, revised version or later response.
- Explain the mismatch: another system, a different event date, an absent reference or an incomplete copy.
These are suggested clues drawn from the file, not claims about required fields in TCE or a City search screen. Avoid supplying an invented identifier just to make the documents appear to join.
For a named record that may be held by SFD, the department’s contact page routes public-record requests through the City Public Records Request Center. Identify the particular report and period sought. SFD’s response tells you whether it holds the copy, can release it and has the complete history.
If the reply provides only part of the requested material, note which object arrived and which remains missing. If one report is missing, log that as a result of that request, separate from whether service or repair happened.
Keep access problems and other approvals separate
If a page fails to open, try again later; that failure says nothing about the property.
For a construction-permit question, use the Seattle building-permit records guide. The final-inspection guide addresses a permit’s later inspection status. Keep those records separate from the recurring hood report.
A submitted report or reported repair does not prove agency acceptance, overall permit closure, occupancy approval or present safety.
Official Seattle pages checked October 6, 2026.