A written warning may be read years after it is written — by the employee, by a manager who has never met them, occasionally by a lawyer. It has to make sense to all of them with nobody present to explain it.
Most warning letters fail that test in the same place: they describe a feeling rather than an event.
What belongs on a written warning
| Field | Why |
|---|---|
| Reference number | So the letter can be cited in later correspondence. |
| The matter | A subject line saying what this concerns. |
| Date discussed | When the concern was raised face to face. |
| Who raised it | The manager who held that meeting. |
| What specifically happened | Dates, instances, and what was expected instead. |
| Review date | When improvement will be assessed. |
| Support available | What help is on offer, and how to reach it. |
| Signatory and title | Who issues this on the organisation's behalf. |
Describe what happened, not what kind of person they are
"You were absent on 28 and 29 July and on 5 August without notifying your manager in advance or submitting leave requests afterwards" is checkable. Someone can agree with it, dispute it, or explain it.
"Poor attitude", "lack of commitment" and "unprofessional conduct" are none of those things. Nobody can improve against them, because nobody can tell when they have stopped — and nobody can defend against them either, which is why they read as unfair even when the underlying concern is real.
If you cannot write the dates, you are not ready to send the letter.
The letter records a conversation that already happened
The template carries a "discussed on" date and the name of the person who raised the concern, because a written warning should never be the first the employee hears of the problem. If it is, the process was wrong before the letter was drafted.
Keep the gap short. A concern discussed on 11 August and confirmed in writing on 17 August reads as a process working. The same letter arriving five weeks later reads as a reaction to something else, and the employee will say so.
Say what happens next, and put a date on it
A warning with no review date never closes. It sits on the personnel file indefinitely, and neither the employee nor their next manager can tell whether the matter was resolved or simply forgotten.
The template asks for three things instead: a review date, a meeting rhythm until then, and the support available if something outside work is the cause. Offering the employee assistance programme costs nothing and is often the part that actually solves the problem.
State the consequence once, plainly. Repeating the threat of dismissal in three separate paragraphs makes the letter sound personal, which undermines it. And follow your own disciplinary policy: if the handbook runs verbal, then written, then final written, say which stage this is — a warning that does not identify its place in the ladder is hard to escalate from.
Right of reply, and the file copy
Give the employee a defined window — seven days here — to respond in writing, and record their comments alongside the letter rather than in place of it. A file holding one side of a disagreement is worth less than a file holding both.
Ask for a signed copy back, and be clear that the signature acknowledges receipt, not agreement; employees often refuse because they assume it means accepting the allegation. If they still refuse, note the refusal and the date, and send the letter by a method that proves delivery.
Then decide how long the warning stays live and record that decision. A warning nobody ever declares spent becomes a permanent mark, which is rarely what anyone intended when they issued it.