In California, your personnel file is your defense. When a PAGA claim lands — and in this industry, they land — the question is rarely whether you treated people fairly. It's whether you can prove it on paper. The write-up you skipped because the officer was "basically fine" is the one that costs you two years later. Here's how to build a file that holds up.
If it isn't written, it didn't happen
That's the whole principle. A verbal warning you never wrote down doesn't exist when it matters. Discipline you applied to one officer but not another isn't just unfair — it's evidence. The file that protects you is contemporaneous (written at the time), specific, and consistent across everyone on the roster.
What to actually document
- Performance — the good and the bad, in specifics, as it happens. Not reconstructed the week you terminate someone.
- Coaching and warnings — date, what was said, what you expected next, signed where you can get a signature.
- Meal and rest breaks — California's premium-pay rules are a PAGA magnet, and your records have to show breaks were provided and recorded.
- Incident reports — every post incident, written the same day, not from memory later.
- Your SB 553 workplace-violence log — required since July 2024 and kept separate from everything else. (More on the Cal/OSHA side here.)
The habits that hold up
- Write it at the time, not at the exit.
- Apply the same standard to everyone — inconsistency is the claim.
- Keep it factual: what happened, not how you felt about it.
- Store it where you can produce it in minutes, not days.
Where this discipline comes from
Clean documentation is a Qualified-Manager-level habit. The QM who keeps the operation audit-ready keeps it PAGA-ready too, because both come down to the same thing: records that match reality, kept current. Treat your personnel file the way you'd treat your BSIS file — because one day a lawyer will.
The cheapest insurance you'll ever buy is a write-up you took thirty seconds to put in writing.
Want your documentation to hold up before a claim tests it?
A straight review of how your operation documents performance, discipline, and breaks.