Published November 9, 2026.
The first week of an operations role is full of small gaps that never appear in a job description. A new hire can have a laptop, a badge, and a schedule and still spend the week unsure who owns the next step. A short check-in script gives the manager a way to find those gaps while they are still cheap to fix. The script is not a performance review, and it should not ask the new hire to grade the manager. Its job is to surface one missing thing, one confusing thing, and one thing that is going well.
Open with permission, not a scorecard
Begin the check-in by saying that the purpose is to remove friction, not to judge the first week. A new hire who thinks the conversation is a test will give safe answers and hide the real blocker. Ask for one tool, one instruction, and one person that were hard to find. Write the answers down while the person is talking so they know the issue is being recorded. Close the opening by naming what will happen to the notes.
Keep the first question broad and the follow-up specific. A useful opening is to ask what took longer than it should have in the first five days. Then ask which system, form, or approval caused the delay. A broad question without a follow-up produces a polite answer, while a specific one produces a fix. The manager should resist defending the current process until the full answer is on the page.
Ask about access before asking about output
Access problems are common in the first week and easy to miss because the new hire may not want to complain. Ask which accounts still require someone else to log in, which folders are read-only when they should not be, and which tools were never set up. Record the date each gap is reported and the date it is fixed. A login that works on day one but not on day three is still an access problem. A named owner should be attached to every open item.
Do not accept a workaround as a permanent answer. A shared password, a borrowed laptop, or a colleague forwarding files creates a security and accountability problem. If the proper access takes time, say so and give the new hire a safe temporary path with an end date. Review the temporary path at the next check-in instead of letting it become normal. The goal is a named account with the least access needed for the work.
Name the first real task and its finish line
A first-week task should be real enough to teach the work and small enough to finish. Ask the new hire to describe the task in their own words, including what done looks like. If the description differs from the manager's, the gap is in the brief rather than the person. Correct the brief in the meeting and send the corrected version in writing. A task with no finish line turns into an open loop that follows the hire into week two.
Check whether the new hire knows who reviews the work and how long the review should take. An unknown reviewer can leave a finished task waiting for days. Record the reviewer, the expected turnaround, and the channel for questions. If the reviewer is unavailable, name the backup before the task starts. The check-in should end with a clear next task, not a general instruction to keep learning.
Make the social path visible
A new hire needs to know who to ask about the work, who to ask about the schedule, and who to ask when something feels wrong. Name three people and the kind of question each one handles. Do not assume the org chart answers this, because the chart shows authority rather than help. Ask whether the new hire has actually spoken to each person. A name on a slide is not a relationship.
If the team is remote or spread across shifts, add the overlap window and the response expectation. A new hire who sends a question at the end of the shift may wait a day for an answer. Write the expected response time for routine and urgent questions. Check whether the new hire knows which channel is appropriate for each. The social path is working when the person asks a question without apologizing for it.
Record one fix and one follow-up date
At the end of the check-in, choose one fix that can be completed before the next week. It might be a missing account, a rewritten task brief, a calendar invite, or an introduction. Name the owner and the date, and put the item where the team tracks work. A check-in that produces a long list and no completed fix teaches the new hire that feedback goes nowhere. One visible fix is worth more than a perfect plan.
Set the next check-in before the meeting ends rather than leaving it to be scheduled later. A short follow-up in week two catches the problem while the context is still fresh. Ask whether the first fix actually solved the issue. If it did not, record why and choose a different fix. The sequence of small fixes is the onboarding program.
Close with an honest summary
End by summarizing what was heard, what will change, and what will not change. A new hire should not leave the meeting wondering whether a concern was accepted or dismissed. If a request cannot be met, explain the constraint and offer the closest safe alternative. Record the decision so the next manager conversation is consistent. Honesty about a limit is better than a promise that will be broken.
Keep the notes in the onboarding record, not in a private manager notebook. The next reviewer should be able to see which gaps were found and how they were closed. Remove sensitive personal details that are not needed for the work. Review the pattern across several hires and fix the most common gap at the source. A check-in script becomes useful when it changes the onboarding process, not only the conversation.