60-Minute New User Training Session
Facilitator Guide — Claude Enterprise Rollout
Who runs this: IT administrator or L&D lead. Deliver live (in-person or Teams/Zoom) or record for async cohorts. Run within 5 working days of account provisioning for each cohort.
Session Objectives
By the end of this session, participants will be able to:
- 1.Write a prompt that produces a usable first draft without iteration
- 2.Understand what data must never go into Claude
- 3.Find and use their department's Claude Project
- 4.Know the Acceptable Use Policy and the consequences of breach
Materials Checklist
- ☐Slides (adapt from the deck template)
- ☐All participants: Claude Enterprise accounts active and tested before the session
- ☐Acceptable Use Policy distributed before or at the start
- ☐Department prompt library link or printout
- ☐Facilitator: screenshare access to Claude.ai
Agenda
00:00 — Welcome and housekeeping (5 min)
- Introduce yourself and the purpose of the session
- Confirm everyone can access Claude Enterprise on their device
- Logistics: questions at any time, session may be recorded
Opening message:
"Today we're not doing AI theory. We're doing 45 minutes of practice. You'll leave with at least one task from your actual job that Claude can already help you do faster."
00:05 — What Claude Enterprise is (and isn't) (10 min)
Cover:
- What Claude Enterprise is: an AI assistant trained on text, accessed via chat
- Strong at: writing, summarising, analysing, brainstorming, coding
- Weak at: real-time information, precise arithmetic, tasks requiring live system access
- Why Enterprise vs personal: data stays under the DPA, admin controls, Projects feature
Live demo (2 min): Open Claude.ai. Prompt: "Summarise this paragraph in three bullet points" — paste a sentence from a company document. Show the result and ask: "Is this the kind of thing you could use?"
Key message:
"Claude is a first-draft machine. It doesn't replace your expertise. It removes the blank page."
00:15 — Acceptable Use Policy (10 min)
Do not skip this section. Every cohort must cover it before active use.
Cover:
- Permitted uses (reference Section 3 of the AUP)
- Three things that must never go in: customer PII, confidential client data, credentials
- Monitoring: usage logs exist and are auditable
- Consequences of breach
Exercise — Spot the violation (3 min):
Show three prompts on screen. Participants vote: compliant or violation?
- 1."Summarise this meeting agenda: Q3 Planning Meeting — 09:00 Welcome and objectives (5 min), 09:05 Q2 results review (15 min), 09:20 Budget proposals by department (20 min), 09:40 Risk register update (10 min), 09:50 Next steps and owners (8 min), 09:58 AOB (2 min)" → Compliant
- 2."Draft a reply to this customer complaint: [email with name and account number]" → Violation — customer PII
- 3."Help me write a job description for a Marketing Manager, salary £45,000" → Compliant
Key message:
"A good rule of thumb: if you wouldn't paste it into a public Google Doc, don't paste it into Claude."
00:25 — Your department's Claude Project (10 min)
Cover:
- What a Project is: a pre-configured Claude environment with a system prompt
- How to find it: [IT to insert location/name]
- What the system prompt does: loads company context — no need to re-explain every time
Live demo (3 min): Open the relevant department Project. Show the Instructions pane. Demonstrate one prompt from the department prompt library.
Exercise — First live prompt (5 min): Everyone opens their department Project, picks one task they need to do this week, types it as a prompt, reads the output. Ask one volunteer to share what they got.
Key message:
"The Project is already set up for your team. You don't need to prompt-engineer. Just describe your task."
00:35 — Prompting skills (10 min)
Four techniques that improve every prompt:
1. Say who it's for
Weak: "Write a follow-up email"
Strong: "Write a follow-up email to a procurement manager who attended our demo yesterday but hasn't replied to my quote"
2. Specify the format
Weak: "Summarise the report"
Strong: "Summarise this report in 5 bullet points for a non-technical director"
3. Give it your raw material
Weak: "Write meeting notes"
Strong: "Convert these rough notes into an action list: [paste notes]"
4. Ask it to try again if the first attempt is wrong
Just say: "That's too formal. Try again in a more casual tone." Claude responds to plain-English feedback.
Exercise (3 min): Each person takes their previous prompt and improves it using one of these four techniques. Compare the new output with the first one.
00:45 — Common questions (10 min)
"Can I use Claude to write my whole report?"
Yes — but you own the accuracy. Review every factual claim before submitting.
"What if Claude gets something wrong?"
Tell it: "this is incorrect — [correct version]". Then verify the revised output independently.
"Can I share the output with clients?"
Yes, if you've reviewed it. Don't present AI-generated content as expert opinion without verification.
"Is my data safe?"
The organisation has a DPA with Anthropic. Claude Enterprise does not use your conversations to train future models. Ask IT for the current DPA summary.
"What if Claude refuses something legitimate?"
Rephrase with more context. If it continues to refuse, contact IT — don't try to work around it.
00:55 — Wrap up and next steps (5 min)
Recap:
- Claude is a drafting tool. You own the output.
- Three things that never go in: customer PII, confidential client data, credentials
- Use your department Project for day-to-day tasks
- If unsure whether something is compliant, ask before you paste
Next steps for participants:
- Full training path: Academy at [academy URL]
- Department prompt library: [link]
- Questions: [IT/L&D contact] or [Slack/Teams channel]
- Session feedback: [form link]
Closing message:
"You now know enough to save time on your first task today. Start small — one email, one set of meeting notes — and build from there."
Facilitator Notes
Before the session
- Confirm all attendees have active accounts (IT to verify 24 hours before)
- Test the department Projects you plan to demo — check system prompts are current
- Have the AUP link ready to share in the chat
- Prepare 2–3 real examples relevant to this cohort's department
Session size
- Optimal: 8–15 participants
- Maximum: 25 (larger groups make live exercises harder to manage)
- For cohorts over 25: split into two sessions or deliver exercises as an async worksheet
Async / recorded delivery
- Record demo segments separately so they can be updated as the UI changes
- Build exercises into a follow-up worksheet that managers check within 5 days
- Add a short quiz on the AUP section (minimum pass score: 100% on the data section)
Tracking completion
Mark all participants as "Claude onboarded" in the HR system after this session. Academy completion of M61 (Getting Started with Claude Enterprise) supplements but does not replace this live session for the first 90 days of rollout.