👥 HR & Recruiting Prompt Generator Free · No Signup

30-60-90 Day Onboarding Plan Generator — With a First-30-Days Deep Dive

⚡ Quick Answer

A 30-60-90 onboarding plan splits a new hire's first quarter into learning (days 1–30), contributing (31–60), and owning (61–90). This generator builds the plan as three checklists — new hire, manager, and People Ops — with milestones, check-in questions, and risk signals per phase, and nothing invented about your company.

⚡ 30-60-90 Day Onboarding Plan Generator — With a First-30-Days Deep Dive

Configure your facts below to generate a production-ready, constraint-locked prompt.

100% Client-Side

A note on the name — why this page targets 30-60-90

Searchers ask for "30-day onboarding plans", but what the results — and good practice — actually deliver is the 30-60-90 structure: thirty days is the first phase of a ninety-day ramp, not the whole plan. So this generator targets the full 30-60-90 plan as its primary output, and gives the first 30 days the deepest treatment of any phase — its own section below — because month one is where onboarding is won or lost. If you genuinely only need month one, the generator's first phase stands alone as a complete 30-day plan.

What this generator does

Most onboarding plans are a single document written for nobody in particular: a list of things that will happen around the new hire. This generator produces the plan as three parallel checklists, because onboarding fails at the seams between owners:

Each phase carries four things: the phase goal in one line, the checklist items with owners, the measurable milestone that proves the phase worked, and the risk signals — the observable early warnings (missed check-ins, no questions by week two, access still pending at day 10) that tell a manager to intervene while it's still cheap. And anything the generator doesn't know — your tools, your rituals, your stakeholders — it leaves as a bracketed [PLACEHOLDER] rather than inventing a plausible-sounding company fact. An onboarding plan full of invented detail is worse than one with honest gaps.

The first 30 days, in depth

Days 1–30 are the learning phase, and they set the trajectory for the whole quarter. A good first month has five components, and the generated plan covers each explicitly:

  1. Before day one (People Ops + manager). Equipment ready, accounts provisioned, buddy named, first-week calendar sent. A new hire whose laptop arrives on day three has learned something about your company you didn't intend to teach.
  2. Week one's map. Who the team is, who the stakeholders are, where decisions get made, where the documentation actually lives. The manager's checklist includes the "unwritten rules" conversation — every team has them; naming them is a gift.
  3. Learning with a purpose. Reading, shadowing, and training tied to the first deliverable: not "learn the product" but "learn the billing flow you'll be changing in week six".
  4. Small, real work early. One bounded, genuinely useful task in weeks 2–3 — small enough to finish, real enough to matter. Confidence in month one comes from a completed thing, not from orientation sessions.
  5. The day-30 check-in. A structured conversation (question set included in the output): what's clear, what's confusing, what support is missing, and a simple 1–5 self-rating of confidence and role clarity — low scores are risk signals to act on this week, not trivia to file.

How it works

  1. Enter the facts of the hire. Role, team, start date, manager, buddy, the systems they'll need, the stakeholders, and — most important — the first deliverable and the day-90 success picture.
  2. Generate the plan. Three checklists across three phases, plus check-in question sets for days 30, 60, and 90.
  3. Fill the placeholders. Every [PLACEHOLDER] is the generator honestly marking something only you know. A plan with five filled placeholders beats a plan with five invented details.
  4. Turn it into a tracker. Copy the checklists into your tool of choice (the output is checkbox-ready markdown) and tick items off with owners visible.
  5. Run the check-ins against the risk signals. The plan tells you what drift looks like at each phase; the check-ins are where you catch it.

The prompt template

PROMPT TEMPLATE 
You are an experienced People Operations specialist designing a new hire's first 90 days.

INPUTS — use only what I supply; leave a [PLACEHOLDER] for anything else:
- Role and team: [role, team]
- Start date: [date]
- Manager: [name] · Buddy: [name, or PLACEHOLDER]
- Systems and tools needing access: [list]
- Key stakeholders to meet: [list]
- First deliverable expected: [describe, or PLACEHOLDER]
- What success looks like by day 90: [describe]

BUILD THE PLAN IN THREE PHASES:
- DAYS 1–30 — LEARN: absorb the product, team, and tools; build relationships; complete one small, real piece of work.
- DAYS 31–60 — CONTRIBUTE: work on real deliverables with support available; first owned project underway.
- DAYS 61–90 — OWN: work independently; first significant deliverable shipped; development goals for the next quarter agreed.

FOR EACH PHASE, PRODUCE THREE CHECKLISTS — New Hire / Manager / People Ops — and for each phase also give:
- The phase goal (one line).
- The measurable milestone that proves the phase worked.
- "What good looks like" (2–3 observable signs).
- Risk signals (2–3 observable early warnings a manager should act on, e.g. access still pending at day 10, no questions raised by week 2, check-in missed twice).
- A check-in question set for the end of the phase (5–6 questions for the manager to ask, including one 1–5 self-rating of confidence and one of role clarity).

