Anthropic made smart reports, in-app surveys and pooled group budgets generally available for Claude Enterprise on October 28, 2026. Smart reports group sampled team transcripts into workstreams. Before acting on a chart, establish two things: which work it covers and how the displayed cost is valued.
Anthropic’s October 28 Enterprise announcement
Write down the report’s boundary
The current Help Center guide lets authorized users choose a team, products and a period of up to the last 28 days. It describes costs at list price and a sample of transcripts. Reports are off by default. Enterprise configurations using customer-managed encryption keys, HIPAA settings or inference on their own cloud provider cannot use smart reports; zero-data-retention Claude Code use is excluded from otherwise supported reports.
Claude Help Center: scope, eligibility, cost basis and setup
Make a short scope record alongside your own analysis: team, dates, included products, sampled-session count and any exclusions. This is a suggested reading method, not an extra product feature. Keep it with exported findings so a colleague can understand what a percentage refers to without reconstructing the setup.
A sampled share needs its denominator
Consider a fictional report that analyzes 40 sessions and classifies 12 as content drafting. The calculated share is 12 ÷ 40 = 30% of those analyzed sessions. These numbers are invented for this exercise; they are not customer results or a measured Claude report.
That calculation does not establish that 30% of the team’s working hours, completed deliverables or all activity involved drafting. Each would require a different denominator and supporting evidence. One session might contain several drafts; another might contain an unfinished attempt. State exactly what was counted.
For a later comparison, retain the same team boundary and product selection where possible. Note changes in the sampling scope, work mix or reporting period. If two reports cover different products, their percentage difference alone cannot tell you whether the underlying workflow improved.
Keep list-price cost and the bill separate
A list-price cost view is useful for locating concentrated usage. Treat an invoice comparison as a reconciliation task: check the period, included services, pricing basis and any documented billing adjustments. Do not silently replace the report’s definition with your organization’s cash payment.
For a fictional planning exercise, suppose a report assigns 90 cost units to a workstream while an internal ledger shows 70 units for a related activity. Do not label the difference a saving immediately. First establish whether both records cover the same sessions, products and dates. Then explain any remaining difference with actual billing records. The two invented figures demonstrate a question to investigate, not a discount offered by Anthropic.
Turn a finding into a bounded change
Anthropic says reports surface deliverables and friction such as missing connectors or failed tool calls. It states that the reports support adoption and investment planning, not individual-performance evaluation or employment decisions.
Suppose a report suggests a recurring connector problem. Choose one workflow, confirm the missing access with its owner and define a small corrective action. Compare accepted outputs and observed failures before and after that change. Record review work too. A recommendation becomes useful when someone can check whether the proposed repair addressed the observed obstacle.
Save the question with the conclusion
End your review with a narrow statement: what the selected sample shows, what remains uncertain and what evidence would resolve it. Keep invoice reconciliation, workflow acceptance and adoption interpretation as separately answerable questions. This makes the next discussion more concrete than a single unlabeled claim that the team is getting more value.
Check the fictional report
