Premium gets the attention. It arrives with the renewal, it has a dollar sign on it, and leadership asks about it. But premium is a lag measure. It reflects claims from years ago, run through a rating formula nobody in your building controls. The report lag column reflects what your people did last month, and it moves the moment they start doing something different.
What the gap between two dates actually measures
Report lag looks like a paperwork number. It is not. When an injury reaches the claims process a week late, something happened during that week. The employee told a supervisor who waited to see if it got better. Or the employee told no one, because the last person who reported an injury got a hard time for it. Or the supervisor passed it to someone who did not know where it went next.
Every one of those is a decision made by a person on the floor, and every one of them lands in the lag column. That is why the way your reporting system works in practice says more about your safety culture than any poster on the wall.
The cost is not small. In Liberty Mutual’s national account data, claims reported 8 to 14 days after the injury already cost 21 percent more and were 26 percent more likely to be litigated than claims reported within 3 days. In NCCI’s study of 44 states, attorneys were involved in 13 percent of claims reported immediately and 32 percent of those reported after four weeks. NCCI is careful to call that a relationship rather than proof of cause, and it is still the pattern you would expect. The longer an injured employee waits with nobody calling, the more likely they are to call someone else.
Why the average hides the problem
If you compute one lag number for the whole company, it will probably look acceptable. That is the trap. An average of 3 days can mean every location reports in 3 days. It can also mean four locations report the same day and one location reports in two weeks.
Those are two very different programs. The first is a system. The second is a few good supervisors carrying a process that only exists where they happen to work.
So sort the column. Group the claims by location, then by department or shift, then by the supervisor who took the report if your data has it. Look at the spread, not the average. Variation is the signal.
The standard to hold it to
Liberty Mutual’s 80 percent within 3 days is a reasonable outside benchmark. Our own standard is tighter: every injury reported within 24 hours, from every location. That is an Amaxx standard, not an industry figure, and we hold to it for a simple reason. The first day after an injury is when the employee decides whether the company is on their side. A report that reaches the right person that day means someone can call the employee that day.
Count your claims reported after 24 hours. Then count how many of those came from the same two or three places. In most programs the late reports cluster, and that cluster is the part of your program that runs on whoever happens to be there.
Is your program actually under control?
Simple to define, hard to run the same way everywhere
Nobody disagrees with “report injuries right away.” It is in the handbook, it came up in the last safety meeting, and every supervisor would tell you they do it. That is exactly why the lag column matters. It does not record what people say they do. It records what they did.
The fix is not another reminder. It is a defined injury response process that every supervisor runs the same way, one owner who checks the lag on every new claim, and a weekly look at which locations missed the standard and why. When a late report gets looked at within days, it stops being invisible, and it gets fixed while the supervisor still remembers what happened.
That is the difference between having a reporting policy and having control of reporting. One is written down. The other is measured every week, at every location, alongside the other measures that show whether a program is working.
What to check this week
- Pull your loss run for the last 12 months.
- For each claim, subtract the injury date from the report date.
- Work out the share reported within 3 days, and compare it with the 80 percent benchmark.
- Count the claims reported after 24 hours, and group them by location and supervisor.
- Take the three slowest locations and ask one question: when an injury happens there, what actually happens in the first hour?
If the answer depends on who is on shift, the program is not under control yet. The good news is that this is one of the fastest measures to move, because it changes as soon as the behavior does.
Contact: mstack@reduceyourworkerscomp.com
©2008–2026 Amaxx LLC. All Rights Reserved under International Copyright Law
Do not use this information without independent verification. All state laws vary. You should consult with your insurance broker, attorney, or qualified professional.
