How to Build an Employee Onboarding Plan with Claude
You'll finish with a complete, role-specific onboarding plan your new hire can actually follow from day one — even if it's their first day tomorrow, even with no onboarding process in place, even if you've never onboarded anyone before. Answer three questions, run one prompt, fill two gaps. Done.
TL;DR
- You'll have a structured, week-by-week onboarding plan in under three minutes — built around the actual role, not a generic template.
- Free plan at claude.ai handles this without issues; no upgrade needed.
- Claude builds the structure; you add the company-specific details it can't know.
- What used to take a full afternoon of googling templates and second-guessing takes 25 minutes, including edits.
Before you start
- A Claude.ai account — free plan is fine. One full onboarding plan, including follow-up edits, fits comfortably in a single conversation.
- A clear enough picture of the role that you can describe what the new hire will do in week one. You don't need a polished job description — a few bullet points of what they'll actually be doing is enough.
- A sense of your capacity to onboard them — are you able to spend two hours with them on day one, or will they largely be working through materials independently? Claude will structure the plan differently based on this.
- A rough list of the tools, systems, or processes the new hire will need to learn. Without this, you'll end up with a plan that sounds complete but skips the practical logistics that actually make a first week work.
How to do it — step by step
Map the first 30 days before opening Claude
Start by answering three questions in a notes app or plain text doc — not because Claude needs a polished brief, but because you need to be clear on the answers before you can give useful input. What does the new hire need to know or be able to do to function independently by the end of week one? Who do they need to meet in the first two weeks, and why does each relationship matter for their work? What's the single most important thing they should be able to do — or understand — by day 30? Spend an extra minute on the day-30 question, because it forces you to define what success looks like, which shapes every earlier milestone. If you're hiring for the first time and don't have clear answers yet, the HR Workflows hub has a short role-scoping exercise that helps you work backward from outcomes to tasks.
Decide what kind of onboarding experience you're building
Before moving on, nail down three things Claude needs to get the structure right: Is this person working onsite, remotely, or hybrid? How much of your own time can you realistically dedicate to them in week one — a few hours total, or are you able to be genuinely available? And is this a complex role where it'll take weeks to ramp up, or one where they can be doing real work by day three? These aren't philosophical questions — they determine whether Claude builds a self-guided onboarding document, a manager-led daily check-in schedule, or something in between. Don't worry if your answer to the time question is "not much" — that's actually useful information that produces a more realistic plan.
Run the prompt and review the draft plan
Now open Claude, paste the prompt below, fill in the green placeholders with your answers, and send. Claude returns a structured onboarding plan — typically covering pre-arrival logistics, week one priorities, key introductions, and a 30-day milestone — in under two minutes. At this point, read the output as a skeleton, not a finished document. You're looking for two things: gaps that only you can fill (specific tools, logins, people, internal processes), and anything that assumes resources you don't have. Don't fix these yet — just note them. The HR Prompt Builder has onboarding-specific follow-up prompts you can use if the first draft needs significant restructuring.
Add what only you know
This is where the plan becomes yours. Go through the draft and add: the specific tools and systems the new hire needs access to and in what order; the names and roles of the people they should meet and what each conversation is for; any unwritten rules or processes that aren't obvious from the outside — how decisions get made, how the team communicates, what "done" looks like for common tasks. Then paste everything back into Claude and ask it to restructure the plan around your additions. A prompt like "Add a day-one logistics section covering access, equipment, and their first-hour check-in. Assume they're starting remotely" usually gets the biggest structural gaps closed in one pass. The AI for HR Teams hub has more examples of these targeted follow-up instructions for common sticking points.
Make it something you can actually hand over
Copy the plan into a shared document and add links, forms, and resources the new hire will need. Then read it once from their perspective — does it tell them what to do on their actual first morning, or does it just describe what a good first week looks like in the abstract? If it's the latter, ask Claude: "Rewrite the day-one section as a concrete to-do list for their first three hours." Send the finished document to the new hire at least 48 hours before their start date.
The prompt
You are helping me build an employee onboarding plan for a new hire. Context: - Job title: [e.g. Marketing Coordinator, Operations Manager, Junior Developer] - Company name and what we do: [e.g. Redfield Studio — a 6-person branding agency working with UK startups] - Working arrangement: [e.g. fully remote, hybrid 3 days in office, or fully onsite] - Start date / urgency: [e.g. starting Monday, or three weeks from now] - What they'll be doing in week one: [List 3–5 specific tasks or activities — be concrete] - Tools and systems they'll need to learn: [e.g. Slack, Notion, our project management tool, Xero — list in order of priority] - Key people they need to meet in the first two weeks: [Name and role, and one sentence on why each relationship matters] - What success looks like at 30 days: [One or two sentences — what should they be able to do or understand independently by then?] - Your available time to onboard them: [e.g. I can dedicate 2 hours on day one and 30 mins daily for the first week; or I have very limited capacity and need this to be mostly self-guided] - Tone: [e.g. warm and encouraging, direct and practical, formal] Using the information above, write a complete employee onboarding plan with the following sections: 1. Pre-arrival checklist — everything that needs to be done before day one (access, equipment, calendar invites, welcome message). 2. Day one schedule — a concrete hour-by-hour or block-by-block plan for their first day. 3. Week one priorities — 3–5 specific things to learn, complete, or understand by end of week one. 4. Key introductions — who they meet, when, and what each meeting is for. 5. 30-day milestone — one clear, measurable thing they should be able to do independently by day 30. 6. Resources and reading — a placeholder list of materials to share (I will fill in the specific links). Write in the tone I specified. Make every item concrete and actionable — avoid vague guidance like "get settled in" or "learn the culture." If I've left anything ambiguous, make a reasonable assumption and flag it at the end so I can correct it.
What the output looks like
Onboarding Plan — Marketing Coordinator, Redfield Studio
Pre-arrival checklist
Send Slack invite and add to all relevant channels by Thursday. Create Notion account and share the team workspace link. Add to the Monday.com project board with view-only access until day three. Send a welcome email with day-one schedule, office address, and point of contact. Block 9:00–11:00 on their calendar for the day-one orientation.
Day one — block plan
9:00–10:00: Orientation with line manager — company overview, how the team works, and a tour of the key Notion pages they'll use most. 10:00–11:00: Tool setup — Slack, Notion, email, and access to the shared drive. 11:00–12:30: Independent reading time — three specific Notion pages (brand guidelines, active client list, current project board). 14:00–15:00: First client context meeting with Senior Designer.
Week one priorities
Understand the active project pipeline and be able to name each client and their current status. Shadow two client briefing calls and take notes. Complete the Notion onboarding checklist (link to follow). Submit first draft of the June content calendar by Friday for feedback.
30-day milestone
By day 30, independently manage the social content calendar for one active client — drafting, scheduling, and reporting without requiring daily check-ins.
Claude vs Gemini for this workflow
| Dimension | Claude | Gemini |
|---|---|---|
| Producing concrete, actionable steps (not vague guidance) | Better | Good |
| Flagging its own assumptions for you to correct | Better | Good |
| Adapting tone to remote vs. onsite vs. hybrid context | Better | Good |
| Integration with Google Docs and Google Calendar | Good | Better |
| Speed on free plan | Good | Better |
| Overall recommendation | Recommended | Solid alternative |
How to customise this workflow
For solo founders onboarding their first ever hire
Start by adding this line to the prompt: "I've never onboarded anyone before — after producing the plan, flag anything that assumes existing HR processes or documentation I probably don't have." Claude will surface the gaps (like a formal employment contract checklist or a written probation policy) without you having to know they exist. Also, before running the prompt, ask Claude in a separate message: "What are the three most common onboarding mistakes made by small businesses hiring their first employee?" The answer takes 30 seconds to read and reframes what you're trying to avoid — which is usually not the paperwork, but the first 48 hours where a new hire feels left alone with no direction. The AI for HR Teams hub has more guides built specifically for business owners doing HR work without a dedicated team.
For freelance HR consultants building plans for clients
If you're producing onboarding plans for multiple clients a month, the setup cost adds up fast. Save a base version of the prompt in your notes tool with your most common client formats — industry, team size, working arrangement — and swap in the role-specific details before each run. That drops the setup from ten minutes to under three. For clients who struggle to articulate what week one should look like, ask them this: "What's the one thing, if your new hire understood it completely by day five, that would make the biggest difference?" That single question usually unlocks the specifics that make an onboarding plan genuinely useful rather than decorative. The HR Prompt Builder has onboarding-specific templates you can adapt per client type and reuse without starting from scratch.
For remote hires starting without in-person orientation
Remote onboarding fails most often in the first 72 hours, when a new hire has access to systems but no obvious place to start. Add these two lines to your prompt: "Assume the new hire has no in-person orientation and will spend their first morning working through materials independently" and "Make the day-one plan explicit enough that they don't need to ask anyone what to do next." The second instruction matters because the default onboarding instinct — "schedule a call and walk them through things" — collapses when you're in different time zones or when the manager is unavailable. Before moving on, check that the day-one section names a specific first task for their first 20 minutes. That's the detail that determines whether someone feels oriented or adrift.
For roles with long ramp-up times (technical or senior positions)
Don't worry if a 30-day milestone feels premature for a complex role — just be honest about it in the prompt. Write something like: "This is a senior role with a genuine 90-day ramp-up; the 30-day milestone should be about relationship-building and context, not independent output." Claude adjusts the structure accordingly and stops setting expectations that would make a new hire feel like they're failing during a normal learning curve. After you get the first draft, ask for a follow-up: "Add a 60-day and 90-day milestone section using the same format." That turns a first-week document into a complete probation-period roadmap, which is useful both for the new hire and for any performance conversations down the line.