What are Claude Enterprise smart reports, and how can they shape your AI training?

Short answer: Smart reports are a new Claude Enterprise feature that analyses a sample of a team's Claude conversations to show what work gets done, what it costs, where people hit friction and which workflows are worth turning into shared skills. Alongside short in-app surveys, they give L&D and transformation teams real evidence for what to train next, but they are for understanding adoption, not for judging individuals.

What Anthropic has released

On 28 October 2026, Anthropic announced smart reports, surveys and pooled group budgets for Claude Enterprise and said all three "are now generally available for Claude Enterprise". In Anthropic's words, smart reports "surface what a team gets done with Claude, and what that work costs."

Anthropic's guide to getting started with smart reports explains how they work. Someone with analytics access picks a team, a time range of up to the last 28 days, the products to include (chat, Claude Code, Claude Cowork or the unified chat and Cowork experience) and any custom questions. Claude then reads a sample of transcripts, groups them into workstreams, attaches spend to each one and writes up what it found. Reports usually take a few hours to generate.

Each report includes sections such as:

• workstreams, by sessions and by spend
• deliverables produced, such as analysis, documentation, content drafts and code
• the most common pain points, such as a connector that wasn't set up, output that didn't match the ask, or rework loops
• work that was new to the organisation, and work people have automated for themselves
• one list of recommendations, including recurring workflows to turn into skills

The second feature is in-app surveys. Staff see a short card in chat, Cowork or Claude Code at a natural break in their work, and Anthropic says a survey takes about 90 seconds. The default questions ask about the most valuable thing someone has done with Claude recently, how Claude changed the time it took, which use of Claude a teammate should copy, and what would break or slow down first if the team lost access. Admins can add or remove questions. Anthropic says responses go to your organisation's admins and that it accesses them only as necessary to operate the service.

The third feature, pooled group budgets, is a spend control for admins, so we won't cover it here.

The limits worth knowing

Smart reports are off by default, and an Owner or Primary Owner has to switch them on. Anthropic's Help Center says they can't be used by Claude Enterprise organisations with customer-managed encryption keys, a HIPAA configuration or a hybrid deployment, and that each organisation can run up to 10 reports a month. Surveys aren't available with a HIPAA configuration.

Anthropic is also clear about what the reports are for. Its Help Center says smart reports help you understand adoption and plan your investment, and "should not be used for evaluating individual performance or making employment decisions." Names are hidden by default. An optional setting lets viewers reveal who ran a session, it is off by default, and each reveal is logged. Sessions that Claude identifies as involving restricted topics, such as health, union activity or personal life, are used only for aggregate analysis.

Why this matters for AI training

It is easy to plan AI training from a licence count, a usage chart and a hunch about who needs help. Smart reports show the actual work instead. For example, if a finance team keeps rebuilding the same reconciliation prompt, that is a candidate for a shared skill and a short training session. If a pain point keeps coming back, such as output that doesn't match what people asked for, that points to a prompting or briefing gap you can train for.

The surveys add the human side. The question about which use of Claude a teammate should copy gives you internal examples, and in our experience colleagues' real examples land better than generic demos. The pattern is simple: run a report and a survey, train against what you find, then repeat a few weeks later.

Practical takeaways by role

L&D leaders: Scope reports to functional teams, not the whole company. The Help Center says team-level reports produce clusters specific enough to act on. Use the recommendations list to choose your next sessions, and turn the best survey answers into worked examples. Our AI upskilling page explains our approach.

HR leaders: Tell staff before anything is switched on: reports look at a sample of conversations, names are hidden by default, reports are not for performance reviews, and survey exports include each person's email. Our page on AI training for HR teams covers the people side of change, and our employee AI policy guide can help you write this into your policy.

IT leaders: Check whether your configuration supports smart reports and surveys, and decide who gets access. The Help Center says owners can let team leads run reports for their own groups without making them admins, and reports can be scoped by groups or, through SCIM, by department or cost center. Anthropic notes that when the same friction appears across many sessions, the fix is often a connector or setting an admin can turn on in minutes.

Transformation leaders: Use the first report as a baseline and compare workstreams and pain points after training, not just a usage number. Our guide to measuring AI training ROI explains how to set that up, and our guide to business AI adoption covers the wider rollout.

A simple plan for the next month

1. Agree the rules. Decide with HR and IT who runs reports, whether attribution stays off and what staff are told.
2. Run one report per team. Start with the teams that use Claude most.
3. Send a short survey. Use the default questions to collect examples worth copying.
4. Train against the findings. Build hands-on practice around the top workstreams and pain points.
5. Measure again. Run a fresh report and survey a few weeks later and compare.

Our earlier post on Claude chat and Cowork coming together covers other recent Claude Enterprise changes, and if your teams use Copilot, see our post on the Copilot Learning agent.

What this means for your team

Smart reports and surveys give you something AI training has often lacked: evidence of how each team actually uses AI and where it gets stuck. They don't fix those gaps on their own. Treat each report as a training brief, act on it with practical, role-based sessions, and keep trust by being open with staff about what is collected and why.

Not sure where your team stands today? Our free AI readiness scorecard takes a few minutes. To see how we help teams get more from Claude, take a look at our Claude training, or browse all our AI training for business. We also run sessions in person, including AI training in Leeds.

Talk to us

If you would like help turning smart report findings into a practical training plan, book a free 60-minute discovery call with Qasim.