Progressive Discipline Examples: What to Say at Each Step

Understanding the progressive discipline structure is the easy part. Verbal warning. Written warning. Final warning. Termination. Most managers can recite that list.

What most managers cannot do is sit down across from an employee and know what to actually say. The progressive discipline structure they understood in the abstract has to become specific words in a real conversation about a real person. That is where it falls apart, either because the manager goes in vague and nothing lands, or because they say something that creates more problems than the original issue.

This post is about the language. See How to Write a Progressive Discipline Policy (With Examples) if you want to see the actual structure of the framework. I am going to walk through three of the most common situations when it comes to having a discipline discussion: attendance, performance, and conduct. I will show you what each step of progressive discipline actually sounds like. Not scripts to read word for word, but real examples of the specificity and structure that make these conversations work.

Before we get into the examples, one ground rule: progressive discipline only holds up legally and practically when it is specific. Every example below names specific dates, specific behaviors, and specific expectations. If your conversations sound like "we've talked about this before" or "your attitude has been a problem," you do not have progressive discipline. You have a collection of conversations that will do nothing for you if the situation escalates. Specificity is not a style preference. It is the whole point.

Step 1: The Verbal Warning

The verbal warning is a documented conversation. The word "verbal" describes how you deliver it (in person), not whether you write it down afterward. Every verbal warning needs a brief contemporaneous note in the employee's file the same day. If you skip that step, the conversation never happened from a documentation standpoint. As the old HR adage goes, “if it isn’t documented, it didn’t happen”.

The conversation itself needs to do four things: state the specific issue, give the employee the chance to respond, set a clear expectation, and tell them what happens next if things do not change.

Attendance example: "I want to talk about your attendance over the past three weeks. You've been late four times, on the 3rd, 7th, 14th, and 19th, each by at least 20 minutes. Our expectation is that you're at your workstation ready to work at 8:30am. I want to hear if there's something going on I should know about."

Let them respond. Keep in mind that there could be a legitimate situation (personal or otherwise) that is preventing them from meeting expectations. But the conversation still needs to happen.

Absent a legitimate reason for the tardiness, say: "Going forward, I need you here at 8:30am every scheduled day. If something happens that's going to make that impossible, I need you to reach out before your shift starts, not after. I'm going to write up a summary of this conversation for your file. If the pattern continues, the next step is a written warning."

Performance example: "I want to talk about your last three project reports, the ones due on the 5th, 12th, and 19th. All three came in after the 5pm deadline, and two of them were missing sections that had to be followed up before we could send them to the client. The expectation is that reports are complete and submitted by 5pm on the due date. Walk me through what happened."

Let them respond. Then say: "Going forward, I expect you to complete reports by 5pm on the due date, every time. If you're going to miss a deadline, I need to know 24 hours in advance, not after it's already past. I'm documenting this conversation, and if we need to have the same conversation again, the next step is a written warning."

Conduct example: "I need to talk about what happened in Tuesday's team meeting. While Maya was presenting, you interrupted her four times before she finished, and you responded to two of her points by saying 'that's not realistic' without any explanation. I could see the rest of the team check out after that. The standard here is that everyone gets to finish before others respond, and pushback needs to be specific, not dismissive. Is there something going on with that working relationship that I should know about?"

Let them respond. Then say: "I need you to let people finish in team settings, and when you disagree, I need you to say why specifically. If we see the same behavior again, the next step is a written warning."

The note you write afterward: It does not need to be long. Something like: "On [date], I met with [employee] to discuss [specific issue]. I described [specific examples with dates]. Employee stated [their response]. I communicated the expectation that [specific standard] effective immediately, and that continued non-compliance would result in a written warning. Employee acknowledged the conversation." That is enough. Date it, save it, file it.

Step 2: The Written Warning

The written warning is a formal document, not a longer version of the verbal warning conversation. It references the prior verbal warning, documents what happened after that conversation, states the expectation again, and makes clear what happens next. The employee signs it to acknowledge receipt. In most situations, having a witness present is best practice. This prevents potential “he said / she said” arguments later.

A few things about the delivery: walk through the document with the employee and give them a moment to actually read each section before moving on. Then ask if they have questions. Then ask for the signature. Tell them clearly that the signature means they received it, not that they agree with it. If they disagree, they can put their response in writing and you will attach it to the document. If they refuse to sign entirely, note that on the document with the date and have a witness co-sign.

