Key takeaways
- Define completion before reviewing the calendar.
- Separate a canceled meeting from a meeting that never existed.
- Use the result to fix the schedule, not to rate the manager.
Question and scope
This study asks what share of the meetings planned for a new hire's first week actually took place, and where the gaps occurred. It compares the schedule created before the start date with the calendar and meeting records for the same week. The result is intended to improve the onboarding schedule and the manager's preparation, not to evaluate the new hire or the manager's commitment. The scope is one employer or one defined hiring group during a fixed period. The study may compare teams or roles, but it should not present a local completion rate as an industry benchmark. A small cohort can reveal a design problem even when most meetings happen, and that distinction should be clear in the report.
| Meeting | Evidence of completion | Common gap | Use |
|---|---|---|---|
| Manager check-in | Calendar event and notes | Moved without a replacement | Reschedule |
| Access verification | Sign-in confirmation | Account not ready | Escalate to IT |
| Team introduction | Attendee list or note | Never scheduled | Add to template |
| First task review | Review note and date | Reviewer unavailable | Name a backup |
Population and unit
The population should be drawn from a frozen list of new hires who started during the window, with the start date, the role, the manager, and the onboarding plan version recorded. Include hires whose schedules were revised after the start date, because the revision is part of the record. Exclude hires who were withdrawn or deferred before their first day, and record the reason. The unit is one planned meeting for one new hire. If a meeting was combined with another, record the combination and count the resulting session once unless the plan defined separate purposes. Report both the planned meeting count and the unique session count.
Evidence standard
Define what counts as completed before reviewing any calendar. A meeting is completed when it was held with the intended participant and a record exists, such as a calendar acceptance, a meeting note, or a short summary. A meeting that was rescheduled and held later in the week counts as completed if the purpose was met. A meeting that was replaced by a written introduction counts as completed only if the plan allowed that substitution. Define the allowed substitutions in advance so the reviewer does not make a judgment call for each case. A canceled meeting with no replacement is a gap, not a completion.
Sampling
Draw the sample from the frozen hire list using a documented method. A simple random sample may be enough for a small cohort, while a stratified sample can ensure coverage of roles, managers, and start weeks. Include hires whose schedules changed and hires whose schedules were stable. Record the selection method and any replacement. If the cohort is small, report every hire rather than a rate. A sample that includes only the smoothest starts will overstate completion, while a sample that includes only problem cases will describe failure modes without showing the base rate.
Reviewer calibration
Two reviewers should classify a calibration set before the main review. Compare their decisions on completed, rescheduled, substituted, and missed. Discuss the cases where they disagree, especially a meeting that was held informally without a calendar record. Revise the definitions and repeat the calibration. During the main review, preserve the initial ratings and the adjudication. If one reviewer counts a hallway conversation as completed and the other does not, the standard is unclear. Report the disagreement rather than hiding it in a final consensus.
Measures and reporting
Report the number of planned meetings, the number completed, the number rescheduled and held, the number substituted, and the number missed. Show the result by meeting type, because a missed team introduction and a missed access verification have different consequences. Include the time between the planned date and the actual date for rescheduled meetings. Use counts and rates together, and state the denominator for every result. A single completion percentage can hide a pattern in which the important meetings are the ones that move.
Analysis
Compare completion across roles, managers, and start weeks only when the subgroup is large enough to support the comparison. Inspect the reason for each gap before assigning a cause. A cluster of missed manager check-ins may reflect a scheduling conflict, while a cluster of missed access verifications may reflect a provisioning delay. The remedy is different, and the report should point to the stage rather than to a general label. A manager with a difficult start week may look worse than a manager with a quiet week even if both followed the same process.
Limitations
The study observes meetings that appear in the calendar and the onboarding record and may miss informal conversations that served the same purpose. It cannot measure the quality of a meeting or whether the new hire understood the content. A completed meeting may still be unhelpful, and a missed meeting may be replaced by a better conversation. System changes, calendar permissions, and manual notes can affect the record. Note the relevant dates and avoid comparing periods as if the instrument stayed constant. The result describes the sampled hires, not every onboarding in the organization.
Privacy and role boundaries
Use the minimum employee information needed for the study. Replace names with study keys, restrict access to the crosswalk, and follow the employer's retention rule. Do not copy calendar descriptions that contain sensitive personal information into the analysis file. The onboarding coordinator may prepare the sample and classify meeting status. The manager or people operations owner decides whether a schedule change was acceptable and what correction is required. The study should not be used to make an employment decision about an individual.
Data collection
Export the onboarding plan and the calendar entries for each sampled hire at the same point in time, and record the export date and the system used. Capture the meeting title, the planned date, the participants, and the status shown in the calendar. Collect any meeting note or summary that the manager or coordinator stored in the approved location. Do not reconstruct a missing meeting from memory after the review begins. If a meeting was held without a calendar entry, record the note and the source, then classify it under the evidence standard rather than treating the note as proof that the planned meeting occurred. Keep the original export with the study file so a second reviewer can reproduce the result.
From finding to controlled change
Choose one change based on the most common or most consequential gap. It might be a required manager check-in, a backup reviewer for the first task, a shorter introduction list, or a rule that a canceled meeting must be rescheduled within two days. Name the owner, the due date, and the measure that will show whether the change helped. Recheck the same measure with the next cohort rather than declaring success after one good week. Keep a short decision log with the finding, the change, the owner, and the result.
Worked example
A new hire's first week includes six planned meetings. The manager check-in is moved from Monday to Wednesday and held. The access verification is missed because the account is not ready, and the IT owner opens a ticket. The team introduction is replaced by a written note that the plan allows, and the first task review happens on Friday. The study counts four completions, one allowed substitution, and one gap. The gap is an access issue rather than a scheduling failure, and the report routes it to the provisioning owner. The example shows why the reason for each gap matters more than the completion rate alone.
Review cadence
Review the schedule after each hiring cohort and before a peak hiring period. A quarterly review may be enough for a stable process, while a monthly review is more useful when a new manager, a new role, or a system change is in play. Record the cadence in the onboarding procedure. Between reviews, keep an exception log for missed or moved meetings. The log helps the team see whether the schedule is drifting before the next formal review. If the log and the review disagree, investigate the difference rather than assuming one source is wrong.
What the report should not claim
The report should not say that a manager is ineffective or that a new hire is engaged. It should say which planned meetings occurred, which were replaced, and which were missed. That distinction matters because a schedule gap can reflect a system problem, a calendar conflict, or an unrealistic plan. The report also should not compare teams as if their roles and start weeks were identical. A difference may reflect the work, the travel, or the hiring volume. Keep the comparison inside the defined standard and state the version used.
Sources and methodology
A bounded documentary review of first-week meeting schedules and calendar records for a defined hiring cohort. The study compares planned meetings with meetings that actually occurred and records the reason for each gap. Public guidance frames the questions but does not validate a local schedule or supply a performance conclusion.
- U.S. Office of Personnel Management — Training and Development current.
- U.S. Small Business Administration — Hire and manage employees current.
- U.S. Department of Labor — New Hire Reporting current.
- NIST Cybersecurity Framework 2.0 current.
- U.S. Equal Employment Opportunity Commission current.
- U.S. Census Bureau current.
Source count: 6. Last verification date: November 4, 2026.
Questions about the findings
What is the unit of analysis?
One planned meeting for one new hire during the first week, with rescheduled and substituted meetings recorded separately.
Does a canceled meeting always count as a failure?
No. The study distinguishes a gap from an allowed substitution and from a meeting that was rescheduled and held.
Put the finding to work
Review the full research library, compare cluster coverage inside Onboarding Experience, and pair these findings with our VA candidate screening support.
