The Early Discomfort Report SOP

Purpose

This procedure turns "my wrist's been a bit sore" from a remark at the truck into a dated record, a task review within two working days, a written change to the work, and two follow-ups. It guarantees that discomfort gets handled while it is still a task problem, which is cheap, instead of when it has become a claim, a lost tech, or a run of shortcut callbacks. It also guarantees the opposite case gets caught: discomfort that is actually an injury leaves this procedure the same day and goes to the injury process.

Without it, the pattern is familiar. A tech mentions soreness once, nobody writes it down, nothing about the work changes, and eight months later the same tech reports a disabling injury with no record that anyone was told.

Scope

Covers: aches, stiffness, or soreness in a body part that the employee connects to work, that came on gradually, with no specific event and no red-flag symptom. Any employee: techs, helpers, dispatchers, office staff.

Does not cover:

• Any discomfort with a specific moment (a pop, a slip, a lift that went wrong) or any red-flag answer at step 2. That goes to The Injury and Near-Miss Reporting SOP the same day.
• Illness, fever, or contagion. That goes to The Sick Tech Policy SOP.
• Formal restrictions from a clinician. Those go to The Modified Duty Assignment SOP.
• Why strain builds the way it does. See related: How Cumulative Strain Injuries Actually Develop.

Roles and responsibilities

The receiver is whoever hears it first. A tech who tells a coworker and not a lead has not reported, so leads ask "did you tell me or just tell him?" and log it on the spot.

Procedure

Step 1. Take the report the same day it is mentioned. The receiver logs six fields: body part and side, when it shows up (start of day, after a certain task, at night), the task the employee links it to, how long it has been going on in days, a 0 to 10 rating right now, and the date. Acceptance: all six fields filled and the entry exists before the end of the shift it was mentioned in. Wrong looks like a passing remark ("back's a little tight") that never becomes an entry, or a rating left blank because "he said it was nothing". Stop rule: if the employee declines to give a rating, log "declined" and continue; a blank field is a defect, a declined one is a record. Hazard: none at this step itself, but if the employee mentions numbness or weakness while mid-task, they stop that task before the conversation continues, because step 2 may pull them off it.

Step 2. Run the red-flag screen. Ask each question and log yes or no: was there a specific moment it started? Any numbness, tingling, or weakness? Pain that wakes you at night or does not ease with rest? Swelling, heat, or a visible change in shape? Pain running down an arm or a leg? Acceptance: five answers logged, all no, and the procedure continues here. Wrong looks like the receiver skipping the screen because the rating is low; a 2 out of 10 with tingling in the fingers is a nerve symptom, not a mild ache. Stop rule: any yes ends this procedure and opens the injury SOP the same day, with this entry attached as its first document. Hazard, emergency half: back pain together with numbness in the groin or inner thighs, or new trouble controlling bladder or bowel, is a same-day emergency room visit, not a report; chest, jaw, or left-arm pain is a 911 call and the employee does not drive themselves. An employee with numbness or weakness in a hand does not finish a powered-tool cut or a ladder climb before the injury process runs.

Step 3. Review the task within two working days. The owner rides along for a half day or reviews the employee's last two weeks of jobs in the schedule, and names the one to three tasks that load the reported body part, with an estimate of hours per week on each and the tools used. Acceptance: tasks named, each with an hours-per-week figure, written into the entry within two working days of the report. Wrong looks like a review that concludes "lift with your legs" or "be more careful"; that is advice to the person, and this step reviews the work. Stop rule: if two working days pass without a review, the entry flags red on the owner's list and the receiver tells the owner directly; a review done late is still done, and the late date is recorded rather than backdated. Hazard: the reviewer on a ride-along enters attics, crawlspaces, and roofs under the same PPE and fall protection the tech uses; a reviewer who skips them is a second exposure, not an observer.

Step 4. Make one written adjustment that cuts exposure to the named task. Choose at least one: a different tool, a two-person rule for the lift, rotating the task across the crew, a route mix with fewer of that job type, a change to how the van is loaded. Acceptance: the change is written with a start date and an expected cut of at least a quarter in the weekly hours on the named task, stated as before and after. Wrong looks like an adjustment that is really a penalty, fewer billable jobs or a pay cut for reporting; that teaches the crew to stop reporting and can be retaliation under OSHA's recordkeeping rule at 29 CFR 1904.35(b)(1)(iv) and Section 11(c) of the OSH Act, which protect the right to report work-related injuries and illnesses. Stop rule: if no change can cut the exposure by a quarter without a clinician's input, the owner suggests the employee see one and the procedure continues with the best available change. Hazard: a new tool or lift aid gets a first-use walkthrough on site, because the first use of an unfamiliar hand truck on stairs or a powered driver at a new torque setting is where the next strain or pinch happens.

