Recordability

Is aggravation of a pre-existing condition OSHA recordable? The significant-aggravation test (1904.5(b)(4))

A bad back, an old knee, childhood asthma — when work makes an existing condition worse, the case can absolutely land on your OSHA 300 Log. But only if the aggravation is 'significant,' and OSHA defines that with a four-outcome test, not a medical debate. Here's how to run it.

LS
LogStead Team
OSHA Recordkeeping
11 min read

An employee with a documented degenerative disc condition lifts a pallet jack handle and feels the familiar pain flare — except this time it doesn't fade by morning, and the doctor writes a prescription and two weeks of lifting restrictions. Another employee with an old high-school knee injury kneels on a concrete floor all shift, goes home sore, ices it overnight, and is fine by Monday. Both had a pre-existing condition. Both got worse at work. Only one belongs on your OSHA 300 Log.

"It was pre-existing" might be the single most common reason employers give for leaving a case off the log — and it is one of the least reliable. Under 29 CFR Part 1904, a pre-existing condition is not a shield. Work-relatedness explicitly includes the situation where an event or exposure in the work environment significantly aggravated something the employee already had. The good news for the person keeping the log: OSHA did not leave "significantly" to argument. It wrote a four-outcome test that you can run with facts you already collect. This post walks through that test, the traps on either side of it, and the scenarios where employers most often get it wrong.

Aggravation is written into the work-relatedness rule itself

The basic work-relatedness requirement, 29 CFR 1904.5(a), reads:

"You must consider an injury or illness to be work-related if an event or exposure in the work environment either caused or contributed to the resulting condition or significantly aggravated a pre-existing injury or illness."

That sentence is the whole ballgame. Aggravation is not an edge case bolted onto the rule — it is one of the three ways a case becomes work-related, sitting right next to "caused" and "contributed to." If an event at work significantly aggravates a pre-existing condition, the case is work-related, and from there it runs through the same general recording criteria as any other injury: death, days away, restricted work or job transfer, medical treatment beyond first aid, loss of consciousness, or a significant diagnosed injury or illness.

Two definitions frame the test. First, what counts as pre-existing: under 1904.5(b)(5), an injury or illness is a pre-existing condition only if it "resulted solely from a non-work-related event or exposure that occurred outside the work environment." The torn rotator cuff from weekend softball qualifies. A back strain from last year's shift on the loading dock does not — that was work-related to begin with, and if it flares up again the question becomes whether you have a new case, which is a different rule (more on that below).

Second, what makes an aggravation significant. That's 1904.5(b)(4), and it deserves its own section.

The four-outcome test: 1904.5(b)(4)

A pre-existing injury or illness has been significantly aggravated, for recordkeeping purposes, when an event or exposure in the work environment results in any of the following:

  1. Death — provided the pre-existing condition would likely not have resulted in death but for the workplace event or exposure.
  2. Loss of consciousness — same qualifier: the pre-existing condition alone would likely not have caused it.
  3. One or more days away from work, days of restricted work, or days of job transfer that otherwise would not have occurred but for the workplace event or exposure.
  4. Medical treatment in a case where no medical treatment was needed for the condition before the workplace event or exposure — or a change in medical treatment necessitated by the workplace event.

Notice what this test is made of: outcomes, not medical philosophy. You are not being asked to apportion causation percentages between the old condition and the new event, or to litigate whether the disc was going to herniate eventually anyway. You are being asked four concrete questions about what happened after the workplace event that wasn't happening before it. Did the employee lose days, get restricted, start treatment, or have their existing treatment changed — because of what happened at work? The comparison baseline is the employee's own condition the day before the event.

The fourth outcome is the one that does the most work in practice, and its second clause is the one employers miss: a change in medical treatment counts. An employee whose pre-existing condition was already being treated — the asthmatic with a maintenance inhaler, the back patient on a standing physical-therapy plan — is significantly aggravated the moment a workplace exposure forces that treatment to change: a new prescription, an increased dose, an added therapy, a referral to a specialist. "They were already seeing a doctor for it" is not the exemption people think it is. The question is whether work changed what the doctor had to do.

