How to Use AI for Employee Onboarding (Plan + Prompts)

Your new hire starts on Monday. The laptop is ordered, maybe. Someone said they would set up the accounts. And the “plan” for their first weeks is a vague idea in your head plus a folder of documents nobody has opened since last year.

Here is how to use AI for employee onboarding without making it feel robotic: spend ten minutes writing down what the new person must be able to do at day 30, 60 and 90, then let ChatGPT, Claude or Gemini turn those facts into a week-by-week plan, a first-week schedule, a welcome email, a new-hire FAQ from your own documents and the questions for each check-in. You check every line against reality. The AI does the drafting. The welcome, the buddy and the conversations stay human.

Done this way, a full onboarding pack takes about an hour instead of a lost afternoon. Below are the six steps, the prompts to copy, a worked example and the things you should never paste into a chatbot.

Why most onboarding falls flat (and where AI actually helps)

If your onboarding feels improvised, you are in good company. Gallup finds that only 12% of employees strongly agree their organization does a great job onboarding new people (Gallup, Why the Onboarding Experience Is Key for Retention).

The reason is rarely bad intentions. It is time. The manager is busy, HR is busy, and the useful knowledge (“who do I ask about invoices”, “what does good look like in month one”) lives in people’s heads. So the new hire gets a login, a handbook and a lot of “just shout if you need anything”.

The SHRM Foundation’s guide on onboarding, written by Talya Bauer, lists what works: do the basics before day one, make the first day special, write an onboarding plan down, involve the people around the new hire, and check in at milestones such as 30, 60 and 90 days. It also notes that new hires get roughly 90 days to prove themselves (SHRM Foundation, Onboarding New Employees: Maximizing Success).

Look at that list again. Most of it is writing: a plan, a schedule, a welcome message, an FAQ, check-in questions. That is exactly the part AI is good at. What it cannot do is the part that matters most to the new person: a manager who makes time and a colleague who answers the “stupid” questions.

• The AI’s job: turn your facts into a clear plan, schedules, emails, an FAQ and check-in questions, and spot gaps in what you wrote.
• Your job: decide what success looks like, check every detail, and show up for the conversations.

Step 1: Write the manager’s brief first (10 minutes)

This is the step everyone wants to skip, and it is the one that makes the rest work. A chatbot that only knows “marketing coordinator” will write a plan for every marketing coordinator on earth. A chatbot that knows what your manager expects writes a plan for this person.

Answer these questions in a plain note, or send them to the hiring manager if that is not you:

1. What must this person be able to do on their own after 30 days? After 60? After 90?
2. Which three or four people (roles are enough) do they need a good working relationship with first, and why?
3. Which tools and accounts do they need, and which ones take longest to learn?
4. What do new people in this role usually get wrong in the first months?
5. Who is their onboarding buddy?
6. Remote, hybrid or on site? Which days are they in the office?

Write the 30, 60 and 90 day answers as things someone could observe. “Understands our processes” is not checkable. “Sends the weekly client report on Friday without help” is.

Step 2: Turn the brief into a 30-60-90 day plan (10 minutes)

Open a new chat in ChatGPT, Claude or Gemini, paste your brief and use this prompt:

You are helping me onboard a new employee. Below is the manager's brief.

Role: [job title]
Team and company: [one line on what the team and company do]
Work set-up: [remote / hybrid / on site]
Brief: [paste your answers from Step 1]

Write a 90-day onboarding plan, week by week, as a table with these columns:
week | focus | tasks | people to meet | how we know this week went well

Rules:
- Use only the facts in the brief. If something is missing, put [ASK] in the cell instead of guessing.
- Every "how we know" cell must be something a manager can observe, not "understands X".
- Weeks 1 to 4 focus on learning and relationships, weeks 5 to 8 on doing real work with support, weeks 9 to 13 on working independently.
- Plain language, no jargon. The new hire will read this on day one.

The [ASK] rule is the important one. AI fills gaps with confident, plausible details: a system you do not use, a meeting that does not exist. Making it mark gaps instead of filling them saves you from handing a new person a plan full of fiction.

Read the table week by week. Fix anything that is wrong, answer the [ASK] cells, and ask a follow-up if a week looks overloaded: “Week 2 has nine tasks. Cut it to the five that matter most and move the rest.”

