Near Miss Report Template: AI Logs, Categorises and Spots Trends

A near miss form needs about eight fields: when, where, what happened, what could have happened, what was done straight away, who saw it, a category and an owner for follow-up. Let workers capture it by voice note or photo, have AI turn it into the form and suggest a category, then review the counts monthly.

The weak point in most factory systems is not the form. It is that nobody fills it in, or that reports pile up unread. Capture has to take under a minute, the coding has to be consistent, and one named person, usually the safety officer, owns the actions. The assistant handles the middle part. It never owns the decision.

Follow me on Instagram@sagnikteaches

What belongs on a one-minute near miss form

Every extra field loses reports. Keep the form to the facts a safety officer needs to decide whether to investigate. Here is a layout with what each field is for.

Connect on LinkedInSagnik Bhattacharya

The reporter completes the first six. The assistant proposes the category and severity guess, and the safety officer confirms them and assigns the owner. Splitting the form like this keeps the worker's job short and the judgement with the person accountable for it.

Subscribe on YouTube@sagnikteaches

Capture on the shop floor: voice note, photo or paper

Typing on a phone with gloves on is the main reason reports are lost. Offer three routes and let people choose.

• Voice note. The worker records twenty seconds on a shared phone or their own, saying where it was and what happened. A transcription tool or an assistant that accepts audio turns it into text. Voice is the fastest route, and it captures what people actually say, though noise on the floor can ruin a recording.
• Photo with a caption. A picture of the spilled oil, the unguarded belt or the pallet in the aisle, with a few words. Photos need a caption because an assistant describing a photo can misread what the hazard is.
• Paper slip. A tear-off card at the line, photographed or typed up at the end of the shift. It is the fallback for people who do not use a phone at work.

Whatever the route, the original stays untouched. Store the voice file, the photo or the slip next to the typed record, so that the safety officer can listen or look when the summary seems wrong. Before sending anything to an assistant, remove names and personal details. Use a business plan that does not train on your content by default, and check your company policy on safety records.

Turning a rough report into a clean record

Here is a prompt that takes a transcribed voice note and produces the form. It tells the assistant to leave gaps where the speaker left them, which is what stops invented detail from entering the log.

Below is a transcript of a worker's spoken near miss report from a small factory. Turn it into the form fields below. Use only what the worker said.

Fields: date/time (if said), location (use only the area names in my list), what happened, what could have happened (state it only if the worker described it; otherwise write "not stated"), immediate action taken, who saw it, category (choose ONE from my list), potential severity (low, medium, high) with a one-line reason.

Location list: Goods in, Press line, Paint booth, Packing, Dispatch yard, Workshop, Other.
Category list: Slips/trips/falls, Falling or moving objects, Vehicles and forklifts, Machinery and guarding, Manual handling, Chemicals and fumes, Electrical, Fire and heat, Housekeeping, Other.

If anything is unclear, list it under "Questions for the safety officer". Do not guess a cause.

Transcript:
[PASTE]

Say a worker's voice note reads: "Packing, about half two. The lad on the forklift came round the end of the racking and I was walking to the label printer. He stopped a metre away. He didn't see me because of the shrink-wrap stack." A usable output (illustrative) looks like this.

Date/time: afternoon, about 14:30 (date not stated)
Location: Packing
What happened: A forklift came around the end of the racking as a worker walked to the label printer. The driver stopped about a metre away.
What could have happened: not stated (the reporter implies a collision with a pedestrian)
Immediate action: forklift stopped; no further action stated
Seen by: the driver
Category: Vehicles and forklifts
Potential severity: high (pedestrian and moving vehicle at a blind corner)
Questions for the safety officer: Was the stack of shrink-wrap blocking the line of sight? Is there a pedestrian route marked at that corner?

Look at what the assistant did well: it kept to the stated facts, marked the missing item as "not stated", and turned the worker's offhand remark about the stack into a question rather than a cause. What the officer would fix: "What could have happened" is an inference, so mark it as the reporter's implication, as the assistant did, and do not treat it as a stated fact until the officer asks. Read each output against the transcript for the first fifty reports. After that, a weekly spot-check of five is enough.

Category coding that stays consistent

Trends only mean something if "forklift near miss" is coded the same way in March as in October. Two habits help. First, keep the category list short, ten at most, and write a one-line definition for each. Second, give the assistant the definitions every time rather than relying on its memory of last month's prompt.

When two categories could fit, the definition decides. Without that, the same event is coded differently each month and the chart wobbles for no real reason. If the assistant chooses a category you would not, correct it and add the example to the definitions. Over a few weeks the definitions improve more than the prompt does.

The monthly trend review

Once a month, the safety officer exports the log and runs a review. The assistant does the counting; the officer reads the result and decides what to do. Use the same prompt every month so figures are comparable.