FORMAT: checkbox markdown (- [ ]) so the plan pastes directly into a tracker. Every item has an owner implied by its checklist. Dates relative to start date ("by end of week 2") unless I gave exact dates.

NEGATIVE CONSTRAINTS:
- Do NOT invent company facts — no tool names, meeting names, values, rituals, people, or policies I did not supply. Use [PLACEHOLDER: …] and name what's needed.
- Do NOT set performance judgements or probation pass/fail criteria — the plan describes support, milestones, and signals; formal evaluation criteria come from HR policy, not from you.
- Do NOT schedule anything on the new hire's first day before they have equipment and access confirmed by People Ops' checklist.
- Do NOT include questions or tasks that probe protected characteristics (family circumstances, health, religion, age) — check-ins ask about the work, the support, and the role only.
Best model for this: Gemini 4 Argon when your inputs are long (full job description + team handbook excerpts) — its context window holds the whole pack; Claude Sonnet 5.5 for the cleanest checklist prose from shorter inputs.

Worked example

Filled inputs: Role: Content Marketing Manager, Growth team. Start: Monday 3 November. Manager: Sara Iqbal. Buddy: Dev (Senior Content Strategist). Systems: CMS, analytics dashboard, project board, design tool. Stakeholders: Product Marketing lead, SEO consultant, Sales enablement manager. First deliverable: audit of the existing blog's top 20 posts. Day-90 success: own the content calendar end-to-end and ship one pillar article.

Output excerpt (Days 1–30, manager's checklist + one risk signal):

Phase goal (Days 1–30): Learn the product, the audience, and how content gets made here — finish with one small shipped improvement.
Manager — Sara:
- [ ] Day 1: team intro + walk Dev through as buddy; hand over the "how we work" doc
- [ ] Week 1: 1:1s booked with Product Marketing lead and Sales enablement manager
- [ ] Week 2: walk through the top-20-posts audit brief together; agree what "done" looks like
- [ ] Week 3: review first audit findings draft; give feedback in the doc, not in the meeting
- [ ] Day 30: run the 30-day check-in using the question set; agree month-2 priorities
Risk signal: audit brief still not started by end of week 2 — usually means access or context is missing, not effort. Ask before assuming.

Guardrails

Frequently Asked Questions

Practical answers covering model choice, workflow integration, and compliance rules.

Each phase needs a one-line goal, the checklists for the people who own the work, a measurable milestone, and the signals that show the phase is drifting. In substance: days 1–30 are learning and orientation — product, team, tools, one small real task, access and equipment complete; days 31–60 are contributing with support — real deliverables underway, first owned project started, stakeholder relationships live; days 61–90 are independent work — the first significant deliverable shipped and next-quarter goals agreed. A phase without a milestone produces drift, because nobody can tell whether it worked.

Split it by what each party controls. People Ops owns everything that must exist before the person can work: contracts, equipment, systems access, compliance training, the buddy assignment. The manager owns context and trajectory: introductions, the "how we work" conversation, check-ins, feedback, and milestone reviews. The new hire owns the doing: the learning, the questions, the deliverables. That's why this generator emits three checklists instead of one document — most onboarding failures are really ownership failures, where everyone assumed someone else had booked the laptop, the access, or the first meeting.

Ask about clarity, support, and surprises — not performance. A proven set: What part of the role is clearest so far, and what is still fuzzy? What do you need that you don't have yet — access, context, introductions? What surprised you most in month one? What's one thing the team does that you would change? And two 1–5 self-ratings: confidence in doing the job, and clarity about what success looks like. A low clarity score at day 30 is the most actionable data point in early onboarding — it means the plan, not the person, needs adjusting.

The generated plan is already checkbox markdown, so it pastes directly into Notion, a project board, or a shared doc and ticks off item by item. For a progress view, add three columns — item, owner, status — and review completion at each phase check-in rather than continuously: a phase that ends 90% complete with the right 10% open (the substantive items) is healthier than one that's 100% ticked through orientation theatre. Some teams add a simple progress bar per phase; the check-in questions in the plan supply the qualitative half the bar can't show.

More detailed than the other two phases — deliberately. Month one is when the new hire knows least and the cost of a missed item (access, introductions, the first small win) is highest, so this page gives days 1–30 their own deep section and the generator its finest granularity: day-level in week one, week-level after. Days 31–60 can be firmer than 61–90 but still flexible; by day 61 the plan should mostly name outcomes and let the now-ramped hire choose the path. Detail should decrease as context increases — that's the shape of a good ramp.

Internal links

--- End of HR & Recruiting cluster file.