Step 3: Build the first-week schedule and day-one checklist (5 minutes)

In the same chat, ask for the practical part. This is where onboarding usually breaks: no account on day one, no one free to say hello, a calendar that is empty or packed wall to wall.

Using the plan above, write:

1. A checklist of everything that must be ready BEFORE day one (accounts, hardware, access, calendar invites), with a column for who owns each item.
2. A day-by-day schedule for week one. Max 3 meetings per day, each with a length and a one-line purpose. Leave real time for setting up and reading.
3. A short list of things the new hire can read or try on their own when they have a quiet hour.

Mark anything you are not sure about with [ASK].

Two things are worth putting in that week on purpose. First, a one-on-one with the manager early in week one. Microsoft’s research found that new hires were 3.5 times more likely to be satisfied with their onboarding when their manager played an active role (Microsoft WorkLab, Strategies for Onboarding in a Hybrid World). Second, a first meeting with the buddy, which leads to the next point.

Step 4: Write the welcome email and intro messages (5 minutes)

A good welcome email before day one answers the questions people lie awake with: where do I go, what time, who meets me, what do I bring, is there lunch. AI writes these well, as long as you give it the real answers.

Write a welcome email to [first name], who starts as [role] on [date].

Facts (use only these, do not add anything):
- Start time and place: [address or "online, link follows"]
- Who meets them: [name, role]
- Their buddy: [name, role]
- What to bring: [list]
- First day in short: [2-3 lines from the schedule]

Tone: warm and human, like a colleague, not HR. Max 150 words.
Then write a 3-line message I can post in our team channel to introduce [first name], and a short note to the buddy explaining what I am asking of them in the first month.

Read the welcome email line by line before you send it. If the AI added “free parking” or “access to our learning portal” and neither exists, that is the first impression you make. The “use only these” instruction cuts this down a lot, but it does not replace your read.

About that buddy: it is worth the effort. Microsoft found that 56% of new hires who met their onboarding buddy at least once in the first 90 days said it helped them get productive quickly, rising to 97% for those who met more than eight times (same Microsoft WorkLab article). So put buddy meetings in the plan, every week or two, not just once.

Step 5: Turn your documents into a new-hire FAQ (15 minutes)

Every team has the handbook, the process docs and that one long email thread that explains how things really work. New people do not read them. They ask the same twenty questions instead.

Upload or paste the documents (with the personal data removed, see below) and ask:

These are our internal documents for new [role]s. Read them as if you started here today.

1. Write the 20 questions a new person is most likely to ask in their first two weeks, and answer each one using only these documents. Quote the document name for each answer.
2. List questions the documents do NOT answer, or where two documents say different things.
3. List anything that looks outdated (old tool names, people, dates).

Parts 2 and 3 are the hidden win. You find out where your documentation has holes before the new person falls into them. If a process is missing completely, write it down properly first. Our guide on using AI to write SOPs shows how to turn “ask Sanne, she knows” into a document anyone can follow.

Claude and ChatGPT both handle long documents well. If you work mostly in Claude, our Claude tutorial for beginners covers uploading files and Projects, so you can keep all onboarding documents in one place and reuse them for the next hire.

Step 6: Prepare the 30, 60 and 90 day check-ins (5 minutes)

The check-ins are where you catch problems while they are still small. SHRM recommends structured conversations at 30, 60 and 90 days, with questions like “who do you talk to when you have questions about your work?” and “what could we have done differently in setting your expectations?” (SHRM, Effective Onboarding Should Last for Months).

Based on the 90-day plan above, write a 30-minute agenda for the [30 / 60 / 90] day check-in.

Include:
- 2 questions about the milestones for this period (from the plan)
- 3 open questions about how they are settling in: people, workload, clarity
- 1 question about what we should change in onboarding for the next person
- a short space for agreeing the goals for the next 30 days

Keep the questions open and friendly. This is a conversation, not an exam.

After the conversation, you can paste your own notes back in and ask for a short summary with agreed actions. For the longer formal review later, see how to use AI to write a performance review. For any meeting in the plan, AI meeting agendas work the same way.

A worked example (fictional, to show the flow)

Say you run a 12-person agency and Lina starts as account coordinator. Your brief says: after 30 days she runs the Monday client status email for two accounts with a review; after 60 days she runs it for all five accounts alone; after 90 days she prepares the monthly client report.