Here is the near miss log for the month (columns: date, area, category, severity, status, days open).
1. Count reports by category and by area. Give a table.
2. Compare with the previous month's table below and list any category that rose or fell by more than 30 per cent, with both numbers.
3. List areas with two or more reports in the same category.
4. List actions still open after 30 days.
5. Show every total so I can check it. Do not suggest causes. Where a pattern might be due to few reports, say the count is small.

Previous month: [PASTE]

An illustrative month for a small metalwork shop with 28 reports might produce the following.

Check the sums: this month 7 + 5 + 4 + 3 + 4 + 3 + 2 = 28, and last month 3 + 6 + 4 + 3 + 5 + 2 + 2 = 25. Both match. The forklift row went from 3 to 7, a rise of more than 30 per cent. Housekeeping, at 2 to 3, also crosses the line, which shows how easily small counts trip a percentage rule. With such small numbers either could be noise, so the officer looks at the content: if five of the seven were at the same corner in Packing, it is a place, not a statistic. The assistant lists those; the officer walks the corner.

Closing the loop: actions and owners

A log without actions is a diary. Every report with medium or high potential gets an owner, a due date and a status. Use a simple order of preference when choosing the fix: remove the hazard, then separate people from it, then change the way the work is done, and only then rely on a sign, protective equipment or telling people to be careful. A prompt can help the officer list options, as long as the officer chooses.

Near miss: forklift and pedestrian at a blind corner in Packing, stack of shrink-wrap blocking sight.
List five possible controls, ordered from removing the hazard to relying on people's behaviour. For each, say what it would cost me in time and roughly what kind of spend (none, low, medium, high). Do not recommend one; the safety officer will choose.

Illustrative output: relocate the stack away from the corner; mark a separate pedestrian route; fit a convex mirror; add a stop line and a horn rule at the corner; brief drivers at the next shift meeting. The officer picks, perhaps the relocation first because it is free and fast, then the marked route. Tell the person who reported it what changed. That feedback is what persuades the next worker to report.

Handling a photo report

A photo tells the safety officer more in a second than three lines of text, but an assistant that describes photos will sometimes describe the wrong thing. Treat its description as a caption suggestion to be confirmed, never as the record. A worker photographs a coil of cable across a walkway in Workshop and writes "cable, walkway". Asking the assistant to describe the image might return "an orange extension cable lying across a concrete floor near a workbench", which is correct, plus "partly under a pallet", which the worker should confirm because it changes the hazard.

This photo and caption come from a near miss report in a small factory. Describe only what is visible, in two sentences. Then list what you cannot tell from the image (for example: whether anyone was nearby, whether the cable is live, how long it had been there). Suggest one category from my list. Do not suggest causes or blame.

The "what you cannot tell" list is the useful part. It turns into the follow-up questions the officer asks the reporter, which is faster than inventing questions from scratch. Keep the original photo with the record, and never let a description replace it.

Three small factories, three different logs

A bakery with a production room

Hot trays, flour dust, wet floors and slicing blades dominate. The category list needs Fire and heat and Slips/trips/falls near the top, and "Cuts and blades" as its own line. Reports cluster at the start of the early shift and just after cleaning. A monthly review that splits by time of day shows whether the cleaning routine leaves wet floors at shift handover.

A woodworking shop

Dust, noise and machine guarding matter most. Add a "Dust and extraction" category and a "Kickback and flying material" one. A near miss that ejects a piece of timber at a bench saw is high potential even when nobody was in its path, so train people to say what the piece did, not only that no one was hurt.

A plastics moulding plant with a forklift-heavy yard

Vehicles dominate, along with hot surfaces and pinch points. Add a "Pedestrian and vehicle routes" tag to the Vehicles category, so the review can tell a blind corner problem from a driver behaviour problem. If four of seven vehicle reports share one corner, the fix is physical. If they are spread across the yard, it is more likely to be a rule or a speed problem.

The structure of the log is the same in all three. Only the category list and the review questions change, which is why you should build the list with the people who work there rather than copy one from a template.

Measuring whether the system works

Three numbers show whether the process is healthy, and none of them is the raw count of reports.

Say 14 actions are open, of which 3 are overdue: 3 divided by 14 is 21 per cent, which is high. The assistant can compute this from the log in seconds; the safety officer's job is to ask why those three are late and who can unblock them. If the same person owns all three, the problem is workload, not the log. The target of 10 per cent is an illustration, so set your own once you have three months of data.

Making people comfortable reporting

No template fixes a culture where reporting feels risky. Three practical rules help. Tell people in writing that a near miss report is never a disciplinary matter by itself. Share what was reported and fixed each month, without names. And thank the person, in person, within a day. If a worker reports their own mistake, treat it as the most useful report in the log, because it shows the system trusts them.

Be careful with anonymity. An anonymous route raises reports in some workplaces and makes follow-up impossible in all of them. If you allow it, keep the follow-up questions in the record, so the officer can still find out what happened by asking around the area.