Attendance document language example: "This written warning follows the verbal warning issued on [date] regarding attendance. Since that conversation, you have had three additional late arrivals: [dates]. This pattern is inconsistent with our attendance policy, which requires you to be at your workstation ready to work at your scheduled start time of 8:30am. Effective immediately, you are expected to arrive at or before 8:30am every scheduled workday. If a late arrival is unavoidable, you must contact your manager before 8:30am with an explanation. Failure to meet this expectation may result in further disciplinary action, up to and including termination."

Performance document language example: "This written warning follows the verbal warning issued on [date] regarding report submission. Since that conversation, you submitted two additional reports after the 5pm Friday deadline: [dates and times]. One report submitted on [date] was also missing the budget summary section. Effective immediately, all reports must be submitted complete and on time by 5pm on the assigned due date. If a deadline is at risk, you must notify your manager at least 24 hours in advance. Failure to meet this expectation may result in further disciplinary action, up to and including termination."

Conduct document language example: "This written warning follows the verbal warning issued on [date] regarding conduct in team settings. Since that conversation, on [date] you interrupted a colleague three times during their presentation and responded to their proposal with dismissive comments in front of the group. For example, [list examples from each date]. Effective immediately, you are expected to allow colleagues to complete their thoughts before responding, and to express disagreement specifically and constructively rather than dismissively. Failure to meet this standard may result in further disciplinary action, up to and including termination."

Step 3: The Final Written Warning

The Final Written Warning follows the same structure as the written warning with two additions: explicit language that the next step is termination, and a specific review date, typically 30 days out. These are not optional. Without them, the "final" warning has no teeth and no defined endpoint. The addition that turns a written warning into a final written warning:

"This is a final written warning. Failure to meet the expectations described in this document from this point forward will result in termination of your employment. Your compliance with these expectations will be reviewed on [specific date]."

At the review date: If the behavior has improved: "Since your final written warning on [date], your [attendance / report submissions / conduct in team settings] has met the expectation we set. I'm noting that in your file. I expect this to continue."

If behavior has not improved: move to Step 4.

Step 4: Termination

Keep it direct and brief. Connect it to the documented process. Do not try to soften it by revisiting the whole history. the employee already knows the history. The meeting is to communicate the decision and cover the logistics, not to relitigate everything that led here. A good rule of thumb to keep in mind is that any person being terminated should not be surprised by the decision to terminate. If you do it correctly, the employee has been on notice, on several occasions, that their behavior or performance has not been meeting expectations.

The opening: "I need to let you know that we're ending your employment, effective today."

The reason: For a performance or conduct termination, keep it at a few sentences: "This follows the verbal warning on [date], the written warning on [date], and the final written warning on [date], which documented continued [attendance issues / missed deadlines / conduct in team meetings] despite clear expectations and a genuine opportunity to improve."

For a layoff: "This is a business decision to eliminate this position. It is not a reflection of your performance."

Then go straight to logistics: "I want to cover what happens next. Your final pay will be [issued today / mailed by [date]] and covers [hours worked through today / any accrued PTO per our policy]. Your benefits coverage ends on [date], and you'll receive COBRA information within the next two weeks. I need to collect [laptop / badge / keys] before you leave today. I am putting this all in a packet for you. Take a moment to read through it and let me know if you have questions about any of the logistics."

Keep the rest of the meeting on logistics. If the employee wants to argue the decision, listen briefly and then: "I understand you see it differently. The decision has been made and it is final."

The Pattern Across All of These

Read back through these examples and you will see the same things every time: specific dates, specific behaviors, specific expectations, specific consequences. At no point does the language say "your performance has been a concern" or "you need to adjust your approach." At every step, there is something concrete. Something that either happened or did not, documented on a date, tied to a standard that was communicated clearly. That is what makes this defensible. Not the steps themselves. Courts and agencies are not impressed by the existence of a verbal warning. They are impressed by documentation that demonstrates the employee knew exactly what was expected, had a genuine opportunity to meet that standard, and chose not to. The language is how you show that.

So, write it down. Be specific. Follow through on the review dates. That is the whole system. If you don’t yet have a Progressive Discipline policy outlined in your employee handbook, our template includes the full four-step framework with documentation requirements at each level, immediate termination offense definitions, manager guidance, and a signed acknowledgment block. The written foundation you need before you need to use it.

→ Progressive Discipline Policy Template — $35 | pragmatichrgroup.com

Editable Word document + PDF. Instant download. Created by a SHRM-SCP certified HR professional.

Questions about this or other HR topics? Visit pragmatichrgroup.com for more resources.