New Hire 30-60-90 Day Check-In
Guide employee onboarding milestones, assess ramp-up velocity, clear roadblocks, and calibrate expectations at 30, 60, and 90 days.
Template Overview
The first 90 days of an employee’s tenure determine their long-term engagement, retention, and time-to-productivity. Without clear, written milestone checkpoints, new hires often feel lost, hesitate to ask questions, and take months to ramp up.
A disciplined 30-60-90 Day review structure provides new team members with transparent expectations at each onboarding phase, transitioning smoothly from initial learning to independent contribution and full team ownership.
This template organizes the onboarding trajectory into distinct milestone checkpoints, evaluating system acclimatization, peer connections, initial code deliveries, and mutual feedback.
Markdown Template Structure
Copy the block below or click Download .md File to add this template directly to your personal vault:
---
title: "New Hire Onboarding Check-In: [New Hire Name]"
date: [YYYY-MM-DD]
new_hire: "[[New Hire Name]]"
manager: "[[Manager Name]]"
onboarding_buddy: "[[Buddy Name]]"
role: "Senior macOS Engineer"
milestone_phase: [Day 30 Check-In | Day 60 Check-In | Day 90 Graduation]
onboarding_status: [Ahead of Schedule | On Track | Needs Support]
tags: [onboarding, new-hire, 30-60-90, management]
---
# New Hire Onboarding Check-In: [New Hire Name] — [YYYY-MM-DD]
## 1. Milestone Expectations & Core Goals
- **Day 30 (Listen & Learn):** Environment setup, code repository navigation, initial commit deployed, 1-on-1s with 5 key teammates completed.
- **Day 60 (Contribute & Collaborate):** Independent ownership of sprint issues, active code reviews, understanding customer use cases.
- **Day 90 (Own & Elevate):** Leading end-to-end feature delivery, proposing architecture refinements, mentoring future hires.
## 2. Current Progress & Accomplishment Review
- **Key Wins Delivered:** Successfully migrated markdown table parser to CommonMark specification ahead of schedule.
- **Systems Mastered:** Familiar with native CoreAudio capture pipeline and local SQLite schema.
- **Relationships Built:** Completed pairing sessions with [[Buddy Name]] and cross-team check-ins with Product.
## 3. Friction Points & Onboarding Gaps
- **What has been harder than expected?** Local developer build documentation had outdated Xcode configuration flags.
- **What resources are missing?** Need access to historical architecture decision records (ADRs).
## 4. Manager Assessment & Guidance
> [!NOTE] Manager Calibration
> High ramp-up velocity. Technical contributions are strong and aligned with team quality standards. Focus next on driving cross-team design discussions.
## 5. Next Milestone Commitments
- [ ] [[New Hire Name]] Update onboarding documentation wiki to fix Xcode configuration flags.
- [ ] [[New Hire Name]] Take ownership of upcoming sprint search indexer PR.
- [ ] [[Manager Name]] Schedule 60-day milestone review for [[YYYY-MM-DD]].
Filled Real-World Example
Here is a realistic example demonstrating how this template captures actual deliberations:
---
title: "Onboarding Check-In: Day 30 — Alex Rivera"
date: 2026-09-20
new_hire: "[[Alex Rivera]]"
manager: "[[Elena Rostova]]"
role: "Systems Engineer"
milestone_phase: Day 30 Check-In
onboarding_status: Ahead of Schedule
tags: [onboarding, new-hire, engineering]
---
# Onboarding Check-In: Day 30 — Alex Rivera — September 20, 2026
## 1. 30-Day Milestone Review
Alex completed all first-month goals within 18 days. Successfully merged PR #412 optimizing memory layout for on-device Whisper transcription.
## 2. Feedback from Onboarding Buddy
Buddy [[Marcus Vance]] reported that Alex paired proactively and quickly understood our strict zero-cloud privacy architecture.
## 3. Commitments for Day 60
- Lead implementation of SQLite FTS5 full-text indexing engine.
- Complete 60-day check-in on [[2026-10-20 Onboarding Check-In]].
When to Use and When to Avoid
When to Use
- Use at the 30-day, 60-day, and 90-day marks of a new team member’s employment.
- Use to establish objective ramp-up milestones and provide clear performance calibration.
- Use to gather constructive feedback on how to improve company onboarding documentation.
When to Avoid
- Avoid using for established tenured team members who have completed their initial year.
- Avoid using for informal daily standup updates.
On-Device AI Integration
Summarize new hire onboarding check-ins with Oyma:
Analyze the onboarding check-in audio transcript:
1. Identify the milestone phase (Day 30, 60, or 90) and current ramp-up status.
2. Outline key accomplishments, PRs shipped, and systems mastered by the new employee.
3. Extract friction points, missing documentation, or onboarding gaps identified.
4. Record manager feedback and commitments established for the subsequent milestone.
Format in clean CommonMark with milestone checklists.
Personnel evaluations and onboarding records remain completely private on your local Mac.
Frequently Asked Questions
What should be accomplished by Day 30?
By Day 30, the new hire should understand system architecture, have development environments configured, ship their first small pull request, and meet core stakeholders.
What is the focus of the Day 60 milestone?
Day 60 focuses on independent feature delivery, deeper ownership of assigned domains, and active participation in team code reviews.
What signifies successful completion at Day 90?
By Day 90, the employee operates with full autonomy, leads medium-sized initiatives, and contributes constructive feedback to improve team onboarding processes.
Write new hire 30-60-90 day check-in in plain Markdown.
Store notes in your local vault, transcribe meetings on-device, and retain 100% data sovereignty.