A Thursday afternoon call from a Pennsylvania warehouse
At 4:10 p.m. on a Thursday, a shift supervisor at a Pennsylvania distribution center calls the HR manager. A picker has hurt a wrist lifting a tote. The employee was seen at an urgent care clinic, was sent home, and will not be in tomorrow. The HR manager also handles sites in two other states and keeps one spreadsheet of "first report" dates.
She has questions that a single date cannot answer. Does this injury trigger the Pennsylvania report at all? Which day starts the count? Who gets the form? And is the number in her spreadsheet a rule, or a habit?
This article walks through what the Pennsylvania state source says about the employer's first report, what it leaves open, and how to keep the cited rule beside the date. By the end you will be able to write down the trigger, the unit, the recipient and the source for your Pennsylvania clock, and mark the one point you still need to confirm with the state.
Reference material with citations, not legal advice. You decide recordability and compensability, and you file.
Pennsylvania employer report of injury LIBC-344: what the state source says
LIBC-344 is the Bureau of Workers' Compensation employer report form referenced in the title. We did not read the form itself, so confirm its current title and filing use on the Bureau's forms page. The form is the vehicle. The duty to file a first report, and its timing, come from the state regulation, 34 Pa. Code §121.5, titled "Reporting injuries to the Bureau":
"(1) Within 48 hours for every injury resulting in death. (2) Within 7 days after the date disability begins for all other injuries covered by section 438 of the act" — 34 Pa. Code §121.5(a) (checked 2026)
The Pennsylvania Department of Labor & Industry (DLI) gives a shorter summary in its flow-of-claim guidance (checked 2026). Broken into the four elements every deadline should carry:
- Death. The trigger is an injury that results in death. The unit is hours: 48. The recipient is the Bureau of Workers' Compensation. The source is 34 Pa. Code §121.5(a)(1).
- Other injuries. The trigger is disability "continuing the entire day, shift or turn, or longer, in which the injury was received" (§121.5(c)). The unit is "days": seven, counted from "the date disability begins." The recipient is the Bureau. The source is §121.5(a)(2). If there is no disability, the rule says a copy "should not be sent to the Department."
- Copy to the employee. The employer sends a copy to the employee "simultaneously with filing it with the Bureau" (§121.5(b)).
Notice what the rule does not say. It gives the number of days. The Department's own computation rule, 34 Pa. Code §121.3a, counts intermediate Saturdays, Sundays and holidays, so these are calendar days, and a last day that falls on a weekend or holiday moves to the next day that is neither. That is the gap this article keeps coming back to.
This article does not quote section 438 of the Workers' Compensation Act, which the rule cross-refers to. Read the current text, and confirm the trigger and day count with the Bureau before you rely on a date. Ask your carrier whether it files the report on your behalf, and get the answer in writing.
The trigger is lost time, not just a visit to a clinic
The second rule applies to disability continuing the entire day, shift or turn in which the injury was received, or longer. A clinic visit alone, with the employee back at work the same shift, does not match that wording on its face. In the opening scenario, the picker was sent home and will miss tomorrow's shift. Whether that meets the rule's wording depends on facts the supervisor needs to record: when the employee left, when they were due back, and what the medical provider said about work.
That fact pattern is yours to assess. The state source tells you the trigger. It does not decide whether your case meets it. Whether the injury is compensable is also a separate decision that the employer, its carrier and the state process work out. Nothing in a first report timing rule settles it.
When the clock starts and which days count
The regulation, as quoted above, states the number of days and the start event. In practice, three questions decide the date on your calendar:
- What starts the count? The rule says "the date disability begins." That is not necessarily the date of injury or the date the employee first reported. Record the date disability began, and confirm with the Bureau if the facts are unclear.
- Are the days calendar or working days? Calendar days: 34 Pa. Code §121.3a includes intermediate weekends and holidays in the count. Other states count differently. California's Labor Code §5401 (2025 code) uses "one working day" for the claim form, so working-day language does appear in state workers' compensation law. A Pennsylvania reader should not borrow that convention. Read what Pennsylvania's own text says.
- Does the count include the first day? The state source does not say.
Worked example
The dates below are hypothetical, to show why the basis matters. Suppose disability begins on a Tuesday, March 3.
- Counting seven calendar days from the day after, the last day is Tuesday, March 10.
- Counting seven working days (Monday to Friday, no holidays), the last day is Thursday, March 12.
Two readings, two dates, two days apart. Neither is a statement of Pennsylvania law. If your tracker shows "7 days" without the basis, it cannot tell you which date to defend. This is also why a date with no cited rule next to it is hard to defend if someone asks how you got it.
Edge cases: the agency summary and the code
The DLI summary and the regulation describe the same seven-day limit in slightly different words. Agency summaries can differ from the code, so read the code for the controlling language.
Do not pick a reading silently. Where a question stays open, do this:
- Quote the 34 Pa. Code §121.5 wording with its source and the date you checked it.
- Check section 438 of the Workers' Compensation Act, which the rule cross-refers to.
- Confirm the timing directly with the Bureau of Workers' Compensation, and keep the confirmation with the case file.
- Record the earliest date any reading would require, and file by that date if you cannot resolve the question in time. That is your decision as the employer, not a rule.
A shorter note on the 48-hour clock for deaths: it runs in hours, so it does not raise the calendar-versus-working-day question in the same way. Treat it as a separate, much shorter clock and make sure the person who receives the news knows to start it immediately.
Keeping the Pennsylvania record defensible
A first report is not the only record created by a lost-time injury. Three other clocks may be running at the same time, and they have different triggers, units and recipients.
The federal OSHA record. If the case is recordable, the employer enters it on the OSHA 300 Log and the 301 Incident Report within seven calendar days of receiving information that a recordable injury or illness has occurred (29 CFR 1904.29(b)(3), checked 2026). The recipient is the employer's own record, kept at the establishment. This is a different clock from Pennsylvania's. Recordability is your decision, made using the OSHA rule, and not the state's. For how the same information feeds both, see first report of injury as OSHA 301.
Federal severe-injury reporting. If the injury is a fatality, in-patient hospitalization, amputation or eye loss, a separate OSHA channel applies, with its own 8-hour and 24-hour limits (OSHA, checked 2026). It runs independently of the Pennsylvania report.
Retention. OSHA 300 Logs, 300A summaries and 301 reports must be kept for five years following the end of the calendar year they cover (29 CFR 1904.33(a), checked 2026). Pennsylvania retention is a separate question to confirm with the Bureau.
What makes any of these defensible is a short record per case: the knowledge date, who knew, which rule applied, the version of the rule you read, and the date you checked it. A spreadsheet can hold the dates. It rarely holds the rule that produced them.
Where tools fit
Most employers handle this with email, calendar reminders and a sheet. That setup is flexible and familiar, and many were built with care. The weak point is the gap between a date and its reason. When a Pennsylvania date sits next to eleven other states' dates, the unit (hours, calendar days, working days) tends to get lost.
For a multi-state employer, the useful features of any tracker are the same:
- a stored rule per jurisdiction, with trigger, unit and recipient;
- the citation and the date it was last checked;
- the knowledge date entered once and carried to every clock.
The Multi-State First Report of Injury Deadline Tracker workbook computes deadline dates from a knowledge date across jurisdictions, applying each clock's unit. It is a reference tool. It does not decide recordability or compensability, it does not submit anything to the Bureau, and you still file. Pennsylvania counts calendar days under 34 Pa. Code §121.3a; check it against the current text before you enter it.
If you are a single-state employer with 20 to 100 employees, a workbook like this is the better fit than a subscription. The ClaimsIntake app is not live. If you want to hear when it launches, there is a waitlist.
For a wider view of how states compare, see the first report of injury deadlines by state overview, and multi-state employer injury reporting if you run sites in more than one state.
Your next step
Do three things this week:
- Read 34 Pa. Code §121.5 and section 438 of the Act, and write down the trigger, unit and recipient.
- Contact the Bureau of Workers' Compensation and ask in writing how it applies "the date disability begins" to your facts. Save the reply.
- Put the citation and the date you checked it beside the Pennsylvania date in your tracker.
Reference material with citations, not legal advice. You decide recordability and compensability, and you file.
When you want that citation-and-date discipline across several states at once, the Multi-State First Report of Injury Deadline Tracker is built around it.
