Published November 3, 2026
The first week is when a new hire decides whether the job matches the offer. They may not say so, and they rarely file a complaint. Instead they notice that the training is thinner than promised, that the schedule changed without explanation, or that no one seems to know who answers their questions. A short, structured check-in at the end of week one gives the team a chance to correct those impressions before they harden into a resignation.
Why the first week matters more than the first month
By the end of the first month, a new hire has usually settled into some version of the routine. They have learned whom to ask, which rules are enforced, and which promises were aspirational. If the experience is poor, they may already be applying elsewhere. The first week is the last point when a small correction can still change the trajectory, because the new hire has enough information to be worried but not enough to have made up their mind.
A first-week check-in is not a performance review. The new hire has barely had time to perform, and treating the conversation as an evaluation invites defensiveness. The purpose is to learn what is confusing, what is missing, and what is different from what they expected. That framing makes it easier for the new hire to be honest and easier for the manager to act on the answers.
Ask about the gap between promise and reality
The most useful question is not whether the new hire is happy. It is what has been different from what they expected. A new hire who expected to shadow a colleague for two weeks but was placed alone on day three will describe a training gap. A new hire who expected a predictable schedule but received a rotating one will describe a stability gap. Those answers point to specific fixes rather than vague morale problems.
Prepare a short list of expectation areas: training, schedule, tools, supervision, and the definition of success for the first month. Ask the new hire to rate each area as clearer, about the same, or less clear than expected. Then ask them to explain any rating that is not positive. This structure gives a quiet employee something concrete to respond to and gives the manager a comparable record across hires.
Separate confusion from disagreement
A new hire may be confused about a process, or they may understand it and disagree with it. Those are different problems. Confusion calls for clearer documentation or a demonstration, while disagreement may call for a conversation about the reason behind the rule. If the manager treats every concern as confusion, the new hire learns that raising a real issue is pointless. If the manager treats every question as a challenge, the new hire stops asking.
The check-in should explicitly invite both. Ask what is still unclear and what the new hire would do differently if they owned the process. Then record the answer without defending the current approach in the moment. The manager can follow up later with context, but the first conversation should focus on collecting the new hire's view. That sequence preserves trust and produces better information.
Review the schedule and the workload
Scheduling is one of the most common reasons a new hire leaves in the first ninety days. A schedule that looked acceptable in an interview can become unworkable once the commute, childcare, or a second job is real. Ask whether the hours worked match what was described and whether the new hire can sustain them. If the answer is no, the manager needs to know now, while there may still be room to adjust.
Workload deserves a separate question. New hires often receive a reduced load during training, then face a full load before they feel ready. Ask how the pace compared with expectations and whether any task felt unsafe or unclear. If the new hire describes being asked to do something before training was complete, treat that as a process failure rather than a personal shortcoming. The answer may reveal that the training plan is being skipped under pressure.
Check the human connections
Retention is often about whether a new hire has someone to turn to. Ask who they would ask if they had a question and whether that person has been available. A new hire who names no one, or names someone who is consistently too busy, is at risk even if the work itself is fine. The manager can then introduce a specific buddy or set a standing fifteen-minute slot for the first few weeks.
Also ask whether the new hire has felt welcomed by the team. This is not a request for praise; it is a check on whether the informal side of the job is working. A team that is friendly in meetings but silent in the shared channel can leave a new hire feeling isolated. If the answer is negative, the fix may be as simple as assigning a peer check-in or including the new hire in an existing routine.
Close with two named actions
A check-in that ends with "let me know if you need anything" produces no change. End with two specific actions, each with an owner and a date. One action should address the new hire's most pressing gap, and the other should address a process issue the manager controls. Write both down and send them to the new hire the same day so there is a shared record.
Follow up on the actions at the end of week two. The follow-up matters more than the original conversation, because it shows whether the manager's commitments are real. A new hire who sees one promised fix delivered is far more likely to raise the next issue early. A new hire who sees nothing change learns to stop expecting improvement.
Use the pattern across hires
After several check-ins, read the answers together. If most new hires report the same training gap, the problem is the onboarding plan rather than any individual. If scheduling concerns cluster in one team, the issue may be a local practice that the broader organization has not noticed. Aggregate patterns are more reliable than a single conversation and more actionable than an engagement score.
Keep the record short and free of sensitive commentary. Store the answers with the onboarding file and review them quarterly alongside early turnover. The goal is not to grade the new hire but to grade the welcome the team provided. That distinction keeps the process honest and makes the first week a retention control rather than a formality.