Scan the QR, run the checklist, capture geo-stamped photos — all without signal. The queue is visible to the tech, not buried in a daemon. Photo-required Fails block submit so nothing ships half-evidenced.
The asset grid colour-codes every device by the tech that owns it. Unclaimed, blocked, and double-claimed assets pop visually so nothing gets skipped or duplicated.
Same inspection, four branded PDFs. A one-page owner summary on top, code-cited AHJ packet for the jurisdiction, risk-graded carrier report for the insurer, and an internal ops record with margin and A/R that never leaves your shop.
Your logo, your colors, your terms. Photos and chain-of-custody hashes ride along — every byte accounted for.
Click an audience to switch the preview. Each layout is rendered from the same signed inspection — only the framing, weight of detail, and disclaimers change.
Plain-English headline summary on top. One critical finding, the dollar amount to fix it, and a one-tap approval button — no asset codes, no jargon.
Left: what a contractor emails today — a dense asset table with truncated codes, no plain-English summary, and a service-fee schedule buried in an appendix. Right: the RedTag OWNER report — one critical finding, the dollar number, the deadline, the approval button.
Brand the report once in onboarding — logo, accent color, license footer, even the cover-letter language. Every audience pack rolls with the same identity, every PDF you send. Nothing in the export says "Powered by" anything.
Every AHJ submission packets the signed PDF, a submission cover letter, the raw photo evidence as captured in the field, the inspector signature image, and a SHA-256 manifest verifying every byte. One ZIP. One click. Defensible the moment it leaves your shop.
Hospitals. Multi-tower campuses. Anything over 200 devices with more than two techs walking it. That's where a browser-only, paper-style workflow stops keeping up — and where contractors burn hours reconciling who-did-what after the fact.
QR or NFC pulls up the asset's history and the inspection form filtered to the right template. Recent scans on this site stay one tap away so techs don't lose their place.
Last passed date, due date, and 38 prior records open instantly — even when the device hasn't seen the cloud in 6 hours.
No buried daemon, no surprise sync prompts. The tech sees the queue depth and the offline state right on the scan view.
Sub-basement reads, faded labels, busted QR? The manual fallback is right there. No back-and-forth to a settings panel.
Every line item carries a required-evidence model. Techs see exactly what's missing before they ever try to submit — and they can't ship a half-evidenced report by mistake.
44px tap targets, color-coded states, no chained dropdowns. The slowest part of any inspection app used to be the form chrome. Not anymore.
Mark a Fail and the system drafts the deficiency for you: NFPA section, severity, asset link, the captured photo. The office never has to re-key it.
We don't let the tech submit a Fail without evidence. The submit button is greyed and the gate banner names the item. Audit trail is intact by construction.
Every offline write — responses, photos, signatures — lands in a visible queue with size, age, and state. Auto-flushes on reconnect. No mystery daemon, no lost work.
Each row shows what it is (response or photo), the byte size, and how long it's been queued. If something hasn't flushed, the tech and the office can both see why.
When the device gets signal back, the queue drains in the background. If the tech wants to force a retry from the loading dock with one bar, the Retry button is right there.
Below the pending list, a Confirmed Today section shows what already flushed and from where. Techs can close out their shift knowing nothing is stuck.
NFPA cadences drive the rule engine, the rule engine drives the schedule, the schedule drives the techs. Sign off in the field and the next visit is already on the calendar.
Forget the spreadsheet of due dates. RedTag-ITM watches every asset against its NFPA frequency, surfaces due-soon + overdue work, and lets you drag a chip onto a tech's day to assign — with the next recurrence pre-anchored to the day they sign.
Unscheduled + overdue work lives in a queue on the left. Each tech is a swimlane, each day is a column. Drag a chip onto a day to assign it — capacity is enforced, conflicts highlight before you drop.
Every recurring rule has an early-grace / on-time / late-grace / overdue tolerance. Jobs slot into the right bucket automatically — dispatcher opens the page, knows what to do first.
Already late · escalation playbook engaged
Should be on a tech's day before week-end
Plenty of runway · plan around technician PTO
Every recurring rule starts from one of these templates. You set the scope (customer / site / system / asset type), we generate the cadence. You can override anchors and grace windows, but the defaults match the code.
Need a cadence we don't ship out of the box (NFPA 96 quarterly hood degreasing, NFPA 291 hydrant flow, NFPA 13 acceptance retest)? Build a custom rule in the editor — the same anchoring + tolerance + routing primitives apply.
Every inspection sign-off is the start of the next inspection. The cron + RecurringSchedule pair guarantees you'll never miss an NFPA cadence — even if every dispatcher takes the week off.
on BuildingReports“incomprehensible to the client”
R/FIREALARMS · 4MO
on a legacy ITM tool“faster on pen and paper”
R/FIREALARMS · 2MO
on BuildingReports“setting up is a 6-week project”
CAPTERRA · 3/5
We import your CSV, set up your branded reports, and run the first inspection alongside you. No card required until day 30.