Permit & Lockout-Tagout (LOTO) Checklist: No Verified Isolation, No Work

The problem this kills

Some jobs can hurt someone if they're done wrong. A panel that's still energized. A line that's still under pressure. A confined space nobody tested. Your safety program has the right checklists — hot-work permits, lockout-tagout steps, lock and tag numbers — but they live in a binder, a PDF, or a tribal habit, and the only thing standing between "we did it right" and "we skipped it" is whether a busy technician remembered to.

When something goes wrong, the question every regulator and insurer asks is the same: prove the energy was isolated before work started, and prove someone competent verified it. If your proof is a paper form in a truck or a memory, you don't have proof. And the moment a job can quietly slide into "in progress" without that proof, the whole program is optional.

The fix is to make the checklist unskippable. The tool decides which jobs need a permit or LOTO, forces the right steps with lock/tag numbers and photos, and refuses to let the job proceed until a crew lead or safety manager has verified the isolation and signed off. You do not need to be a developer to build it.

What you'll build

A simple internal web tool for your field-service and safety team. You import your work orders (from a CSV or Google Sheet) and your rules for which job or asset types require a permit, lockout-tagout, or both. For any applicable job, the tool generates the right checklist and makes the technician complete it — capturing each lock number, tag number, and photo proof of the isolation. A crew lead or safety manager then verifies and approves the completed permit/LOTO. Until that approval is recorded, the job is hard-blocked from moving to "in progress" — there is no override path that skips verification. Every LOTO record, with its photos and approval, exports to CSV for your audit and insurer.

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 business — how jobs are dispatched and who works them today, which job and asset types actually trigger a permit or LOTO, the exact steps in your checklists, how you number locks and tags, your typical and peak job volumes, who is allowed to verify and approve an isolation, and the messy edge cases like group lockouts, shift changes, and a single work order with multiple energy sources. It reads a short spec back to you for a thumbs-up, then builds the tool around your rules and your checklists instead of a generic template. From there it walks the agent through the data model, the rules engine that flags applicable jobs, the checklist and photo-capture flow, the verify-and-approve gate, the hard proceed-block, and the CSV export. Every step ends with a ready-to-copy prompt.

The governance it includes (this is the point)

This isn't a toy. The plan builds in the controls a real safety function needs: login so only your team can use it, row-level security so people only see their own organization's jobs, a complete audit trail of every checklist step, photo, verification, and approval (who, what, when), a hard human-in-the-loop gate so no job reaches "in progress" until a competent person verifies the isolation and signs off, and duplicate guards so the same work order can't get two LOTO records — deduped on the work order plus its LOTO. The whole tool exists to make the safe path the only path: the technician documents, a competent person verifies, and only then does the job proceed.

Who it's for

Technicians who do the lockout, crew leads who verify it, and safety managers who answer for it. If you can describe which jobs are dangerous and what your checklist requires, you can build this.

You've got this — open the plan, paste the first prompt, and you'll have an unskippable LOTO gate running by the end of the afternoon.