A Tuesday afternoon injury at an Ohio plant
At 3:15 p.m. on a Tuesday, a line operator at a metal-fabrication plant outside Columbus tells her supervisor that her back hurts after lifting a die. She finishes the shift, goes home, and texts the next morning that she is staying in bed. The supervisor forwards the message to the HR manager, who also covers safety for the plant and two warehouses in other states.
The HR manager knows how to start a report for her Pennsylvania site, where a private carrier takes the first notice. Ohio feels different. She remembers that the state runs its own fund, but not what that changes: who receives the first report, which form starts it, or which date she should write on the calendar.
Her questions are the ones this guide answers. By the end, you will be able to name Ohio's statutory reporting clock with its trigger, unit, recipient and source. You will also know where the rule stops and your own decision begins, and what to confirm directly with the Bureau of Workers' Compensation.
Why a state-fund state changes who receives the report
In most states, an employer buys workers' compensation coverage from a private insurer and reports an injury to that carrier. Ohio works differently. North Dakota, Ohio, Washington and Wyoming are the four monopolistic workers' compensation states (checked 2026), where coverage must come from a state fund. This guide covers Ohio only.
For the HR manager, that has a practical effect. There is no carrier to phone and no carrier portal to learn. In Ohio the state fund is administered by the Bureau of Workers' Compensation (BWC), and ORC §4123.28 directs the report to the BWC. For a state-fund employer, the "first report" and the "claim" sit with one agency.
This also makes Ohio the easiest state to describe in one sentence and one of the easiest to mishandle in a multi-state spreadsheet. A tracker built around "notify the carrier" has no column for a state agency that is also the carrier. The recipient field has to be Ohio-specific.
The rest of this guide separates three things people tend to blend: the statutory duty to report, the form (the FROI-1) most readers associate with starting a claim, and the employer's own decisions about what a case is.
What the Ohio BWC first report of injury rule says
Reference material with citations, not legal advice. You decide recordability and compensability, and you file.
The statutory duty sits in Ohio Revised Code §4123.28. Under that section, an Ohio employer must keep a record of injuries and occupational diseases causing seven days or more of total disability, and must report them to the Bureau of Workers' Compensation within a week after acquiring knowledge of the injury or death (ORC §4123.28). We could not read the official statute text for this update, so confirm the current wording and timing with Ohio BWC.
Each element of that clock is worth stating separately:
- Trigger: the employer acquires knowledge of an injury or death, in a case that causes seven days or more of total disability.
- Unit: a week, as the statute words it. The statute does not say how the week is counted here, so confirm with the BWC.
- Recipient: the Bureau of Workers' Compensation.
- Source: ORC §4123.28.
The statute's own words are short enough to quote:
"Within a week after acquiring knowledge of an injury or death therefrom" — Ohio Revised Code §4123.28; confirm the current text with Ohio BWC
Where the FROI-1 fits
Ohio employers and BWC materials refer to the first report of injury as the FROI-1, and readers searching for the "ohio froi-1 form" are usually looking for how a claim begins. We have not sourced the BWC's own FROI page text for this guide, so we do not state here which filing channel satisfies §4123.28, or who is permitted to submit the FROI-1 on an employer's behalf. Confirm both on the BWC's website or with the BWC directly.
The same applies to the Ohio Administrative Code. The BWC administers additional rules around reporting, and some may carry their own day counts or conditions. We do not print any figure we have not sourced. If you rely on a day count other than the statutory week, cite the specific Administrative Code section and write down the date you checked it.
One more point on dates. The statute runs from knowledge, not from the injury date. If the first notice is a text message sent the next morning, as in the opening scenario, the knowledge date is the date the employer received that message. A reportable-case file that records only the injury date cannot show which date started the clock.
What you decide, and how self-insured employers differ
The statute tells you when to report and to whom. It does not decide, for you, whether a particular absence meets the trigger. Whether a case reaches seven days or more of total disability, and whether you treat it as reportable, is a judgment you make from the facts and the cited text. ClaimsIntake does not make that call.
Recordability under OSHA is a separate decision. A case can be reportable to the BWC without being OSHA-recordable, and the reverse. Different tests, different clocks, different recipients. If your team treats "the claim" and "the OSHA entry" as one event, the guide to workers' comp claims versus OSHA recordables walks through where they diverge.
Self-insured employers
Ohio's self-insurance option, if your site uses it, may follow a different reporting path from a state-fund employer's. We have not sourced a self-insured reporting deadline or channel, so we do not state one. If your Ohio site is self-insured, confirm with the BWC which report applies, to whom it goes, and by when, then record the answer and the date you got it.
That is a deliberate gap. A deadline without a citation and a verification date is hard to defend later. When we cannot cite it, we say so.
Ohio next to other states and the OSHA clocks
The point of a multi-state view is that the same Tuesday injury can start several clocks with different recipients. The table below shows how Ohio's duty compares with two other states in this guide's scope. Each row gives trigger, unit, recipient and source.
| State | Trigger | Unit | Recipient | Source |
|---|---|---|---|---|
| Ohio | Knowledge of an injury or death causing seven days or more of total disability | Within a week; how the week is counted is not stated, so confirm with Ohio BWC | Bureau of Workers' Compensation | ORC §4123.28 |
| Florida | Actual knowledge of an injury or death | Within 7 days; calendar days under Florida's rules (Fla. Admin. Code R. 69L-56.002(18)) | The employer's carrier | Fla. Stat. §440.185(2) |
| Michigan | Disability exceeding seven consecutive days, a death, or a specific loss | Immediately, per one WDCA publication | Workers' Disability Compensation Agency and the carrier | Michigan WDCA |
Notice what the table shows. Ohio's trigger is a disability threshold, Florida's is knowledge alone, and Michigan's recipient list has two entries. A single "days to file" column hides all of that. The full set of states is laid out in the first-report deadlines by state guide.
Federal OSHA clocks run separately
The Ohio first report does not satisfy any OSHA duty. Two federal clocks may run alongside it, depending on the facts:
- An employer must enter each recordable case 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, in the employer's own records (29 CFR 1904.29(b)(3), eCFR current October 15, 2026). Recordability is your decision.
- An employer must report a work-related in-patient hospitalization, amputation or loss of an eye to OSHA within 24 hours, and a fatality within 8 hours (29 CFR 1904.39(a); OSHA reporting page, checked 2026).
Confirm which agency's channel covers your site, using OSHA's State Plans page. The OSHA recordkeeping requirements overview covers the log and retention rules in more detail.
Where tools fit, and what to do next
Most Ohio employers handle this with a mix of email, calendar reminders and a spreadsheet. That approach is familiar and flexible, and many teams build theirs carefully. Its weakness is structural: a spreadsheet holds dates, not the rule that produced them, and it keeps no record of which source was in force when the clock started.
The BWC's own channels are free and authoritative. They are the place the employer files. A tool can sit beside them, but it cannot replace them.
ClaimsIntake's store workbooks are built for this gap. The Multi-State First Report Deadline Tracker computes first-report deadline dates for each state from a knowledge date, so a single Ohio case and a Pennsylvania case can sit in the same view with their own recipients and counts. It computes dates; you still decide what the case is and you still file. For a multi-site owner juggling several states, the multi-state injury reporting guide explains the wider workflow. The ClaimsIntake app is being built and will add a rule table in which each row will carry its citation and a "last verified" date. It is not live yet, and no rule row is yet verified for any state.
A practical checklist for Ohio:
- Write down the knowledge date for every case, not only the injury date.
- Cite ORC §4123.28 in your procedure, with the date you last checked it.
- Confirm with the BWC which filing satisfies the statute, who may submit it, and whether any Administrative Code rule adds its own timing.
- If you self-insure, get the reporting path in writing from the BWC.
- Keep the OSHA clocks on a separate line, with their own triggers and recipients.
If you are ready to put those dates in one place, the Multi-State First Report Deadline Tracker is the workbook to start with. ClaimsIntake never submits anything to the BWC or to OSHA, and it holds no medical records. You decide and you file.
