Progressive Discipline

Progressive discipline is an approach in which an employer responds to a performance or conduct problem with a sequence of increasingly serious steps, each one recorded, giving the employee notice of the standard, notice of the shortfall, and a chance to correct it.

For at-will employees it is a management practice rather than a legal obligation. In a unionized workplace, or in a public employer operating under a just cause standard, something close to it is usually required by the agreement or by policy, and the procedural details become enforceable.

The typical sequence, and why it is a framework not a ladder

A common sequence runs: a documented coaching conversation, a written warning, a final written warning sometimes paired with a suspension or a performance improvement plan, and then termination. Some employers add a verbal warning as a distinct first step, though a verbal warning that is not written down anywhere does not exist for any later purpose.

The sequence is a default, not an entitlement. Serious misconduct, such as violence, theft, harassment, falsification of records, or a safety violation that endangers others, is normally handled by immediate investigation and, if substantiated, immediate action at whatever level the conduct warrants. A policy that describes the steps as available options the employer may apply in any order, depending on the severity and circumstances of the conduct, preserves that flexibility.

Severity is not the only variable. The steps also reset or accumulate over time, and the policy should say how. Most employers treat a warning as active for a defined period, commonly six to twelve months, after which it stops counting toward escalation but stays in the file. Without that rule, either every past issue counts forever or nothing does, and managers make the call inconsistently.

A distinction worth keeping explicit: performance problems and conduct problems behave differently. A performance shortfall generally warrants support, a defined improvement period, and a measurable standard, because the assumption is the person is trying. A conduct problem warrants a clear instruction to stop, because the assumption is the person can comply immediately. Blending the two into one process produces improvement plans for people who broke a rule and warnings for people who need training.

Running a disciplinary step

The same sequence applies at every level, with the seriousness of the document changing rather than the method.

1. 1Establish the facts before the conversation. For conduct issues that means an investigation proportionate to the allegation, not a conclusion based on one account.
2. 2Identify the standard the employee did not meet and where it is written: a policy, a job description, a documented expectation, or a prior instruction. A standard that exists only in the manager's head is not a standard.
3. 3Check consistency. Look at how comparable situations involving other employees were handled, and be prepared to explain any difference on grounds other than who the employee is.
4. 4Check timing and context before acting. If the employee recently reported a concern, requested an accommodation, took protected leave, or raised a pay issue, the sequence needs review by HR before it proceeds, and the pre-existing documentation of the problem becomes important.
5. 5Write the document before the meeting, so the conversation is grounded in specifics rather than in recollection.
6. 6Hold the meeting in private, state the specific behavior and its effect, refer to the standard, and give the employee a genuine opportunity to respond. If new information emerges, pause rather than finishing the script.
7. 7State clearly what has to change, by when, and what happens if it does not. Ambiguity here is the single most common defect: an employee who leaves unsure whether they were disciplined was not put on notice.
8. 8Offer whatever support is real, such as training, tools, or a schedule change, and record it. If an accommodation need surfaces, stop the disciplinary track and start the interactive process.
9. 9Have the employee sign to acknowledge receipt, noting that signing indicates receipt and not agreement, and record a refusal to sign rather than treating it as a failed step.
10. 10Give the employee the chance to add a written response, and keep it with the document.
11. 11File the document in the personnel file and confirm the next-step trigger and any follow-up date are on someone's calendar.
12. 12Follow up on the date promised, whether the outcome is improvement, no change, or partial change. A step with no follow-up teaches the employee that the deadline was not real.

What a written warning has to contain

A warning is evaluated later on whether a stranger could read it and understand what happened. Most cannot.

• The date of the document and the dates of the incidents it addresses. Undated or vaguely dated warnings carry almost no weight.
• The specific behavior, described factually. "Missed the shift start on the fourth, seventh, and eleventh, arriving between twenty and fifty minutes late each time" rather than "has an attendance problem".
• The standard and where it comes from, quoted or referenced.
• The business effect: what the shortfall caused, in coverage, in errors, in cost, or in impact on others.
• What prior conversations occurred and when, so the chain is visible in the document itself rather than only across a set of files.
• The required change, stated in observable terms, with a date or a review period.
• Any support the employer is providing.
• The consequence of no change, stated plainly, including that further action up to and including termination may follow.
• Space for the employee's response, and their signature acknowledging receipt.
• The signature of the manager, and of the HR reviewer where the process calls for one.

Where it goes wrong

The failures are consistent, and each one shows up plainly in the file.

• Documentation created after the decision. A file where the first written record is dated days before the termination reads as the record of a decision already made.
• Vague language. "Attitude", "not a culture fit", and "communication issues" describe an impression rather than a behavior, and none of them can be corrected because none of them can be measured.
• Inconsistency between comparable employees. Two people with the same conduct and different outcomes is the most common evidentiary problem in a discipline case, and the explanation has to be something other than who they are.
• The surprise termination. An employee whose reviews were satisfactory and whose file is empty, terminated for long-standing performance problems, presents a contradiction the employer has to explain.
• Discipline that closely follows protected activity, such as a complaint, an accommodation request, a leave, or a wage question, without documentation that predates it.
• Steps with no follow-up, which signal that neither the deadline nor the consequence was real.
• Copying a template and leaving generic language in it, which suggests the specifics were never assessed.
• Skipping HR review on the final step, which is where consistency, timing, and legal exposure are supposed to be checked.
• Positive performance reviews issued while active warnings are open, which is common when review season and discipline are run by different processes and never reconciled.

The documentation chain is the point

When a termination is questioned, whether in a charge, a claim, an unemployment hearing, or an internal escalation, the employer has to answer two questions: what was the reason, and how do you know. The documentation chain answers both. A file containing a dated coaching note, a written warning specifying the behavior and the required change, a follow-up showing what happened next, and a final document referencing the earlier ones tells a coherent story that does not depend on anyone's memory.

That is also why the chain has to be built while things are happening rather than assembled at the end. Contemporaneous records are credible because they were created before the outcome was known. Reconstructed ones are not, and the difference is usually visible from the dates alone.

The secondary benefit is the one managers actually notice: a meaningful share of employees who receive clear, specific, early feedback correct the problem. A process designed only to build a termination file misses those cases entirely, because the employee never learns what to fix in time to fix it.