A warning letter is read twice. Once by the employee, on the day, and once months later by somebody deciding whether what followed was fair — with no memory of the meeting, no context, and no way to ask you what you meant.
What the letter is actually for
The conversation is the message. By the time a letter is being written, the employee has usually already been told; the letter exists so that the conversation is checkable afterwards by people who were not in the room.
Who those people are is worth being concrete about. A manager who inherits the team next year and needs to know what has already been raised. Whoever decides on confirmation, an increment or a promotion. The employee themselves, arguing that this never happened. And, if things go far enough, a lawyer or a labour officer reading the file cold.
None of them can be handed the tone of voice you used. They get the document. That is the whole reason the fields below are not optional decoration.
| Field | Why it is there |
|---|---|
| Reference number | So the letter can be cited later without ambiguity |
| Date of issue | Fixes the letter in the sequence of events |
| Employee name, ID, designation | Identifies one person in a company with two Rahuls |
| Subject line | Says what this concerns before the body is read |
| The conduct, with dates | The part that can be checked against records |
| Date it was discussed | Shows the letter follows a conversation |
| Who raised it | The manager who held that meeting |
| Expected standard | What "improved" actually means |
| Review date | When it will be assessed |
| Consequence | What happens if the standard is not met |
| Support offered | Training, adjusted roster, whatever is genuinely available |
| Signatory and title | Who issues this on the organisation's behalf |
| Acknowledgement block | Employee signature, date, and space for a reply |
Our free warning letter template lays these out in that order, which is also roughly the order a stranger reads them in.
Describe the conduct, not the person
Almost every weak warning letter fails in the same sentence. It characterises the employee instead of recording an event.
Your attitude has been unprofessional of late and you have shown a lack of commitment to the team.
Nothing there can be verified, disputed, or complied with. Compare:
You were absent on 28 and 29 July and on 5 August 2026. On each occasion you did not inform your reporting manager in advance and did not submit a leave request afterwards, as required by clause 4.2 of the leave policy.
Every clause in the second version is checkable against attendance records. That is the entire difference. The same rewrite applies to lateness — "repeatedly late" becomes "late on four of the eleven working days between 1 and 15 July, by between 40 and 95 minutes" — and to quality, and to conduct in meetings. Numbers and dates, not adverbs.
It is tempting to treat the vague version as the softer, kinder option. It is not, and it is worth being blunt about why a vague warning is worse than none at all.
- The employee cannot comply with it. "Improve your attitude" has no test attached. They cannot tell whether they have done it and neither can you, so the review meeting becomes a second argument about characterisation rather than an assessment.
- It is evidence against you, not for you. A file of vague warnings does not show a documented performance problem. It shows a manager who was unhappy for a long time and never said what about, which reads as a paper trail assembled to justify a decision already taken.
- It contaminates the specific one. When you eventually write a precise, well-evidenced letter, it sits in a file next to three vague ones, and the file as a whole reads as personal.
If you cannot name a date and a fact, you are not ready to write the letter. That is not a writing problem, it is a signal to go back and find out what actually happened.
Anchor it to the conversation that came first
A written warning should rarely be the first the employee hears of a problem. Say so explicitly, and name the meeting.
This letter follows our discussion on 6 August 2026, attended by yourself, Priya Nair (Reporting Manager) and Anil Kumar (HR), in which the attendance record above was reviewed with you.
That single sentence does three jobs. It shows there was a process, so the letter does not read as an ambush. It fixes a date the employee demonstrably knew, which matters enormously if the conduct continues afterwards — a repeat on 20 August is a different fact once you can point at 6 August. And it closes off "nobody ever told me", which is otherwise the most common response and the hardest one to disprove.
If there genuinely was no prior conversation — because the conduct was serious enough that the first formal step is a written warning — say that, and say why. Silence on the point looks like an omission; a stated reason looks like a decision.
The same logic applies to escalation. If this is a second warning, cite the first by reference number and date, and state what has or has not changed since. A warning that does not acknowledge its predecessors makes every letter in the file look like a first offence, which is precisely the impression you do not want to create if you later need to show a pattern.
Say what changes, by when, and who checks
Three things have to be in the letter, and they are frequently reduced to one vague paragraph.
The standard. Not "improve", but the observable behaviour you want to see. "Report at your rostered start time, and where that is not possible, inform your reporting manager before the start of the shift and submit a leave request the same day." Written that way, both of you can tell in September whether it happened.
The review date. A named date, not "going forward". Without one the warning never ends — it just sits in the file, and neither side knows whether it is still live. That cuts both ways. For the employee, an open-ended warning is a permanent mark with no route back. For the organisation, you cannot escalate cleanly from a warning you never formally closed. While you are at it, state how long the warning remains on record: six months is a common period, and saying it prevents a two-year-old letter being cited in an appraisal forever.
The consequence. State it in your own policy's terms and no stronger. "If the required standard is not met by the review date, further disciplinary action may follow, which may include a final written warning or termination of employment." Do not threaten a step your policy does not provide for, and do not be so hedged that the employee cannot tell this is serious. Both errors are read as bad faith later, in opposite directions.
Then name the support. If there is an underlying cause — health, a changed commute, a workload nobody rebalanced — a warning that ignores it will not fix the behaviour, and the omission is conspicuous in hindsight. Offering something specific and having it declined is a much stronger record than offering nothing.
Acknowledgement, and the right of reply
Hand over a signed copy, and keep an acknowledged copy on file. The acknowledgement block should say plainly that signing confirms receipt, not agreement — otherwise employees who disagree refuse to sign, and you are left with no evidence the letter was ever delivered.
If they refuse to sign anyway, that is survivable as long as you record it. Note on the file copy that the letter was handed over and read out, the date and time, and the name of a witness present, then send the same letter to their registered email address and keep the sent copy. A refusal that is documented is a fact. A refusal that leaves you with nothing is a letter that, as far as the record is concerned, does not exist.
Then offer the right of reply, in the letter, with a window: the employee may submit a written response within seven days, and it will be placed on file alongside this letter. Do it because it converts a one-sided document into a record of a process — but also because replies occasionally contain something you did not know. An approved leave that never reached the system. An instruction from a second manager that contradicted the roster. It is considerably better to learn that in August than from a lawyer in March, and if the reply changes nothing, you have still shown the person was heard.
The short version
- Name the conduct and the dates. If you cannot, you are not ready to write the letter.
- Reference the conversation that preceded it, with the date and who was present.
- State the standard, the review date and the consequence in your policy's own terms.
- Offer a right of reply, and file whatever comes back with the letter.
- Keep an acknowledged copy, and record delivery and a witness if acknowledgement is refused.
The test is whether someone reading the file in a year can tell what happened, what was asked for, and whether it changed. If they can, the letter did its job — regardless of whether anyone but the employee ever reads it.