The baseline is the employee, not a healthy employee

Run the four outcomes against this employee's actual pre-event condition. If they could work full duty with their bad knee before Tuesday, and after Tuesday's event they can't — that's outcome 3, regardless of how fragile the knee already was. The rule's "but for" language does the apportionment for you: you're only counting consequences that would not have occurred without the workplace event.

The flip side matters just as much. An aggravation that produces none of the four outcomes is not significant, and the case is not recordable — even though the employee genuinely hurt more at work. The employee who kneels all shift on an old knee injury, self-treats with ice, and returns to full duty had a real aggravation with a first-aid-level outcome. Ice packs, over-the-counter medication at over-the-counter doses, and the rest of the first-aid list don't constitute medical treatment — that's the same first-aid vs. medical treatment line that decides ordinary recordability, and it applies to aggravations with full force. Soreness that resolves with first aid and costs no work time fails all four outcomes. Not recordable.

"But work was only part of the cause" — the causation standard

Here is where employers most often talk themselves out of a recordable case. The reasoning goes: the disc was degenerating for a decade; the lift at work was maybe ten percent of the story; surely a ten-percent cause isn't "significant."

OSHA has rejected that reasoning explicitly. In a January 13, 2004 interpretation letter, the agency explained that a case is presumed work-related if an event or exposure in the work environment is a discernable cause of the injury or of a significant aggravation — and that the work event "need only be one of the discernable causes; it need not be the sole or predominant cause." The word significantly in 1904.5(b)(4) modifies the aggravation's consequences — the four outcomes — not the size of work's share of the blame. A minor-seeming workplace event that tips a fragile condition into prescription treatment or lost days is a significant aggravation, full stop.

A February 28, 2014 interpretation letter pushes the point further in a direction that surprises people: even normal body movements at work — walking, bending, climbing stairs — count as "events" that trigger the work-relatedness presumption. In that letter, an employee's knee gave out while climbing stairs at work; one physician later opined the injury was non-occupational because there was no forceful mechanism. OSHA's answer: climbing the stairs was the event, the presumption applied, and the case was recordable. The same letter is a useful reminder about dueling medical opinions — when health-care professionals disagree, the employer must make the call based on the most authoritative evidence: best documented, best reasoned, most persuasive. You cannot simply shop for the opinion that says "pre-existing" and file the case away.

Workers' comp logic does not transfer

Many state comp systems do apportion causation between the pre-existing condition and the work event, and a comp carrier may deny a claim precisely because the condition was mostly pre-existing. None of that moves the OSHA determination — the two systems ask different questions, and a comp denial does not take a case off your 300 Log. Run 1904.5(b)(4) on the outcomes and record accordingly, whatever the carrier decides.

The one true escape hatch: symptoms that merely surface at work

There is a legitimate exemption sitting next to the aggravation rule, and keeping the two straight is most of the job. Under 1904.5(b)(2)(ii), an injury or illness is not work-related if it "involves signs or symptoms that surface at work but result solely from a non-work-related event or exposure that occurs outside the work environment."

The operative word is solely. The employee who wrenched their shoulder in a weekend softball game and feels it stiffen while sitting in Monday's staff meeting has a non-work-related case — nothing at work did anything; the workplace was just where the symptom clock happened to strike. But change the facts slightly — the sore shoulder gets re-injured hoisting a case of product onto a shelf — and you've left the exemption entirely. Now a work event contributed, the exemption's "solely" is broken, and you're back in the four-outcome aggravation test.

In practice the distinction turns on one investigative question: did anything happen at work? An event, an exposure, a task, a movement — however ordinary. If yes, the (b)(2)(ii) exemption is off the table and 1904.5(b)(4) decides the case. If truly nothing happened at work beyond the passage of time, the case stays off the log no matter how dramatically the symptoms surfaced there.

