The Tech Who Would Not Report the Back Injury

Why this matters

The injury report arrived on a Wednesday, filed from an urgent-care waiting room. By then the injury was six weeks old, the tech could not stand up straight, and the workers' comp carrier's first question was why nobody had said anything for six weeks. The owner's first reaction was that the tech had hidden it. That was true, and it was also useless, because it explained nothing the shop could change. This case reconstructs what happened from the shop's own records, after the fact, the way an owner would have to do it, and the gaps in those records turn out to be as much of the finding as the injury.

The record, as reconstructed

A residential HVAC shop, 14 techs. Tech Ray, eleven years in the trade, three with this shop, one of its best. The owner pulled everything with Ray's name on it from the six weeks before the report: job notes, dispatch logs, timesheets, callbacks, and, with Ray's permission, a few texts to coworkers. Laid end to end:

FROM THE RECORD - Ray, lower back
Wk 0 Thu  job note: "condenser set, solo -
          helper pulled to no-heat call"
Wk 1 Mon  text to coworker: "back is cooked, can
          you take the attic one at 2?"
Wk 1-5    avg time on site 1.6 h -> 2.1 h
          calls per week 22 -> 17
Wk 2 Mon  called out sick, no reason given
Wk 3 Wed  callback: unit panel left off, ladder job
Wk 4 Mon  called out sick, no reason given
Wk 5      swapped 4 attic calls with coworkers
Wk 6 Tue  could not stand out of the van; urgent care
Wk 6 Wed  first injury report filed

From Thursday of week 0 to Wednesday of week 6 is 41 days. For 41 days, every signal of an injured back was in the shop's own systems, and nobody read them as one.

What each piece said, read in the order it was written

The job note. "Condenser set, solo." A condenser is commonly 100 lb or more and is a two-person lift in this shop's own practice. The helper had been pulled to a no-heat call, and Ray set it alone rather than reschedule. This is the probable injury event, and the shop only knows it because Ray happened to write "solo." There was no field anywhere for "lifted alone" or "this hurt," so if he had written the usual "condenser set," the event would be invisible.

The text on Monday of week 1. "Back is cooked." This is a direct report of injury, made to a coworker instead of to the shop. The coworker took the attic call and said nothing; asked later, he said Ray asked him not to make a thing of it. That is the culture in one exchange: the pain was reported, and the report went sideways instead of up.

The productivity numbers. Time on site rose from 1.6 hours to 2.1 hours per call, an increase of 0.5 hours, or about 31 percent of the 1.6-hour baseline. Calls per week fell from 22 to 17, 5 fewer, about 23 percent. Dispatch noticed the slower calls and put it down to a run of harder jobs. Nobody checked whether the jobs were actually harder. They were not: Ray's job mix in weeks 1 to 5 was the same blend of maintenance and repair as the five weeks before.

The two Monday call-outs. Weeks 2 and 4. The shop's attendance practice did not ask a reason and did not track patterns. Two Mondays out of five, from a tech who had missed perhaps two days in the prior year, is a pattern worth a private conversation, and a sibling card covers having it (see related). Ray said later that the weekend was when his back stiffened, and Monday mornings were the worst.

The callback. In week 3, a customer called because the unit's access panel had been left off after a repair on a call that involved a ladder. Ray's first callback in months. A tech in pain cuts the step that requires one more awkward bend. The callback was logged as a quality miss and discussed with Ray as one.

The swapped attic calls. Four in week 5, arranged directly between techs. Dispatch saw the swaps and approved them, because swaps between techs were routine. Nobody asked why the same tech was giving away attic calls.

The report. In week 6, Ray could not get out of the van at a customer's house. A coworker drove him to urgent care, and the injury report was filed the next day.

Why nobody connected it

Every piece was seen by someone. The coworker had the text. Dispatch had the times, the counts and the swaps. The service manager had the callback. The office had the call-outs. Nobody had all of them, and no single piece crossed a threshold that anyone had set. The shop was not short of information; it had no place where information about one person's body came together, and no one whose job it was to look.

