At a glance
| Document type | Employer letter template |
|---|---|
| Issued by | Employer |
| Templates included | 5 ready to use versions |
| Download format | Word (.docx) |
| Statutory reference | Industrial Relations Code, 2020 |
| Last reviewed | 26 August 2026 |
| Maintained by | Engage HR editorial team |
The escalation ladder, and what each rung is for
Skipping a rung is the most common reason a dismissal is questioned. So is issuing the same letter three times and calling it escalation.
| Counselling record | Written warning | Final written warning | Show cause notice | |
|---|---|---|---|---|
| What it says | This was raised with you and here is the note of it. | This happened, it is not acceptable, and here is what follows if it recurs. | This has recurred after a warning, and the next step is dismissal. | This is alleged, explain yourself before we decide. |
| Has a finding been made | No finding, a conversation. | Yes, on the incident stated. | Yes, on the incident and on the recurrence. | No. Making one before the reply is the error to avoid. |
| Employee response | Recorded in the note. | Sought before issue, recorded in the letter. | Sought before issue, recorded in the letter. | The entire point of the document. |
| Typical currency | Not a formal record, though kept. | Stated period, commonly six to twelve months. | Stated period, usually twelve months. | Days. A long window suggests the outcome is settled. |
| Used wrongly for | Serious misconduct that needed a formal process. | Poor performance, which it cannot fix. | A first incident, skipping the earlier rung. | Announcing a decision already taken. |
Standard warning letter format
Nine elements. The letter is short, and the discipline is in what it records rather than how it is expressed.
- Header. Employee name, code, designation, department, date, and what the letter is: a written warning, or a final written warning.
- The incident. What happened, on what date, at what place. Specific enough that a reader who was not there understands it.
- The standard breached. The policy, rule or standing order the conduct fell short of, named.
- Prior steps. Any earlier discussion, counselling or warning on the same subject, with dates.
- The employee's explanation. What they said when it was put to them, recorded fairly, including where it was not accepted and why.
- The finding. That the conduct occurred and is not acceptable, stated plainly.
- What is required now. The specific change expected, and from when.
- The consequence. What will follow if it recurs, stated without ambiguity.
- Currency and acknowledgement. How long the warning stays on record, and a signature block for receipt.
The acknowledgement should record receipt, not agreement. An employee who disputes the finding can still have received the letter, and asking for agreement produces a refusal that becomes a second dispute.
5 letter templates
Employee Warning Letter for first written warning, attendance
The most common warning issued. Note that this version is for unapproved absence, which is conduct, not for absence caused by circumstance, which is not.
[Company Letterhead] Ref: [Reference Number] Date: [Date] STRICTLY PRIVATE AND CONFIDENTIAL [Employee Name] Employee code: [Employee Code] Designation: [Designation] Department: [Department] Sub: Written warning Dear [Employee Name], 1. The incident You were absent from work on [Dates of Absence] without applying for leave in advance and without informing [Manager Name] before the start of your shift on any of those days. 2. The standard The attendance policy at [Policy Location] requires leave to be applied for in advance through [System Name], and requires that where an absence is unavoidable, [Manager Name] be informed before the start of the shift. 3. Prior steps This subject was discussed with you on [Date of Prior Discussion], when [Manager Name] explained the requirement to you. A note of that discussion is on your record. 4. Your explanation This was put to you on [Date Put to Employee]. You said [Employee's Explanation, recorded fairly]. We have considered this and [accepted it in respect of [Aspect] / do not accept it as an explanation for the absence, because [Reason]]. 5. Finding We find that you were absent on the dates stated without approval and without notifying your manager, and that this falls below the standard required. 6. What is required With immediate effect, all leave is to be applied for in advance through [System Name]. Where an absence is genuinely unavoidable, you must inform [Manager Name] before the start of your shift, by [Method of Notification]. 7. Consequence This is a written warning. If there is a further instance of unapproved absence, or of failing to notify, [Company Name] will consider further disciplinary action, which may include a final written warning. 8. Currency This warning will remain on your record for [Warning Currency Period] from the date of this letter. 9. Support If there is any circumstance affecting your attendance that we should know about, including anything for which an adjustment might help, speak to [HR Contact]. Raising it will not count against you. Please sign the enclosed copy to confirm you have received this letter. Signing confirms receipt only and does not record agreement with its contents. Yours sincerely, [Manager Name] [Manager Designation] Received: Signature: ______________________ Name: [Employee Name] Date: [Date]
Employee Warning Letter for written warning, conduct towards colleagues
Behaviour cases turn on what was actually said or done. Vagueness here is what makes the warning unusable at the next stage.
[Company Letterhead] Ref: [Reference Number] Date: [Date] STRICTLY PRIVATE AND CONFIDENTIAL [Employee Name] Employee code: [Employee Code] Designation: [Designation] Department: [Department] Sub: Written warning Dear [Employee Name], 1. The incident On [Date of Incident] at approximately [Time] in [Place], during [Context, for example a team meeting], you [Description of Conduct, stated specifically: what was said or done, and to whom]. This was witnessed by [Number] colleagues. 2. The standard The code of conduct at [Policy Location] requires all employees to treat colleagues with respect and prohibits [Relevant Provision]. 3. Prior steps [Either: This subject was raised with you on [Date] by [Manager Name]. / Or: There has been no prior discussion with you on this subject.] 4. Your explanation This was put to you at a meeting on [Date of Meeting], attended by [Attendees]. You said [Employee's Explanation, recorded fairly]. We have considered your explanation and [accepted it in respect of [Aspect] / do not accept that it justifies the conduct, because [Reason]]. 5. Finding We find that the conduct described above occurred, and that it falls below the standard required by the code of conduct. 6. What is required You are required to conduct yourself in accordance with the code of conduct at all times. Specifically, [Specific Behaviour Required, stated as an observable action rather than an attitude]. 7. Consequence This is a written warning. Any repetition of this or similar conduct will result in further disciplinary action, which may include a final written warning or, depending on the seriousness, dismissal. 8. Currency This warning will remain on your record for [Warning Currency Period] from the date of this letter. 9. Your right to respond If you disagree with this warning, you may set out your position in writing to [Appeal Contact] within [Appeal Period] of receiving this letter, and it will be considered. Please sign the enclosed copy to confirm receipt. Signing confirms receipt only and does not record agreement. Yours sincerely, [Manager Name] [Manager Designation] Received: Signature: ______________________ Name: [Employee Name] Date: [Date]
Employee Warning Letter for final written warning
This rung exists to put dismissal in view. If the letter does not say that, it is not a final warning whatever it is headed.
[Company Letterhead] Ref: [Reference Number] Date: [Date] STRICTLY PRIVATE AND CONFIDENTIAL [Employee Name] Employee code: [Employee Code] Designation: [Designation] Department: [Department] Sub: FINAL WRITTEN WARNING Dear [Employee Name], 1. The incident On [Date of Incident], you [Description of Conduct, stated specifically]. 2. The standard This falls below the standard required by [Policy or Rule Name] at [Policy Location]. 3. Prior warnings You received a written warning dated [Date of Prior Warning] in respect of [Subject of Prior Warning]. That warning remains current until [Prior Warning Expiry Date] and stated that a further instance would result in further disciplinary action. 4. The meeting A disciplinary meeting was held on [Date of Meeting], attended by [Attendees]. You were informed of the allegation in advance by letter dated [Date of Invite] and were given the opportunity to respond and to be accompanied by [Accompaniment Permitted]. 5. Your explanation You said [Employee's Explanation, recorded fairly]. We have considered this and [Outcome of Consideration, with reasons]. 6. Finding We find that the conduct described occurred, that it falls below the required standard, and that it occurred while a written warning was current. 7. What is required [Specific Change Required], with immediate effect. 8. Consequence This is a FINAL WRITTEN WARNING. If there is any further instance of this or similar conduct, or any other misconduct, while this warning is current, [Company Name] will consider terminating your employment. 9. Currency This final written warning will remain on your record for [Final Warning Currency Period] from the date of this letter. 10. Appeal You may appeal against this warning by writing to [Appeal Contact] within [Appeal Period] of receiving this letter, setting out your grounds. Your appeal will be considered by someone not involved in this decision, and you will be told the outcome in writing. Please sign the enclosed copy to confirm receipt. Signing confirms receipt only and does not record agreement. Yours sincerely, [Signatory Name] [Signatory Designation] Received: Signature: ______________________ Name: [Employee Name] Date: [Date]
Employee Warning Letter for counselling note, before any warning
Not a warning, and it should not be headed as one. This is the record that makes a later warning fair, because it shows the person was told first.
[Company Internal Note] RECORD OF COUNSELLING DISCUSSION Date of discussion: [Date] Employee: [Employee Name], [Employee Code] Designation: [Designation] Department: [Department] Discussion held by: [Manager Name], [Manager Designation] Also present: [Other Attendees, or "None"] 1. WHAT WAS DISCUSSED [Description of the conduct or issue raised, with the dates or instances it relates to.] 2. WHY IT WAS RAISED [The standard, expectation or policy the conduct fell short of, and the effect it had.] 3. WHAT THE EMPLOYEE SAID [The employee's response, recorded as they put it, including any circumstance they raised.] 4. WHAT WAS AGREED [Specific action, by whom, and by when. Where support was offered, what it is.] [Manager Name] to: [Action] [Employee Name] to: [Action] 5. WHAT HAPPENS NEXT [Manager Name] will review the position with [Employee Name] on [Review Date]. This discussion is a counselling conversation. It is not a disciplinary warning and does not form part of any disciplinary record. It is noted so that both parties have the same recollection of what was discussed and agreed. A copy of this note has been given to [Employee Name]. NOTE FOR THE MANAGER: keep this factual. Do not head it as a warning, do not state consequences, and do not use the counselling route for conduct that needs a formal process. If the conduct is serious, start the disciplinary procedure rather than recording a conversation about it. [Manager Name] [Manager Designation] Date: [Date]
Employee Warning Letter for written warning, breach of a specific policy
Where the breach is of a rule with a written threshold, the warning becomes straightforward: name the rule, state the breach against it.
[Company Letterhead] Ref: [Reference Number] Date: [Date] STRICTLY PRIVATE AND CONFIDENTIAL [Employee Name] Employee code: [Employee Code] Designation: [Designation] Department: [Department] Sub: Written warning Dear [Employee Name], 1. The incident On [Date of Incident], you [Description of the Breach, for example: submitted an expense claim of [Claim Description] which did not comply with the requirements of the travel and expense policy]. 2. The rule breached [Policy Name] at [Policy Location], clause [Clause Reference], requires [The Requirement]. Your [Action] did not comply with that requirement because [Specific Reason]. 3. Prior steps [Either: This is the first occasion on which this has arisen. / Or: A similar issue was raised with you on [Date].] 4. Your explanation This was put to you on [Date Put to Employee]. You said [Employee's Explanation, recorded fairly]. We have considered your explanation and [Outcome of Consideration, with reasons]. 5. Finding We find that the requirement at clause [Clause Reference] was not complied with on the occasion described. 6. What is required With immediate effect, you are required to comply with [Policy Name], and specifically to [Specific Requirement]. If you are unsure whether something complies, ask [Policy Owner Contact] before rather than after. 7. Consequence This is a written warning. A further breach of this policy will result in further disciplinary action, which may include a final written warning. 8. Currency This warning will remain on your record for [Warning Currency Period] from the date of this letter. 9. Appeal You may appeal by writing to [Appeal Contact] within [Appeal Period] of receiving this letter. A copy of [Policy Name] is enclosed for your reference. Please sign the enclosed copy to confirm receipt. Signing confirms receipt only and does not record agreement. Yours sincerely, [Manager Name] [Manager Designation] Received: Signature: ______________________ Name: [Employee Name] Date: [Date]
What it has to contain
| Element | Why it matters |
|---|---|
| The specific incident, with a date | A warning about a general pattern with no instances attached cannot be answered by the employee and cannot be relied on later. If the incident cannot be described with a date and a place, it is not ready to be a warning. |
| The standard the conduct fell short of | Naming the policy, rule or standing order turns a manager's displeasure into a breach of something the employee could have read. Where no written standard exists, the warning is harder to sustain and the gap is worth fixing first. |
| The employee's explanation, recorded | Putting the allegation before deciding is what makes the process fair, and recording the response is what shows it happened. Where the explanation was not accepted, the letter should say why, not omit it. |
| A stated consequence | The sentence about what follows if it recurs is what distinguishes a warning from a complaint. It is also what makes the next step defensible, because the employee knew what was at stake. |
| The currency of the warning | A warning that never expires is treated as unfair, and one with no stated period leaves an argument about whether an incident two years later counts as a repetition. State a period and apply it. |
| A route to challenge it | An employee who disputes the finding needs somewhere to say so. An appeal considered by someone not involved in the decision costs little and removes the complaint that there was no way to be heard. |
| Acknowledgement of receipt, not agreement | The employee may dispute the finding and still have received the letter. Asking for agreement produces a refusal to sign, which then becomes a second dispute on top of the first. |
How to write one
- Confirm this is conduct, not capability. Ask whether the person is choosing not to do something or trying and falling short. Conduct goes to a warning. Capability goes to a performance improvement plan. A warning issued for a capability gap achieves nothing and delays the process that would have helped.
- Establish the facts before writing anything. Get the dates, the place, what was said or done, and who saw it. A warning drafted from an impression and supported afterwards reads as a conclusion looking for evidence.
- Check what procedure binds you. Where standing orders apply to the establishment, they govern the disciplinary procedure and set out what counts as misconduct. Where they do not, your own disciplinary policy does. Either way, follow the process that applies rather than the one in a template.
- Put it to the employee before deciding. Tell them what is alleged, give them enough notice to think about it, hold the meeting, and listen. A warning issued without hearing the person is the single most common procedural defect, and it is entirely avoidable.
- Decide the rung honestly. A first instance ordinarily gets a first written warning. Jumping to a final warning because the manager is frustrated undermines the ladder, and issuing three identical written warnings in place of escalation does the same thing from the other direction.
- Write it the same day, and issue it promptly. Warnings delivered weeks after the meeting lose their connection to the incident and suggest the organisation was deciding what to do. Draft it while the meeting is fresh and issue it within a few days.
- Diarise the expiry. Record when the warning lapses and remove it from consideration when it does. Relying on an expired warning as a prior step is a defect that is easy to spot and hard to explain.
Telling conduct apart from capability
Almost every problem with warning letters traces back to one question asked wrongly at the start: is this person choosing not to do something, or trying and falling short?
Conduct is a choice. Not turning up without telling anyone, being abusive to a colleague, submitting a claim that is not genuine, ignoring a safety rule. The instrument is a warning, and it works by telling the person to stop and saying what follows if they do not.
Capability is a gap. The person is doing the work and the work is not good enough. A warning cannot fix that, because there is nothing for the employee to stop doing. Telling someone to be better, with a consequence attached, produces anxiety rather than improvement, and the employer ends up with a file full of warnings and an unresolved performance problem.
Two practical consequences follow. Where the answer is capability, use a performance improvement plan with objectives, support and a review date. And where a case genuinely has both elements, run them separately rather than folding the capability issue into a conduct process, because the two need different evidence and lead to different places.
What procedure actually binds you
Before choosing a rung, it is worth establishing which procedure the organisation is required to follow, because that is not always its own policy.
Under section 28 of the Industrial Relations Code, 2020, the standing orders Chapter applies to every industrial establishment in which three hundred or more workers are employed, or were employed on any day of the preceding twelve months. Where the Chapter applies, standing orders govern the conditions of service they cover, and those characteristically include what constitutes misconduct and the procedure for dealing with it. A disciplinary policy that conflicts with applicable standing orders does not displace them.
Where the Chapter does not apply, the organisation's own disciplinary policy governs, together with anything the appointment letter incorporates. That is a lower bar procedurally, but it is still a bar the employer set for itself, and departing from your own published process is one of the easier defects for an employee to point at.
Under section 4 of the same Code, every industrial establishment employing twenty or more workers must have one or more Grievance Redressal Committees, with equal numbers representing the employer and the workers. An employee who disputes a warning may well route it there.
The meeting before the letter
The letter records a decision. The meeting is where the decision is actually made, and skipping it or running it as a formality is what most often undoes an otherwise reasonable outcome.
A workable meeting has a small number of features. The employee is told in advance what the allegation is, in enough detail to prepare, and with enough notice to think. They are told they may be accompanied, where the organisation permits that. They are shown the material relied on rather than hearing it summarised. They are given the chance to give their account without interruption. And notes are taken.
The part managers find hardest is genuinely holding the outcome open. If the letter is already drafted, the meeting is theatre and the employee will sense it. The test is whether an explanation could have changed the result. If not, the meeting was not a hearing.
Where an explanation raises something new, such as a health issue, a caring responsibility, or an instruction from another manager, the right response is to adjourn and check rather than to press on. Those are the cases where issuing the warning anyway looks worst afterwards.
Currency, and letting warnings expire
A warning should have a stated life and should end at the end of it.
Six to twelve months for a written warning and twelve months for a final written warning are common, and the exact period matters less than stating one and applying it. The reason to have a period at all is that a warning is intended to correct behaviour, and someone who has corrected it should not carry the record indefinitely.
Two failures recur. The first is silence: the letter states no period, and years later the employer treats a spent warning as a live prior step, which is straightforward to challenge. The second is administrative: the period is stated and nobody tracks it, so the warning sits on the file and gets counted whenever the file is read.
The fix is to record the expiry date as a date, diarise it, and check the record before treating anything as a prior step. An escalation built on an expired warning is a defect that is easy for someone else to spot and difficult to explain away.
Common mistakes
| Mistake | Why it causes trouble | What to do instead |
|---|---|---|
| Issuing a warning for poor performance | A warning tells someone to stop doing something. Where the person is already trying, there is nothing to stop, so the conduct continues and the employer has documented the wrong problem. | Use a performance improvement plan for capability, with objectives, support and a review date, and keep warnings for conduct. |
| No stated consequence | The letter records displeasure without putting anything at stake. When the conduct recurs and the employer escalates, the employee can fairly say they were never told what would follow. | State plainly what will happen if it recurs, and make sure the stated consequence is one the organisation would actually apply. |
| Deciding before hearing the employee | The letter is drafted before the meeting and the meeting becomes a formality. Where the employee had an explanation that would have changed the outcome, the process failed in a way that is visible on the file. | Hold the meeting first, take notes, and draft afterwards. Record the explanation and, where it was rejected, the reason. |
| Vague description of the conduct | Wording such as unprofessional behaviour or a bad attitude cannot be answered or verified, and at the next stage there is no record of what the employee was warned about. | Describe what was said or done, when, where, and to whom, in terms a reader who was not present would understand. |
| Three written warnings instead of escalation | Issuing the same rung repeatedly signals that nothing follows, which is exactly the opposite of the intended message, and makes an eventual dismissal look abrupt. | Escalate deliberately: written warning, then final written warning, then the stated consequence. If you are not prepared to escalate, reconsider whether a warning was the right instrument. |
| Relying on an expired warning | A prior warning outside its stated currency is treated as spent. Using it as the basis for escalation is a defect that undermines an otherwise sound decision. | Diarise expiry dates and check the record before treating anything as a prior step. |
Statutory reference
- Act
- Industrial Relations Code, 2020
- Key limits
- This page addresses how to record a warning and the sequence it sits in. It does not state what standing orders must provide for on misconduct or the procedure for certifying them, and it states no rule on termination, which is dealt with separately.
| Provision | What it says |
|---|---|
| Section 28 | Applies the standing orders Chapter to every industrial establishment in which three hundred or more workers are employed, or were employed on any day of the preceding twelve months. |
| Section 4 | Requires every industrial establishment employing twenty or more workers to have one or more Grievance Redressal Committees, with equal numbers representing the employer and the workers. |
Frequently asked questions
What should a warning letter to an employee contain?
The specific incident with a date and place, the standard or policy it fell short of, and any prior steps on the same subject. The employee's explanation and how it was considered, the finding, what change is required, and what will follow if it recurs. Then how long the warning stays on record, and a signature block recording receipt rather than agreement.
How many warnings before termination in India?
There is no fixed number. What matters is that the process the employer is bound by was followed, that the employee was told what was wrong and what would follow, and that the escalation was proportionate. Where standing orders apply to the establishment, they set out the procedure and should be followed rather than a number remembered from a template.
Can an employee refuse to sign a warning letter?
Yes, and it usually happens when the signature block asks for agreement rather than receipt. Reword it to record receipt only. If the employee still declines, note the refusal on the letter, have a witness record it, send a copy by email the same day, and proceed.
What is the difference between a warning letter and a show cause notice?
A show cause notice comes before any finding: it sets out what is alleged and asks the employee to explain before a decision is made. A warning letter comes after: it records that the conduct was found to have occurred and states what follows if it recurs. Issuing a warning without first putting the allegation reverses the order.
How long does a warning letter stay on an employee's record?
For the period the letter states, commonly six to twelve months for a written warning and twelve months for a final written warning. The period should be stated in the letter and diarised, because relying on a warning after it has lapsed is an easy defect to identify.
Can a warning letter be issued for poor performance?
It can be, but it rarely helps. A warning tells someone to stop doing something, and where the person is already trying there is nothing to stop. Capability shortfalls are better addressed through a performance improvement plan with measurable objectives, stated support and a review date.
Does the employee have to be heard before a warning is issued?
Putting the allegation to the employee and considering their response before deciding is what makes the process fair, and it is the step most often skipped. Where standing orders or the organisation's own policy set out a procedure, that procedure has to be followed, and failing to follow your own published process is straightforward for an employee to point at.
Should a warning letter be sent by email or given in person?
Give it in person at the end of the process, take acknowledgement of receipt, and follow with an emailed copy the same day so there is a record of delivery. A warning that first appears in an inbox, with no meeting beforehand, tends to be the one that is disputed.
Disciplinary records in Engage
Engage keeps the counselling note, the meeting record, the warning and its expiry date against the employee rather than in a manager's drive, so the sequence is visible to whoever picks the case up next. Expiry dates raise reminders and lapsed warnings drop out of the current record, which prevents an escalation being built on a warning that has already spent.
Book a demo