Incident & Near-Miss Reporter: Catch the Close Call Before It's an Injury

The problem this kills

A technician almost steps off a ladder that wasn't footed. A delivery driver swerves around a forklift that pulled out blind. A panel arcs when a breaker that should have been locked out wasn't. Nobody got hurt — this time. And because nobody got hurt, nobody writes it down. The near-miss evaporates, the hazard stays, and three weeks later the same close call lands someone in the ER.

When incidents do get reported, it's worse: a paper form in a truck glovebox, a text to a supervisor who's busy, a photo that lives on someone's phone forever. The safety manager finds out late, can't tell a sprained wrist from a recordable injury, assigns a fix in a hallway conversation that nobody tracks, and then can't prove any of it happened when the auditor or insurer asks. Reporting feels like punishment, so people stop doing it. You don't need to live like this, and you don't need to be a developer to fix it.

What you'll build

A dead-simple internal web tool your field staff open on their phones. In about two minutes they file an incident or a near-miss: what type, where, who was involved, what happened, and a few photos straight from the camera. Near-misses can be filed anonymously so people actually report them. The moment a serious event comes in, the tool escalates immediately — your safety manager (and whoever else you name) gets pinged right away instead of finding out tomorrow.

Every report lands in the safety manager's queue. They review it, confirm or correct the severity classification, and assign corrective actions — each with an owner and a due date. Those actions are tracked to closure: open, in progress, done, with reminders chasing the ones that slip. Nothing is "fixed" until a person says it's closed. The whole incident log and its corrective actions export as a clean CSV in the exact columns your safety system, EHS software, or spreadsheet expects.

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 — your real incident types and severity tiers, what makes something "serious" enough to escalate, who your safety manager and backups are, how you want anonymous near-misses handled, your sites and how they're named, your corrective-action and due-date rules, and the messy edge cases (a report that's really for another contractor's crew, two people reporting the same event, a near-miss that should have been a recordable). It then tailors the form, the severity logic, the escalation, 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 mobile report form with photo upload, the immediate-escalation rule, the safety-manager review-and-classify gate, corrective-action assignment and closure tracking, and the CSV export — each step with a ready-to-copy prompt. There's also a fallback so you can build the whole thing today even with no integration to your existing safety system.

The governance it includes (this is the point)

This is real safety-and-compliance tooling, so it ships with the controls a serious operation needs: login so only your team can use it (with a narrow, safe path for anonymous near-miss submissions), row-level security so you only ever see your own organization's reports, a complete audit trail of who reported, reviewed, classified, assigned, and closed each item and when, a hard human-review gate so a safety manager confirms the severity and signs off on the corrective actions before anything is treated as official, and duplicate guards keyed on the incident plus its timestamp so the same event reported twice doesn't become two records. That audit trail and closure history is exactly what an OSHA inspector, an insurer, or a certification auditor asks to see.

Who it's for

Field technicians, drivers, and crews who need to report a close call in two minutes without paperwork; safety managers and HSE/EHS coordinators who own classification and corrective actions; and operations managers who need proof that hazards get fixed. It fits HVAC, electrical, plumbing, construction, facilities, utilities, logistics, manufacturing, and any field operation that wants near-misses surfaced and incidents tracked to closure instead of forgotten. If you can describe how your team decides what's serious and who fixes it, you can build this.

You've got this — start with the plan, paste the first prompt, answer the interview, and you'll have your first incident reported, reviewed, and tracked to closure the same afternoon.