Webinar replay · Inspect Point Assistant + Inspection Assistant

Get your SOPs out of the binder.

Forty minutes inside a real account: a vacant-building procedure gets loaded in the office, and a technician pulls it up on site instead of calling in.

Watch · 40 minRecorded Tuesday, October 13, 2026
  1. 0:00Welcome and what this session covers
  2. 1:59Poll: how the room uses AI today
  3. 3:03Five problems every shop reports
  4. 5:51The two assistants and what each one does
  5. 8:03Three rules customers actually run
  6. 12:50Loading an SOP into the system
  7. 17:27Poll: where SOPs live today
  8. 18:40A technician hits a vacant building
  9. 22:56Questions customers ask before turning it on
  10. 29:19Live Q&A

What 11 fire protection companies told us about their own procedures

Sixteen customers joined live and 11 answered the polls, so this is a room rather than a survey. It still lines up with what the hosts said they hear every week.

Where SOPs live today

  • A shared drive4
  • Paper binders or printed packets3
  • Nothing written down3
  • A separate training system1

One company in 11 keeps procedures in something built to hold them. Everybody else is relying on a folder, a binder or somebody's memory.

Who checks that a tech followed the SOP

  • Nobody checks consistently4
  • The office catches it when something looks off4
  • A manager reviews the report afterward2
  • The customer or the AHJ catches it1

Eight of 11 find out by accident or not at all. One is finding out from the customer, which is the expensive way.

How a company rule gets from somebody's head onto a technician's screen

Getting the procedure in

Two ways in, both from the office. An admin uploads a procedure you already wrote, or types a single rule directly. Setup lives with office staff, and technicians never author anything.

Uploads are text or markdown files. A Word document, a PDF or a Google Doc converts in a couple of clicks. Once the file is in, the assistant reads it, asks about anything unclear, and shows you its interpretation before it saves. You confirm the reading is right, and only then does the rule exist.

If the procedure is not written down anywhere, that is the actual work. One customer talked a procedure into a voice recorder, had the transcript cleaned up, and uploaded the result. Turning the assistants on is a toggle. Writing down what you already know is the part that takes an afternoon.

Deciding where it applies

A rule does not have to apply everywhere. One example from the session: a healthcare rule, where every deficiency at those accounts carries a photo. Write it once against the accounts it belongs to instead of repeating it in every handoff. The office can preview what a rule will do before it is live, and rules stay editable, because procedures change.

What the office gets

The office side is a chat against your own records. Show me Q3 deficiencies. What inspections are overdue. The answer comes back as a list you can download and work from.

Your rules reach the reporting side too. A company that runs October through December as Q1 sets that once, and every Q3 question after it returns the right date range without anybody rebuilding an export.

What the technician gets

Office staff write the procedures. Technicians read them. That is the whole split, and it is why nobody has to trust a tech to maintain anything.

In the field, the tech opens the inspection on the iPad they already carry, taps the assistant, and types the situation in plain words. In the recording: this building is vacant, what is my procedure?

What comes back is your own procedure, written by your office, and the assistant names the document the answer came from so the tech can check the original. Do not start the inspection. Call this person. Here is her number. In the demo the contact in that procedure was not set up as a contact on the account at all, and the technician still got her details.

“What I most commonly hear is it’s up here in their head. A lot of people have these SOPs, but the techs can’t access them. New employees can’t access them easily because they’re scattered about.”

Jenn Doyle, Co-Founder, Chief Culture Officer

“Every time we’re delayed in getting that report out, that means we’re delayed in getting an invoice out, which means we’re delayed in getting paid.”

Jenn Doyle

What the room asked

Every answer below was given live on the recording. The timestamps jump to it.

Does this work if we run Inspect Point alongside another service platform?

Yes, and the hosts were specific about which half does what. Inspection Assistant still gets completed reports back clean and fast, so whatever you push into for billing or quoting gets better input. Inspect Point Assistant still queries the asset and deficiency data that lives in Inspect Point, which is data you often cannot query the same way somewhere else. Technicians keep access to the manufacturer and device detail that lives there too. Hear it at 29:19

What are customers who already use it saying?

Three things. Every piece of in-product feedback routes to the product team and gets read, praise and complaints landing in the same place. What they hear most is about reporting work that disappears, where a pull that used to mean five separate exports and a pivot table now comes back directly. The third theme is data consistency, because rules keep the same fields filled the same way across buildings, which makes scheduling, quoting and invoicing less messy. Hear it at 32:21

Why does the upload only take text and markdown files?

Those formats carry the words without the noise. A PDF brings photos, branding and layout that the system then has to interpret, and interpretation is where a procedure gets subtly wrong. A Word document, a PDF or a Google Doc converts in a couple of clicks, which is how the hosts prepared the session's own examples. Hear it at 36:12

What if a technician gets a wrong answer?

It is the same fix as any other wrong answer on an inspection. Either the technician corrects it and resubmits, or the office does. Each technician only sees their own work, so there is not much for one person to break. Hear it at 22:56

What if my techs will not use it?

The hosts named this as the most common pushback they hear. Their answer was that it does not add steps to a technician's day, it removes a phone call. They also took the suspicion head on: this is not a monitoring tool watching what a tech does. Hear it at 24:07

How long does setup take?

Turning it on is a toggle and some configuration. Writing down the procedures that currently live in people's heads is the real timeline, and the hosts said so bluntly to the people who had just answered "nothing written down" in the poll. Hear it at 25:03

What does it cost?

It runs through your account manager. Pricing is per user and they walk you through it. Hear it at 25:49

One attendee raised a hand at the end and could not be unmuted, and was asked to type the question instead. It never got answered on the recording, so it is not here.

See it on one of your own procedures.

Pick the procedure your office explains over the phone every week. The vacant building, the account that needs a photo on every deficiency, the customer with its own fiscal calendar. We will show you what it looks like once it is loaded, and what your technician sees when they hit it on site.