30-min call with RobBook a proof-of-concept call
Job 04 · Service and impairments

// Fire protection contractors · A later job

The impairment paperwork, drafted after a person decides the system comes down.

Impairment notifications for sprinkler, alarm, standpipe and kitchen hood shutdowns, tested as a free AI proof of concept on 20 to 30 impairments your office already handled. Once a person has decided a system is out of service, AI drafts the notices to the fire department, the insurer and the alarm monitoring company, the tag text, the fire watch log sheet and the restoration notice. Your reviewer compares each draft with the paperwork that really went out.

Book a proof-of-concept call30 minutes with Rob
Past impairments
20 to 30
Notices sent by AI
None
System access
None

// The one job

A riser comes down tomorrow. Several parties have to hear first.

A planned shutdown at a distribution warehouse: your crew will drain a riser to replace a corroded section of main. Before the valve closes, someone tells the fire department, the owner's insurer and the alarm monitoring company, writes the tags, warns the tenants and lines up a fire watch if the work runs long. When the riser is back, they all hear again, and the same building details get typed into every form.

In the proof of concept, AI reads the work order, ticket or report behind each past impairment and drafts the whole set of paperwork for it: each notice with its recipient and deadline, tag text for every location, a fire watch log sheet set to that jurisdiction's patrol rules, and the restoration notice that closes it out. Deciding, sending and signing are left to people. Your reviewer checks each draft against what your office and the owner's impairment coordinator actually sent.

Job and reportShutdown decided
Building
System
Valve or panel
Decided by
WorkStartExpected end
Illustration, not one of your jobs
One job
every notice
Impairment packetDrafts to approve
Jurisdiction
Insurer
Monitoring
Coordinator
NoticeToBy when
Illustration, not a real notice

// Where it gets hard

The same facts, owed to several parties, on different forms and clocks

Each insurer runs its own program. AXA XL Risk Consulting's impairment guideline sorts impairments into emergency, planned and hidden, and wants planned ones reported to its Impairment Center at least 48 hours ahead. Its RSVP red tag tears in two: the Shut-Off Tag hangs on each closed valve, and the Office Reminder stays in the office of whoever supervises the impairment. The same guideline tells owners not to let outside contractors impair protection alone. QBE North America wants 48 hours' notice of a planned impairment expected to pass 10 hours, with the systems affected, partial or complete, expected length and precautions. AEGIS wants anything longer than one shift reported online, down from 12 hours before its April 2026 revision, with one printed copy on the impaired system and one in the control room. The draft follows the insurer named in the job and flags a job with none on file.

Each jurisdiction asks in its own way. Bellevue, Washington's impairments handout wants a Report of Impaired System e-mailed at least five business days before any shutdown longer than 10 hours, naming the technician doing the work and an emergency contact, and has tenants told by e-mail, lobby signs, flyers and calls. Canandaigua, New York takes its out-of-service notice by fax, besides the call to the alarm monitoring station, with boxes for the reason and the type (pre-scheduled, emergency, damage or hidden, maintenance) and a return-to-service section reading fully operational except as noted. The draft fills in the form the building's jurisdiction uses and leaves blank anything the job doesn't support.

Tags go wherever the next person will look. The model fire code, as Canandaigua and Syracuse print it, carries tags past the valves and connections to the fire alarm control unit, the fire alarm annunciator and the fire command center. Bellevue's table moves a kitchen hood's tag to the control valve of its extinguisher cylinder, puts a fire pump's at the fire command center, and uses a short-term tag for shutdowns under 10 hours. QBE's sample sprinkler tag records how many turns it took to close the valve, who closed it, and who reopened it and when, and goes into the maintenance logs once it comes off. The draft writes tag text for each location that building actually has.

Fire watch rules change at the city line. Santee, California's fire watch packet has every floor and common area patrolled at least once an hour by a state-bonded, insured security service or someone the Fire Marshal approves, with no other duties; the signed log of each patrol's time, route and observations goes to the Fire Marshal daily, and the watch ends only on written or electronic word, never verbal. Mobile, Alabama sets patrols every 15 minutes where people sleep, in institutional buildings and in occupied assembly spaces, and every 30 minutes elsewhere. The draft sets up the log sheet for the building's jurisdiction; who stands the watch and when it ends stay with people and the fire marshal.

Closing out is a second round of notices. Under the model code's section on restoring systems to service, the impairment coordinator confirms that inspections and tests show the system works, that supervisors, the fire department, the owner, the insurer and the alarm company have been told protection is back, and that the tags are off. QBE adds a main drain test to confirm the system is back to its pre-impairment condition, and Bellevue asks which portions of the system were restored. Your reviewer will look first for: a party missing from the list, a notice later than the insurer's or the jurisdiction's lead time, a tag location left out, a patrol interval taken from the wrong city, and a restoration notice that doesn't answer every notice that opened the impairment.

// What you send

What the test needs from your service office