Be careful, too, about how the assistant's summaries are shared. A monthly summary posted on the noticeboard should carry counts and fixes, not full transcripts. A transcript can identify a person through a detail, such as "the lad on the forklift", even after names are removed.

What to do when the data is thin

A ten-person factory may log only four or five near misses a month. Percentages are meaningless at that size; one report moves a category by 20 per cent. Switch to reading, not counting: the officer reads every report in the month, and the assistant's job shrinks to listing repeats and open actions. Move to quarterly trend charts, where 15 reports can show something, and ask the assistant to say plainly when the sample is too small to compare.

When the log grows, the same prompts keep working because they ask for tables and arithmetic you can check. Change the date range and nothing else. The guide to spotting patterns in complaints, returns and defects uses a similar approach for product problems, and the matching non-conformance report tutorial covers what to do when the problem is a defect rather than a hazard.

A mistake: coding the story, not the hazard

A hypothetical shop coded every near miss involving a particular press as "Machinery". The log showed twelve in a quarter, and a plan was made to review the press guarding. The assistant had not been given definitions, so it coded a dropped tool, a slippery floor beside the press and a pallet dispute as machinery because the press was named in each. The real hazards were housekeeping and handling. The fix was the definitions table above and a rule that the category follows the hazard, not the location.

The same shop made a second error: the assistant was asked what caused the events, and it offered plausible-sounding reasons that no one had said. The safety officer added a line to the prompt, "do not suggest causes", and the causes now come from interviews.

What the safety officer keeps, and what the assistant never does

• The officer decides which reports to investigate and which to close.
• The officer sets severity and confirms category.
• The officer owns the action list and the review meeting.
• The assistant never closes a report, never assigns blame and never suggests a worker was at fault.
• Anything about an injury, however small, goes into your normal incident process; the near miss log is not the place to decide whether something is reportable.

For the incident side, the workplace incident report template sets out fields and wording. For finding causes once a report is chosen for investigation, the root cause analysis prompts keep the assistant to questions rather than conclusions. If you are curious how another sector approaches the same log, the pharmacy near miss log and the construction near miss app show different capture methods.

Starting small: the first month

1. Agree the category list and definitions with the people who work on the floor.
2. Print the form on a card and put a pick-list of locations on it.
3. Choose one capture route to begin with, usually voice notes for a floor with gloves and noise.
4. Run the transcript prompt on every report and read each output against the original.
5. Hold a ten-minute review at the end of the month and publish three results: how many were reported, what changed, and what is still open.

Do not judge success by the count in month one. A new system usually collects more reports because people trust it. Judge it by whether an action has been closed, whether the same corner appears less often, and whether people mention the system without being asked. The assistant's job is to save the safety officer the sorting, so the officer's time goes on the corner, the guard and the conversation.

Near miss reporting questions from small factories

What counts as a near miss?

An event that did not injure anyone or damage anything, but could have. A pallet that slides off a forklift and lands in an empty aisle is a near miss. A tool left on a guard rail that falls beside a worker is another. If you would have written an incident report had someone stood one step closer, record it.

How do I get workers to report?

Make it fast, make it safe and show results. A form that takes a minute, no blame for the person reporting, and a visible fix within a couple of weeks matter more than any poster. Reports fall quickly when people see nothing change.

Can AI decide what caused a near miss?

No. It can sort reports into categories and spot repeats, but cause comes from the people who saw it and the safety officer who investigates. Tell the assistant to code only what is written and to flag anything vague for a human to ask about.

Is it safe to put reports into an AI tool?

Remove names and any personal or health details first, use a business plan that does not train on your content by default, and keep the original reports in your own system. Check your company policy and any rules that apply to safety records before you start.

How many near misses should we expect?

There is no universal figure. A rising count in the first months usually means people are trusting the system, not that the site has become less safe. Watch the mix of categories and the time taken to close actions rather than the raw total.

Further reads

• AI Quality Control for Small Manufacturers: Where to Start — Where small manufacturers can start with AI on quality.
• Where Should a Small Manufacturer Start With AI? — Where a small manufacturer should start with AI.
• AI Incident Response Plan for Small Businesses (With Template) — A template for responding when something goes wrong.
• How to Check AI Is Doing Good Work, Not Just Fast Work — Check that AI is doing good work, not just fast work.
• How to Write a Health and Safety Policy With AI and What to Check — Check a safety policy drafted with AI.
• AI for Industrial Manufacturing: Read Downtime Logs to Find Repeat Stops — A practical CSV walkthrough for finding repeated line stops, checking the arithmetic and choosing a maintenance action.
• Daily Production Report: Summarise Counts, Scrap and Stops With AI — Three messy shift sheets become one page: units against plan, scrap by reason, stops by cause, and the one thing the owner must act on.
• Maintenance Request Form: Triage Factory Requests by Urgency — A factory-floor maintenance request form, four urgency levels, a safety override and an AI step that tags and routes each request.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: the template and figures are illustrative; apply your own site's safety rules and ask a qualified safety adviser about your legal duties.