Prepare the record before the meeting
A thirty-day review should use the onboarding plan, the first-week notes, the access record, and the completed task samples. Ask the new hire and the manager to add the questions they still have. The coordinator should mark which items were resolved and which remain open. Do not rely on memory or a single conversation to reconstruct the month.
Keep the preparation short enough that it actually happens. A one-page summary with the role outcomes, the first-month tasks, the access granted, the training completed, and the open questions is usually enough. If a system can produce the access and training record, attach it rather than retyping it. The review is a decision meeting, not a documentation exercise.
Check role clarity against real work
Ask the new hire to describe the role's main outcome in their own words. Compare that description with the role memo and the manager's expectations. If the descriptions differ, record the gap and decide which one is correct. A new hire can complete every task and still misunderstand the purpose of the role.
Review two or three examples of completed work. Ask what the new hire used as the source, what they were unsure about, and what they would do differently. The manager should identify whether the issue is instruction, access, skill, or an unrealistic workload. Do not turn the sample review into a broad performance rating; the goal is to fix the onboarding design while it is still early.
Close or reassign every open item
List the open items from the first month: missing access, incomplete training, unclear ownership, unresolved questions, and any equipment or schedule issue. Give each item an owner and a date. If an item cannot be closed in the review, record the next step and the person who will follow up. Do not leave an item open without an owner.
Decide whether the new hire is ready for the next set of tasks. If not, say what must be true before the scope expands. If yes, record the added task and the review point. The decision should be based on observed work and the support available, not only on time elapsed. A thirty-day review is a checkpoint, not an automatic confirmation.
Feed the findings back into onboarding
At the end of the review, identify one change that would help the next new hire. It might be a clearer role memo, an earlier access request, a better training example, or a named backup for the manager. Record the change, the owner, and the date it will be tested. Do not list every possible improvement; choose the one with the clearest effect.
Compare the finding with the previous cohort and with the first-week notes. If the same gap appears repeatedly, change the template or the sequence rather than coaching each new hire individually. Keep the review summary with the onboarding record. The value of the thirty-day review is not the meeting itself; it is the closed loop between what happened and what the next hire will experience.
Continue building the workflow
Related support: onboarding operations support, contact us. The U.S. Equal Employment Opportunity Commission employment opportunity guidance and 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.
Write a first-week check-in agenda that produces decisions
A first-week check-in agenda that turns a status conversation into named decisions, owners, and follow-up dates.
