- name
- progressive-discipline
- description
- Use when designing or applying progressive discipline — covers the escalating sequence, documentation, gross misconduct exceptions, and consistency.
# Progressive Discipline
## Purpose
Progressive discipline is the escalating sequence of corrective action used to address performance or conduct issues that fall short of immediate termination. The system serves three purposes:
1. **Give the employee a real opportunity to improve** (most people respond to clear feedback)
2. **Document the company's process** (legal and audit defensibility)
3. **Protect against arbitrary action** (consistency across managers and employees)
## Standard Sequence
| Step | Tool | When |
|------|------|------|
| 1 | Coaching / verbal warning | First instance; documented in 1:1 notes |
| 2 | Written warning | Repeat or more serious; formal document |
| 3 | Final written warning | Last chance; clear consequence stated |
| 4 | Suspension (rarely) | Pending investigation, or specific situations |
| 5 | Termination | Prior steps have not produced change |
Not all situations require all steps. Match the response to the conduct.
## When to Skip Steps (Gross Misconduct)
Some conduct warrants termination without progressive steps. Common categories:
- **Violence or threats of violence**
- **Theft or fraud**
- **Harassment or discrimination** (substantiated, severe)
- **Serious safety violations**
- **Falsification of records**
- **Significant breach of confidentiality or IP**
- **Drug or alcohol policy violation in safety-sensitive roles**
- **Insubordination of a serious nature** (rare; requires careful analysis)
Document the rationale. Counsel review is essential. Ensure consistency with how the company has handled comparable conduct previously.
## What Each Step Should Contain
### Verbal Warning / Coaching
- Specific behavior at issue
- Why it's a problem
- What's expected instead
- Documented in manager notes (1:1 doc, written record)
- Employee aware it's a corrective conversation, not casual
### Written Warning
- Date
- Specific behavior with dates
- Policy or expectation violated
- Prior conversations referenced
- Required behavior change (specific, measurable where possible)
- Time frame for improvement
- Consequences if behavior doesn't change
- Support being offered (training, coaching, accommodation if applicable)
- Employee response captured
- Employee signature (or "declined to sign" with witness)
- Distribution (employee copy, HR file, manager file)
### Final Written Warning
- Same structure
- Explicit: "This is a final warning. Failure to [specific behavior] will result in termination."
- Often paired with a brief improvement period
- Counsel involvement increases at this stage
### Suspension
- Rare in most modern workplaces
- Appropriate during investigation when continued presence creates risk
- Paid or unpaid (jurisdiction-specific; FLSA implications for exempt employees)
- Time-bounded
- Documented rationale
### Termination
- See `difficult-conversations` skill and `offboarding-architect` agent
- Brief, clear, kind, prepared conversation
- Severance per policy
- Counsel review essential
## Documentation Standards
The single most consequential aspect of progressive discipline.
Documentation must:
- **Be contemporaneous** (close to the event)
- **Cite specific behavior** (not character, mood, attitude)
- **Reference policy or expectation** violated
- **Capture the conversation faithfully** (employee response included)
- **Be consistent across employees** (same template, same standard)
- **Be free of legally problematic language** (no comments about protected characteristics, no speculation about motive)
Sloppy documentation:
- Fails to protect the employee (when memory fades)
- Fails to protect the company (in legal disputes)
- Suggests the discipline was driven by something other than what's stated
## Consistency: The Comparator Test
For any disciplinary action, ask:
- How have we handled comparable conduct before?
- Is this employee being treated the same as comparable past employees?
- If different, is the difference explained by specific facts (not by demographic, age, leave history, etc.)?
A pattern of treating comparable conduct differently — especially correlated with protected characteristics — is the strongest pattern in employment litigation.
Maintain a precedent log (under privilege where possible): for each disciplinary action, the conduct, the outcome, and the rationale. Reviewed by HR + counsel before applying inconsistent treatment.
## Performance vs. Conduct vs. Capacity
Progressive discipline is designed for **conduct issues** — the employee can change, but isn't.
For **performance issues** (the employee is trying but can't deliver), consider:
- Coaching first
- Role / scope adjustment
- Performance Improvement Plan (PIP) — see `performance-management-systems`
- Demotion or move
Treating a performance issue as a conduct issue (or vice versa) creates legal exposure and corrodes trust.
For **capacity issues** (the employee can't deliver due to medical / disability / personal):
- Engage the accommodations interactive process (`employee-relations-partner`)
- Don't discipline what's actually a disability
- Engage counsel; ADA implications are constant
## PIP vs. Discipline
Both are corrective. Different tools:
- **PIP**: performance-focused; specific outcomes to demonstrate; time-bounded; investment in support
- **Discipline**: conduct-focused; specific behavior to stop or start; documented warnings
Some situations warrant both (e.g., performance plus attendance issues). Document distinctly.
## Pretext Risk
A common legal exposure: progressive discipline applied to one employee that another employee (with comparable conduct) didn't receive — and the affected employee is in a protected class.
The legal frame: "pretext" — discipline as cover for an unstated, illegitimate reason. Avoid by:
- Consistency
- Documentation that traces clearly from conduct to consequence
- Counsel review for protected-class employees, recently-protected-leave employees, recently-complained employees
## Manager Coaching
Most progressive discipline failure happens at the manager level:
- Avoidance of the verbal warning step (skipping straight to written when behavior persists, with no record)
- Vague documentation
- Inconsistent application across the team
- Discipline applied long after the conduct (loss of credibility and legal weight)
Manager training should include:
- When to use progressive discipline
- How to document
- How to deliver the conversation
- When to involve HR / counsel
- The comparator test
## Common Failures
- **No verbal warning step**: written warning surprises the employee
- **Vague documentation**: "attitude problem" without behavioral specifics
- **Reconstructed after the fact**: employee terminated, file written up post-decision
- **Inconsistent application**: same conduct, different outcome, demographic patterns
- **Discipline used to cover ER cases**: respondent in a harassment investigation gets a sudden performance write-up
- **Skipping straight to termination** without prior steps when prior steps were warranted
- **Manager bypassing HR**: documentation inconsistent; legal review missed
- **"Final written warning" issued repeatedly**: the word "final" loses meaning
## Cross-References
- `employee-relations-partner` agent
- `workplace-investigations` skill
- `performance-management-systems` skill (PIP track)
- `difficult-conversations` skill
- `policy-writer` agent
- `legal-and-jurisdictional-boundaries` rule
## Key References
- SHRM body of knowledge on corrective action
- EEOC guidance on adverse employment actions
- State-specific employment law (varies; counsel-driven)
- McCord, P. (2017). *Powerful* — on consistent honest documentation
View on GitHub