Probation Reviews That Produce a Decision Instead of a Delay

Most probation reviews end in a shrug. The manager has no evidence, the new hire has no clear feedback, and the meeting produces an extension that nobody wanted. A probation review produces a decision when the evidence starts in week one, not the week before the meeting.

That is the whole method. Collect a little each week, answer three questions at the end, and the meeting takes twenty minutes because the work already happened.

What to collect from week one

You need a short record, not a file. Five minutes a week is enough.

• What they were given. The actual work, with dates. Not the job description.
• What they finished. Delivered, reviewed, closed. Whatever the finish line means in your team.
• Where they got stuck, and for how long. Getting stuck is normal. Staying stuck without asking is the signal.
• Feedback given, and what changed after. This is the single most useful column. A person who adjusts after one conversation is a very different hire from one who needs the same conversation four times.
• Anything outside their control. Systems access that took three weeks, a project that was cancelled, a manager who was away. Without this, a slow start looks like a slow person. Someone who has just relocated to Dubai will collect more of these in month one than most.

That last item is why the record has to start at week one. Nobody remembers in month three that the laptop arrived nine days late.

Write five lines a week: work given, work finished, where they got stuck, feedback given and what changed after it, and anything outside their control. That record is the probation review. The meeting is just where you read it out.

The three questions to answer

At the end of the period, the review answers three questions and nothing else.

1. Can they do the work? Evidence from finished work, not from impressions. If the honest answer is that you do not know, that is a finding about your record keeping, and it usually means the work you assigned was too small to judge.

2. Do they improve when told? Look at the feedback column. Someone who is not yet good but moves after feedback is a good hire early in a curve. Someone who is fine now but does not respond to feedback is a harder problem later.

3. Would you hire them again, knowing what you know now? Ask it plainly, in private, before the meeting. The gut answer arrives fast and it is usually consistent with the evidence. When the gut says no and the evidence says yes, look harder at the evidence, because one of the two is being influenced by something you should name.

Three answers, three sentences. That is the decision.

Why extending is usually a decision you already made

An extension is sometimes legitimate. A genuine interruption, a long absence, a project cancelled halfway through: those are real reasons to add time.

The rest of the time, an extension means one of two things. Either the manager knows the answer is no and does not want to say it, or nobody collected any evidence and needs more time to start.

Both are worth naming honestly, because both hurt the new hire. Someone who is not working out learns it later, with a worse story to tell. Someone who is doing fine spends another two months uncertain about whether they still have a job, which is not a state anyone does their best work in.

If you are about to extend, answer one question first: what specific evidence will exist in eight weeks that does not exist now, and who is responsible for producing it? If you cannot name both, you are delaying a decision, not gathering information. A no also reopens the earlier question of whether to hire again or resequence the work.

Running the meeting

Keep it short and keep it in order.

1. Read back the record. Work given, work finished, feedback and what changed. Facts before opinions.

2. Give your answer to the three questions, plainly, in the first five minutes. Do not build up to it.

3. Then ask for theirs. What did they find harder than expected, what support was missing, what would they want in the next quarter.

4. Write down what happens next, with dates, whether the answer is yes or no.

Confirmation should feel like a real event, not an email nobody sends. If the answer is no, say it early in the meeting so the person is not answering questions while waiting for bad news, and start planning the weeks that follow the same day.

Local employment rules on notice, process and documentation vary, so check what your own contracts and jurisdiction require before you set the timeline.

The habit that makes all of this work

None of the above is difficult. It fails because the weekly record does not exist, and the record does not exist because it lives nowhere in particular.

Put it where the person's other records already live: their start date, their team, their manager, their leave. When the work history and the employment record sit together, a probation review is a report you open rather than a document you reconstruct. That is the practical argument for keeping project data and HR data on one set of records, and it is most obvious in exactly this meeting.