Third-party inspection reporting is how a fire department collects inspection, testing, and maintenance reports from the private contractors who do the work. Instead of mailing, emailing, or faxing a report, the contractor files it through an online platform the department has chosen, such as The Compliance Engine, IROL, or LIV (from LivSafe). The vendors say the platform costs the department nothing; it is funded by filing fees charged to the inspection companies that submit reports. The department gets the reports filed in its jurisdiction in one place, organized by building and system, and the platform takes over much of the reminder and deficiency follow-up that staff used to do by hand.
For a contractor, the inspection work is the same. What changes is the paperwork after it: the reports the department requires now go to the department as well as the customer, through the department's platform, with its own login, format, fee, and follow-up when something fails.
Why departments use reporting platforms
The fire protection systems in a jurisdiction are maintained by many different contractors, each with its own report format. When those reports arrive by email, fax, and mail, it is hard for the department to tell which buildings were inspected, which reports never arrived, or whether a deficiency found in March was ever repaired.
A platform puts the submitted reports in one place, tied to the building and the system, and shows what is due, what is missing, and what is still open. Brycer, which runs The Compliance Engine, and IROL both offer report review by their own staff, who check submitted reports for accuracy and completeness before the department acts on them. All three platforms describe automated reminders and notifications, which take much of the chasing off the department's staff.
The enforcement decisions stay with the department. Brycer says a department that uses its review service keeps its enforcement authority. The platform collects and organizes the reports, and the fire marshal's office decides what to do about a building that is out of compliance.
How a report gets from your technician to the department
- The department adopts a platform and sets a start date. Contractors usually learn about it from a notice sent by the fire marshal's office, and the department's fire prevention page names the platform and the date.
- You register your company. Johnston County, North Carolina's notice, for example, says there is no fee to register your company with The Compliance Engine. Each building on the platform is a record the department keeps (The Compliance Engine and LIV call them premises), so each report lands on the right property and system. IROL links the service provider, the owner, and the department to each other through ID codes issued at registration.
- The technician inspects as usual. Before the first job in a new jurisdiction, check which report format and attachments the department accepts, so the office has what it needs to file.
- Someone files it. Depending on what the department accepts, that means uploading the finished report, entering the results in the platform's own form, or both. Where a fee applies, the platform bills it to the inspection company.
- Check that it went through. Save the submission reference and look at its status. A report can be held before it is processed; on The Compliance Engine, that happens when the payment card fails or the department has not yet reviewed a new property. It can also be rejected because something is missing, which is different from an accepted report that lists deficiencies.
- Review flags the deficiencies. Where the department uses report review, the platform's reviewers confirm the report is complete and review the deficiencies. The owner and the department see the open items.
- Report the repair. When the deficiency is fixed, report the repair through the platform's correction process, with whatever proof it asks for. On The Compliance Engine, the correction goes to the department for approval before the item closes, and the steps differ depending on whether your company reported the original deficiency.
If a report is rejected, read the reason, correct the report, and resubmit it. The Compliance Engine's own guidance is to correct and resubmit as soon as possible. Ask the department if the reason is unclear, or the platform's support team if the problem is technical.
Who pays the filing fee
The inspection company pays. Brycer says The Compliance Engine costs jurisdictions nothing and is funded by inspection filing fees, charged per system report. LIV describes the same arrangement: no direct cost to the department, sustained by a nominal filing fee paid by the inspection companies that submit reports. IROL charges nothing to departments and lets service providers pay as they go or by quarterly invoice.
Do not expect the department to waive it. The Los Angeles Fire Department says the fee is neither regulated nor collected by the city, so the city cannot exempt anyone from it. Some departments exempt certain filings; San Diego, for example, says repair reports do not incur a submittal fee. Ask before you assume. Amounts vary by platform, by jurisdiction, and sometimes by system or report type, and they change over time. Get the current fee for each jurisdiction from the platform before you price work there.
Then decide how the cost reaches the owner: a separate line on the invoice, which shows the owner the money goes to the department's platform, or built into the inspection price for buildings in that jurisdiction. Either way, put it in the service agreement before the first invoice shows it. IROL's FAQ addresses disputes over whether electronic filing is covered by an existing service agreement, and it encourages the service provider and the owner to negotiate.
What changes from one jurisdiction to the next
Adopting a platform does not make reporting uniform. Expect each of these to differ:
- Platform: neighboring departments can choose different platforms, so a contractor working across a region may file through more than one.
- Required reports: some departments want every report, including the ones that passed. Johnston County requires both compliant and non-compliant fire protection system test reports through The Compliance Engine. Others focus on the problems. Edmonton, Alberta requires LIV submissions for reports with defects the owner or its agent is unwilling or unable to correct, and recommends uploading all fire protection system reports.
- Covered systems: The Compliance Engine also handles backflow prevention assemblies and elevators, so some jurisdictions route backflow test reports through the same platform as fire protection reports.
- Report format: some departments accept your report as a PDF. On The Compliance Engine, a short form takes a PDF attachment, and a long form has you answer the questions in the platform.
- Filing deadline: some departments set a deadline for filing after the inspection date. Read the adoption notice; the last jurisdiction's rule may not carry over.
- Filing fee: it varies by platform and jurisdiction, and sometimes by report type.
Keep one list of the jurisdictions you work in, with the platform, the start date, which reports are required, the accepted format, the filing deadline, the fee, and who in your office files. For each job, save the submission reference and its status, so an unfinished filing stays visible until it is accepted.
The department's fire prevention page and its adoption notice are the sources to trust. If a vendor's map and a department's page disagree, ask the department.
The three platforms at a glance
| The Compliance Engine | IROL | LIV | |
|---|---|---|---|
| Operated by | Brycer | Brycer, which announced its acquisition of IROL in January 2026 | LivSafe |
| Footprint the vendor states | Over 2,000 jurisdictions | No count on the pages cited | 350+ jurisdictions in the US and Canada |
| What it covers | Fire protection systems, backflow prevention assemblies, and elevators | Third-party ITM reporting, plus fire alarm registrations, property risk assessments, and pre-plan and occupancy inspections | ITM reporting and deficiency tracking, plus the department's own inspections and permits |
| How inspection companies pay | A fee per system report | Pay as you go or quarterly invoicing | A filing fee when reports are submitted |
| Report review | Review by Brycer's specialists | Standard with third-party reporting, by IROL's review department | Review workflows described; who performs the review is not stated |
Coverage figures are each vendor's own claim, from its website in October 2026. Confirm the platform for each property with the department.
Where your inspection software fits
Someone in your office has to submit each required report, check that it was accepted, fix the ones that come back, and report the repairs. When the office files directly in the platform, that means logging in, finding the property, uploading the report or entering the results system by system, and coming back later for the repair. Across several jurisdictions, it is the kind of work that slips during the busy season.
The options:
- File from your inspection software. Some inspection platforms connect directly to these systems, so reports go to the department's platform from the software instead of being uploaded one at a time.
- Hand the filing to the platform. Brycer offers Compliance Sync, a managed service in which contractors send completed reports and Brycer's staff enter them into The Compliance Engine. Brycer describes it as a service with nothing to install, for contractors who want Brycer to handle report submission.
- File in the platform yourself. This works at lower volume if one person owns it, with the jurisdiction list above and the department's notices routed to them.
Inspect Point integrates with all three platforms. In the 12 months to early October 2026, 135 customers sent 30,363 reports to The Compliance Engine, IROL and LivSafe through Inspect Point. The partner pages for The Compliance Engine, IROL, and LIV list what each connection carries. Filing with the department does not send the customer a copy. The office can publish the report, along with the proposals and invoices for any repair work, to the Inspect Point customer portal. Inspect Point tracks each deficiency through New, Out for Quote, Quote Accepted, and Fixed.
A checklist for a jurisdiction that just adopted a platform
- Confirm the platform and the start date from the department's notice or its fire prevention page.
- Register your company on the platform.
- Find out which reports are required (every report, or only the ones with deficiencies), which systems are covered, what format the department wants, and the filing deadline.
- Get the current filing fee for that jurisdiction and decide how it will appear on your invoices.
- Update your service agreements and tell customers in that jurisdiction before the first invoice carries the fee.
- Decide who files reports, checks that each one was accepted, fixes rejections, and answers the department's notices.
- If you use an integration, set it up for that jurisdiction's properties and check the first submission in the platform.
For how the fire department's own inspection differs from the inspections contractors perform, see fire department inspection vs. contractor inspection.
Common questions
Do passing reports have to be filed?
It depends on the jurisdiction. Johnston County, North Carolina requires both compliant and non-compliant fire protection system test reports through The Compliance Engine. Edmonton requires LIV submissions for reports with defects the owner is unwilling or unable to correct, and recommends uploading the rest. The adoption notice says which rule applies.
What should I do if a report is rejected?
Read the stated reason, correct the report, and resubmit it, then confirm the new status. Ask the department if the reason is unclear, or the platform's support team if the problem is technical. The filing is not complete until the corrected report is accepted.
Can the building owner pay the filing fee instead of the contractor?
The platforms describe billing the inspection company that submits the report. What you charge the owner is between you and the owner, so put the fee in the service agreement.
What happens if a report is never filed?
Then the filing the department requires is incomplete. Check whether the report was submitted and whether it is held or rejected, and ask the department what it needs. The department decides what enforcement follows.
Is Brycer the same company as IROL?
They are now under one owner. Brycer announced on January 8, 2026 that it had acquired InspectionReportsOnline.net, the company behind IROL, and IROL's own site now says it has been powered by Brycer since December 31, 2025.
Sources
Platform and department details were checked against these pages in October 2026. Fees, requirements, and coverage change; the department's current notice wins over anything here.
- Brycer: The Compliance Engine, What is TCE?, Report Review Services, Compliance Sync, and the IROL acquisition announcement
- The Compliance Engine support: Ready for Payment, Open and Rejected Reports, Template Types, Submit a Repair Report, and Mark Deficiencies as Compliant
- IROL: IROL home (now powered by Brycer), Third-party reporting and FAQs, Community Compliance, and Preplan and Inspection Program
- LIV: LIV home and the LIV platform page
- City of Edmonton: Fire inspection report submission
- Los Angeles Fire Department: The Compliance Engine FAQs
- Johnston County, North Carolina Fire Marshal: Reporting to TCE
- City of San Diego Fire-Rescue: The Compliance Engine
See Inspect Point run on your own inspections. A 30-minute demo, no commitment.