Claude Enterprise Release Review Checklist

To use this checklist, copy it with the "Copy page" button above or open the Google Doc version, then run it once a week. Read the companion guide to Claude Enterprise release reviews for the reasoning behind each question.

Claude Enterprise release review checklist

A free template for AI Ops leads and CIOs running Claude Enterprise. Review every release in 30 minutes: what changed, who it reaches, which decisions it touches, whether there's an opportunity in it, and what you've decided.

0. Review details

• ☐ Organisation:
• ☐ Reviewer (AI Ops lead or equivalent):
• ☐ Review date:
• ☐ Period covered (since last review):
• ☐ Sources checked: Claude release notes, the relevant Claude Help Center admin guides, any admin emails from Anthropic

1. Triage

List every release since your last review, then put each one in a tier.

• Act now: on by default (or on from a set date) and touches data, sharing, connectors or cost.
• This month: opt-in or beta, with a plausible use case worth a pilot.
• Note only: no action needed. Record it so the log is complete.

2. The five questions (one set per "act now" or "this month" release)

Q1. What changed, and what's the default?

• ☐ Feature name:
• ☐ Status: beta / generally available
• ☐ Plans it applies to:
• ☐ Default on our plan: on / off / on from (date):
• ☐ Where the setting lives (e.g. Organization settings > Artifacts):
• ☐ Admin guide link:
• ☐ Exceptions (e.g. HIPAA-enabled organisations, CMEK, data residency):

Q2. Who gets it, and what can it touch?

• ☐ Who gets it by default (everyone, a role, nobody until enabled):
• ☐ Data it can read:
• ☐ Where outputs are stored, and who can see them:
• ☐ Sharing outside the organisation: possible / off by default / not available
• ☐ Connected apps or connectors involved:
• ☐ Data residency supported: yes / no / unknown
• ☐ What's recorded in audit logs or the Compliance API:
• ☐ Cost: counts against existing seat limits / bills at API rates / other:

Q3. Does it change a decision we've already made?

• ☐ AI policy (data rules, acceptable use, sharing):
• ☐ Approved tools and features list:
• ☐ Security review needed (new connector, data source or vendor): yes / no
• ☐ DPIA screening needed: yes / no
• ☐ Training material or champion briefing to update:
• ☐ Cost model or spend limits to update:

Q4. Is there an opportunity in it?

• ☐ Opportunity in the backlog it could serve (or a new one):
• ☐ Process and outcome it might move:
• ☐ Impact (1–10):
• ☐ Confidence (1–10):
• ☐ Ease (1–10):
• ☐ ICE score (Impact × Confidence × Ease, out of 1,000):
• ☐ Next step: pilot / add to backlog / no action

Q5. Decide, tell people, log it

• ☐ Decision: enable for everyone / pilot with a group / hold / turn off
• ☐ Groups or custom roles (if piloting):
• ☐ Owner:
• ☐ Review date:
• ☐ Message to users drafted and sent:
• ☐ Line added to the steering group update:

3. Release log

Keep one row per release. Share it with security, data protection and your sponsor.

4. Message to users (copy and edit)

Subject: What's new in Claude this week, and what we've decided

[Feature] is now [available to everyone / available to a pilot group / on hold]. What it does: [one sentence]. What you can and can't use it for: [one or two rules]. Questions: [contact or channel].

5. Steering group line (copy and edit)

[Release] [enabled / piloting with (group) / held] from [date]. Reason: [one phrase]. Opportunities scored: [number].

Implementation notes

Run it in the same slot every week

Fifteen minutes when nothing has shipped, thirty when something has. Monthly is too slow: a default-on feature can reach every user between reviews.

Read the admin guide, not just the launch post

Launch posts explain what a feature does. Admin guides tell you the defaults, the exceptions and where the setting lives. Record the link in Q1.

Decide before the default date

When a feature is announced as "on by default from" a date, review it before that date. Turning a template off later doesn't remove what people have already made with it.

Use the organisation switch and custom roles together

On Claude Enterprise, the organisation-level setting is the main switch and custom roles control access underneath it. To pilot with one group, the organisation setting has to be on.

Route connectors through security review

If a release adds a connector, a new data source or a new vendor, put it through your connector security review before you enable it.

Score opportunities like any other use case

A release is a possible use case, not a priority in itself. Score it with ICE against the rest of your backlog, and only pilot it if it beats what's already there.

Template by Kowalah, UK Anthropic Implementation Specialist — kowalah.com/resources/templates