The Performance Conversation Follow-Up

Staff

Performance & Feedback

Direct

For when you've had a formal performance conversation with a staff member — and need a written record that is also fair to the human on the other end.

Use this after a formal performance conversation — the one where you named specific gaps, set expectations with dates, and both of you knew it was official. It sits one rung up from Naming It Early: that one is informal and consequence-free by design; this one is documentation with structure — gaps, expectations, support, a check-in date, and what's at stake.

The fairness test for this email: the staff member should be able to read it and know exactly what to do differently, by when, and what help they'll get. If it documents the problem but not the path, it's a court exhibit, not leadership.

BEFORE YOU SEND

Make it yours: this email is ready to use as-is for one common version of this situation — edit to your style and your situation's needs. The four bold sections describe a sample case — late arrivals and slow parent replies, with matching expectations, support, and next step. Rewrite all four for your situation, and the closing strength sentence too. Set the follow-up meeting 2–4 weeks out.
The conversation comes first, always — this email should contain nothing the staff member didn't already hear out loud. Surprises in a performance email destroy the trust the conversation built.
Make every expectation observable. "Better classroom management" can't be met or missed; "circle time starts by 9:15 with the full group seated" can.
Name real support. If the email lists expectations but the support line is "let me know if you need anything," you've handed them a test, not a plan.
Send it within a day, and calendar the check-in before you hit send. A missed check-in date on a performance plan tells your whole staff how seriously you take these.
Follow whatever formal process your center has (acknowledgment signature, HR file copy). This template is the communication layer, not a substitute for your documentation procedure.

EMAIL TEMPLATE — EDITABLE

CUSTOMIZE FREELY

Subject:

Our Conversation Today — Expectations and Support

Tone

Clear · Fair · Documented

Hi [First Name],

Thank you for the conversation today. These aren't easy meetings for anyone, and I appreciated that you stayed engaged with me all the way through it.

Here's a recap of what we covered — if anything doesn't match your memory of the conversation, tell me this week while it's fresh.

Where the gaps are. We talked about two specific areas: arrival time — you've been more than 15 minutes late six times this month, which leaves the toddler room out of ratio at opening — and parent communication, where two families this month received no reply to messages in the app for over 48 hours.

What needs to change, and by when. Starting Monday: clocked in and in your room by 7:30, and parent messages answered within 24 hours on your working days.

How I'll support you. If the morning schedule itself is the obstacle, I'm open to talking about your shift — but that conversation has to happen before the next late arrival, not after. And I'll set up the app's auto-reminder so messages don't slip past a busy morning.

Where this goes. We'll meet again on [Date] to look at how these weeks went. I want to be straightforward with you: if we don't see consistent change by then, the next step is a formal written warning under our personnel policy. You deserve to know exactly where things stand.

I also want this in writing: the bond you've built with the children in your room is real — parents mention you by name, and I see why. That's why this conversation was worth having. I'm not documenting a problem I've given up on; I'm investing in someone I want to keep.

[Your Name]

Click anywhere in the email to edit · Replace all [bracketed fields] with your specifics

Copy Email Reset to Original

Adapt It

They disagreed with the assessment in the meeting: Record the disagreement honestly — "I know you see the arrival issue differently, and I've noted your view that [their position, stated fairly]. The expectations above stand either way, and I'm glad to keep talking about the underlying schedule." Documentation that erases their side reads as rigged — and will, rightly, be challenged.

The gap is skill, not will: Shift the support section's weight — more training, pairing with a mentor teacher, observation time — and soften the consequence line to match: "If these weeks show us this room isn't the right match for your strengths, we'll talk honestly about what is." Effort problems get warnings; skill problems get coaching. Confusing the two loses coachable people.

This follows a previous conversation that didn't stick: Say so plainly — "We talked about this on [Date], and I own that I let the follow-up slide. This time the check-in is on both our calendars." Owning your half of a stalled process buys you the standing to hold their half firmly.

What Not To Say

"We've had some concerns." — Whose? About what? Passive vagueness feels ominous instead of fair. Every concern in this email has a subject, a specific, and a date attached, or it doesn't go in.
"This is your last chance" (unless it contractually is). Escalation language you can't or won't back up teaches staff that none of your language means anything. Say exactly where things stand — no darker, no rosier.
"I hate having to do this." — The email is not about your discomfort, and performing reluctance invites them to comfort you or dismiss the message as something you were forced into. You're choosing to lead; write like it.
Comparisons to other staff — "everyone else manages to arrive on time." The standard justifies itself. Comparisons turn a private expectation into a public ranking, and your staff room will feel it within a week.

The Performance Conversation Follow-Up

Related Articles