Ninety Days, Not a Countdown: Making Probation a Working Assessment

Probation is one of the most underused management tools in UK organisations. It is written into contracts, tracked by HR, and often experienced by new starters as a countdown. The final week arrives; a form is completed; a decision is made. By then, the most useful period for mutual assessment has passed.

This is not a failure of HR administration. It is a failure of management design. Probation should be a structured period of mutual assessment, not a test that everyone pretends not to be taking.

The administrative countdown

In many organisations, probation is treated as a diary entry. A reminder appears at day 85. A manager is asked to confirm whether the new starter has passed. The conversation, if it happens, is compressed into a short meeting. The employee has spent three months trying to infer the rules. The manager has spent three months intending to have a proper conversation.

The result is predictable. Good starters receive little useful feedback. Struggling starters receive too little signal, too late. Managers avoid difficult conversations because the process does not require them until the end. HR inherits a late-stage problem that could have been resolved earlier.

What probation is actually for

Probation has two legitimate purposes. The first is to assess whether the role, the person and the organisation are a good fit. The second is to help the new starter become effective. These purposes are connected. A probationary period that only assesses at the end is not an assessment. It is a delayed decision.

A better model treats probation as a mutual assessment. The manager assesses capability, conduct and fit against clear outcomes. The employee assesses whether the role, workload, management and working arrangements are as described. Both parties should be able to raise concerns early. Both should know what good looks like.

This is change management at the smallest unit: a new starter's relationship with the organisation. Get it right and the return is significant. Get it wrong and the cost appears later as turnover, re-recruitment, team disruption and lost confidence.

A 30/60/90 framework that earns its place

A useful probation framework is simple enough to be used and specific enough to be fair.

Before day one, the manager and new starter should agree three to five success measures for the probation period. These should describe outcomes, not personality. For example: handles most routine customer queries within the service standard by day 60; completes the first monthly report without close supervision by day 45; builds working relationships with the three key internal stakeholders by day 30. The measures should be recorded and shared with HR.

The first 30 days should focus on context, relationships and access. The manager should check that the new starter has the tools, introductions and information needed to do the job. The day-30 checkpoint is not a formal performance review. It is a clarity review. What is unclear? What has been harder than expected? What has the manager learned about the role? What should change in the plan?

The day-60 checkpoint is an evidence check. The manager and employee should review progress against the success measures. This is the point for honest, specific feedback in both directions. If there are gaps, the manager should agree a focused plan with dates. This is also the last sensible point to fix a problem without a late-stage surprise.

The day-90 checkpoint is the formal decision. If the 30-day and 60-day conversations have been done properly, this should confirm what both parties already know. The decision should be recorded, but the conversation should not be the first time the employee hears a concern.

Checkpoints should test clarity, not personality

A common weakness in probation is that checkpoints become vague. Managers ask whether things are going well. Employees say yes. Nothing is tested.

A better checkpoint uses evidence and questions. What work has been completed? What has not? What support has been requested? What has been provided? What would the manager expect to see by the next checkpoint? What would the employee like to change?

This is not about creating a bureaucratic trail. It is about making the assessment real. A short, documented conversation every 30 days is usually enough.

Early honesty protects retention

If there is a concern, raise it at day 20, not day 80. This is the hardest advice to follow, because early conversations can feel premature. But late-stage surprises are more expensive. A probationary dismissal at the end of three months disrupts the team, restarts recruitment and damages the confidence of everyone involved. An early conversation may still lead to the same outcome, but it gives the employee a fair chance to respond and the manager a fair basis for the decision.

Early honesty also protects good starters. A capable employee who is struggling because of unclear priorities or poor onboarding needs to hear that before it becomes a performance narrative. The problem may be the process, not the person.

Keep governance proportionate

Probation decisions should be consistent, recorded and fair. Managers need guidance on evidence, reasonable adjustments and the difference between a capability concern and an onboarding gap. HR should review outcomes for patterns. But governance should not turn probation into an obstacle course.

The test is simple: does the process help managers make better decisions earlier? If it only produces paperwork at the end, it is not adding value.

A better use of the first ninety days

Probation should not be a countdown. It should be a working assessment with clear outcomes, regular checkpoints and honest conversations. For UK organisations, that is a practical way to improve retention, reduce late-stage surprises and make the first ninety days useful for everyone.