Reports & Data

The incident data is the feedback loop: the incident report with the 5-Why and the RIDDOR check, the near-miss register with the trend that predicts the incidents, and the incident data analysis in Power BI — the guide, the KPIs (the TRIR, the LTIR, the near-miss ratio), the DAX, and the live demo chart with the sample dataset. The three tools together are the reporting system: the event is recorded, the cause is found, and the trend is read.

The report without the cause is the paper; the cause without the action is the opinion; the action without the trend is the one-off. The incident report is where the 5-Why takes the event from the pedestrian in the path to the change control that does not cover layout — the fix is at the bottom of the five, not the top. The near-miss register is the leading indicator: the four slips at the same patch are one problem, and the drain is the action, and the ratio of the near misses to the recordables is the number the management review reads first. The Power BI incident report is where the two meet the directors: the TRIR and the LTIR on the line, the by-type bar, the KPI cards against the targets, the refresh scheduled and the email on the Monday. Build the three in that order, and the reporting system is the one that predicts the incident instead of describing it.

Every tool in this category works the same way: it runs in your browser, it scores or checks as you go, nothing is uploaded, and it prints as a signed, dated document you can file. The professional version — the sign-off, the audit, the training — runs through umer-hse.pro.

The report is the moment the site stops hiding from what happened. The UK law is the Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 2013, and the deadlines are short and specific: deaths, dangerous occurrences and specified injuries within 15 days to the HSE; an incapacitation of more than seven days within seven days; a work-related disease within 14 days. The OSHA side runs on its own clock — a workplace death reported within eight hours, a hospitalisation, amputation or loss of an eye within 24 hours, and the annual 300A summary posted for a set window each spring. The internal report, the one to the supervisor and the file, has no legal deadline and a bigger importance: it is the record that the site learned from the event.

The mistake that costs sites is the report that dies in the pocket. The near miss that was not written. The injury that was reported as a warning. The incident that was "not reportable" because nobody decided it was. The system that holds is the short one: the event is reported the same shift, the first facts are recorded while they are fresh, the report is reviewed at the next toolbox, and the action is closed with a date and a name. The RIDDOR is the tip of the iceberg — the site that reports only what is legally required is reporting only what it has already failed on.

The tools in this section take the incident from the moment to the record: the incident report that holds the facts, the investigation that finds the cause and not the culprit, and the analysis that turns the year of incidents into the three or four that matter. The reporting duty is in the Resources, the templates are there too, and the audit of the reporting system itself runs through umer-hse.pro.

• RIDDOR: the death, the dangerous occurrence and the specified injury within 15 days; the over-seven-day incapacitation within seven; the disease within 14
• OSHA: the workplace death within eight hours, the hospitalisation or the amputation within 24
• The near miss is the free lesson — report it before it finds a person
• The finding needs the owner, the action, the date and the verification — the loop that closes