How to Write Up an Employee
A write-up is only useful if two things are true: it's specific enough that the employee knows exactly what has to change, and it's documented well enough to hold up if the situation escalates later. Most write-ups fail on one or both counts, either too vague to act on or too thin to defend. This covers what belongs in every write-up, a reusable template, and scripts for the most common scenarios that lead to one.
What a Write-Up Actually Is
A write-up, sometimes called a written warning or a disciplinary notice, is a formal, documented record that a specific performance or conduct issue occurred, what's expected going forward, and what happens if it doesn't improve. It's usually one step in a progressive discipline process, not a first resort and not a final one. Its purpose is twofold: give the employee a clear, factual account they can act on, and create a consistent record the business can point to later.
This article is general information, not legal advice. How write-ups should be structured, applied, and retained can vary by state, industry, and company policy. Consult an employment attorney or your own HR policy for guidance specific to your business.
The Write-Up Template
This structure works across almost any scenario. Fill in the specifics, keep the language factual, and avoid characterizing motive or intent.
Employee Written Warning
Employee Name / Position
[Name], [Job Title]
Date of Write-Up
[Date]
Date(s) of Incident
[Specific date or date range]
Description of the Issue
On [date], [factual, specific description of what happened, no interpretation of motive].
Policy or Expectation Involved
[Reference to the specific handbook policy, job expectation, or prior instruction]
Prior Related Discussions
[Date(s) of any earlier verbal or written coaching on this same issue, or "None" if this is the first instance]
Expected Corrective Action
[Specific, measurable expectation going forward, with a timeframe if applicable]
Consequences If Not Corrected
[Next step in the progressive discipline process, stated plainly]
Signatures
Manager: ___________________ Employee: ___________________ Date: _______
Scenario Scripts
Performance Issue: Missed Deadlines or Quality Problems
Anchor performance write-ups to specific, measurable instances, missed dates, error counts, incomplete deliverables, rather than a general sense that quality has slipped.
Attendance or Tardiness Pattern
Reference the specific dates and the written policy threshold, not a general impression that attendance "has been an issue."
Policy Violation: Dress Code, Phone Use, or Safety
Name the exact policy and the specific, observed behavior. This is one of the easiest scenarios to document cleanly, since the standard itself is usually already written down.
Behavioral or Conduct Issue With Coworkers
This is the category most prone to vague language. Describe the specific observed behavior, not a character judgment like "disrespectful" or "difficult" on its own.
Insubordination or Refusal to Follow a Direct Instruction
Insubordination write-ups carry more weight than most, so precision matters even more here: document exactly what was asked and exactly how it was declined.
How to Deliver a Write-Up
- Deliver it in person, not by email alone, so there's room for a real conversation and questions.
- Keep it private, away from coworkers.
- Read through the specifics together rather than just handing over a document to sign.
- Give the employee a chance to respond, and note their response on the document if relevant.
- Have a witness present, typically another manager or an HR representative, especially for more serious write-ups.
Common Mistakes That Weaken a Write-Up
Avoid: vague language like "bad attitude" or "not a team player" with no specific incident behind it. Piling multiple unrelated issues into one write-up instead of documenting each clearly. Inconsistent enforcement, writing up one employee for something that was overlooked for someone else in a similar role. Waiting weeks after the incident to document it, which weakens the record and makes exact details harder to recall accurately. Including any language that references a protected characteristic, even in an aside unrelated to the core issue.
Where a Write-Up Fits Into Progressive Discipline
| Stage | What It Looks Like | Documentation Level |
|---|---|---|
| Verbal warning | Informal coaching conversation about a first instance | Brief note in the employee's file with the date |
| Written warning | Formal write-up using the template above | Full written record, signed by both parties if possible |
| Final written warning | Formal write-up stating this is the last step before termination | Full written record, explicitly referencing prior warnings |
| Termination | End of employment if the pattern continues | Full documented history from every prior stage |
How Updoot's Performance Tool Helps
A write-up is only as strong as the record behind it, and that record is much easier to keep consistent inside a system than scattered across memory and email.
- Performance review and HR tools: keeps every write-up, coaching note, and prior warning tied to the employee's record in one place, so a pattern is easy to show rather than reconstructed from memory.
- Project management: provides a factual record of missed deadlines or incomplete work, useful evidence for performance-related write-ups.
- PTO and attendance tracking: supplies the exact dates and occurrence counts an attendance write-up needs to be specific and accurate.
- Org chart: confirms the correct manager and reporting line for who should be delivering and signing the write-up.
All of it lives in the same platform, so a write-up is backed by a consistent, dated record instead of a memory of what happened.
Frequently Asked Questions
A write-up should include the employee's name and role, the date and specific description of the incident, the policy or expectation that was violated, any prior related discussions, the corrective action expected, the consequences if it isn't corrected, and signature lines for both the manager and the employee.
No, an employee generally cannot be forced to sign, and a signature typically only acknowledges receipt of the document, not agreement with its contents. If an employee refuses to sign, note the refusal on the document with a witness present rather than treating it as a separate issue.
As specific as possible. Vague language like "poor attitude" or "not a team player" is hard to act on and hard to defend later. A write-up should describe the specific incident, the date, and the specific policy or expectation involved.
There's no universal number. Most companies use a progressive discipline process, verbal warning, written warning, final written warning, termination, though serious misconduct can skip directly to termination. The exact structure should be defined in company policy and applied consistently.
A write-up itself is a business record, not a legal action, but it can become evidence in a later dispute over a termination or other employment decision. This is exactly why accuracy, consistency, and avoiding any language tied to a protected characteristic matters. Consult an employment attorney for guidance on a specific situation.
Updoot's performance review tools keep write-ups, coaching notes, and prior warnings in one consistent record tied to each employee, so documentation is standardized and easy to reference if a pattern needs to be shown later.
Final Takeaway
A good write-up does two jobs at once: it gives the employee something specific enough to actually act on, and it gives the business a record specific enough to stand behind later. Use the template, keep the language factual instead of characterizing intent, document the same way every time, and treat it as one step in a progressive process rather than an isolated event. This article is general information, not legal advice specific to your business or state.