How to Document a Performance Improvement Plan by Email: A Guide for HR

A performance improvement plan is one of the highest-risk documents in HR. Done right, it protects the company and gives the employee a fair opportunity to succeed. Done wrong — or documented poorly — it becomes exhibit A in a wrongful termination or discrimination claim.

Email is where most PIP documentation lives or dies. Here's how to use it correctly.

Why Email Documentation Matters for PIPs

When a terminated employee brings a legal claim, one of the first questions their attorney asks is: when did the company first raise performance concerns, and what was communicated?

If the answer is "six weeks before termination, in a verbal conversation we didn't document," you have a problem. If the answer is "nine months ago, in a written email outlining specific concerns, followed by a formal PIP with documented check-ins and clear outcomes," you have a defensible record.

The quality of your email documentation doesn't just affect litigation outcomes. It affects whether claims are filed at all. Attorneys evaluating potential cases look at the paper trail. A well-documented PIP process often signals that a claim will be expensive and hard to win.

Before the PIP: Documenting the Performance Issues

The PIP should not be the first documentation of performance concerns. Courts and juries are skeptical of performance problems that appear on paper for the first time shortly before termination.

Before the formal PIP, your email record should show:

Specific, contemporaneous feedback. When a manager has a performance conversation with an employee, they should follow up by email. Not a long formal document — a brief summary of what was discussed and what the expectation is.

Example: "Following up on our conversation today about the Johnson account. As we discussed, the project timeline has slipped by three weeks. I need you to send the client a revised schedule by Friday and keep me updated weekly on progress."

Patterns, not incidents. A single missed deadline is not a PIP case. A pattern of missed deadlines documented over six months is. Your pre-PIP emails should show the pattern — multiple conversations, multiple opportunities to correct.

Clarity about expectations. Vague concerns like "attitude issues" are hard to defend. Specific behavioral expectations that are communicated in writing and not met are defensible.

The PIP Email: What It Must Include

When the formal PIP is issued, an email should accompany the written document. The email should:

Clearly identify the performance issues. Specific, observable behaviors or results. Not personality assessments or vague characterizations.

State the expected standard. What does "acceptable performance" look like? Be precise. "On time" is vague. "Project status reports submitted by 5 PM every Friday" is not.

Set the timeline. How long is the PIP period? When will performance be evaluated?

Describe the support available. What resources, training, or manager involvement is the company providing?

State the consequences. If performance does not improve to the stated standard within the stated timeframe, what happens? Say it plainly.

Request confirmation. Ask the employee to reply confirming receipt and acknowledging that they've reviewed the document.

This email, combined with the signed PIP document, creates the foundation of your record.

Check-In Documentation During the PIP

A PIP with no contemporaneous documentation during the improvement period is a weak PIP. Regular email check-ins serve two purposes: they give the employee genuine feedback and opportunity to course-correct, and they create a real-time record of performance during the period.

Good check-in emails:

• Reference specific performance against the stated goals
• Note what's improved and what hasn't
• Keep the employee informed of where they stand
• Are regular and consistent, not just saved for bad weeks

Bad check-in emails: "Just checking in." "Keep up the good work." Emails that don't actually document anything about performance.

If an employee is not on track during the PIP, that needs to be in the email record — in plain language, during the PIP period, not assembled after the fact.

The Outcome Email

When the PIP concludes — whether the outcome is successful completion, extension, or termination — document it by email.

For successful completion: acknowledge the improvement specifically, note the standards that were met, and make clear the employee is no longer on a PIP.

For termination: do not go into extensive detail in the termination email itself. The details are in the prior documentation. The termination email should state the decision, effective date, and logistics. The substance is in the record you've built.

Common Documentation Failures

Retroactive documentation. Writing up performance concerns for the first time after a complaint is filed or after termination. Courts are skeptical. Create the record as you go.

Inconsistent language between verbal and written. Telling an employee verbally that things are improving while sending emails that document ongoing problems creates a credibility problem. Be consistent.

Not capturing employee responses. If an employee pushes back on a PIP or disputes the performance concerns by email, document your response. Ignoring a dispute in the email record doesn't make it go away — it makes it look like you had no answer.

Generic emails without specifics. "Performance has not improved" is not documentation. "The Q2 revenue target was $400K. Actual revenue was $220K, representing the third consecutive quarter below target" is documentation.

The Bigger Picture

A well-documented PIP process is fair to employees and protective of the company. It forces managers to be specific about what they need, gives employees a genuine chance to understand and meet expectations, and creates a record that is defensible in any forum.

The email thread from the first performance conversation through the PIP conclusion is the most important document in any termination-related employment claim. Build it carefully.