OSHA Logs and Incident Reports: An AI-Assisted Safety Program for Nonprofits
Food banks, thrift stores, shelters, home visiting programs, and residential services employ people who lift, drive, clean, de-escalate, and work alone in other people's homes. When someone gets hurt, the organization owes a set of records and reports that many nonprofit managers have never been told about: the OSHA 300 log, the 300A summary posted every February, electronic submission for some establishments, and phone calls to OSHA that are due in hours rather than days. This article explains who must keep which records, what makes an injury recordable, how state plans, workers' compensation, volunteer injuries, and workplace violence rules fit around them, and where AI can carry the paperwork load while people keep the judgment calls and the care of anyone who was hurt.
Most nonprofit leaders think of workplace safety as a concern for construction companies and factories. Then a warehouse associate at the food bank strains his back unloading a pallet, a shelter case manager is bitten while separating two residents, a thrift store sorter is cut by broken glass hidden in a donation bag, or a home visitor slips on an icy porch. Each of those events triggers obligations under the Occupational Safety and Health Act, under your state's workers' compensation system, and often under your insurance policies. The organizations that handle them well are the ones that had a simple system in place before the injury happened.
The federal recordkeeping rule, found at 29 CFR Part 1904, asks covered employers to do three things. Keep a log of recordable work-related injuries and illnesses on OSHA Form 300 with a detailed incident report on Form 301 or an equivalent. Summarize the year on Form 300A and post that summary where employees can see it. And, separately, report the most serious events to OSHA directly within strict hour-based deadlines. On top of that, some establishments must submit their data electronically each year. None of this is complicated once you know which parts apply to you, but the exemptions are counterintuitive, and a surprising number of human services organizations assume they are exempt when they are not.
This is a good place for AI to help, with clear limits. Incident narratives arrive as hurried emails, voice memos, and handwritten notes. Written safety programs and job hazard analyses never get drafted because no one has the time. Near-miss reports pile up without anyone looking for patterns. Training materials exist in English only, while the warehouse crew speaks Spanish, Vietnamese, and Haitian Creole. AI is genuinely useful for all of that. What it should not do is decide whether an injury is recordable, tell anyone how to treat an injury, or come anywhere near the clinical response when an incident involves a client in crisis.
We will cover whether your organization must keep OSHA records at all, what counts as recordable, the annual posting and electronic submission calendar, the severe injury reporting deadlines, how state plans, workers' compensation, and workplace violence laws such as California's SB 553 fit in, how to think about volunteer injuries, and a practical division of labor between AI tools and the people responsible for safety. If insurance claims are already on your mind, our guide to using AI for nonprofit insurance claims covers the claims side in more depth. This article is general information, not legal advice. Rules change, state plans vary, and your workers' compensation carrier, an employment attorney, or your state's OSHA consultation program should confirm the specifics for your organization.
Does Your Nonprofit Have to Keep OSHA Logs?
Nonprofit status does not exempt an organization from the OSH Act. If you have paid employees, OSHA covers you, either directly through federal OSHA or through an OSHA-approved state plan. What the recordkeeping rule offers instead are two partial exemptions, one based on size and one based on industry. Both are "partial" because, as discussed below, neither one excuses you from reporting fatalities and severe injuries.
The size exemption applies if your organization had ten or fewer employees at all times during the previous calendar year. The test looks at peak employment across the whole organization, not at each site, and it counts part-time, seasonal, and temporary workers you supervise day to day. A food pantry with eight regular staff that hires six seasonal drivers for the holiday rush crossed the threshold during that period, and it needs to keep records for the following year.
The industry exemption is where nonprofits most often get it wrong. OSHA publishes a list of lower-hazard industries, by NAICS code, whose establishments do not need to keep routine records regardless of size. That list, Appendix A to Subpart B of Part 1904, includes religious organizations, grantmaking and giving services, social advocacy organizations, civic and social organizations, child day care services, most schools, and offices of physicians and other outpatient care. A policy advocacy group, a community foundation, or a congregation is typically exempt from routine recordkeeping.
Many of the nonprofits with the most physical work are not on that list. Community food and housing, and emergency and other relief services (the NAICS group covering food banks and many shelters), individual and family services (where many home visiting and family support programs fall), vocational rehabilitation services, nursing and residential care facilities, warehousing and storage, and used merchandise stores, which is how OSHA's tables classify thrift operations, are all absent from the partially exempt list. If your organization runs any of these, you should assume you must keep records once you pass ten employees, and confirm the classification rather than guessing.
The industry exemption also works establishment by establishment. A multiservice agency whose administrative office would be classified as social advocacy may still have a warehouse, a residential program, or a retail store that is not exempt. Classify each physical location by what it primarily does. When in doubt, keeping the log is the safer choice: an organization that keeps records it did not strictly need has lost a little time, while one that skipped records it needed has a citation waiting for the first inspection.
A quick coverage check for each location
Answer these per establishment, then confirm with the current OSHA tables
- Did the organization as a whole have more than ten employees at any point last calendar year, counting seasonal and temporary staff?
- What does this location primarily do, and what NAICS code fits that activity rather than the organization's mission statement?
- Is that code on the partially exempt list in Appendix A to Subpart B?
- Is the location in a state plan state that applies its own recordkeeping rules or exemption list?
- Has OSHA, the Bureau of Labor Statistics, or a state agency sent a written request to keep records or complete a survey? If so, you must comply regardless of exemptions
What Counts as Recordable, and What Does Not
Not every injury goes on the log. An injury or illness is recordable when it is work-related, is a new case, and meets at least one of the general recording criteria in 29 CFR 1904.7: death, days away from work, restricted work or transfer to another job, medical treatment beyond first aid, loss of consciousness, or a significant injury or illness diagnosed by a physician or other licensed health care professional. Needlesticks and cuts from sharps contaminated with another person's blood, which can happen in shelters and residential programs, have their own specific recording rule.
The line between first aid and medical treatment decides more cases than anything else. OSHA's first aid list is defined and closed: things like nonprescription medication at nonprescription strength, cleaning and covering wounds with bandages or butterfly strips, hot or cold therapy, elastic wraps and non-rigid supports, removing a splinter, eye patches, and drinking fluids for heat stress. Prescription medication, stitches or sutures, rigid splints, physical therapy, and similar interventions are medical treatment. A volunteer coordinator who cuts her hand on a box cutter and gets it cleaned and bandaged at the front desk has a first aid case. If she goes to urgent care and gets three stitches, it becomes recordable.
Work-relatedness is presumed for events in the work environment, with listed exceptions such as voluntary participation in a wellness program or eating food brought from home. For mobile staff, the question gets harder. A home visitor injured in a car crash while driving between client homes is generally in a work-related situation. The same person injured while running a personal errand on the way home generally is not. Write down the facts you used to decide, because the reasoning matters as much as the conclusion if anyone ever asks.
Timing and privacy matter too. You have seven calendar days after learning of a recordable case to enter it on the log and complete the incident report. Certain cases are "privacy concern cases," including sexual assaults, mental illnesses, HIV, hepatitis, or tuberculosis infections, and injuries to intimate body parts. For those you write "privacy case" in place of the employee's name and keep a separate confidential list. For a shelter or residential program, this provision is not an edge case. Build it into your procedure from the start, and remember that the log is a document employees and their representatives are entitled to see.
Usually recordable
If the case is also work-related and new
- Any day away from work after the day of injury, or restricted duty
- Stitches, prescription medication, rigid splints, or physical therapy
- Loss of consciousness, however brief
- A diagnosed fracture, cracked rib, or punctured eardrum
- Needlesticks or cuts from sharps contaminated with blood or other potentially infectious material
Usually not recordable
Still worth logging internally as an incident or near miss
- Bandages, cleaning a wound, ice packs, or over-the-counter pain relievers at normal strength
- A doctor visit for evaluation only, with no treatment beyond first aid
- Injuries during a personal errand or a voluntary recreational activity
- Injuries to true volunteers who are not employees (covered later in this article)
- Close calls where no one was hurt, which belong in your near-miss log
The Annual Calendar: Posting the 300A and Submitting Electronically
Recordkeeping has a yearly rhythm, and the dates are fixed. After the calendar year ends, you review the 300 log for completeness and prepare the Form 300A summary, which totals the number of cases, days away, days of restricted work, and injury types, along with the annual average number of employees and total hours worked. A company executive must certify the summary. For a nonprofit, that generally means an officer, the highest-ranking person at the establishment, or that person's supervisor. It should not be signed by whoever happened to fill it out.
The certified 300A must be posted from February 1 to April 30 in a place where notices to employees are customarily posted. Establishments with zero recordable cases still post a summary showing zeros. For programs where staff rarely visit a central office, such as home visiting teams or scattered-site housing, think about how employees will actually see it, and consider supplementing the physical posting with a copy on the staff intranet. The log, the summary, and the incident reports must be kept for five years following the end of the calendar year they cover.
Some establishments must also submit data electronically through OSHA's Injury Tracking Application (ITA) by March 2 of each year, which was the deadline for 2025 data this past spring. Three groups are covered. Establishments with 250 or more employees that must keep records submit their 300A. Establishments with 20 to 249 employees in industries listed in Appendix A to Subpart E submit their 300A. And since the rule that took effect January 1, 2024, establishments with 100 or more employees in industries listed in Appendix B to Subpart E also submit case-level data from their 300 and 301 forms.
These lists matter for nonprofits. Appendix A to Subpart E includes community food and housing and emergency relief services, vocational rehabilitation, nursing and residential care facilities, warehousing and storage, and used merchandise stores. So a regional food bank warehouse or a thrift store with 20 or more employees likely needs to file a 300A online each year. Appendix B, the higher-hazard list, includes residential care facilities, vocational rehabilitation, warehousing, and used merchandise stores, so a large residential program or a big thrift operation with 100 or more employees may need to submit individual case data too. Submissions require the establishment's Employer Identification Number, and the ITA offers a coverage tool that tells you whether a given establishment must file.
One caution about electronic submission: OSHA publishes some of the submitted data. The agency does not collect employee names or addresses through the ITA, but incident descriptions written carelessly can still identify a person, particularly in a small program. Write narratives that describe the event without unnecessary identifying details, which is another place where a consistent, edited report format pays off.
An OSHA recordkeeping calendar for a nonprofit
Assign one owner and set reminders for every date
- Within hours of a severe event: report to OSHA (8 hours for a fatality, 24 hours for hospitalization, amputation, or eye loss)
- Within 7 calendar days of a recordable case: enter it on the 300 log and complete the 301 incident report
- January: review the prior year's log, calculate hours worked and average employees, prepare the 300A
- By February 1: have an executive certify the 300A and post it at each establishment through April 30
- By March 2: submit through the ITA for each covered establishment
- Ongoing: keep logs, summaries, and reports for five years, and update entries if a case changes
Severe Injury Reporting: Hours, Not Days
The most urgent obligation applies to every employer under OSHA's jurisdiction, including organizations exempt from keeping logs. Under 29 CFR 1904.39, you must report the death of an employee from a work-related incident within eight hours of learning about it. You must report an in-patient hospitalization of one or more employees, an amputation, or the loss of an eye within 24 hours. Fatalities are reportable if the death occurs within 30 days of the incident, and hospitalizations, amputations, and eye losses are reportable if they occur within 24 hours of it.
Definitions matter here. An in-patient hospitalization means formal admission, not a visit to the emergency room that ends with the person going home, and admissions solely for observation or diagnostic testing are not reportable. An amputation includes the loss of a fingertip, even without bone loss. Reports go to OSHA by phone to the nearest area office, through the 24-hour hotline, or through the online reporting page. Voicemail, fax, and email do not count. State plan states may have their own reporting channel and, in some cases, a broader list of reportable events, so know yours in advance.
Picture the realistic version. A forklift tips at the food bank warehouse at 4:30 on a Friday. The operations director rides to the hospital with the injured employee, the executive director is on a plane, and the person who knows the OSHA rules is on vacation. That is why the reporting procedure needs to be written down, short, and known to every supervisor: who calls, what they say, which number they use, and where they record that the call was made. The clock starts when the organization learns of the event, and a supervisor counts as the organization.
AI has a narrow, useful role in this moment and a firm boundary around it. A pre-built checklist that an AI tool helped you draft, sitting in a binder and on supervisors' phones, is valuable. An AI assistant that helps the supervisor organize the facts for the call (what happened, when, where, who, the nature of the injury) can reduce errors. But the first priority is the injured person, and getting them proper medical care is a job for 911, trained responders, and medical professionals. Nobody should be consulting a chatbot about how to treat an injury, and the decision about whether an event meets the reporting threshold belongs to a person who has read the rule.
The one-page severe incident procedure every supervisor needs
Write it before you need it, and keep it where supervisors can reach it at any hour
- Get the injured person care first: call 911 for anything serious and follow your first aid plan
- Notify the designated safety lead and a backup by phone, with names and numbers listed
- Decide whether the event is a fatality, in-patient admission, amputation, or eye loss, and note the time you learned of it
- Report to OSHA or your state plan within the deadline, using the phone line or online form, and record the confirmation
- Preserve the scene and equipment where safe, photograph conditions, and collect witness names
- Notify your workers' compensation carrier and, where appropriate, your other insurers
State Plans, Workers' Comp, and Workplace Violence Rules
OSHA rules are the floor, not the whole picture. According to OSHA's State Plans page, 22 state plans cover private-sector workers as well as state and local government employees, and several more cover public employees only. A nonprofit in California, Washington, Oregon, Michigan, Minnesota, North Carolina, or another state plan state answers to that state's agency, which must be at least as effective as federal OSHA and can be stricter. Some state plans have different reporting channels, additional reportable events, or their own standards that do not exist federally. Organizations operating in several states should map which agency covers each location.
Workers' compensation is a separate system with separate forms. Every state requires employers to report work injuries to their workers' compensation carrier or state agency, usually within a short window measured in days, and many require you to give the injured employee a claim form promptly. The workers' comp first report of injury and the OSHA 301 ask for overlapping information, but they are not interchangeable, and the thresholds differ: an injury may require a workers' comp report without being OSHA-recordable, and vice versa. A good internal incident report captures everything both systems need, so that each form can be completed from one source of truth rather than from memory a week later.
Workplace violence is an area where state law has moved faster than federal law. There is no federal OSHA workplace violence standard for general industry, though OSHA can cite employers under the General Duty Clause for recognized hazards. California's SB 553, codified at Labor Code section 6401.9, required most California employers to have a written workplace violence prevention plan in place by July 1, 2024. As Gallagher's summary of the law explains, the plan must address reporting and response procedures, hazard assessment, a violent incident log, training, and anti-retaliation, with limited exemptions such as locations closed to the public where fewer than ten employees work at a time. The log must cover every workplace violence incident, including threats, not only those causing injury, and incident logs and investigation records must be kept for five years. Cal/OSHA is also developing a general workplace violence standard, so California organizations should watch for changes.
For shelters, drop-in centers, harm reduction programs, thrift stores, and food distribution sites, which all have regular contact with the public, this is not abstract. Even outside California, a written plan reflects good practice, and insurers increasingly ask about one. Organizations working in especially sensitive settings may find useful context in our article on AI in domestic violence shelters, which addresses the confidentiality expectations that shape documentation in those programs.
Questions to settle for each state you operate in
A one-page map per state saves panic later
- Is this a federal OSHA state or a state plan state, and what is the reporting number?
- Does the state require a written injury and illness prevention program?
- What is the workers' comp reporting deadline, and which form goes to whom?
- Is a workplace violence prevention plan or incident log legally required?
Three systems, one incident
Different purposes, different thresholds
- OSHA records: recordable cases on the 300 log and 301, plus severe event reports
- Workers' compensation: employer's first report to the carrier or state, often for any injury needing care
- Violence and internal logs: state-required incident logs and your own near-miss records
Volunteer Injuries: Off the Log, Still Your Responsibility
Nonprofits are unusual employers because so much of their physical work is done by people who are not employees. The OSH Act covers employees, and true volunteers who receive no compensation are generally not employees for OSHA purposes. Their injuries do not go on the 300 log, and a volunteer's hospitalization does not trigger the 24-hour OSHA report. That is the narrow answer, and it is often misread as "volunteer injuries do not matter."
They matter a great deal. A volunteer who falls from a stepladder while stocking shelves can bring a negligence claim against the organization. Your general liability policy, a volunteer accident policy if you carry one, and your board's understanding of risk all depend on prompt, accurate documentation. The federal Volunteer Protection Act of 1997 shields volunteers from some personal liability for their own acts, but it does not protect the organization itself. And the hazard that injured a volunteer will eventually injure an employee if no one fixes it.
The categories also blur. A "volunteer" who receives a stipend, regular meals, or other meaningful compensation, works under close supervision, or is required to put in hours as a condition of a program may be treated as an employee by OSHA, a state agency, or a workers' compensation board. Court-ordered community service workers, AmeriCorps members, interns, and participants in workforce training programs each raise their own questions. If your thrift store or warehouse relies on any of these groups, get a written answer from counsel or your carrier about how each is classified, and record the reasoning.
The practical approach is to use one internal incident report for everyone, employee or volunteer, with a field that records the person's status. Recordability is then decided only for employees, while every incident feeds the same hazard review. Your volunteer onboarding process is the place to introduce safety rules, lifting technique, reporting expectations, and any tasks volunteers may not perform, such as operating a forklift or a box baler.
Volunteer safety practices that hold up under scrutiny
Not OSHA requirements, but the expectations insurers and courts apply
- Document every volunteer injury on the same incident form employees use, with status recorded
- Keep a list of tasks restricted to trained employees, such as powered equipment and balers
- Give a short, documented safety orientation before the first shift, and keep sign-in records
- Check with your broker whether volunteer accident coverage makes sense for your risk profile
- Get a written classification for stipended volunteers, service members, interns, and trainees
Where AI Carries the Safety Paperwork
Safety recordkeeping suffers less from bad intentions than from friction. The forms are tedious, the information comes in late and in pieces, and the person responsible usually has a different full-time job. That is exactly the kind of work where AI tools help. Each of the uses below keeps a person in charge of the facts and the decisions, while the tool handles structure, consistency, and drafting.
Turning messy narratives into consistent reports. A supervisor's account of an injury is often a three-sentence text message, a voice memo recorded in the parking lot, or a paragraph that mixes what happened with opinions about who was careless. Give an AI tool your organization's incident report template and the raw account, and ask it to organize the facts into the fields you use: date, time, location, task being performed, object or substance involved, body part, nature of injury, treatment received, and witnesses. Ask it to list the information that is missing rather than filling gaps with guesses, and to flag blaming language so the final report describes conditions and events. The supervisor then reviews, corrects, and signs. The result is a report that feeds the 301, the workers' comp form, and your internal hazard review without three people retyping it.
Drafting a written safety program and job hazard analyses. Many states require a written injury and illness prevention program, and every organization benefits from one. AI can produce a solid first draft structured around your actual operations: who is responsible, how hazards are identified and corrected, how incidents are reported and investigated, how training works, and how employees can raise concerns without retaliation. It can also draft job hazard analyses for specific tasks by breaking each task into steps, listing the hazards in each step, and proposing controls. Unloading a delivery truck, sorting donated clothing, cleaning a shelter bathroom, and driving to home visits each deserve one. The people who do the work should review every analysis, because they know where the real hazards are. Your employee handbook should reference the safety program rather than duplicating it.
Spotting patterns in near-miss and incident logs. A single near miss is an anecdote. Fifty of them over a year show where the next injury will happen. Once your reports follow a consistent format, an AI tool can group them by location, task, time of day, and hazard type, and summarize what it sees: repeated reports of the loading dock door sticking, a cluster of back strains during Saturday distributions, verbal threats concentrated at one site during evening hours. Treat these summaries as prompts for a human review, not as findings. Removing names before analysis protects privacy and keeps the focus on conditions rather than individuals.
Drafting training in multiple languages. Safety training only works if people understand it, and warehouse, retail, and facilities crews at many nonprofits speak several languages. AI can draft short, plain-language training sheets, toolbox talk scripts, and posters, then translate them. Translation of safety content needs human review by a fluent speaker, ideally someone who does the job, because a mistranslated warning can be worse than none. Our guide to reviewing AI translations for quality describes a practical review process.
Keeping the calendar. The 300A posting window, the ITA deadline, five-year retention, annual training refreshers, and periodic plan reviews are easy to forget because they come around once a year. A simple AI-assisted workflow can generate the annual task list, draft reminder emails to site managers, prepare a 300A worksheet from the year's log, and produce the checklist for the executive who certifies it. This is also where organizations that already use AI for grant compliance tracking can extend the same habits to safety.
A reusable incident-structuring prompt
Adapt to your own report template
"Here is our incident report template and a supervisor's raw notes, with names removed. Organize the facts into the template fields. Do not infer or add facts. List every field you could not fill and the question the supervisor should answer. Flag any language that assigns blame or states opinions, and suggest neutral wording that describes what happened."
- The supervisor reviews and signs the final version
- The safety lead decides recordability separately
Safety documents AI can draft well
Each one reviewed by someone who does the work
- Written injury and illness prevention program tailored to your sites
- Job hazard analyses for lifting, sorting, driving, cleaning, and home visits
- Five-minute toolbox talks and one-page training sheets in several languages
- Workplace violence prevention plan drafts and incident log templates
- Quarterly near-miss summaries and annual 300A preparation worksheets
Where People Decide, and Where AI Stays Out
Recordability is a legal judgment with consequences. An AI tool can explain the criteria, quote the regulation, and help you organize the facts, but it can also confidently misclassify a case because it does not know that the doctor prescribed a medication, or that the employee was moved to light duty the next day. The person responsible for the log should make each call, record the reasoning, and consult OSHA's published interpretations, the state plan, or counsel when a case is genuinely unclear. A model's answer is a starting point for that review, never the entry on the log.
Care for anyone who was hurt belongs entirely to people. Supervisors call 911, provide first aid within their training, accompany the person to care when appropriate, and follow up afterward. Return-to-work conversations, accommodation decisions, and communication with an injured employee's family are human responsibilities. So are the decisions about discipline or retraining after an investigation. AI can help draft a respectful follow-up message or a return-to-work checklist, but the relationship and the judgment are not delegable.
When an incident involves a client in crisis, keep AI on documentation logistics only. A shelter worker injured while a resident was in acute distress, or a staff member threatened during an intake, may need an incident report, an OSHA entry, a workers' comp claim, and a violent incident log entry. AI can help format those documents and track their deadlines. It should not be used to assess the client, interpret their behavior, recommend how staff should respond to them, or make any decision about their care or services. That work belongs to trained staff and clinical professionals, and the client's information should not be entered into a general-purpose AI tool at all.
Privacy runs through all of this. Injury records contain medical information, and some incidents involve clients whose identities are protected by program confidentiality rules. Remove names and identifying details before using any AI tool, use only tools your organization has approved for this category of data, and make sure your AI acceptable use policy says so explicitly. If you have not assessed which tools are appropriate for sensitive records, a data privacy risk assessment is the right first step.
Good uses of AI in a safety program
Working from de-identified facts
- Structuring raw incident accounts into a consistent report format
- Drafting safety programs, hazard analyses, and violence prevention plans
- Summarizing near-miss trends for a human safety review
- Drafting and translating training, with fluent human review
- Maintaining the posting, submission, retention, and training calendar
Where AI does not belong
People only
- Deciding whether a case is recordable or reportable
- Advising on first aid or medical treatment for an injured person
- Assessing, interpreting, or responding to a client in crisis
- Receiving names, medical details, or client records in unapproved tools
- Assigning blame or recommending discipline after an incident
Building the Program in a Quarter
A small nonprofit does not need a safety department to get this right. It needs one accountable person, a handful of written procedures, and a habit of reviewing what happened. A realistic approach is to build the core program over about three months, using AI to compress the drafting so that staff time goes to review, walkthroughs, and training.
In the first month, settle coverage. Classify each establishment, decide whether you must keep logs, confirm whether any location must submit through the ITA, and identify your state plan and workers' comp reporting rules. Write the one-page severe incident procedure and distribute it to every supervisor. Set up the 300 log, either on OSHA's forms or in an equivalent format that captures the same information, and create your internal incident report template.
In the second month, draft the written program. Use AI to produce first drafts of the injury and illness prevention program, a workplace violence prevention plan if your state requires one or your work involves the public, and job hazard analyses for your five or six highest-risk tasks. Walk each site with the people who work there and revise the drafts based on what you see. Present a summary to leadership and, for larger organizations, to the board's risk or finance committee. Our article on AI risk registers for nonprofit boards shows how to bring operational risks like this into board oversight.
In the third month, train and set the rhythm. Deliver short training in the languages your staff speak, document attendance, and introduce near-miss reporting with a simple form and a promise that reports will not lead to blame. Put the annual dates on a shared calendar with reminders. Schedule a quarterly review of incidents and near misses. And if you want an expert second look, most states offer a free, confidential OSHA On-Site Consultation program for small businesses, which is separate from enforcement and can be a good fit for nonprofits that qualify.
Minimum viable safety program checklist
What should exist by the end of the quarter
- A named safety lead and backup, with authority to fix hazards
- A coverage memo for each establishment: logs, ITA submission, state plan, workers' comp rules
- A one-page severe incident procedure in every supervisor's hands
- A 300 log, a 301-equivalent incident report, and a confidential privacy case list
- A written safety program, job hazard analyses, and a violence prevention plan where needed
- Multilingual training with attendance records, and a near-miss reporting form
- A calendar with the 300A posting window, ITA deadline, retention dates, and quarterly reviews
A reminder on verification: exemption lists, submission requirements, penalty amounts, and state rules change over time. Before relying on any rule described here, check the current text on OSHA's website or your state plan's website, and confirm workers' compensation obligations with your carrier. When a specific case is unclear, ask your state's OSHA consultation program or an employment attorney.
Conclusion
Workplace safety recordkeeping is one of those obligations that nonprofits with physical operations often discover only after an injury or an inspection. The rules themselves are manageable. Know whether each location must keep the 300 log, understand what makes a case recordable, post the 300A from February 1 to April 30, submit through the ITA by March 2 if your establishment is covered, and report fatalities within eight hours and hospitalizations, amputations, and eye losses within 24. Around those core federal rules sit your state plan, your workers' compensation system, any state workplace violence requirements, and the practical and legal reality of volunteer injuries.
AI changes how much of this a small team can realistically sustain. It turns scattered accounts into consistent reports, drafts the written programs and hazard analyses that otherwise never get written, surfaces patterns in near misses, produces training people can actually read in their own languages, and keeps the annual dates from slipping. Those are real gains, and they free staff time for walkthroughs, conversations, and fixing hazards, which is where safety actually improves.
The lines are just as clear. People decide recordability and reportability. People care for anyone who was hurt. When a client in crisis is involved, AI stays on paperwork and deadlines, and trained staff handle everything else. An organization that holds those lines and lets AI carry the administrative load will have better records, fewer surprises, and, most importantly, fewer people getting hurt doing the work of the mission.
Put Your Safety Paperwork on Solid Ground
We help nonprofits set up AI-assisted workflows for incident reports, written safety programs, multilingual training, and compliance calendars, with clear rules about what stays with people. Your counsel, carrier, and safety professionals make the determinations. We help you arrive organized.