SB 553 for restaurants: what California restaurant owners must do

Are restaurants covered by SB 553?

Yes, with very few exceptions. The statute's main small-business carve-out applies to worksites with fewer than ten employees that are not accessible to the public — but a dining room, bar, or counter-service area is accessible to the public by definition. That exemption doesn't reach restaurants.

A multi-location restaurant group evaluates coverage separately at each worksite, not across the business as a whole. A location with eight employees is close to the threshold — if it's open to the public (it is), coverage likely applies even at smaller headcounts, because the public-accessibility test controls. If you're uncertain, run the coverage checker for a clear read with the reasoning shown.

The full exemption analysis — including the rules for delivery-only kitchens (ghost kitchens are more nuanced) and food trucks — is in the coverage guide.

The restaurant threat landscape

SB 553 classifies workplace violence into four types. For food service, the breakdown typically looks like this:

• Type 2 — customer/patron. The dominant category. Guests angry at wait times, intoxicated patrons who escalate when cut off or asked to leave, dine-and-dash confrontations, drive-through disputes, delivery-driver altercations at the pickup window. Late-night and bar operations carry higher baseline exposure. (These same patron-aggression and cash-handling hazards show up in the retail guide, since the storefront exposure is closely related.)
• Type 1 — robbery. Restaurants handle cash nightly. A predictable close-out routine — same time, same person, same route to the safe or the bank — is a target. This is a reasonably foreseeable hazard at nearly every full-service location.
• Type 3 — co-worker. Kitchen hierarchy and high-stress service environments produce their own friction. A smaller but real category in food service.
• Type 4 — personal relationship spillover. Domestic violence situations that follow an employee to work — a concern at any worksite, but worth naming explicitly in the plan.

The WVPP must reflect the hazards of your specific location: a daytime family diner and a late-night bar-restaurant have genuinely different risk profiles. Copy-paste plans that don't name real hazards are the primary thing Cal/OSHA inspectors fault.

What your restaurant WVPP must cover

The plan is required to identify and address the hazards present at your worksite. For a restaurant, the hazards that almost always need to be named (the SB 553 compliance checklist walks through the full set of required elements):

• Patron aggression and de-escalation. Who is responsible for intervening when a guest becomes hostile? What's the procedure for removing someone? Is staff allowed to physically intervene, or do they call for backup and wait? Write it down.
• Intoxicated guests. The decision to stop service, the procedure for asking someone to leave, and what happens if they refuse. Servers need a script and management backup — the plan should name both.
• Cash handling and nightly close-out. What is the safe-drop procedure? Does staff vary the timing? Is a buddy system in place for parking-lot exposure? These controls belong in the plan, not just in informal practice.
• Parking lot and exterior. Lighting conditions, escort policy for late-night departures, where the lone-employee exposure exists (last person to leave, early opening). If the parking lot has a history of incidents, that belongs in the hazard assessment.
• Delivery pickup zones. Third-party delivery drivers picking up orders are technically members of the public. If tension at the pickup window is a regular occurrence, name it.
• How to report without fear of retaliation. The statute requires this in the plan — and in food service it matters more than in most industries because front-of-house staff have real economic incentives not to report anything that might cause a scene at a table.

The model WVPP walkthrough covers how to fill in each section of Cal/OSHA's model WVPP, section by section before filling in the blanks.

Training for a high-turnover team

Restaurants are among the highest-turnover industries in California. That creates a specific compliance failure mode: the original rollout gets done, and then waves of new hires start work without ever being trained because nobody remembered to add it to onboarding.

The fix is structural:

• Embed initial training in day-one onboarding. Not a separate event — the same session where they fill out I-9 and read the employee handbook. The law requires initial training before the employee starts working under the plan.
• One annual all-hands date. Pick a fixed date — slow season works well — and train everyone at once. This is far simpler than tracking individual anniversaries for a team that turns over every six months.
• Train on your hazards, not just the law. A generic video covering California Labor Code isn't enough. The training must cover your site's specific hazards and procedures — the patron complaint script, the cash close-out routine, who to call. That content can only come from your own plan.
• Name the interactive Q&A requirement explicitly. After any training content (video, slides, handout), there must be an opportunity for employees to ask questions of someone who knows your plan. In most restaurants that's the owner or general manager. Write it into the onboarding flow: "15-minute Q&A with [Manager Name]."
• Keep the attendance record. Date, session summary, trainer name and qualifications, names and job titles of everyone present. One year minimum. An inspector will ask for this before they ask for anything else.

The incident log in food service

The violent incident log is where food-service employers most often fall short — not because incidents don't happen, but because of underreporting culture.

Front-of-house staff, especially servers working for tips, are motivated to keep a conflict quiet rather than escalate it to management. A guest who threw a fork or made a threatening remark gets handled at the table — and never makes it into the log. Over time this builds a false compliance picture: zero incidents logged, but staff who can describe a long list of incidents if you ask them directly.

The plan and training must address this directly:

• The log captures every act or threat of violence — verbal or written threats included, regardless of whether anyone was injured or police were called. The only carve-out is lawful self-defense or defense of others. A regular who made a threatening comment is still a log entry; the relationship doesn't change the obligation.
• Retaliation for reporting is prohibited by the statute — and should be stated in the plan in plain terms, not buried in a paragraph of legalese.
• Names stay out of the log. The log records what happened, the type of violence, any injury, and any corrective action — not the victim's or witness's name. This removes one barrier to reporting.
• The log is retained for five years and must be produced within 15 calendar days if an employee requests a copy. See the incident log guide for every required field — and the SB 553 penalties guide for what a missing or empty log can cost, since each missing element is a separate citation.

Frequently asked questions