What this course is, and what it is not
This course helps you plan a Claude rollout as an IT administrator, operations lead or sponsor. Before any planning starts, you need two ground rules.
- The course is independent of Anthropic. It is not written, reviewed or endorsed by Anthropic, and it is not official documentation. It reproduces none of Anthropic's course or documentation text.
- Anthropic's own pages are the authority. Claude's plans, features, names and limits change often, sometimes monthly. Where this course and a current Anthropic page disagree, the Anthropic page wins.
Treat the course like a consultant's briefing on a software licence: useful for structure and judgement, but you still read the vendor's contract and price list before you sign.
Do this now: open a blank document or spreadsheet called "Claude rollout: feature register". You will fill it in throughout the course.
Why verification is a rollout skill
A rollout plan is a set of promises to your organisation: "we will have single sign-on", "we can cap spend", "audit logs are available". Each promise rests on a feature that exists on a specific plan today. Three things commonly go wrong:
- The feature moved. It is now on a different plan or seat type than last quarter.
- The name changed. Products are renamed, and old names linger in blog posts and slide decks.
- It is not generally available. The feature is labelled beta or preview, so it may change or be withdrawn.
Third-party articles, reseller pages, videos and AI-generated summaries are useful leads. They are not evidence. That includes this course.
The four authoritative places to check
Use these Anthropic-run sources. Each answers a different kind of question.
- Pricing page (claude.com/pricing). Answers: which plans exist, what they cost, what seat types there are, and which headline features sit on which plan. It also marks some features as beta.
- Claude Help Center (support.claude.com). Answers: how a feature works, who can configure it and on which plan. It is organised into collections, including one for Team and Enterprise plans and one for identity management, and it carries release notes that show what changed recently.
- Privacy Center (privacy.claude.com). Answers: how data is handled, retained and used, with material for commercial customers.
- Trust Center (trust.anthropic.com). Answers: security and compliance evidence, such as certifications, that your security or procurement team will ask for.
A quick routing rule:
- "What does it cost, and which plan has it?" → pricing page.
- "How do I switch it on, and who is allowed to?" → Help Center.
- "What happens to our data?" → Privacy Center.
- "Can we prove it to an auditor?" → Trust Center.
Some web addresses have changed over time (older support.anthropic.com links, for example). If a bookmark redirects, check that you have landed on an Anthropic-owned domain before trusting the page.
How to verify a claim: five steps
Follow this procedure whenever a feature, name, limit or plan claim appears in your plan.
- Write the claim as one testable sentence. Not "Enterprise has better security" but "Audit logs are available on the Enterprise plan".
- Pick the right source using the routing rule above.
- Find the claim on the page itself. Read the actual page, not a search-engine snippet or summary. Note the exact product name and plan the page uses.
- Look for status labels. Check whether the page marks the feature as beta, preview or similar, and whether it is limited to certain plans, seat types or roles.
- Record the result in your feature register with the link and today's date.
If two Anthropic pages appear to disagree, or you cannot find the claim, do not guess. Mark it unconfirmed and ask Anthropic's support or sales team in writing.
Label every feature: confirmed, beta or unconfirmed
Every line in your register gets exactly one status.
- Confirmed: a current Anthropic page states it, for the plan you intend to buy, with no beta or preview label.
- Beta: an Anthropic page states it but labels it beta, preview or similar. You may pilot it; do not make a commitment that depends on it.
- Unconfirmed: you could not find it on an Anthropic page, or your only source is a third party. Do not build it into the plan until it is resolved.
Use these columns:
| Feature or claim | Plan | Status | Source link | Date checked | Checked by |
|---|---|---|---|---|---|
| Audit logs | Enterprise | Confirmed | Pricing page | 10 Oct 2026 | (your name) |
| Claude Security | Enterprise | Beta | Pricing page | 10 Oct 2026 | (your name) |
| A limit quoted in a reseller blog | Team | Unconfirmed | None yet | 10 Oct 2026 | (your name) |
The first two rows reflect what the pricing page showed on the date given. They are examples of the format, not facts to copy. Check them again yourself.
The date matters as much as the status. "Confirmed" with no date is a rumour with a tick next to it. A dated entry tells the next reader how stale it might be.
When to re-check
Set these triggers now:
- Before signing or renewing a contract.
- Before each rollout stage, such as moving from pilot to a wider group.
- When the Help Center release notes mention a feature in your register.
- On a fixed schedule, for example monthly, for anything marked beta or unconfirmed.
Key takeaways
- This course is independent of Anthropic and is not official documentation; Anthropic's current pages override it.
- Four sources settle claims: the pricing page, the Claude Help Center, the Privacy Center and the Trust Center.
- Verify with five steps: state the claim, pick the source, read the page, look for status labels, record the result.
- Label every feature confirmed, beta or unconfirmed, with a source link and the date checked.
- Third-party content is a lead, never evidence. Re-check before commitments and at each rollout stage.