How to Document Employee Discipline at a Small Business (So It Holds Up)

Q: Can I fire someone if all the warnings were verbal?

Usually yes, especially in at-will states, but 'can' and 'should' are different. Without documentation you're exposed if the termination is challenged, because you can't show the pattern or that the employee knew. The safer move is to document forward starting today and run one clean written warning before you act, unless there's an immediate safety or misconduct issue.

2026-06-01 · HR Cadence Hub Team

There's a sentence I hear from solo HR people more than almost any other. A manager comes to you ready to fire someone, you ask for the documentation, and they say "I've talked to them a million times." Then you have to be the person who explains that if none of those talks were written down, as far as the record is concerned, they never happened.

It's one of the most frustrating parts of being a department of one. You didn't have the conversations. You weren't in the room. But you're the one who has to defend the termination if it gets challenged, and right now you're defending it with nothing.

This post is about closing that gap. Not by becoming the documentation police, because you don't have time for that, but by building a documentation habit into how your managers already work. Here's how to document employee discipline at a Small Business so it actually holds up the day you need it.

Why verbal warnings don't count (even when they really happened)

Let's be fair about something first. The conversations your managers had were probably real. The employee probably was warned, more than once. The problem isn't honesty. The problem is that "we talked about it" isn't evidence, and a termination that gets challenged is decided on evidence.

When an employee files for unemployment, or files a discrimination or retaliation claim, or just hires a lawyer, the question is never "did the manager mean well." The question is "what can you show." A documented pattern of performance issues, with dates, specifics, and proof the employee knew, is a defense. A manager's memory of "a million" conversations is a story, and the other side gets to tell a different one.

There's a particular trap here for Small Businesses. The employee requests leave, or discloses a disability, or reports a concern, and two weeks later the manager wants to fire them for performance. If your only documentation starts after that protected activity, the timeline reads like retaliation even when the performance problems are genuinely old. The note your manager skipped writing six months ago is the note that would have protected you now.

What "good documentation" actually looks like

Good documentation isn't a formal write-up with HR letterhead every single time. It's lighter than people think, and the lightness is the whole point, because anything heavy won't get done.

A usable disciplinary record has five things:

- The date. When the conversation or incident actually happened, not when you got around to writing it down. - The specific behavior. "Missed the Tuesday client deadline," not "bad attitude." Observable facts, not character judgments. - The standard. What was expected instead. "Deliverables are due by end of day on the agreed date." - The conversation. That you talked to the employee about it, and what they said back. - The consequence stated. What happens if it continues.

That's it. Five lines in an email to yourself, or a note in your HR system, written the same day. The "same day" part matters more than the format. Documentation written three months later in a panic, right before a termination, ends up looking exactly like what it is.

One word that should almost never show up in your records: "attitude." Nearly every "bad attitude" complaint is really a specific behavior the manager hasn't named yet. Push for the behavior. "Bad attitude" won't hold up. "Interrupted two coworkers in the Monday meeting and pushed back on the assignment in front of the client" will. If you want a deeper version of this for formal reviews, our [solo HR performance review guide](/blog/performance-reviews-solo-hr-guide) walks through writing behavior-based feedback that protects you.

How to get managers to document without becoming the documentation police

Here's the real problem. You know what good documentation looks like. Your managers know they're supposed to do it. It still doesn't happen, because in the moment, having the hard conversation feels like the work and writing it down feels like homework.

You don't fix that with a policy memo. You fix it by making the writing-down part take 60 seconds and happen while the conversation is still fresh.

A few things that actually move the needle:

- Give them a template, not a form. A three-line email format they can send from their phone beats a PDF they have to open on a laptop. Date, what happened, what you said. Done. - Make "send me a one-line note" the close of every escalation. When a manager comes to you about an employee, your last sentence is always "send me a quick note on what you just told me so it's on the record." Every time, until it's a reflex. - Build a recurring prompt. A monthly nudge to each manager ("any coaching or discipline conversations this month worth logging?") catches issues while they're small and quietly builds a paper trail long before anyone's thinking about termination.

The managers who skip documentation usually aren't lazy. They're busy, and the cost of not documenting is invisible right up until the day it's enormous. Your job is to shrink the moment-of-effort and move the reminder upstream of the crisis.

