Onboarding

A first-week check-in agenda that produces evidence

A repeatable first-week check-in agenda that reviews observed work, unresolved questions, access barriers, and the next practice step.

By OnboardingEmployees editorial team | | 6 min read

A first-week check-in agenda that produces evidence
On this page
  1. Give each check-in a different purpose
  2. Start with the work, not the personality
  3. Ask about the source and the stop rule
  4. Review the open questions list
  5. Make the next practice step explicit
  6. Watch for barriers the new hire cannot fix
  7. Close the week with a short record
  8. Use the pattern, not the script
  9. Related reading

Give each check-in a different purpose

A first-week check-in should not become a daily status report. Each conversation should have a purpose: confirm priorities, review a work product, resolve an access barrier, or set the next practice step. When every meeting tries to cover everything, the new hire learns that the agenda is unpredictable and the manager learns very little. Write the purpose at the top of the note before the meeting.

If the purpose is to review a completed task, ask the new hire to send the artifact and the source record in advance. If the purpose is to resolve a blocker, name the system, the owner, and the decision needed. A clear purpose makes the conversation shorter and the evidence stronger. The manager should keep the same agenda structure for the first few weeks, even when the topics change. Repetition helps the new hire prepare and makes it easier to compare one week with the next. A stable structure is not bureaucracy; it is a way to make progress visible.

Start with the work, not the personality

Open the conversation with a specific task the new hire completed or attempted. Ask them to walk through the request, the source they used, the action they took, and the result. This sequence shows whether they understood the workflow and whether the record supports the outcome. Avoid broad questions such as how is it going.

They invite a polite answer and give the manager nothing to coach. A better question is which part of the task was hardest to verify, or where did you have to guess. The answer points to a missing instruction, an access problem, or a skill that needs practice. When the work is sensitive, review a redacted example or a controlled exercise rather than a live client file. The goal is to observe the decision process, not to expose information to unnecessary review. The manager should state the boundary before the meeting so the new hire knows what can be shared.

Ask about the source and the stop rule

A new hire needs to know where the authoritative source lives and when to stop. Ask them to name the source they used for the task and what they would do if two sources disagreed. If they cannot answer, the onboarding material may describe the tool but not the authority. The stop rule should be simple enough to remember under pressure.

A practical rule is to pause when the task needs a decision outside the written scope, a new recipient, broader access, or a change to a client promise. The manager should praise a clean stop and explain why it was correct. Record the new hire's answer and any follow-up coaching. If the same source confusion appears in two check-ins, revise the job aid or the example. Coaching an individual will not fix a document that points to the wrong system.

Review the open questions list

A shared question list prevents the new hire from interrupting for every uncertainty or saving everything for Friday. The list should show the question, the date, the owner, and the status. The manager can review it quickly and route items that need another team. During the check-in, pick one or two questions and discuss them in depth.

A long list reviewed superficially teaches the new hire that questions are collected but not resolved. A short list with visible answers teaches the opposite. If a question has been open for more than a few days, ask why. The delay may be a missing permission, an unclear policy, or a manager who has not made a decision. Record the cause and the next check rather than letting the item disappear.

Make the next practice step explicit

End each check-in with one practice step for the next cycle. Name the task, the expected evidence, the support available, and the date of the next review. A focused step is easier to observe than a general instruction to improve. Choose work that is meaningful but recoverable.

If an error could expose customer data or trigger a payment, use a controlled exercise or a close review. The new hire should have a chance to act, make a small mistake, and correct it with support. The manager should also name what went well and why. Specific positive feedback helps the new hire repeat the behavior. Generic praise is as hard to apply as generic criticism, because it does not identify the choice that worked.

Watch for barriers the new hire cannot fix

A quiet new hire may be doing well, or may be blocked by access, unclear ownership, or a workload that never materialized. Ask directly which tasks could not start and who owns the dependency. Record the answer even when it reflects a problem outside the new hire's control. If the same barrier appears across multiple new hires, treat it as an onboarding design issue.

A missing account, a late equipment shipment, or a manager who is unavailable during the first week are process problems. Fixing them for everyone is more effective than asking each new hire to be more proactive. Do not rate the new hire on a system they could not enter or a decision nobody delegated. The evidence should distinguish effort from opportunity. That distinction protects the employee and gives the manager a more accurate view of readiness.

Close the week with a short record

At the end of the week, write a short record with the tasks observed, the questions resolved, the barriers open, and the next practice step. Keep it factual and avoid personality labels. The record should be usable by the next reviewer and by the new hire. Share the record with the new hire so they can correct factual errors.

This is not a formal performance review; it is a shared account of the week. A brief correction now is easier than a misunderstanding later. Review the record before the next check-in and compare it with the work actually completed. If the plan and the record diverge, ask why. The answer may show that the onboarding plan was too ambitious, the access was late, or the new hire needs a different example.

Use the pattern, not the script

A good check-in agenda is a pattern, not a script to read aloud. The manager should adapt the questions to the role while keeping the same evidence standard. The new hire should leave knowing what was observed, what remains open, and what happens next. After a month, review several check-in records together. Look for repeated questions, recurring access issues, and tasks that never became real. Choose one change to the onboarding plan and test it with the next hire. The goal is a first week that produces evidence and a clear next step, not a perfect conversation.

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.