How to log and investigate near misses
A near miss is a free lesson: something that could have hurt someone and did not. Sync logs near misses, accidents and incidents on the same form, tells your health and safety team straight away, and keeps the record attached to the job it happened on.
- Who uses it
- Anyone on site, plus the H&S team who pick it up.
- Where it lives
- Health & Safety, then Create H&S report.
- What it covers
- Near misses, accidents and incidents, on one form.
- Who hears about it
- Your H&S users, automatically, as soon as it is saved.
Before you start
Logging one takes two or three minutes. It is worth doing while it is fresh, so have this to hand:
- You know which project it happened on.
- You have the date and the time, not just the day.
- You know who is reporting it, and who saw it.
- You have any photos to hand, taken at the time if possible.
Start a report
Open Health & Safety in the sidebar. The quick actions at the top include Create H&S report and Log a near miss, which is the same form with the type already set.
The form runs in three steps: report details, description, then additional details.
Choose the type
One form covers three kinds of event, chosen in Type.
Something that could have caused harm but did not. The ones worth logging most, because they are free lessons.
Someone was hurt. Record it here, and remember this does not replace your RIDDOR obligations.
Damage, loss or a dangerous occurrence without injury, such as plant damage or a dropped load.
The type also drives the reference: a near miss is saved as NMR, so you can tell what a report is from its number alone.
Fill in the report details
The left-hand panel is who, what and when.
Generated for you, prefixed by the report type, so a near miss reads NMR00004.
Required. It is what ties the report to a job and makes the analysis charts work.
Required, and it takes a time as well as a date. Record when it happened, not when you got round to logging it.
Required. Who is making the report.
Optional, but worth filling in while people still remember.
Set the location
The right-hand panel takes the address where it happened: Address 1, Town/City, County and Postcode are all required.
On a large site, use Address 2 for the part of it that matters, the plot, the block, the level. "Second lift, east elevation" is more use to an investigator than a postcode.
Describe what happened
Step two opens with Description, which is required. Write what happened, in order, in plain language.
Describe the event and the conditions, not the person. "Board was not secured and was dislodged by wind" tells you what to fix. "Scaffolder was careless" does not, and makes the next person think twice about reporting anything at all.
Attach photos or video
Beside the description sits Photos / Videos, which takes files by drag and drop.
Photographs taken before anything is moved are the single most useful thing on a report. If the scene has already been made safe, say so in the description.
Check who gets notified
Underneath, Sync lists your Health & Safety users (notified automatically). They are told as soon as the report is saved, without anyone having to remember to forward it.
Notify additional users copies in anyone else: the contracts manager, the project lead, whoever needs to know on this particular job.
Record any resolutions
The last step asks Any resolutions? Use it for what was done at the time: the area was closed off, the board was re-secured, the machine was taken out of service.
It can be left empty and filled in later, but a line here is what separates a report that led to something from one that just got filed.
Save the report
Choose Save Report. Sync confirms it has been created, opens the record, and the notifications go out.
If the form will not move on, a required field is outlined in red further up. The date is the usual one, because it has to be picked from the calendar.
Read the report record
The record shows the details, the description and the resolutions side by side, with the status, reference, date and time, project, location, whether it was reported to a manager, who reported it and any witnesses.
Three actions sit at the top: Edit report, Update status and Create investigation.
Wakefield
West Yorkshire, WF1 2DP
Scaffold board left unsecured on the second lift was dislodged by wind and fell to the exclusion zone below. No one was in the area at the time. Work in the bay stopped and the lift was re-checked before anyone went back up.
Boards re-secured and the lift re-inspected by the scaffold contractor the same morning. Toolbox talk on securing materials at height scheduled for the Monday briefing.
Open or archived
A report has two statuses, and only two: Open and Archived. New reports are Open.
Archive it when it is genuinely closed out, not to tidy the list. Open reports are what the dashboard counts, so an archived one that was never resolved is a lesson quietly thrown away.
Create an investigation
Where something deserves a proper look, Create investigation opens a linked form. It carries the report's reference, type, date and location across, and asks for:
- Conclusions, what you found.
- Learning points and recommendations, what changes as a result.
- An investigation report and supporting files, if you have produced one.
Save and link investigation attaches it to the report, so the event and what you concluded about it stay together.
Find reports later
The Reports module under Health & Safety lists every report across every project, filtered by status, reference, project name, who reported it, type or date.
This is what you open when an auditor asks what happened on a job, or when you want to know whether this is the third time something similar has been logged.
Read the near miss analysis
The Health & Safety page has a Near miss analysis tab with a date range and four views.
The split between open and archived reports in your date range.
Which jobs are generating reports, and whether the trend is moving.
Report count against the hours logged on each project.
Density rather than raw count, so a big busy site is not unfairly flagged against a small quiet one.
What you can and cannot do
- Log a near miss, accident or incident from the same form.
- Record the date and time, the people involved and the exact location.
- Attach photos or video taken at the scene.
- Notify extra people beyond the H&S team who are told automatically.
- Record what was done about it in Resolutions.
- Escalate a report into a linked investigation with conclusions and learning points.
- Filter every report by project, type, status or who reported it.
- Pick a status other than Open or Archived. There is no in-between state on a report.
- Log a report without a project. It is what connects the report to a job and to the analysis.
- Rely on this for RIDDOR. Sync records what happened; reporting it to the HSE where required is still your duty.
- Manage audit corrective actions here. Those sit with audits, not with reports.
Common issues
A required field is empty and will be outlined in red, usually the date. Every field marked with an asterisk has to be filled before the form will move on.
Users with the health and safety role are notified automatically and are listed on the description step. Anyone else has to be added under Notify additional users before you save.
That is what Open means. Use Resolutions to record what was done, and Create investigation where it warrants a proper look. Archive it once it is genuinely closed out.
Check the date range at the top of the Health & Safety page, and that the report has a project against it. The density chart also needs projects with at least 50 hours logged.
Site managers have a cut-down version of this form built for on-site use. See the site manager guide.
Good report checklist
A report worth reading in six months has:
- The right type is selected: near miss, accident or incident.
- The project is right, because the analysis depends on it.
- The date and time are when it happened.
- The description says what happened, not who is to blame.
- Photos are attached while the scene is still as it was.
- Witnesses are named while they still remember.
- Resolutions record what was actually done about it.
Summary
To log and investigate a near miss in Sync:
- 1Open Health & Safety and choose Create H&S report, or Log a near miss.
- 2Pick the type, the project and the date and time it happened.
- 3Describe it plainly, attach photos, and check who is being notified.
- 4Record any resolutions, then save it.
- 5Work the report: resolve it, escalate it to an investigation, archive it when closed.
- 6Use the near miss analysis to see the pattern rather than the one-offs.
The hard part of near miss reporting was never the form, it was getting people to bother. Making it quick, telling the right people automatically and showing the pattern back to the site is what turns a pile of reports into fewer accidents.