Chat with us, powered by LiveChat
Home
Product
What Is InspectSync Platform Modules Onboarding AI Features
See It
Screenshots & Walkthrough Videos Showcase (See a read-only version of the Office App) Fire Alarm Inspection Demo (Walk a fire alarm inspection from the technician's phone) Fire Extinguisher Inspection Demo (Walk an extinguisher round, scan units and swap from the van) Sprinkler Inspection Demo (Walk a wet sprinkler inspection from the riser to the control valves)
Company
About Contact Deficiency of the Week (Just for Fun) Pricing Login Book a Walkthrough Try It Risk-Free for 30 Days
Workflow

NFPA 72 Fire Alarm Inspections in InspectSync

This workflow shows how InspectSync handles the periodic inspection and testing of fire alarm and signaling systems under NFPA 72, device by device, from the contract that owes the visit to the report and the repair quote. It is written for fire alarm contractors who want to see where each step lands in the platform.

NFPA 72 sets the inspection and testing requirements for fire alarm and signaling systems. A fire alarm inspection in InspectSync is a device-level job: the building's panel, initiating devices and notification appliances are assets with a device type and sub-type, a floor and a location, and the technician records a result for each one from the phone.

You can walk a sample fire alarm inspection yourself in the Field app demo.

[CONTENT NEEDED: a short, reviewed statement of which NFPA 72 test frequencies and device types the standard fire alarm forms cover. Have a licensed inspector confirm before publishing.]

Steps

  1. The contract owes the visit. The customer's agreement records the building, the fire alarm inspection type, the frequency and the lead time, and the inspection job is generated from it on time.
  2. The building lists the devices. Panels, initiating devices and notification appliances are assets under the fire alarm system on the building in CRM, so the visit is pre-loaded with what has to be tested. A device the technician finds that is not on the list is added from the field.
  3. Dispatch schedules it. The job is placed on a technician and a day from Dispatch or Team Scheduling, alongside the other work in that part of town.
  4. Devices are tested on the phone. The field app presents each device; the technician records the answers, notes and photos per device, marks a device no-access with a reason when it cannot be reached, and every question required for report submission is answered before sign-off.
  5. The report renders at sign-off. When the visit is signed, the fire alarm report PDF is generated. The office sends it in one action to the contacts holding the Reports role, and it can be published to the customer portal automatically under the customer's publishing rules.
  6. Failed devices become deficiencies. Each failure is a deficiency on the building and the device, with a type, tracked until a later visit verifies it corrected.
  7. The repair is quoted and scheduled. The job waits in the Quote Queue until the quotes it needs exist; the service quote is priced, sent, and on acceptance becomes a service job.
  8. The job is billed from the queue. Completed work waits in the Billing Queue until it is invoiced, so nothing finished goes unbilled.

Related modules

  • Contracts — Recurring inspection agreements that generate their own jobs, renewals and obligations.
  • Jobs — Scheduling, dispatch, field inspections, same-day reports and the deficiency-to-quote loop.
  • CRM — Customers, buildings, assets, contacts, national accounts and the sales pipeline in one record.
  • Billing — Billing queue, invoices from the job, online payment, AR aging, QuickBooks and Square.
Try It Risk-Free for 30 Days Book a Walkthrough