Step 5. Follow up at 7 and 14 days. The owner asks for a fresh 0 to 10 rating and re-runs the five red-flag questions from step 2 at each follow-up, and checks the adjustment is actually in use. Acceptance at day 14: rating down at least 2 points from the report, or at 2 or below, and five no answers at both checks. Wrong looks like a follow-up done by text with "all good?" and a thumbs-up, which re-runs nothing. Stop rule: any red-flag yes at either check, or a rating that is the same or worse at day 14, ends this procedure and opens the injury SOP the same day, with a suggestion to see a clinician. This is the step that fails when the discomfort was an injury all along, and it fails by design: the screen is repeated because nerve symptoms often arrive after the ache does. Hazard: none at this step, it is a conversation; but a yes to weakness or numbness takes the employee off ladders, roofs, and powered cutting until the injury process clears them.

Step 6. Close the entry and check for a pattern. Close when the rating has held at 2 or below for a week. Record whether the adjustment stays or is retired, and why. Then check the log: two or more reports on the same task from different employees within 90 days makes the adjustment the standard for everyone who does that task. Acceptance: closed entry with an end date, the adjustment's fate, and the pattern check result written down. Wrong looks like an entry left open forever or closed with no decision about the change. Stop rule: if the employee reports the same body part again within 90 days of closing, reopen the same entry rather than starting a new one, so the history reads as one story. Hazard: none at this step, it is a decision made at a desk.

The record this produces

One log entry per report, kept in the shop's employee-safety log (a form in the field app, a shared sheet, or the injury SOP's own log with a "discomfort" type). It holds the six report fields, five screen answers with the date of each screen, the task review with hours per week, the adjustment with before and after hours, two follow-up ratings, and the close.

Who reads it later: the owner, monthly, for patterns; the injury SOP owner if a stop rule fires; and, if a claim follows, the workers' compensation insurer. In some states an employee's report of symptoms counts as notice of a work injury and starts the clock on the employer's own reporting duty, and the deadlines for both vary by state, so a dated entry protects the employee and the shop. Ask your carrier how they want it delivered.

Whether any of this goes on an OSHA 300 log depends on 29 CFR 1904.7: a report by itself is not recordable, but medical treatment beyond first aid or a restriction that removes a routine job function because of a work-related injury can be. Employers with ten or fewer employees during the previous calendar year are partially exempt from keeping the log under 1904.1, though not from reporting a fatality or serious injury under 1904.39. Keep the medical details in this log apart from the personnel file.

A worked pass

An HVAC tech, Marcus, mentions at Monday's huddle that his right forearm has ached after the third call of the day for about two weeks.

DISCOMFORT LOG  #2026-031         Opened: Mon wk 1
Body part / side ... right forearm, wrist side
Shows up ........... after 3rd call, gone by morning
Linked task ........ panel screws, hand nut driver
Duration ........... 14 days
Rating now ......... 4 of 10
Screen (Mon) ....... event N  numb N  night N
                     swell N  radiate N
Task review (Wed) .. hand driving about 5 h/wk
Adjustment (Thu) ... clutch driver for panels,
                     target about 1 h/wk hand
Follow-up day 7 .... rating 3, NIGHT TINGLING Y
                     thumb + 2 fingers, woke 2x
Disposition ........ STOP: injury SOP, same day

• Step 1, pass. The lead logs six fields before Marcus leaves the shop. Rating 4.
• Step 2, pass. Five no answers. The procedure continues.
• Step 3, pass. The owner reviews two weeks of tickets on Wednesday, the second working day after the report. About 22 calls a week, most opening two or more panels by hand: roughly 5 hours a week of hand nut-driver work. One task named.
• Step 4, pass. A powered driver with a clutch goes on the truck Thursday with a ten-minute walkthrough on the clutch setting so screws are not stripped or overdriven. Hand driving drops from about 5 hours a week to about 1, a cut of 4 hours, which is 80 percent, well past the quarter the step requires.
• Step 5, fail at day 7. Marcus rates the ache a 3, down 1 point from the 4 at report, and the forearm is better. But the re-run screen gets a yes: tingling in his thumb and two fingers that woke him twice last week. That is a numbness-or-tingling yes, which is a stop rule regardless of the rating. The owner opens the injury SOP that afternoon, attaches the log entry, and suggests Marcus see a clinician and take the physical demands of the job with him. He stays off powered cutting until he is seen.

Read back against the steps: the day-7 rating improved by 1, which would have looked like success under a rating-only follow-up, and the day-14 gate of a 2-point drop had not yet been reached. The repeated screen is what caught it. A shop that only asked "is it better?" would have closed this entry at day 14 and met the nerve symptom months later as a claim.

References

• OSHA, 29 CFR 1904.7, 1904.35, 1904.1 and 1904.39 (recording criteria, employee reporting rights, small-employer exemption, severe injury reporting)
• OSH Act Section 11(c), protection against retaliation for reporting
• See related: The Injury and Near-Miss Reporting SOP
• See related: How Cumulative Strain Injuries Actually Develop
• See related: Building a Shop Where People Report Pain Early