Published October 27, 2026.
Decide what each checkpoint is for
The thirty day checkpoint should test whether the new hire has the access, training, and context to do the job. The sixty day checkpoint should test independent work on core tasks. The ninety day checkpoint should review the full role and set the next development goals. Each has a different purpose and a different set of questions.
Put the dates on the calendar at acceptance
Create the three meetings when the start date is confirmed. Invite the manager, the new hire, and the HR contact or skip-level where the policy requires it. A checkpoint that is scheduled late becomes a catch-up conversation with no chance to correct course.
Use a shared preparation sheet
Before each meeting, the manager and employee should each note what is working, what is unclear, and what needs to change. The sheet should include the core tasks for the role and the evidence of progress. It is a preparation aid, not a scorecard to be filed without discussion.
Distinguish learning gaps from performance concerns
A new hire who has not yet handled a complex case may be on schedule. A new hire who repeatedly misses a core task after training may need a documented performance conversation. Use different language and different follow-up for each. Confusing the two makes the process feel arbitrary.
Record the support provided
If the manager promises training, a shadowing session, or a tool fix, record the owner and the date. At the next checkpoint, check whether the support actually happened. A performance concern that traces back to missing support is an onboarding problem, not an employee problem.
Handle role changes and extensions
If the role changes, the start date moves, or the employee transfers, update the checkpoint dates and the criteria. Do not apply the old ninety day plan to a different job. Record the reason for the change and who approved it.
Close the ninety day review
Summarize the evidence, the agreed strengths, the development areas, and the next goals. Confirm whether the employee is confirmed in the role under the organization's policy. Give the employee a copy and store the record with the employee file.
A support role example
A new operations coordinator meets the thirty day learning goals but is still slow on the billing queue at sixty days. The manager discovers the training video was outdated. The team updates the guide, the employee gets a shadowing session, and the ninety day review shows the improvement with dates and examples.
Review the pattern across hires
At the end of each quarter, look at checkpoint themes across new hires. Repeated gaps in the same system or training module point to an onboarding fix. Repeated manager delays point to a scheduling or workload issue. Use the pattern, not a single case, to change the program.
- Thirty day purpose
- Sixty day purpose
- Ninety day purpose
- Preparation sheet
- Support commitments
- Final decision
Sources
- SHRM onboarding toolkit
- U.S. Equal Employment Opportunity Commission
- BLS Employer Costs for Employee Compensation
- Plain Language Guidelines
Continue building the workflow
Related support: virtual assistant role brief, virtual assistant onboarding checklist. The U.S. Equal Employment Opportunity Commission explains that employment selection procedures should be job related and consistent with business necessity.