The first draft plan from ChatGPT looked tidy, but it scheduled “CRM training” in week one. You do not use a CRM. You use a shared spreadsheet. Because of the [ASK] rule, the tool also flagged that it did not know who approves her client emails in the first month. You filled that in (you, until week four), replaced the CRM line and cut week two from eight tasks to five.

The FAQ step was the eye-opener. Out of 20 questions, the AI could not answer four from your documents, including “what do I do if a client emails me directly about billing?” Nobody had ever written that down. Ten minutes later it was a short paragraph in the handbook, and Lina never had to ask.

Total time: about an hour, spread over two days. Lina got a plan on day one that said what was expected of her, in her words, with names next to the tasks.

Can you automate employee onboarding with AI?

Partly, and the boring parts are the ones worth automating. Once your plan and emails exist, a tool like Zapier, Make or n8n can send the welcome email on a set date, create the checklist tasks in your project tool, and remind the buddy and manager before each check-in. Our guide to Zapier AI automation shows how to set up flows like that, and automating client onboarding with Make.com uses the same pattern for clients that you can copy for staff.

Start manual for the first hire. Automate on the second or third, once you know which steps you repeat every time. Automating a messy process just gives you a fast messy process.

What not to paste into a chatbot

Onboarding touches personal data, so be careful here:

• Leave out: salary, contract details, home address, ID or bank numbers, health information, and anything from the hiring process about the candidate. The AI does not need any of it to write a good plan. A first name and a role are enough.
• Check your account type: on ChatGPT Free, Plus and Pro, your conversations can be used to train models unless you switch off “Improve the model for everyone” under Settings, Data controls. On ChatGPT Business and Enterprise, OpenAI says it does not train on your inputs by default (OpenAI Help, How your data is used).
• Follow your company’s AI policy. If there is one, it wins. If there is none, internal process documents are usually fine to use once personal details are removed, but ask before uploading anything marked confidential.

Common mistakes

• Skipping the brief. Without it you get a generic plan that could be for any company, and the new hire notices.
• Sending AI text unread. One invented benefit or wrong address in a welcome email costs trust before day one.
• Filling every hour. A week one with eight meetings a day leaves no time to set up, read and think. Three is plenty.
• Letting the plan replace the people. A perfect document does not answer the question “is it OK to ask this?” A buddy and a manager do.
• Making a new pack for every hire. Save the brief, prompts and FAQ. Next time you only change what is different for the role.

Questions people ask about AI for employee onboarding

Which AI tool is best for onboarding?

For writing plans, emails and FAQs, ChatGPT, Claude and Gemini all do a good job. Use the one your company already pays for or allows, because the data rules matter more here than small quality differences. If you are new to it, start with our ChatGPT tutorial for beginners.

Will new hires feel it is impersonal?

Only if you let the AI do the human parts. A clear plan written with AI help, plus a manager who meets them in week one and a buddy who checks in, feels more personal than an improvised first week. Do not use AI to write the things that should come from you, like a personal note on their first day.

Can I use this for remote employees?

Yes, and it matters even more there, because nobody overhears answers at the next desk. Put the buddy meetings and the manager’s one-on-ones in the calendar from day one, and make the FAQ easy to find.

How long should onboarding last?

Longer than a first day or week. The SHRM Foundation guide suggests check-in milestones at 30, 60, 90 and 120 days and up to a year (SHRM Foundation). The 90-day plan in this guide covers the most intense part.

I am the new hire. Can I use this too?

Yes. Ask your manager the Step 1 questions in your first week, then use the Step 2 prompt to draft your own 30-60-90 day plan and bring it to your first one-on-one. Most managers are glad when someone does that.

Want a quick knowledge check in week one? A short quiz built from your own handbook beats a long FAQ nobody opens. Here is how to make a quiz with AI from the same documents you already gathered for the new-hire FAQ.

Your next 20 minutes

Before your next hire starts, write the Step 1 brief, paste it into a new chat with the Step 2 prompt, and fix whatever the [ASK] cells turn up. That plan alone puts you ahead of most first weeks people experience.

Still hiring? Our guides on using AI to write a job description and creating interview questions with AI cover the steps before day one. And for more practical AI workflows you can use at work this week, start with the free Launchpad on our home page.