Fire & Life-Safety Inspection Logbook: Always Audit-Ready
Turn a spreadsheet of fire extinguishers, exit signs, and emergency lights into a phone-friendly inspection logbook with checklists, photo evidence, overdue alerts, and a safety-officer approval gate before any failed device is closed out.
A web tool where you import your life-safety devices, the system schedules recurring inspections, an inspector completes a checklist with timestamped geotagged photos on their phone, any failure auto-raises a corrective action, a safety officer reviews and approves the remediation before the device is closed, and you get loud overdue alerts plus an immutable compliance log you can export as CSV for auditors.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- A Resend account (free)
- A device list CSV (location, type, frequency, last-inspected date)
- A phone for on-site photo checks
- Claude Code or any AI coding agent
The problem this kills
Your fire extinguishers, exit signs, emergency lights, alarms, and eyewash stations all need checking on a schedule — monthly, quarterly, annually — and an inspector or fire marshal can walk in any day and ask for proof. So the burden of "are we compliant?" usually lives in a binder, a clipboard, or a spreadsheet that nobody trusts. Tags get initialed but never logged, a failed extinguisher gets noted on a sticky note that vanishes, and nobody can tell you at a glance which devices are overdue right now.
When the auditor shows up, the scramble begins: digging for photos, reconstructing dates, hoping the gap between "we inspected it" and "we can prove we inspected it" doesn't become a citation. You don't need a $40k facilities platform to fix this, and you don't need to be a developer. You need a logbook that schedules itself, captures proof on a phone, screams when something's overdue, and keeps a tamper-proof history.
What you'll build
A simple internal web tool. You import your device list — each life-safety asset with its location, type, inspection frequency, and last-inspected date — and the tool builds a recurring inspection schedule. An inspector opens the tool on their phone, sees what's due, and walks the building completing a type-specific checklist (a fire extinguisher checklist is different from an eyewash-station one), marking each item pass or fail and snapping timestamped, geotagged photos as evidence. Any failure auto-raises a corrective action — a work order — for that device. A safety officer reviews failed and flagged items, approves the corrective work, and only after the fix is approved does the device get marked remediated and closed. The whole thing tracks overdue inspections loudly, keeps an immutable inspection history for auditors, and exports the full register as CSV.
What's inside the Implementation Plan
The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your building and your devices — what equipment you inspect, how you name and tag locations, which frequencies each device type follows, what your checklists actually contain, your typical and peak inspection volumes, who's allowed to approve a remediation, and the messy edge cases (a device under repair, a missed cycle, a shared building, a device that gets relocated) — and then it tailors the data model, the checklists, the schedule, and every later step to your answers. This is not a generic template; the agent reflects a short spec back to you and waits for your thumbs-up before it builds anything. From there it walks the agent through the import, the recurring scheduler, the mobile checklist with photo capture, the auto-raised corrective actions, the safety-officer approval gate, the overdue alerts, and the CSV export — each step with a ready-to-copy prompt. There's also a fallback so you can build and run the whole thing today with just a spreadsheet and no integration to any existing system.
The governance it includes (this is the point)
This is compliance tooling, so it ships with the controls an auditor wants to see: login so only your team can use it, row-level security so you only ever see your own organization's buildings and devices, a complete audit trail of who inspected what and when and who approved each remediation, a hard human-approval gate so no failed device is ever marked "fixed" until a safety officer signs off on the corrective work, and duplicate guards keyed on (device + inspection date) so the same inspection can't be logged twice. The inspection history is append-only — records can't be quietly edited after the fact — which is exactly what makes the log trustworthy when someone official asks for it.
Who it's for
Facilities and EHS coordinators, safety officers, and building managers who own life-safety compliance and are tired of clipboards, missing photos, and audit-day panic. If you can describe your devices, your inspection frequencies, and who's allowed to sign off on a fix, you can build this.
You've got this — start with the plan, paste the first prompt, answer the interview, and you'll see your first inspection schedule light up the same afternoon.