Build a 30-60-90 Day Onboarding Plan with Weekly Goals and Owners

Get a 30-60-90 day onboarding plan split into weekly goals, each with a named owner, a done-when test and a manager check-in question per phase.

Prompt

Prompt
You are an HR business partner who designs onboarding plans for growing teams.

Your job: build a 30-60-90 day onboarding plan for a new hire on my team.

Before writing anything, ask me these questions in one message, numbered, then wait for my answers:
1. What is the role, its level, and the start date?
2. Who is on the team (manager, buddy, key partners), and do they work remote, hybrid or in office?
3. Which tools and systems will the new hire use every day?
4. What should this person own or deliver by day 90?

Rules:
- Use weekly goals for weeks 1-4, then two-week blocks for days 31-90.
- Every goal starts with a verb and names one owner (new hire, manager, buddy, IT or a named person).
- Every goal has a done-when test someone can check. Never write "get familiar with".
- End each phase with one check-in question the manager asks in a 1:1.
- Keep week 1 focused on access, people and context, not output.

Output format:
## Days 1-30: Learn
Table: Week | Goal | Owner | Done when
Check-in question:
## Days 31-60: Contribute (same table and check-in)
## Days 61-90: Own (same table and check-in)## Risks to watch (3 bullets)

Finish with one line naming any assumption you made or information I did not give.

Example output

At a glance30-60-90 day onboarding for a remote CSMThree phases with weekly goals, owners and check-ins
  1. Learn: tool access and team introsWeek 1HubSpot, Zendesk, Slack, Gong set up; 5 teammate calls
  2. Learn: shadowing and certificationWeeks 2-4Shadow 6 calls, modules 1-3, review 10 accounts
  3. Contribute: lead calls, take accountsWeeks 5-6Lead 4 check-ins, take over 10 accounts
  4. Contribute: QBRs and playbookWeeks 7-8Run 2 QBRs, document one playbook gap
  5. Own: grow book and save plansWeeks 9-10Book of 25 accounts, save plans for 3 at-risk
  6. Own: renewals and learningsWeeks 11-13Q3 renewal conversations, 10-minute team session

Example for: a remote Customer Success Manager joining a 6-person CS team at a B2B SaaS company, managed by Priya, buddy Marcus.

Days 1-30: Learn

WeekGoalOwnerDone when
1Set up access to HubSpot, Zendesk, Slack and GongITAll four tools log in without errors by day 2
1Meet each CS teammate in 20-minute video callsNew hire5 calls held, notes shared with Priya
2Shadow 6 customer calls with MarcusBuddyNew hire writes a one-paragraph summary of each
3Complete product certification modules 1-3New hireQuiz scores of 80% or higher
4Review 10 assigned accounts and flag health risksNew hireRisk list reviewed with Priya in 1:1

Check-in question: What has surprised you most about our customers, and what is still unclear?

Days 31-60: Contribute

WeekGoalOwnerDone when
5-6Lead 4 check-in calls with Marcus listeningNew hireMarcus gives written feedback on each call
5-6Take over 10 accounts as primary contactManagerAccounts reassigned in HubSpot, customers emailed
7-8Run 2 quarterly business reviewsNew hireDecks reviewed by Priya, both QBRs held
7-8Document one gap in the onboarding playbookNew hireEdit suggested in the team wiki

Check-in question: Which part of the job feels slower than it should, and what would fix it?

Days 61-90: Own

WeekGoalOwnerDone when
9-10Grow book to 25 accountsManager25 accounts show the new hire as owner
9-10Build save plans for 3 at-risk accountsNew hirePlans approved and first actions logged
11-13Hold renewal conversations for Q3 accountsNew hireAll Q3 renewals have a logged next step
11-13Present 90-day learnings at team meetingNew hire10-minute session delivered

Check-in question: What do you want to own in the next quarter that you don't own today?

Risks to watch

  • Remote isolation: if buddy calls slip below twice a week, Priya should step in.
  • Account handover gaps: missing notes from the previous owner can stall weeks 5-6.
  • Certification delays push back solo calls; protect 4 hours a week for training in weeks 2-3.

Assumption: renewal targets were not given, so day-90 goals measure activity, not revenue.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Asking about role, team, tools and day-90 goals first means the plan fits your hire instead of a generic checklist.
  • Naming one owner per goal stops tasks falling between manager, buddy and IT.
  • Done-when tests and phase check-in questions make progress easy to track in real 1:1s.

Use this a week or two before a new hire starts. Have the role, team names, main tools and 90-day expectations ready. Works in ChatGPT, Claude or Gemini; paste the result into your onboarding doc.

Common edits

  • Ask for a version written to the new hire in second person to send before day one.
  • Change the phases to 2-4-8 weeks for interns or short contracts.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in HR & Management