How do you train your staff to use Claude at work?

You train your staff to use Claude by putting them on a business plan, then getting them to do their own work in it, with clear rules on what data goes in and the habit of checking every answer. Good training covers four things: prompting with real tasks, setting up shared Projects, checking outputs and following your data rules. Run it in small, hands-on groups, built around the jobs each team does every week.

Get those right and Claude becomes part of how your team works. Skip them and you end up with a few keen people using it well, everyone else ignoring it, and nobody quite sure what's been pasted where.

What is Claude, and which plan does a business need?

Claude is the AI assistant made by Anthropic. Your team can use it to draft, summarise, rewrite and work through documents, and to think a problem through before they put pen to paper.

The plan matters before anyone is trained, because it decides who controls the account. Anthropic's plans page in 2026 splits Claude into individual plans (Free, Pro and Max) and Team and Enterprise plans for organisations. Team is listed "For teams of 2 to 150", and Enterprise is "For large businesses operating at scale". Team comes with central billing and administration, single sign-on (SSO) and "No model training on your content by default". Enterprise adds controls larger organisations need, including audit logs and custom data retention controls.

On the individual plans, Anthropic's comparison lists model training as "Opt-out", so the setting sits with each person's own account. That's fine for someone trying Claude at home. For work, you want the business to hold the account, the settings and the admin controls, so the first rule of any rollout is simple: company work goes in the company plan.

What should Claude training actually cover?

A good session spends almost all of its time with people working in Claude on their own tasks, not watching slides. It needs to cover:

• Prompting with real tasks: briefing Claude properly on jobs from your team's actual week
• Projects: building shared workspaces so the whole team starts from the same documents and instructions
• Checking outputs: knowing what to verify, and who signs off, before anything is used
• Data rules: what can go in, what never goes in, and which account to use.

Each of these builds on the one before. People who can brief Claude well get more from Projects, and people who understand Projects find it easier to check where an answer came from.

How do you teach prompting without it turning into theory?

You start with the work. Before the session, each person picks two or three tasks they do every week: a client update, a tender response, meeting notes, a policy summary, a report for the board. Those tasks become the exercises.

Then you teach people to brief Claude the way they'd brief a capable new colleague who knows nothing about your business. Who is this for? What's it based on? What does a good result look like, and how long should it be? Give Claude the document, the reader and the purpose, and the first draft improves straight away.

The other half of prompting is the follow-up. Staff need to practise pushing back: asking Claude to cut a section, change the tone, explain its reasoning or try a different structure. Treat the first draft as the start of the conversation. The people who keep going with it are the ones who end up with work they can use.

How do Projects help a whole team use Claude the same way?

Projects are the feature that turns Claude from a personal tool into a team one. Anthropic's help centre article on Projects (2026) explains that "Projects allow you to create self-contained workspaces with their own chat histories and knowledge bases." You can upload documents and files to a project's knowledge base, and set project instructions for each one to shape how Claude responds.

The part that matters for a business is sharing. The same article says that "For users on Team and Enterprise plans, projects can be shared with other members of your organization", with view or edit access. So a sales team can share one project holding its service descriptions, tone of voice guide and approved case studies, and every proposal starts from the same facts. An operations team can do the same with its procedures.

Training should cover more than how to click "create project". Your team needs to agree who owns each shared project, what goes into its knowledge base, and who keeps it up to date. A project full of last year's prices does more harm than no project at all.

How should staff check what Claude gives them?

Claude writes clearly and confidently, and that's exactly why checking needs to be a habit rather than an afterthought. Polished writing tells you nothing about whether a date is right, whether a figure is really in the source or whether a promise was ever made.

The best habit is to check against the source. If Claude summarised a document in a project, ask it to point to where each key point came from, then look. Recalculate any number that matters. Read anything going to a client in full before it's sent. And make one rule plain: the person who sends it owns it, whoever drafted it.

We've signed the Responsible AI Use Campaign's 10 principles, and human oversight is built into our Claude sessions. Your team gets the speed, and the decisions stay with the people who sign them off.

How do you roll Claude out across the business?

Start with the set-up, then train, then build on what people learn.

First, choose the plan and get the admin in place: who manages the account, how people sign in, and which connections to other tools are switched on. Anthropic's Team plan help article (2026) lists connectors for Google Drive, Gmail, Google Calendar, GitHub, Microsoft 365 and Slack, and admins can "Set spending caps at organization and individual user levels." Decide what's on before your staff log in.

Second, write the data rules down in plain English and teach them in the session. If you haven't got a policy yet, our article on whether it's safe for staff to use AI at work sets out what one should include.

Third, train by team, in groups small enough for everyone to work hands-on. Build the first shared projects in the session itself, so people leave with something they'll use the next morning, not a set of notes.

After that, ask each team which tasks Claude is saving them time on, and build those into their projects and prompts so everyone benefits.

How does DLR Programmes train teams on Claude?

Our Claude training for staff is built around your team's real tasks, your plan and your data rules. Sessions run for groups of up to 12, at your premises anywhere in the UK, at a venue or live online. Sessions are priced per group, with a fixed price confirmed before you book, and attendees rate our workshops 5/5.

If your team uses Claude alongside Microsoft Copilot or ChatGPT, we cover those in the same programme. You can see how our sessions are put together on our AI training for staff page, and how bookings work on our private team training page.

Frequently asked questions

Do staff need a paid Claude plan to be trained?

No, not for the basics: Anthropic says Projects are available to all users, including free accounts. For company work, use Team or Enterprise, because sharing projects with colleagues needs one of those plans and they keep the account under your business's control.

Is our data used to train Claude?

On Team and Enterprise, not by default: Anthropic's plans page lists model training as "None by default" for both. On Free, Pro and Max it's listed as "Opt-out", which is why work belongs on a business account.

Can you train us on Claude and other AI tools together?

Yes. Our sessions cover Claude, Microsoft Copilot, ChatGPT or any other AI tool your business has approved, together or on their own.

How many people can you train at once?

Up to 12 in each session, which keeps everyone working in Claude rather than watching. Larger teams book several sessions.

Get your team working in Claude

Tell us which Claude plan you're on and which teams you'd like to start with, and we'll come back with a session plan and one fixed price for each group. Call +44 1382 699595 or tell us about your team.