How-to: Prep Your 30-Day Check-In
Your 30-day check-in is not a pop quiz you either pass or fail. It is a structured conversation with your manager about whether onboarding is working: access, clarity, relationships, early delivery, and support. People who wing it get vague reassurance. People who prep leave with priorities, feedback, and a realistic plan for the next 30 days.
Time box: 45–60 minutes to prep the day before (or weekend before) a 30-minute check-in. The meeting itself is usually 25–40 minutes; confirm with your manager.
Home base: New hire hub. Pair with the Individual Contributor hub for how to show progress without theater. Managers running the other side should also see the day-one and 90-day pieces in this series and the New Manager hub.
When to use / when not
Use when:
– You are approaching ~30 calendar or working days in role (follow your company’s definition)
– Your manager scheduled a check-in, or you should request one if none exists
– You want clarity on “what good looks like” before habits harden
– You have early signal on blockers (access, training, scope confusion)
Do not use when:
– You are in an HR-sensitive situation that needs a formal channel first (how HR works)
– You plan to use the meeting only to complain with no examples or asks
– You have been there far longer and need a normal 1:1 or performance conversation instead
If your company uses a buddy-led 30-day instead of manager-led, still prep; bring the same artifacts.
Prep
Gather a simple packet:
- Role scorecard: what you think success looks like at 30 / 60 / 90 (even if unofficial)
- Wins list: 3–5 concrete things you learned, shipped, or unblocked (no inflated metrics)
- Open questions: priorities, stakeholders, decision rights, tools
- Blockers: access, documentation gaps, unclear owners
- Feedback ask: one or two areas you want your manager’s read on
- Draft 30–60 plan: what you propose to focus on next
Map key partners using how departments work together so you can name who you still need time with.
Steps
- Skim onboarding docs and your offer/role notes (10 min). Re-anchor on why you were hired.
- Build the wins / learning list (10 min). Prefer specifics: “shadowed three customer calls” beats “learning the business.”
- List blockers with owners (10 min). Every blocker needs a next ask, not just a vent.
- Draft three priority questions (5 min). Example: “What should I optimize for this month: depth in X or breadth across Y?”
- Write a proposed next-30 plan (10 min). Three outcomes max.
- Send a short pre-read (5 min). Help your manager show up ready.
- In the meeting: lead with progress, then blockers, then asks, then feedback.
- After: send a summary note the same day.
Script (what to say / send)
Pre-read message:
Ahead of our 30-day check-in, here’s a one-pager: (1) what I’ve focused on, (2) early wins/learning, (3) blockers, (4) proposed priorities for days 31–60. I’d like your feedback on whether I’m aimed at the right outcomes.
Opening:
“Thanks for making time. I want to confirm I’m learning the right things, clear blockers, and align on the next 30 days. I’ll keep us to the doc.”
Progress beat:
“Three things I’m glad I did: [A], [B], [C]. The biggest learning was [insight].”
Blocker beat:
“I’m still blocked on [access/decision]. I’ve tried [steps]. Ask: can you unblock or point me to the owner this week?”
Priority ask:
“For days 31–60 I propose focusing on [1], [2], [3]. What would you cut or add?”
Feedback ask:
“Where should I improve based on what you’ve seen so far: communication, pace, quality, or stakeholder management?”
Close + summary email:
Thanks for today’s 30-day. Agreements: priorities [list]; you’ll help with [unblock]; I’ll deliver [checkpoint] by [date]. Next check-in aim: ~60 days.
Output artifact
30-day check-in one-pager:
- Role context (one paragraph)
- Learning and wins (bullets)
- Relationships started / still needed
- Blockers + asks
- Proposed 31–60 outcomes
- Feedback questions for manager
Keep it to one page. Attach links; do not paste novels.
Watch-outs
- Only good news. Hiding confusion delays help. Name risks early.
- Only bad news. Balance with evidence you are trying.
- No ask. Managers cannot read minds; end with decisions you need.
- Comparing your day 30 to someone else’s year three. Ask for the bar for your role at 30 days.
- Skipping stakeholders. If you only talk to your team, you will miss how how sales works or finance constraints shape the work; schedule those intros.
- Treating it as a grade. It is a steering conversation. Use it to steer.
- Forgetting to write it down. Memories diverge; the summary email is part of the deliverable.