Probation management: how to never miss a confirmation deadline again

A missed probation confirmation is one of the most expensive small mistakes in HR. In many jurisdictions — including India and much of the GCC — an employee whose probation period lapses without a formal decision is often deemed confirmed by default, whether or not their performance justified it. And even where the legal exposure is small, the message sent to a new joiner who hears nothing on the day their probation was supposed to end is corrosive: nobody is paying attention.

Why probation slips through the cracks

Probation fails for a structural reason, not a people reason. The dates live in an HRIS or a spreadsheet, the reviews live in email, and the reminder system is a calendar entry someone set four months ago. Each new joiner adds another parallel timeline, and every manager tracks theirs differently. At 50 employees this is survivable. At 500, with hiring spread across departments and locations, some confirmations will be missed — it is only a question of how many.

The 30/60/90 framework

The fix is to treat probation as a workflow with fixed milestones rather than a date to remember. At 30 days, the manager confirms that expectations and goals were actually communicated — most probation disputes trace back to expectations that were never written down. At 60 days, a structured check-in records progress against those expectations, giving the employee time to correct course while correction is still possible. At 90 days (or whatever your probation length is), a formal review produces one of three decisions: confirm, extend with specific conditions, or exit.

Every milestone needs an owner and a fallback

A milestone that nobody is chasing is a wish, not a process. Each step needs a named owner — usually the direct manager — an automatic reminder before the due date, and an escalation to HR when the due date passes without action. The escalation is the part most home-grown systems skip, and it is the part that actually prevents misses.

Decisions need evidence, not vibes

Extension and exit decisions get challenged. When they do, the difference between a defensible decision and a liability is documentation: the expectations set at day 1, the check-in records, the specific gaps identified and the support offered. If your probation reviews consist of a manager saying "not quite there yet" in a hallway, you have neither fairness nor protection.

What this looks like in practice

In MeritFlo, probation is a configurable workflow: you define the milestones, the review templates and the approval chain once, and every new joiner enters the same track automatically. Managers get reminders, HR gets a live view of every open probation and its status, and every decision — confirm, extend or exit — is recorded with its supporting reviews. The confirmation letter goes out because the system queued it, not because someone remembered.

Probation is often the first workflow teams move off spreadsheets, because the deadlines are legally meaningful and the volume is predictable. It is also the fastest to show value: the first time the system catches a confirmation that would have lapsed, it has paid for itself.