In short
- For UK businesses training 10 or more people
- Around 16 people per workshop, with multiple sessions for larger groups
- Delivered on-site anywhere in the UK, or live online
- A scoping call confirms tools, licences, tasks and format
- Price depends on group size and format
About this course
A serious, hands-on Claude AI training course for UK teams and professionals who want to get useful work out of Anthropic Claude. One day, with workshops of around 16 people and multiple sessions for larger teams, built around your team's actual tasks — covering prompting, Projects, Artifacts, long-document workflows, Skills, connectors and safe use.
Course details
The standard course is one full day, delivered as roughly six hours of instruction and hands-on practice. It can also be split into two half-days for teams who cannot lose a whole working day, or condensed into a half-day introduction.
Workshops usually run with around 16 people so everyone gets time with a trainer during the exercises. Larger groups are run as multiple sessions.
In-person at your offices anywhere in the UK, at a venue in Leeds, or live online for distributed teams.
We usually need two to three weeks between the first conversation and delivery. That covers a short scoping call, gathering example tasks from your team, and tailoring the exercises. Faster turnarounds are sometimes possible — ask.
See it in action
What a Claude session actually looks like
Choose a tool and explore a sample task, from brief to draft to human review.

A consultancy turning discovery-call notes into a client workshop proposal.
Sample brief
Brief
Prompt — workshop proposal for Harlow & Finch
Written by the account lead
You are helping me draft a workshop proposal.
Reader: Head of Operations. Decision: approve a pilot.
Discovery call notes: 40-person ops team, monthly supplier reports take two days.
Sections: context, proposed sessions, what changes, next step.
Rules: no invented figures, flag every assumption, under 700 words.
Sample draft
AI-assisted draft
Draft proposal — Harlow & Finch
Generated from the brief above
1. Context
Your operations team of roughly 40 spends about two days a month assembling supplier reports from several sources.
2. Proposed sessions
Session A — drafting and summarising with agreed house rules.
Session B — the supplier report, worked end to end on your own template.
3. Assumptions
Assumption: attendees can sign in to Claude on your current plan.
Assumption: the report template can be shared with sample data removed.
Sample review
Human review
Review pass — before it leaves the building
Account lead's edits
"Two days a month" checked against the call notes — kept, wording softened to "around two days".
Assumption about licences moved to the top so it is not missed.
Session B renamed to match the client's own term for the report.
Removed a sentence implying a saving the team has not measured.
Signed off by the person who owns the relationship, not by the tool.
A cross-department Teams meeting turned into owners, actions and a follow-up email.
Sample brief
Brief
Meeting notes — warehouse handover review
Teams recording and chat notes
Tuesday, 45 minutes. Operations and Customer Service.
Night-shift handover sheet keeps arriving incomplete.
Priya to look at the template; Marcus unsure who owns the printer list.
Agreed: trial a shorter sheet from the start of next month.
Someone mentioned a customer complaint — detail not captured.
Sample draft
AI-assisted draft
Actions extracted by Copilot
Decisions separated from discussion
Decisions
Trial a shortened handover sheet from the 1st.
Actions
Priya — redraft the handover template — by Friday.
Marcus — confirm who maintains the printer list — by Wednesday.
Open questions
Which customer complaint was referred to? Not stated in the recording.
Sample review
Human review
Follow-up email — checked, then sent
Drafted in Outlook by the meeting chair
Subject: Handover review — decisions and actions
The due dates in the draft (Friday, Wednesday) were not in the meeting — they are assumptions, and were confirmed with Priya and Marcus before the email went out.
Owners confirmed with each person; anything unconfirmed stayed marked as proposed.
Open question left in the email rather than guessed at.
One "agreed" downgraded to "proposed" — the recording did not show agreement.
Prompt saved to the team library so the next chair reuses it.
A campaign brief becoming a customer email, then a fact and tone review.
Sample brief
Brief
Campaign brief — spring service reminder
Written by the marketing lead
Audience: existing customers, last service over 12 months ago.
Purpose: book a service slot online.
Tone: plain, warm, no hard sell, British spelling.
Must include: booking link, opening hours, cancellation terms.
No customer data pasted in. No discount claims — none approved.
Sample draft
AI-assisted draft
Email draft, version 1
Plus two alternative openings
Subject: Time for your annual service?
It's been a while since we last saw your vehicle. Booking takes a minute and slots are open through April.
Alt opening A: leads on the reminder.
Alt opening B: leads on the booking link.
Marked: "slots open through April" needs confirming with the workshop.
Sample review
Human review
Fact and tone review
Checked by the marketing lead
Availability confirmed with the workshop before the claim stayed in.
Cancellation terms corrected against the current policy page.
Opening B chosen — shorter, and the ask is visible on a phone.
Removed an implied guarantee about same-week slots.
Final wording approved by a person before scheduling.
Scattered project notes becoming a Workspace-style summary, then verified.
Sample brief
Brief
Project notes — office move, week 6
Google Docs bullets and a Meet summary
Fit-out contractor confirmed for the second week of June.
Desk count still under discussion — sheet says 62, facilities said 58.
IT cutover date not yet agreed.
Summary needed for Thursday's steering group. No supplier names outside the team.
Sample draft
AI-assisted draft
Draft summary in Docs
Structure agreed first: status, decisions needed, risks
Status
Fit-out is scheduled for the second week of June. Desk numbers are unresolved.
Decisions needed
Confirm the desk count (sheet: 62 / facilities: 58).
Agree an IT cutover date.
Conflict shown rather than averaged or silently resolved.
Sample review
Human review
Verification before sharing
Project manager's pass
Both desk figures checked against the sheet's latest tab.
Contractor dates confirmed with the email thread, not the summary.
Supplier name removed — the document goes wider than the team.
Structure saved as a template for next week's update.
Explore the curriculum
Pick a topic, see how it is taught
Four of the topics covered in Claude training: pick one to see a sample exercise and what attendees take away.
Working with long documents
Sample exercise
Attendees bring one long, non-sensitive document — a policy, a scope or a report — and work through summarising it for a specific reader and decision.
What attendees leave with
A reusable summarising prompt, plus a short note of what had to be checked by hand.
Structured drafting
Sample exercise
A rough brief is turned into a structured draft with required sections, a word limit and a rule that assumptions are listed separately.
What attendees leave with
A drafting prompt a colleague can reuse on the same document type.
Safe use and guardrails
Sample exercise
Teams sort their own everyday material into what can, cannot and should never go into the tool, and write the rule in plain words.
What attendees leave with
A short internal guardrail note the team agrees on the day.
Review habits
Sample exercise
A deliberately confident but partly wrong draft is reviewed against a checklist the team writes themselves.
What attendees leave with
A review checklist: what to check, who signs off, what never gets pasted in.
What you'll learn
- How Claude differs from ChatGPT and Gemini, and where it genuinely shines
- Writing strong prompts and system prompts for Claude
- Using Claude Projects, Artifacts and long-context windows effectively
- Working with long documents, research and structured analysis
- Turning repeated tasks into Claude Skills and reusable workflows
- Understanding connectors and MCP, and what to connect first
- Using Claude safely with company information and sensible guardrails
How we deliver this training
Instructor-led workshop
A practical, hands-on session led by a Day Seven trainer. Run in-house for your team, or join an open workshop in Leeds. UK-based, jargon-free, and built around the work your team does.
Get a training proposalExample exercises we can scope for your team
We agree the exercises with you before the session, so they match the work your team does.
- A document-analysis workflow: taking a long report, contract or tender and producing an accurate structured summary or comparison table, checked against the source
- A Project set up for a live piece of work, with the right background context and custom instructions
- One repeatable team task packaged as a Skill or saved brief, so the whole team runs it the same way
- An Artifact your team can reuse — a template, table or small internal tool
- A short governed-use note: what can be pasted in, what needs verifying, and who checks it
What we need from you beforehand
- A short scoping call to agree the tools your team uses, the tasks that matter and the format that fits your week.
- Confirmation that attendees can sign in to the tool on their team's current plan or licences before the day.
- Two or three real, non-sensitive examples per team — a typical document, report or email thread — so exercises use your own work.
- A named internal contact for room, kit and joining details, plus anything your IT or security team needs to approve first.
How to tell whether it worked
- Agree at scoping which two or three tasks the training should make faster or easier, so there is something concrete to look at afterwards.
- Compare the time taken and the quality of the output on one selected task before and after the session, so there is a performance measure alongside how people feel.
- Capture a simple confidence rating from attendees before and after the session on those same tasks.
- Ask managers a month later whether the agreed tasks are being done with the tool, and how often.
- Keep the team's shared prompt library as a visible sign of use — an empty library a month on is a useful signal in itself.
Our guide on measuring AI training ROI sets this out in more detail.
Who it's for
The curriculum
Prompting and briefing Claude
- How Claude interprets instructions, and why structure beats clever wording
- Writing system prompts and reusable briefs for recurring tasks
- Giving context, examples and constraints so output needs less editing
- Iterating on a poor answer instead of starting again
Projects: giving Claude persistent context
- Setting up a Project for a team, client or ongoing piece of work
- What belongs in project knowledge and what does not
- Custom instructions at project level for consistent tone and format
- Keeping projects tidy so answers stay accurate over time
Artifacts and building small tools
- Using Artifacts for documents, tables, diagrams and simple apps
- Iterating on an Artifact rather than regenerating from scratch
- When an Artifact is the right output and when plain chat is faster
- Sharing and reusing what you build with colleagues
Long-document and research workflows
- Working across long reports, contracts, tenders and research packs
- Structured extraction: turning a long document into a usable summary or table
- Comparing several documents and spotting inconsistencies between them
- Checking Claude's answer against the source before you rely on it
Claude Skills
- What Skills are and how they package a repeatable way of working
- Choosing tasks in your team that are worth turning into a Skill
- Writing clear instructions and supporting files for a Skill
- Maintaining Skills so they do not quietly go stale
Connectors and MCP
- What the Model Context Protocol is, in plain terms
- How connectors let Claude read from and act in your existing systems
- Deciding what to connect first, and what to keep out of reach
- Questions to put to IT and security before connecting anything
Safe and governed use
- What is and is not safe to put into Claude, with clear examples
- How consumer, Team and Enterprise plans differ on data handling
- Checking outputs: hallucination, confident errors and where the risk sits
- Drafting a short internal usage policy people will actually follow
Embedding it after the day
- Choosing two or three real tasks per person to apply it to immediately
- Building a shared prompt and Skills library for the team
- Identifying internal champions and how to support them
- A simple way to review what is working a month later
What your team can do by the end
- Write a brief for Claude that produces usable output on the first or second attempt, rather than after ten rounds of nudging
- Set up a Project with the right background context and custom instructions for an ongoing piece of work
- Take a long document and produce an accurate structured summary, and check that summary against the source
- Build and edit an Artifact — a document, table or small tool — and share it with colleagues
- Turn a recurring team task into a reusable Skill or saved prompt rather than rewriting it each time
- Explain in plain language what a connector does and what questions to ask before enabling one
- Recognise when an answer needs verifying, and know what information should never be pasted in
- Explain to a colleague where Claude fits alongside the other AI tools your organisation uses
Who delivers the training
Training is delivered by Qasim Ahmed, founder of Day Seven. Qasim has 15 years leading digital learning teams across Aviva, KPMG and William Hill, and designs sessions around what actually works with real teams rather than what looks good in a demo.
That background shapes the format. Sessions are hands-on, jargon-free, and built around tasks your team brought with them. We would rather your people leave with three things they will genuinely use on Monday than a tour of every feature.
Day Seven is UK-based and delivers training in person across the UK and live online.
Still deciding between Claude and ChatGPT for your team? We have written an even-handed comparison covering strengths, weaknesses, governance controls and cost at team scale — including where ChatGPT is the better choice.
Read our Claude vs ChatGPT comparisonFrequently asked questions
Before you buy
If you are still building the business case, our guides cover what AI training costs in the UK, how to choose an AI training provider and how to measure the return on AI training.
