How to Deliver a Below-Expectations Performance Review

A below-expectations rating should never be the first time someone hears they're struggling. But even when the ground has been laid, delivering the formal rating is its own conversation, and rushing it or softening it into vagueness undoes the honesty you owe them.

Key Takeaways

  • If this rating is a surprise, that's a failure of the months before the review, not just this meeting. A below-expectations rating should already be familiar from earlier 1:1s and documented feedback.
  • State the rating early and plainly. Burying it under ten minutes of context makes people brace for something worse than what you're about to say, and it reads as you being unable to just say it.
  • Use specific, behavior-based examples for every area rated below expectations, not general impressions. "Your communication needs work" gives them nothing to act on. "Three of the last four status updates were late" does.
  • End with what happens next in concrete terms: a development plan, a PIP, a timeline. A below-expectations rating with no defined path forward reads as a warning shot with nothing behind it.

The conversation

Read it once before you go in, then use it as a guide rather than a script to read word for word. The order matters more than the exact phrasing - get the structure right and your own words will carry it.

  1. Confirm there are no surprises left to defuse

    Before the meeting, check honestly whether this rating has already been signaled in earlier conversations. If it hasn't, the real problem predates this meeting and you should be ready for a harder reaction than the rating alone would cause. Reviewing the pattern across a few months of notes is easier if you've kept them somewhere consistent. Perform Review's AI Manager Coach draws on your team's review history for exactly this kind of prep.

    • Pull your 1:1 notes and any written feedback from the period and confirm the gap was raised in real time, not just now.
    • If it wasn't raised clearly before, be ready to own that directly rather than pretending this was always obvious.
    • Write the rating and the two or three specific reasons behind it in plain language before you walk in.

  2. Open with the rating, not a run-up

    State the outcome first. A long preamble before the actual news makes people spend the setup bracing rather than listening, and by the time you get to the rating they've often stopped hearing detail anyway.

    • You: I want to start with where we landed. This review is a below-expectations rating.
    • Them: Okay... I wasn't expecting that going in, honestly.
    • You: I want to walk through exactly why, with specifics, and then talk about what happens from here.

  3. Give the specific evidence, not a vague impression

    This is the part that determines whether the conversation feels fair or feels arbitrary. General language like "needs to step up" gives someone nothing to work with and invites the reasonable question of what that actually means.

    • You: There are two areas. The Baxter project shipped six weeks late with no early flag to me, and two of your last three peer reviews mentioned missed handoffs on your team.
    • Them: The Baxter delay wasn't really on me, procurement held that up for weeks.
    • You: Some of that's fair, and I should know the full picture - I do also need us to talk about when you'd have flagged the risk to me if procurement hadn't been the cause.

  4. If they push back on the rating itself

    Some people contest the rating directly, sometimes with real points about context you didn't have. Take the specifics seriously without turning the whole rating into something negotiable on the spot.

    • Them: This feels like it's coming out of nowhere. I don't think this rating reflects my year.
    • You: Tell me what you think I'm missing - I want to make sure I have the full picture.
    • Them: I picked up two projects when Dana left and never got credit for that.
    • You: That's real, and I'll go back and check the record on it. It doesn't change the pattern on delivery and handoffs, but I want to make sure that context is actually reflected.

  5. What to avoid saying

    A handful of habits make this conversation feel worse than the news itself, usually because they dodge specifics or quietly promise something you can't actually guarantee.

    • "This isn't personal" - unhelpful and untrue in the way they'll hear it. Of course it feels personal, and pretending otherwise reads as dismissive.
    • "You're not the only one" - it may be true, but it tells them you're treating their specific performance as part of a general problem instead of taking their situation seriously.
    • "I'm sure you'll bounce back next cycle" as a closer with nothing behind it - reassurance without a plan isn't actually reassuring.

  6. Lay out what happens next in concrete terms

    A below-expectations rating with no defined path forward reads as a warning with nothing behind it. Whether the next step is a development plan or a formal PIP, they need to leave knowing exactly what it involves.

    • State plainly whether this triggers a formal process (like a PIP) or a less formal development plan, and what the difference means for them.
    • Name two or three specific, measurable things that need to change, and by when.
    • Set the date of the next real check-in, not the next formal review cycle, something sooner.

  7. Follow up in writing and change your own behavior after

    How you show up in the weeks after this conversation is what tells them whether the path forward was real or just something said to end the meeting.

    • Send a written summary of the rating, the reasons, and the agreed next steps within a day or two.
    • Increase the frequency of check-ins for a while, rather than letting this fall back into the normal cadence.
    • Actually notice and name improvement when it happens. A below-expectations rating followed by silence until the next cycle is its own kind of failure.

That's the whole conversation

Every real version of this conversation goes slightly differently. What is above is the shape that holds regardless of how they react - what to actually say in the moment is still yours to find.

Work through this against your own team

The Perform Review AI Manager Coach does two things this page cannot, because both are built from your own logged wins and your own reviews.

Guides: When a review of a direct report is written, your AI Coach can turn it into preparation for the meeting itself: talking points anchored to your strongest evidence, the honest gaps between their case and your rating, the pushback you are likely to get with answers to it, and a script you can say out loud.

Monthly Sessions: A read on your team every month, person by person: who is thriving, who is under-evidenced before calibration, the patterns across the team, and the conversations worth having this month. Reply to any part of it and the AI Coach answers on that specific point.

Both are included with and exclusive to Pro. See Pro.

More Manager Guides