Most frontline turnover happens inside the first 90 days. The employee leaves before they have become productive, before the recruitment cost has paid back, and often before anyone has asked them how it is going.
This blueprint sets out what to cover at each stage of the first 90 days, who is responsible, and what to measure.
What is a 30/60/90-day plan?
A 30/60/90-day plan is a structured framework that sets out what a new employee should learn, achieve and be supported with during their first three months. It divides the window into three phases: learning and orientation in the first 30 days, contributing with support in days 31 to 60, and working independently with clear goals by day 90.
The plan belongs to the manager, not to HR. HR provides the framework. The manager makes it happen.
Why the first 90 days decide retention
Three things happen in this window that determine whether someone stays.
First, the employee compares the reality of the job to what was described during recruitment. Any gap between the two becomes a source of quiet disappointment that compounds over weeks.
Second, they form a view of their manager. The relationship with the direct manager is the strongest single predictor of whether a frontline employee stays, and that relationship is established in the first few weeks.
Third, they decide whether the organisation is somewhere they can build something. That judgement is made on evidence: was there a plan, did anyone check in, was development discussed, did anyone notice their work.
Prosper's onboarding survey data shows 43% of employees said their onboarding experience did not meet their expectations. Nearly half start a new role already disappointed, and most organisations never find out until the resignation arrives.
Days 1 to 30: Orientation and confidence
Goal: the employee knows what they are doing, who to ask, and that they were expected.
The first 30 days are about reducing uncertainty. A new starter is simultaneously learning a role, a team, a set of systems and an unwritten culture. Every piece of structure you provide reduces the cognitive load.
What to cover: role expectations and what good looks like, workplace health and safety induction, essential policies with acknowledgement, systems and tool access, introduction to the wider team, and the first informal feedback conversation before the end of week one.
Manager actions: personally welcome them on day one, check in daily for the first week even briefly, assign a buddy who is not their manager, and hold a documented 30-day conversation.
What to measure: onboarding checklist completion, policy acknowledgement, and a short survey at day 30 asking whether the role matches expectations and whether they feel supported. This is covered in more depth in our employee onboarding guide.
Automate the first 30 days
Prosper assigns onboarding checklists by role, team and location automatically — and shows managers exactly who is on track.
Book a consultationDays 31 to 60: Contribution with support
Goal: the employee is contributing meaningfully and knows how they are tracking.
By day 31 the novelty has worn off and the real work has started. This is where a new starter either builds momentum or quietly stalls.
What to cover: first goals agreed and written down, role-specific skills consolidated, feedback given on early work, relationships built beyond the immediate team, and any gaps in training identified and addressed.
Manager actions: shift from daily check-ins to a weekly one-to-one, give specific feedback on actual work rather than general encouragement, and ask directly what is getting in the way.
What to measure: whether goals have been set and documented, one-to-one completion rate, and whether the employee can articulate what success looks like in their role.
Days 61 to 90: Independence and direction
Goal: the employee works independently and can see a future.
The final 30 days shift from support to direction. The employee should be operating without close supervision and starting to think about what comes next.
What to cover: a formal 90-day review, confirmed performance expectations for the next quarter, the first development conversation, and feedback from the employee on their own onboarding experience.
Manager actions: hold a real review rather than letting the probation date pass unmarked, ask where they want to be in twelve months, and document a development plan.
What to measure: 90-day review completion, development plan created, and a 90-day survey capturing their experience while it is still fresh enough to act on.
The 90-day checklist
Before day one: welcome message from the direct manager, logistics confirmed, workspace and access ready, buddy assigned, day one schedule prepared.
Day one: manager welcome, team introductions, workplace tour, safety induction, onboarding checklist assigned, first tasks explained.
Week one: daily manager check-in, buddy catch-up, role-specific training started, key stakeholders met.
Day 30: documented check-in conversation, onboarding survey sent, gaps identified and addressed, initial goals discussed.
Day 60: goals written and agreed, weekly one-to-ones running, specific feedback given, training gaps closed.
Day 90: formal review completed, next-quarter expectations confirmed, development plan documented, 90-day experience survey sent, onboarding formally closed.
Common mistakes
Treating induction as onboarding. A day one safety briefing is induction. Onboarding runs for three months. Organisations that stop after day one see the highest early turnover.
Front-loading everything into week one. Six hours of policy reading on day one produces fatigue, not competence. Spread the learning.
Leaving it to the manager without a framework. Good managers will build their own plan. Stretched managers will not. Without a standard framework, the new starter experience depends entirely on which manager they report to.
No follow-up after week one. This is the single most common failure. Without 30, 60 and 90-day check-ins, problems surface at the exit interview.
Inconsistency across sites. If a new starter at one venue gets a structured experience and a new starter at another gets an apron and a shrug, you do not have an onboarding process. You have several.
Making it consistent across every site
The difficulty with a 90-day framework is not designing it. It is running it consistently across 10, 30 or 50 locations with managers who are already stretched.
This is where a frontline employee app changes the economics. Checklists assign automatically by role, team and location. Reminders chase completion without a manager having to remember. Surveys trigger at day 30 and day 90 without anyone scheduling them. And leadership can see, at a glance, which sites are following the framework and which are not.
The framework is the same either way. The difference is whether it actually happens.
Frequently asked questions
A structured framework setting out what a new employee should learn, achieve and be supported with during their first three months — orientation in the first 30 days, supported contribution to day 60, and independent work with clear goals by day 90.
Because the reality of the job does not match what was described, the relationship with their manager was not established, or nobody checked in early enough to catch a problem while it was still small.
HR provides the framework, the templates and the tracking. The direct manager owns the relationship and the conversations. Frameworks without manager ownership do not work.
Ask directly whether the role matches what was described at interview, whether they have what they need, and what is getting in the way. Document the conversation and act on what you hear.
Standardise the framework and automate the delivery. Checklists assigned by role and location, automated reminders, and surveys that trigger at day 30 and day 90 remove the dependence on individual managers remembering.
Checklist completion, policy acknowledgement, one-to-one completion rate, whether goals have been documented, 30 and 90-day survey scores, and 90-day retention rate.