Aggravation or new case? Where 1904.6 takes over

One more boundary. Everything above concerns a condition that was never work-related — softball shoulders and childhood asthma. When the "pre-existing" condition is actually a previously recorded work-related case that flares up again, you've left 1904.5(b)(4) and entered the new-case rule, 29 CFR 1904.6.

The short version: it's a new case (a second log entry) only if the employee had completely recovered from the earlier one — all signs and symptoms gone — and a new workplace event or exposure brought them back. If the original case never fully resolved and the same injury is simply continuing or worsening, you generally update the original entry rather than record a duplicate — the classification, day counts, and outcome on the existing line change instead. (Chronic occupational illnesses like silicosis are recorded once, ever; recurring acute conditions like occupational asthma episodes triggered by new exposures are recorded each time.) If the flare-up changes the case's day counts, remember those counts follow the same counting rules as any other entry, including the update duty on the stored log.

Four scenarios, worked

The degenerative disc and the pallet jack. Documented degenerative disc disease, never work-related, managed without treatment. A lift at work triggers pain that leads to a prescription anti-inflammatory and a two-week, 20-pound lifting restriction. Work event? Yes. Outcomes: medical treatment where none existed before, plus restricted days. Recordable — classify as restricted work, count the days.

The old knee and the concrete floor. High-school ACL tear, fully healed years ago. A shift of kneeling leaves the knee swollen; the employee ices it overnight, takes OTC ibuprofen at the label dose, and works full duty the next day. Work event? Yes — kneeling counts. Outcomes: none of the four (first aid only, no lost or restricted time). Not recordable. Document why and keep the note.

The asthmatic and the cleaning-chemical mix-up. An employee with lifelong asthma, controlled on a maintenance inhaler, is exposed to fumes from an improper chemical mix and needs a new rescue prescription plus a changed maintenance dose. Work exposure? Yes. Outcome 4's second clause — a change in medical treatment — is squarely met. Recordable, as an illness (respiratory condition), even though the employee "already had asthma and was already being treated."

The softball shoulder in the staff meeting. Weekend injury; the shoulder stiffens Monday while the employee sits at a desk. No event, task, or exposure at work played any role. 1904.5(b)(2)(ii): signs and symptoms surfacing at work from a solely non-work cause. Not work-related, not recordable — and worth a one-line memo saying exactly that.

Write the determination down while the facts are fresh

Aggravation cases age badly. Two years from now, the log line (or its absence) will be all that's left unless you documented the reasoning: what the pre-existing condition was, what happened at work, and which of the four outcomes did or didn't follow. "Not recorded — pre-existing knee condition, aggravation resolved with first aid, no lost/restricted time, no treatment change; 1904.5(b)(4) outcomes not met" is one sentence, and it is the difference between a defensible determination and a shrug during an audit or inspection.

LogStead builds that discipline in. The recordability wizard walks every case through the 1904.5 work-relatedness test — including the significant-aggravation outcomes — and the general recording criteria in a fixed order, then saves the reasoning behind each answer alongside the case, so the "why" survives as long as the log does. Recordable aggravations flow onto the right establishment's 300 Log with their day counts feeding the 300A totals automatically. You can pressure-test a live case right now with the free recordability checker — no account needed.

When in doubt

If a workplace event touched a pre-existing condition at all, don't reach for "it was pre-existing" — reach for the four outcomes. Death, loss of consciousness, lost/restricted/transfer days, new or changed medical treatment: any one of them, traceable to the work event, makes the case recordable. If none occurred, it isn't — and a dated note saying so is worth more than the instinct ever will be.

Ready to simplify compliance?

LogStead determines recordability, generates your 300, 300A, and 301 forms, and keeps your records accurate and audit-ready. Try it free for 14 days.

Get Started for Free