The other half is why Ray did not say anything. He said three things when the owner asked him, later, in a conversation that was not about blame:

• He thought it would settle down in a few days, as minor tweaks had before. Most low-back strains do improve within weeks, which made this a reasonable bet in week 1 and an unreasonable one by week 3.
• He did not want to be the senior guy who got hurt doing a lift he knew was a two-person job.
• He had once heard the owner say, about a former employee's claim, "every time somebody gets a little sore it's a comp claim." Years earlier. He remembered it word for word.

That last one is the finding the owner least wanted. The language card covers how a single remark like that keeps a crew quiet for years (see related).

What the delay cost

Recovery. The treating physician noted that six weeks of working on the injury, including the attic crawling and the ladder work, had likely made it worse than it would have been with early care and modified duty. Ray was off work entirely for seven weeks, then on restrictions for four more. Nobody can say exactly what an early report would have changed, but the doctor's view was that a strain treated in week 1 commonly returns to full work in a few weeks.

The claim. Workers' compensation notice deadlines are set by state law. Many states require the employee to notify the employer within a set window, commonly 30 days in a number of states and shorter in some, and Ray's report came at day 41. Many states also excuse late notice where the employer had actual knowledge of the injury or was not prejudiced by the delay, and whether a coworker's knowledge counts as the employer's is exactly the kind of fact-specific question the carrier and, if it is disputed, an attorney will argue over. The carrier opened the claim with a causation question: with a six-week gap, how do we know this happened at work? The "solo" job note and the week-1 text ended up being the evidence that it did. This is not legal advice; the carrier and the tech's own counsel, if he retains one, handle those questions, and the shop's job is to report promptly and hand over the record.

The federal recordkeeping layer. If the shop keeps an OSHA 300 log (most construction-sector employers with more than 10 employees must, under 29 CFR Part 1904), a recordable injury goes on the log within seven calendar days of the employer receiving information that it occurred (29 CFR 1904.29(b)(3)). The question of when the employer "received information" now had a messy answer. The same Part requires employers to have a reasonable procedure for reporting injuries that does not deter reporting, and to tell employees they have the right to report without retaliation (29 CFR 1904.35). A procedure that nobody uses because of how the owner talks about claims fails the spirit of that rule, whatever the binder says.

What the shop changed so the next one reports on day one

A discomfort report, separate from an injury report. The shop adopted an early-discomfort report with its own SOP (see related): a two-minute, no-claim, no-blame note that something hurts, filed with the service manager. It deliberately does not start a claim. It starts a look at the work: a two-person lift rule, a lighter week, a referral if it does not clear. The owner's view was that Ray would have filed one in week 1 if it had existed and had not sounded like a comp claim.

A "lifted solo" field on the job note. Any two-person lift done alone is now a field, not a word someone might happen to write. Dispatch reviews it weekly. Two in a week for one tech gets a conversation; a helper pulled away mid-job gets a reschedule instead of a solo lift, by standing rule.

One person who looks at the whole picture. The service manager now does a 15-minute weekly look across every tech for three signals together: time on site up more than 20 percent against their own prior four weeks, a call-type the tech keeps swapping away, and absences. Any two together prompt a private check-in. Run against Ray's record, that review would have flagged him in week 2, when the time-on-site rise and the first call-out first landed together.

The owner's sentence. The owner told the crew directly, at a huddle, that he had once said something about comp claims that he was wrong to say, that reporting pain early is what he wants, and that the discomfort report exists so nobody has to decide whether something is "bad enough." That took about a minute and was, by the crew's later account, the change that mattered most.

What changed in the numbers. In the year after, the shop logged 11 discomfort reports. Two became injury reports, both filed within a day of the event. The other nine cleared with a work change and no lost time.

References

• OSHA 29 CFR Part 1904, including 1904.29 (forms and timing) and 1904.35 (employee involvement and reporting procedures)
• Your state workers' compensation agency, on employee notice deadlines and late-notice rules
• See related: The Early Discomfort Report SOP
• See related: The Language That Keeps People Quiet About Pain
• See related: A Strong Tech Keeps Calling In on Mondays