Build a documentation cadence (so it's not a fire drill at termination)

The reason documentation feels impossible is that most Small Businesses only think about it reactively, once a termination is already on the table. By then you're trying to reconstruct a year of conversations in an afternoon, and that never goes well.

The fix is to make documentation a small recurring rhythm instead of an emergency. A workable cadence for a department of one looks like this:

- Monthly: a standing prompt to managers to log any coaching or disciplinary conversations from the past month. Five minutes each. - Quarterly: a quick review of anyone with two or more logged issues. Are they trending toward a formal performance plan? Catch it before it's a termination. - At every formal step: verbal warning, written warning, performance improvement plan, final warning. Each step documented, dated, and acknowledged by the employee in writing, even if that's just a "received" reply to your email.

This is the same muscle as the rest of solo HR operations. If you've already set up recurring compliance reminders, you know the pattern. Documentation is just one more recurring task that protects you. Our guide on [how to build an HR cadence system](/blog/how-to-build-hr-cadence-system) covers the broader framework, and the same rhythm that keeps your [HR audit checklist](/blog/hr-audit-checklist-small-business) on track is exactly what keeps documentation from piling up.

The progressive discipline ladder (verbal, written, PIP, final) only works as a defense if every rung is documented. A manager who jumps from "a million conversations" straight to "fire them" hands the employee a procedural argument for free. The ladder, documented, is what makes the eventual termination look measured and fair, because it was.

When the paper trail isn't there yet: what to do right now

Maybe you're reading this because you're in it today. A manager wants to terminate, the documentation is thin, and you can't time-travel. Here's the honest playbook.

First, do not back-date anything. Ever. A record created today, dated today, that honestly describes the current situation is far more defensible than a "reconstructed" note a plaintiff's attorney can date-stamp from your system's metadata. Back-dating turns a weak case into a fraud problem.

Second, document forward starting now. Have the manager write down, dated today, exactly what's happening and what's been said, framed honestly ("I've raised the missed deadlines with this employee several times over the past few months; this week specifically..."). Then run a real, documented conversation with the employee. A clear written warning today, with a defined improvement window, gives you a clean record to stand on in 30 days.

Third, weigh the risk honestly. If the employee has recently engaged in any protected activity (a leave request, a complaint, a disability disclosure), slow down and consider a 30-minute call with an employment attorney before you act. A thin paper trail plus a protected-activity timeline is the exact fact pattern that turns a routine termination into a claim. This isn't the moment to save the legal fee. Once the dust settles, your [offboarding checklist](/blog/employee-offboarding-checklist-small-teams) is where you make sure the exit itself is clean and consistent.

Documentation is one of those parts of HR where the work is cheap and boring right up until the day it's the only thing standing between your Small Business and a five-figure settlement. The managers who document look like they're doing extra work. They're actually buying the cheapest insurance there is.

FAQ

Can I fire someone if all the warnings were verbal? Usually yes, especially in at-will states, but "can" and "should" are different. Without documentation you're exposed if the termination is challenged, because you can't show the pattern or that the employee knew. The safer move is to document forward starting today and run one clean written warning before you act, unless there's an immediate safety or misconduct issue.

How long should I keep disciplinary documentation? A good default is the length of employment plus at least four years, since most wage, discrimination, and wrongful-termination claim windows fall inside that range. Some records carry longer retention rules, so when in doubt, keep them. Storage is cheap and a missing record is expensive.

What's the difference between a verbal warning and a written warning if I'm documenting both? The verbal warning is the conversation; the written warning is a formal document the employee signs or acknowledges. Even a verbal warning should be documented (a dated note that the conversation happened), but a written warning is a heavier, named step on the progressive discipline ladder. The point of writing down the verbal one is so the ladder is provable end to end.

Do I really need a formal progressive discipline policy at a Small Business? You don't have to publish a rigid policy, and sometimes you shouldn't, because a strict policy can lock you into steps you don't want in a serious case. But you do need a consistent practice. Treating similar issues similarly across employees is what protects you from a discrimination claim. Consistency is the goal; a binder is optional.

What should an employee write-up actually include? Date, the specific observable behavior, the standard that wasn't met, what was discussed, the consequence if it continues, and a place for the employee to acknowledge receipt. Keep it factual and behavior-based. Leave out adjectives about the person and stick to what happened.

---

Want every recurring HR task, including your monthly documentation prompt and quarterly discipline review, sitting in one place that nudges you before each deadline? That's the whole idea behind [HR Cadence Hub](https://hrcadencehub.com). And if you want the backbone to start from, grab the [free 2026 HR Compliance Calendar](https://hrcadencehub.com/compliance-calendar-2026). It maps the federal and state deadlines to the months they actually hit, so the recurring stuff (documentation included) stops living in your head.