20 to 30 impairments
Copies only
01

20 to 30 past impairments

Planned and emergency shutdowns your office handled, across sprinkler, alarm, standpipe and hood work, each with the work order, ticket or report behind it.

02

The paperwork that went out

Every notice, tag, fire watch log and restoration notice as sent, with who received it and when, including any a fire marshal or insurer sent back.

03

Each building's parties

The jurisdiction, the insurer and its impairment program where you know it, the alarm monitoring company, and the owner's impairment coordinator.

04

NDA first, look-alikes if needed

Impairment records show when a customer's building was unprotected, so the NDA is signed before any file moves. If an owner won't allow copies, we rebuild look-alike jobs with your reviewer.

// Before it starts

Agreed before the first job is drafted

Before any file is sent, the owner names the judge and writes down what a good packet looks like.

Impairment test termsOwner signs off
Reviewer
Named by the owner. Often the service manager or the coordinator who sends impairment notices now.
Success criteria
Agreed in writing first, including how a missed party or a late notice counts
Impairment decision
Made by a person before any draft starts, never by AI
Price
A range for the live job, before the first impairment is drafted
NDA
Signed before any job file moves

// How it's judged

Each draft packet beside the paperwork your office sent

Impairment by impairment
Notice by notice
Same 20 to 30 impairmentsYour office's paperworkThe proof of concept
Every party that had to be toldFilled in from your impairmentsFilled in from your impairments
Notice timing against each lead timeFilled in from your impairmentsFilled in from your impairments
Tag text for each locationFilled in from your impairmentsFilled in from your impairments
Fire watch log set to local rulesFilled in from your impairmentsFilled in from your impairments
Restoration notices that close each opening oneFilled in from your impairmentsFilled in from your impairments
Drafts your reviewer had to correctFilled in from your impairmentsFilled in from your impairments
Waiting on your jobs. No cell holds anything before your own past shutdowns are drafted.Your reviewer marks each row against the criteria you agreed at the start.

// After a yes

About 30 days on live shutdowns

Once your reviewer says yes, the job runs for about 30 days on impairments as your office plans them or as emergencies come in.

Nothing goes out unapproved. A person checks every notice, tag and log sheet and sends it themselves; the draft lists who must be told and by when, and flags any lead time that has already passed.

Its fixed price is agreed after the test and signed before the live run starts. Long-interval calendars, deficiency quotes or the next job are priced separately, and monthly support starts once a job is live.

// After impairments

What could come next

Possibilities, ranked
One at a time
  1. 01

    Fire watch log review

    Returned fire watch logs read for missed patrol times and unsigned sheets before your office forwards them to the fire marshal.

    Next
  2. 02

    Long-interval test calendars

    Each building's three-year and five-year work dated from past reports, so planned shutdowns can be booked and announced early.

    Then
  3. 03

    Impairment histories for insurers

    A dated list of every impairment per building across a policy year, drafted for the owner's insurer or risk manager when they ask.

    After that

// One hard limit

It drafts the notices. People decide, sign and send them.

A person decides that a system is out of service before anything is drafted, so the proof of concept never decides that a system is impaired, and never that one meets code. It notifies no fire department, insurer, alarm company or tenant, ends no fire watch, and never signs, certifies or changes an inspection report. No date in a draft binds the owner or the jurisdiction until a person approves it. Your licensed staff, the impairment coordinator and the authority having jurisdiction make those calls.

Priced per job. You get a range before the proof of concept and a fixed price before you sign.

The range comes on the call, once we know about how many impairments your office handles in a month and how many jurisdictions and insurers they involve.

// Questions

Impairment paperwork questions from service offices

Will the AI notify the fire department or the insurer?
No. It drafts each notice and lists who must receive it and by when. A person reviews it and sends it by whatever channel that fire department or insurer accepts.
Who decides that a system is impaired?
Never the AI. Your technician and the owner's impairment coordinator decide, and under the model fire code the building owner assigns that coordinator, or serves as coordinator when no one is named. Drafting starts only after the decision is on record.
Our customers have different insurers with different programs. Can one test cover that?
Yes, if the past impairments you send span several insurers. Programs differ in lead time, duration thresholds and tags, so the success criteria spell out what a correct notice looks like for each one.
What about emergency impairments in the middle of the night?
The people on call still make every call themselves. In a live run, the draft catches up the written notices and restoration paperwork from the ticket afterward, for a person to approve before anything is sent.
Rob Eason

Rob Eason, founder

// Book a proof-of-concept call

Bring your last few shutdowns and the notices that went with them.

A 30-minute call with Rob covers your company, your role, the job you'd test first and roughly how many impairments your office handles each month. Impairment files stay with you until the NDA is signed.

  • Co-owned a 60-employee financial services firm and sold his share to his partner.
  • Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
  • 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
  • 4.3/5 from 6 Google reviews of Massmarket AI.
  • Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
  • Takes every proof-of-concept call himself.