Employee Write-Up Template: Documenting Performance Issues

A write-up exists for two reasons, and small businesses tend to focus on only the first: it tells the employee clearly what needs to change, and it creates a record that protects the business if the situation eventually leads to termination. A write-up that only does the first job — vague, verbal-in-writing, never really specific — does almost nothing for the second, which is usually the moment it actually matters.

What makes documentation weak

Vague language. "Needs to improve attitude" describes a feeling, not an observable behavior, and it's nearly impossible to show later that a specific, correctable expectation was communicated. "Raised voice at a colleague during the Tuesday team meeting" is specific, dated, and describable to anyone reviewing it later.

No prior conversation referenced. A write-up that appears with no history of the issue being raised looks — and may genuinely be — a first mention of a problem being escalated straight to formal discipline, which is a weaker position if it's later challenged.

No clear expectation going forward. A write-up should state plainly what needs to happen differently and by when. Without this, it's a record of a complaint, not a documented opportunity to correct course, which matters for how it will be read later.

Inconsistent standards. If the same issue was written up for one employee and quietly let go for another, the documentation itself can become evidence of inconsistent, and potentially discriminatory, treatment — the opposite of the protection a write-up is meant to provide.

A template that holds up

Employee name and date:

Date and description of the specific incident or pattern: [What happened, when, and how it was observed — facts, not characterizations]

Expectation that was not met: [The specific standard, policy, or prior instruction this falls short of]

Prior discussion of this issue, if any: [Date and brief summary of any earlier conversation about it]

What needs to change: [Specific, observable, and achievable — not "do better"]

Timeline for improvement: [A specific date or period, not "going forward"]

Consequence if the issue continues: [Stated plainly — next step in your discipline process, up to and including termination]

Employee signature: [Acknowledges receipt, not necessarily agreement]

Manager signature and date:

Verbal warning first, or straight to written?

For most performance and minor conduct issues, a verbal conversation first — followed by a short note-to-file even if it isn't formatted as a full write-up — is the more proportionate first step, and it also demonstrates the issue was raised before escalating to formal documentation. Serious misconduct (safety violations, harassment, theft) reasonably skips straight to written documentation or termination, since the point of a graduated process is proportionality, not a rule that every issue must start small.

How this connects to a later termination

If a termination ever needs to be defended — to an unemployment claim, a complaint, or in the rare case a legal dispute — the write-up trail is usually the single most important piece of evidence a small business has. A termination without documentation behind it is far harder to defend than one backed by a specific, consistent, dated record showing the issue was raised and a real opportunity to correct it was given.

This is also why consistency across employees matters more than any individual write-up's wording — a documented pattern that was applied evenly is what actually holds up, not the presence of paperwork alone.

When a write-up isn't the right tool

Not every issue belongs in a formal write-up. A one-off, minor mistake that's already been addressed informally and doesn't recur usually doesn't need a written record — over-documenting minor issues can make a workplace feel punitive and can dilute the seriousness of write-ups when they're genuinely needed. The judgment call is whether the issue is a pattern, a serious one-time event, or something already resolved through a normal conversation.

Delivering the write-up itself

How a write-up is delivered matters almost as much as what it says. A private, calm conversation where the manager walks through the document, explains the reasoning, and genuinely listens to the employee's account before finalizing anything tends to land better — and holds up better later — than a write-up simply handed over with no discussion. If the employee raises a factual correction (a date that's wrong, context that changes the picture), it's worth actually incorporating that rather than issuing the document unchanged purely to avoid appearing to back down. A more accurate document protects the business better than a rigid one.

Keeping a record even when it doesn't lead anywhere

Not every documented issue leads to further discipline — sometimes a single write-up is genuinely enough, and the behavior corrects itself. Even then, it's worth keeping the record in the personnel file rather than discarding it once the issue resolves. If a similar or different issue comes up from the same employee later, having the earlier documentation on file — even if it was successfully resolved at the time — gives useful context for whether a pattern is forming. When a write-up doesn't resolve the issue on its own, a formal performance improvement plan is usually the next step before termination.

The short version

A write-up that actually protects a small business is specific, dated, references any prior conversation, states a clear path to correct the issue, and is applied the same way for the same issue regardless of who committed it. Vague language and inconsistent application are what turn documentation from a genuine safeguard into a liability of its own.