SB 553 for nonprofits, churches, and faith organizations

Is there a church or nonprofit exemption? No.

Let's answer the anxious question first, because it's the one keeping board members and pastors up at night: there is no exemption from SB 553 for being a church, a religious ministry, a faith-based nonprofit, or any other 501(c)(3). The statute does not carve out organizations by mission, belief, or tax status. SB 553 is part of California's labor code, and it reaches employers — including nonprofit employers.

That can feel surprising, because faith organizations are used to certain religious accommodations in other areas of law. But workplace safety is different. The duty here is to protect the people who work for you, and the law treats a paid youth director, a part-time office administrator, or a salaried executive director the same way it treats an employee of any business. If your organization is an employer, it has employees to protect, and SB 553's framework applies.

So the right frame isn't "are churches exempt?" It's the same frame every California employer uses: do I fit one of the narrow exceptions completely? The most relevant one for a small congregation or grassroots nonprofit is the small-worksite exemption, and as we'll see, public-facing ministry tends to fail it. Our full coverage guide walks through every exception in detail.

Do volunteers count?

This is the genuinely confusing part, and it's worth getting right because so much of a church or nonprofit's work is done by people who aren't on payroll.

Volunteers are generally not employees. A congregation that runs entirely on volunteers — no paid pastor, no paid staff, no one drawing a wage — would not have employees, and without employees there is no employer-employee relationship for SB 553 to attach to. A small all-volunteer mutual-aid group is in a genuinely different position from an employer.

But the moment you have paid staff, you are an employer. One paid position is enough. A part-time bookkeeper, a stipended worship leader, a single administrative assistant, a salaried director — any of these makes your organization an employer, and SB 553 applies to your employees. The plan exists to protect those paid workers, even though most of the people in the building on a given day may be volunteers and congregants.

There's a second subtlety worth flagging. The small-worksite headcount test asks how many employees are working at the site at any given time, but the test is about physical presence at the busiest moment — including temporary workers and contractors, not just the payroll roster. The more important point for most faith organizations is the public-accessibility condition below, which is usually what decides coverage long before headcount does.

Why public services and events change the answer

Here is the rule that catches most congregations and service nonprofits: any worksite that is open to the public is covered regardless of headcount. Coverage is assessed per worksite, and a public-facing site does not get the small-worksite exemption.

The small-worksite exemption only holds when all three conditions are true at the same time:

• fewer than 10 employees are working at the site at any given time (physical presence at the busiest moment, including temps and contractors — not the payroll roster);
• the site is not accessible to the public; and
• you maintain a compliant Injury and Illness Prevention Program (IIPP) under Title 8 §3203.

Faith and service work is, by its nature, often public-facing. A worship service open to anyone who walks in, a public concert or festival on the grounds, a food pantry that serves the community, a warming shelter, a community meal, a thrift store, an open prayer room — all of these make the site accessible to the public. When that's true, the second condition fails, the exemption doesn't apply, and your paid employees are covered no matter how small your staff is.

That's the heart of why "we're tiny" doesn't get most congregations off the hook. It isn't the size of your staff that decides it; it's that you open your doors to the community. If you're not sure how your specific situation lands, run it through the SB 553 coverage checker — it's built around exactly this per-worksite, public-accessibility logic.

The hazards faith and service organizations should document

SB 553 organizes workplace violence into four types, and faith and service settings touch most of them. Naming the right risks for your actual ministry is what makes a plan credible rather than generic.

• Distressed and in-crisis individuals (a recurring hazard). Churches and nonprofits are often where people in crisis come for help — someone facing eviction, addiction, a mental-health emergency, or acute grief. Staff and volunteers regularly make contact with people under extreme stress. This is a foreseeable hazard that many faith and service organizations should identify and plan for, not improvise around in the moment.
• Food pantries and shelters. Clientele arriving at a pantry, a shelter, or a community meal may be hungry, exhausted, frightened, or in withdrawal. Lines, limited supplies, and stressful circumstances can escalate. This commonly warrants its own section in the plan with de-escalation and staffing procedures.
• Public services and large gatherings (Type 1 and Type 2). An aggressor with no legitimate business at the site (Type 1, criminal intent) and a person the organization serves — a congregant, a guest, a program participant (Type 2, customer/client) — are distinct risk categories. Large open gatherings concentrate both.
• Worker-on-worker conflict (Type 3). Tension among paid staff, between staff and a former employee, or with a supervisor is workplace violence's third type and applies in nonprofits exactly as it does anywhere else.
• Personal-relationship spillover (Type 4). An outsider with a personal connection to an employee — a domestic or former partner, for instance — who shows up at the site is the fourth type. Close-knit congregations sometimes see these situations follow a staff member or a member to the building.

Remember that what counts as loggable workplace violence is broad: every act or threat of violence — including verbal or written threats — regardless of whether anyone was injured or whether police were called. The only carve-out is lawful self-defense or defense of others. A threat shouted at a volunteer in the food line belongs in the log even if no one was touched.

What your written plan must cover

The written Workplace Violence Prevention Plan (WVPP) must be site-specific and in effect at all times. It names the person or people responsible, and it has procedures for the items below. For a faith or service organization, the key is to write it around the people you actually employ and the public you actually serve.

• Name a responsible person. Identify who owns the plan — often the executive director, a designated staff lead, or an administrative pastor. Volunteers can help carry it out, but accountability sits with the organization's leadership.
• Reporting without retaliation. Staff need a way to report incidents and concerns without fear, with the anti-retaliation protection stated plainly. This matters in tight-knit organizations where reporting an incident involving a long-time member can feel awkward.
• Crisis-contact and de-escalation procedures. Because contact with distressed individuals is a recurring hazard, the plan should describe how staff de-escalate, when to disengage, when to call for help, and when to involve law enforcement.
• Event and service procedures. For public worship, festivals, pantries, and shelters, describe staffing, entry and exit awareness, and the steps to take if a gathering turns volatile.
• Emergency response. What happens during an active threat — communication, evacuation or lockdown, and accounting for staff. Many organizations coordinate this with their existing emergency and safety planning.
• Multi-employer coordination. If you share a site with another tenant, host an outside program, or use contractors, the plan addresses how you coordinate on safety.
• Review and revision. Reviewed at least annually, after any incident, and whenever a deficiency appears.

If you're starting from the free Cal/OSHA template, our section-by-section walkthrough of the model WVPP explains what each blank is asking for — and which blanks get employers cited when they're left generic.

Training and the incident log apply to your staff

Training under SB 553 reaches everyone who is an employee — full-time, part-time, and seasonal staff, plus supervisors and managers. It happens at three moments: initially (when the plan is established, or before a new hire works under it), annually, and whenever a new hazard appears or the plan changes. Crucially, training must include interactive questions and answers with someone knowledgeable about your own plan — not a generic video. For a small nonprofit, that "someone knowledgeable" is usually the director or the responsible staff lead.

A word on volunteers and training: SB 553's training mandate is written around employees. Many organizations nonetheless choose to brief regular volunteers on reporting and de-escalation as a matter of good practice and overall safety — that's sensible, but the legal training requirement is about your paid staff.

The violent incident log applies too. It records each incident by type, circumstance, and corrective action, and it deliberately omits personal identifying information — names of the people involved go in the separate investigation record, not the log. The log must be kept five years and produced to an employee within 15 calendar days of a request, free of charge. The full field list is in our incident log guide. When you're ready to put it all together, the SB 553 compliance checklist turns the written plan, training, log, and reviews into a concrete to-do list — and because each missing program element is its own potential citation, it's worth understanding the penalty structure before an inspection rather than after one.

Sources

Frequently asked questions