Open with the new hire's questions, not a status recital
A first-week check-in should start with what the new hire could not complete or did not understand. Ask for the specific task, the instruction used, and the point where progress stopped. This surfaces onboarding defects that a general question about how things are going will miss. It also gives the manager a concrete reason to change an instruction or remove an access blocker.
Keep the opening short and do not turn it into a performance review. The first week is a test of the onboarding design as much as of the new hire. Record the questions and the answers in a shared note. If a question reveals a missing document or an unclear owner, assign the fix to the onboarding process rather than to the new hire.
Review the plan against what actually happened
Bring the first-week plan to the meeting and compare it with the calendar and task record. Identify the sessions that happened, the sessions that moved, and the tasks that were never started. Ask whether each gap was caused by access, a missing input, a scheduling conflict, or an unclear instruction. Record the cause rather than only the fact of the gap.
Do not treat a moved session as a failure by default. A session that was replaced by a written briefing may be fine if the plan allowed that substitution. The question is whether the new hire received the information and knows what to do next. If the same session moves for several hires, the plan or the owner needs to change.
Make one or two decisions and name the owners
End the check-in with a small number of decisions. A decision might be to grant a missing access, change a training sequence, assign a buddy for a specific task, or move a review to the following week. Write the decision, the owner, and the date it will be checked. Avoid a long action list that no one reviews before the next meeting.
Separate a decision from a suggestion. If the manager is not ready to decide, record the question and the person who will answer it. If the new hire needs a decision from someone outside the meeting, name that person and the date the answer is expected. The next check-in should begin with the status of those decisions, not with a fresh status recital.
Close the loop before the next meeting
Send a short note after the check-in with the decisions, the owners, and the next date. Ask the new hire to reply if the note misses something important. Keep the note in the onboarding record so the next manager or coordinator can see what was agreed. A note that only says great meeting is not a record.
Review the open decisions at the start of the next check-in. If an item is still open, ask why and decide whether to change the owner or the date. If the same issue appears across several new hires, route it to the onboarding review rather than solving it one person at a time. The agenda is working when it produces fewer repeated questions and clearer ownership.
Continue building the workflow
Related support: onboarding operations support, contact us. The U.S. Office of Personnel Management — Training and Development workforce development and manager support resources.
Related reading
A preboarding document queue with named owners
A preboarding queue that shows who owns each document, what is missing, and when the start-date decision must be made.
A thirty-day onboarding review that closes open items
A thirty-day review that checks role clarity, access, training, and open questions before the first month ends.
