Source: ai-research/claude-blog-smart-reports-surveys-pooled-budgets-2026-10-28.md — Anthropic first-party blog post, claude.com/resources/articles/smart-reports-surveys-pooled-budgets (fetched 2026-10-28). Product launch for Claude Enterprise admins.
Three additions to the Claude Enterprise admin surface: Smart Reports (qualitative usage analysis from transcript sampling), In-App Surveys (structured team feedback), and Pooled Group Budgets (shared spend allocation across a group). Together they address the measurement gap between raw token-spend dashboards — covered in Admin Spend Visibility and Control — and the qualitative question of whether Claude is being used well.
Key Takeaways
- Smart Reports go beyond metrics. An admin picks a team, a date range, and relevant products. Claude samples transcripts, groups work into workstreams, and surfaces: spend per workstream, deliverables produced, common friction points (missing connectors, failed tool calls), and recommendations for converting recurring patterns into skills or repository rules. Output is shareable as an artifact.
- Smart Reports are for adoption planning, not individual evaluation. The product is explicit that findings are designed for understanding adoption and planning investment — not for evaluating individual contributors. Admins with billing permission can raise spend limits directly from the report; team leads can be granted access to run reports for their own groups.
- Custom questions can be saved as templates. Beyond the default workstream analysis, admins can ask their own questions and save them as recurring report templates, making the tool adaptable to different business units or use-case mixes.
- In-App Surveys capture what metrics miss. Default survey questions cover: most valuable recent use, time savings, practices worth copying, and what would break without Claude. All are oriented toward qualitative value signals that token-usage data can’t answer directly.
- Survey controls are granular. Admins control which employees receive surveys, when, and where they appear. Responses export to a spreadsheet. Compatible with customer-managed encryption keys (CMEK). Survey data follows the org-wide retention period if one is set.
- Pooled Group Budgets smooth uneven consumption. A shared monthly budget for a group means heavy users don’t hit individual limits while lighter users have leftover budget. Individual member limits still act as guardrails — a member is stopped by whichever limit runs out first (individual or pooled).
- Budget request and alert flow is built in. Members can request more budget from within Claude; admins review those requests. Setup suggests an amount based on recent usage. Billing admins receive email alerts at 50%, 75%, 95%, and 100% of the pooled budget.
How to Use
- Start Smart Reports before your next budget conversation. The workstream-grouped spend view is more defensible to leadership than a raw token breakdown — it answers “what are we actually getting done?” rather than “how many tokens did we use?”
- Identify friction with the failed-tool-call data. The Smart Report surfaces missing connectors and failed tool calls as friction categories. This is the fastest way to identify which integrations would have the highest ROI without surveying teams manually.
- Set pool size from usage data, not guesses. The setup wizard suggests an amount based on recent usage — use it. Undersized pools recreate the individual-limit problem at the team level.
- Use surveys to find transferable patterns. The “practices worth copying” question is the highest-value default item. Answers feed directly into skill development — a recurring workflow someone has refined becomes a candidate for a formal skill.
Related
- Admin Spend Visibility and Control — the quantitative layer; this article adds the qualitative layer on top
- Agent Guardrails: Hooks, Permissions, and Sandboxing Patterns — governance at the tool-permission level; spend and survey controls are the organizational complement
- Building Skills — recommended action when Smart Reports identify recurring workflows worth formalizing
- Claude Code Costs and ROI on Google Cloud — the Google Cloud–specific cost framework that complements these admin controls