Probation Period Management Checklist

A probation period fails quietly. Nobody sends a memo saying expectations were never written down or that the only feedback was silence until week eleven. It just ends in a bad decision made too fast, or a good hire lost because nobody checked in. This is the ongoing work of running someone through it well, from the first week to the decision point.

Key Takeaways

  • Set the probation criteria in writing in week one, not week eight. SHRM data shows roughly 28% of new hires either leave or are let go during probation, and most of those cases trace back to expectations nobody actually wrote down.
  • Run at least three structured touchpoints: a kickoff in week one, a formal mid-point check-in, and a close-out meeting before the decision date. Ad hoc feedback alone leaves both sides guessing where things stand.
  • Document every check-in as you go, not from memory at the end. A decision built on three months of notes survives a challenge; a decision built on a manager's general impression does not.
  • Decide early if the outcome is trending toward a no, and say so before the final meeting. Ending someone's probation as a total surprise is the single most common complaint about how this is handled.

The Checklist

Work through it in order. Tick things off as you go and your progress is saved on this device, so you can come back to it over the days before the conversation rather than doing it all in one sitting.

  1. Put the criteria in writing before day one ends

    Probation exists to answer a specific question: can this person do this job. That question needs a specific, written answer key, not a general sense of "fitting in."

    • List the concrete outcomes or competencies this person needs to demonstrate by the end of probation, not just "perform well."
    • Separate must-haves (the things that end probation if missing) from areas you expect are still developing.
    • Share the list with them directly in week one, in writing, so there is no ambiguity about what they are being measured against.
  2. Build the onboarding support around the criteria

    A probation period that is really just a countdown clock, with no active teaching or resourcing behind it, sets people up to fail on things they were never actually shown how to do.

    • Confirm they have the access, tools, and training needed to hit the criteria you wrote down, not just a laptop and a login.
    • Assign a buddy or informal mentor separate from you, so they have somewhere to ask basic questions without it looking like a performance signal.
    • Block recurring time on your own calendar for this person in the first few weeks. Deprioritizing them because they are "still ramping" is how early problems go unnoticed.
  3. Run a real kickoff conversation, not just a welcome chat

    The first week sets the tone for whether this person believes feedback is coming or believes silence means things are fine.

    • Walk through the written criteria together and confirm they understand what a pass looks like.
    • Tell them explicitly how often you will check in and what those check-ins will cover.
    • Ask what support or context they think they are missing right now, while it is still cheap to fix.
  4. Give feedback continuously, not just at the checkpoints

    Formal check-ins catch what continuous feedback missed. They should never be the first time someone hears a concern.

    • Flag concerns the same week they happen, specifically and without waiting for the next scheduled meeting.
    • Note wins as they happen too. A probation period that only surfaces problems reads as a countdown to termination, and people disengage accordingly.
    • A simple running log, even something like Perform Review's Achievement Log, makes it easy to note wins and concerns as they happen instead of trying to reconstruct them at the mid-point check-in.
    • If you would not be comfortable saying a piece of feedback out loud this week, that is a sign you are sitting on it too long.
  5. Hold a genuine mid-point check-in

    This is the point where a struggling probation should already be visible, and where a manager who has been avoiding the conversation runs out of road.

    • Review progress against each written criterion explicitly, not just how the relationship feels.
    • Name any criterion that is currently a no, and say plainly what needs to change before the end date.
    • Document the conversation the same day, including what was said and what was agreed.
  6. Escalate early if it's trending toward a fail

    A probation period that ends in termination should never be the employee's first indication something was wrong. That gap is where most unfair-dismissal and morale complaints come from.

    • Loop in HR as soon as a fail looks like the likely outcome, not in the final week.
    • Give the employee a clear, written account of what is missing and what would need to change, even if the odds are low.
    • Confirm what documentation your company requires to support an extension or a non-confirmation before you get to the deadline.
  7. Prepare the close-out decision before the final meeting

    The decision should be made and supportable before you walk into the room, not worked out live in front of the employee.

    • Review the full record against the original criteria, not just the last few weeks.
    • Decide among the three real outcomes: confirm, extend with named conditions, or end employment, and know which one this is before the meeting.
    • Prepare next steps for whichever outcome it is, including a written summary to send the same day.
  8. Deliver the decision directly and follow through

    However the decision lands, how it is delivered is what the person remembers and what shapes whether a confirmed hire stays engaged past probation.

    • Lead with the decision, then the reasoning, in that order.
    • If confirmed, tell them plainly what happens next: any remaining conditions closed out, and what standard review cadence they now move into.
    • If extended or ended, put the agreed terms or the reasoning in writing within the day, so there is no gap between what was said and what is on record.

That is the whole checklist

Everything above is general by design, so it holds for most people in most companies. The specifics of your own case are the part it cannot cover.

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