How to onboard your team to AI with a simple checklist

By the end of this, you will have a simple checklist for introducing AI to your team well, covering what to set up, what to share, and what to agree together.

Introducing AI to a team is less about the tools and more about the groundwork. Get a few basics in place first, and people start with confidence rather than confusion. Skip them, and you end up with everyone quietly working it out alone, which is slower and riskier.

This checklist keeps it light. You can work through it in an afternoon, and none of it needs a big budget or a technical background.

What you will need

• Any AI chat tool to help you tailor the wording: Claude, ChatGPT, or Gemini.
• A rough sense of what your team does day to day, and which tasks eat the most time.
• 15 to 25 minutes to adapt the checklist, then a short session with your team.

Step 1: Know what good onboarding covers

Before you tailor anything, it helps to see the shape of it. Good onboarding does four things: it sets up the practical basics, it shares a bit of know-how, it agrees a few sensible ground rules, and it gives people a first win so AI feels useful straight away.

Jot down anything specific to your world first. A design team cares about very different tasks from a finance team, and the checklist should reflect that.

What to expect: a short list of your own priorities to fold into the checklist below. If you are not sure what matters most, the checklist covers the common ground.

Step 2: Start from this checklist

Copy the checklist below. It is deliberately short and practical. The parts in square brackets are for you to fill in.

Onboarding [team name] to AI

Set up
[ ] Pick the tools people should use, and say which are approved for work.
[ ] Sort out access and logins so nobody is blocked on day one.
[ ] Note which tools are fine for sensitive work and which are not.
[ ] Point everyone to our AI policy (or write a short one first).

Share
[ ] Run a 30-minute session showing two or three real examples from our work.
[ ] Share a few starter prompts people can copy and adapt.
[ ] Explain what AI is good at (drafting, summarising, ideas) and where it slips
    up (facts, figures, anything niche).
[ ] Name one person to ask when someone gets stuck.

Agree together
[ ] Agree what should never be pasted into public AI tools.
[ ] Agree that a human always checks anything before it goes out.
[ ] Agree when to mention that AI helped, and when there is no need.
[ ] Agree to share what works, so good prompts spread across the team.

First win
[ ] Ask everyone to use AI on one real task this week.
[ ] Regroup briefly and swap what worked and what did not.

Last reviewed: [date]

What to expect: a complete starting point you could use almost as-is. It is written so anyone can follow it, not to impress a training department.

Step 3: Adapt it to your team

Now make it yours. Paste the checklist into an AI tool along with your notes from Step 1, and let it tailor the wording to your work. A clear prompt does most of the heavy lifting.

Here is an onboarding checklist for introducing my team to AI, plus some notes
about how we work. Please adapt it to fit us, keep it short and in plain English,
and suggest two or three example tasks a [your industry] team could try as a
first win.

[paste the checklist and your notes]

What to expect: a tailored checklist in your team’s language, with example tasks that actually fit their day. Read it through and change anything that does not sound like you.

If it does not work: if it comes back long or generic, reply with “Shorter and more specific to us, please, and cut anything that is not essential.”

Step 4: Explain how AI actually works, briefly

People use AI far better when they understand roughly what it is doing. You do not need a lecture. A five-minute explanation of why AI sometimes gets things wrong, and why public tools may keep and learn from what is typed into them, saves a lot of trouble later.

If you want help pitching it at the right level, ask an AI tool to do the explaining for you.

Explain to a non-technical work team, in plain English and under 200 words, how
AI chat tools produce their answers, why they can sound confident and still be
wrong, and why they learn from the text people type in. Keep it friendly and
practical, not scary.

What to expect: a short, clear explanation you can read out or paste into your session. It gives people enough of the how to make sensible choices about what they share.

Wrapping up

Work through the checklist once, then keep it somewhere everyone can find it, so new joiners get the same start. Onboarding is not a one-off event. Revisit the checklist every few months as tools change and your team gets more confident.

Keep it human: the aim is a team that reaches for AI with good judgement, not one that is nervous about getting it wrong. Pair the checklist with our guides on what AI can do for your job and does your employer allow AI, and consider writing a short AI policy for your team to sit alongside it.