30-60-90 day check-ins: what to ask at each milestone and what to do with the answers

Day 30 is about expectations. Does the job match what they were told, and did training prepare them? Day 60 is about the manager. Are they getting support and clear goals? Day 90 is about the decision. Looking at the next twelve months, do they see themselves staying? If not, what is driving it? The core script stays the same each time. Only the focus moves.

Two rules make the plan work. First, someone other than the manager asks, because the manager is often the reason people leave. Second, every conversation is scored into the same fields. By day 90 you have one record per person and a list of names to act on.

Below are the questions for each milestone, the reasons behind them, and a template you can copy. You will also see how to run it when you have four hundred new hires a quarter instead of four.

Ask people who left within a year when they first thought about leaving. The answer is rarely month eleven. It is the first three months. Maybe the job turned out different from the pitch. Maybe training ended before they were ready. Or the manager who hired them handed them to a supervisor who never checks in.

None of this surprises anyone who has run frontline hiring. What is missing is a way to hear it while it can still be fixed. A 30-60-90 plan does that, if the conversations are honest and the answers reach someone.

The first check-in is short and mostly listening. Open with "How has your experience been so far, these first few weeks?" and let them set the tone. Then, without reading a list, steer toward the three things that go wrong early.

Expectations. Does the work match what they were told when they were hired? A gap here is one of the most common reasons people give on the calls we run. At day 30, a talk with the manager can still fix it before it turns into a resignation.

Training. Ask "How effective was the training in helping you do your job?" Score it afterward on a five-point scale. People who say training was only slightly effective, or not effective, are about to struggle. They will likely be blamed for it.

Settling in. How settled do they feel in the team? Is there anything they need that they have not asked for? Small requests at day 30 are cheap to grant.

Do not ask the twelve-month question yet. It is too early for a real answer, and asking it makes the call feel like an interrogation.

By day 60 the honeymoon is over, and the manager makes the biggest difference. Ask "How satisfied were you with the support and guidance from your manager during this period?" Then ask if their goals are clear. Do they know what good work looks like this quarter? Have they had a real one-on-one?

This is where having a neutral person ask pays off. A supervisor running this check-in gets a 4 out of 5 from everyone. A neutral voice on the phone hears "mostly absent, honestly" from the people already updating their resumes.

On this call, also ask if anything has come up that they raised with someone here. The answer splits concerns into two groups. Some nobody has heard. Others were heard and ignored. Each group needs a different person to step in.

Now ask the gate question plainly: "Looking at the next twelve months, how do you feel about staying on here?" Read the whole answer. "I think so, but let's see" means unsure. It does not mean yes.

Branch from there. Ask settled people what keeps them and what to keep doing. Ask unsure people for the one thing holding them back and what would need to change. Ask people who may leave what is driving it, whether they have raised it, and the one thing that would make them stay. Close every call with the 0 to 10 recommend question.

The full set of branching questions, with the reason for each, is in our guide to employee check-in questions.

You choose the milestones. Retail and banking teams often add a check-in before the season when they usually lose people. Many also add a six-month or yearly check-in that repeats the gate question. Each milestone has its own group and its own script. Each person's calls build up on one record. So if someone was settled at day 90 and unsure at six months, you see the change.

The manager should hold their own one-on-ones, and those are separate from the check-in. The check-in is where the employee can talk about the manager. HR can run it, but HR in the same building often gets a guarded answer too.

What works is a neutral voice, on the phone, in the language the employee actually speaks. Start with one honest line: what you share goes to senior HR leadership, under your name, so someone can act on it. Tell people up front that it is not anonymous. An anonymous program feels safer, but nobody can act on it.

Score every call into the same fields: commitment (committed, unsure, at risk), reasons to leave and reasons to stay from fixed lists, and what they asked for. Also record whether they raised it with anyone, training effectiveness, manager support and the recommend score. Keep their own words next to every category.

Set risk with a written rule. High: said they may not stay, or raised something that needs a formal review. Medium: unsure, or settled but would not recommend. Low: settled. Unknown: never reached. Never count unknown as low.

Then give HR a working list of names instead of a report. Let them filter by team, manager, reason and time in the job. Each row should open the person, their quotes and the recording. Protect people in the totals: never show a chart for a group smaller than five. If you hold back a group, name it and show its headcount instead of dropping it quietly.

Everyone gets the opening and the close. The middle changes with the milestone.

Three check-ins for each of four hundred new hires a quarter is twelve hundred conversations. Nobody has that many HR business partners. That is why most 30-60-90 plans quietly turn into a day-30 email survey.

To keep it a real conversation, make it a calling program. An AI counselor phones each person at the milestone you set. It opens by asking which language they would like and says where the feedback goes. It runs the script and asks follow-ups when an answer is thin. Then it scores the call into the fields above. It makes three attempts within working hours. If someone says "call me tomorrow at four", it books that callback. A very short call never counts as complete. You get the list of names, a report for each person, and a workbook for each group with the action list already written.