Reports · what is ready to take into the room?

The three reports read today’s numbers, and 4 frozen reports are on file — the newest from 24 September.

counted over every document on Contoso’s illustrative record

Frontier Firm Report

You are Advancing — 78 of 100.

Open · Deck · Listen

License Report

$43,200 a month in licenses, each waiting for a user — rerouted, never removed.

Open · Deck · Listen

Value Report

$2,700 a month came back — most of it caused by Aristo, and proven.

Open · Deck · Listen

The move

Freeze today’s figures into a record you can send — pick the report and who it is for.

Generate a report

Adjust every detail — the seven steps

Generate a report

Seven steps, and nothing is written until the last one. Every step is its own address, so Back, reload and a link to a colleague all work exactly as they look.

Back to the library

Contoso · 6 available periods · 13 reportable teams · 6 paid products · As of: 24 September 2026

1Report type
2Period
3Scope
4Audience
5Content
6Format and delivery
7Review

Step 1 of 7 — Report type

Which document do you need?

Frozen when generated

Which document do you need?

Each of these is generated as its own frozen document, with its own history, schedule and take-away artifact.

Monthly department chargebackWhat the estate cost, which teams consumed it, how much of what they hold is being used, and what waits for a user. This is the one document Aristo FREEZES: its figures are stored as they stood on the day it was generated, so the copy you send stays the copy they read. License ReportWhat is bought, what is assigned, what waits for a user and what that costs — the document a licensing conversation is held over. Generate it once or monthly; each run retains the exact canonical deck it produced. Value ReportWhat the estate has got back for what it spends — the document a renewal is argued with. Each generated run retains the exact canonical deck it produced. Frontier Firm ReportThe score, the band and the moves behind them — the document a leadership team reviews progress against. Each run retains the audience-cut canonical deck.

Cancel

Frozen — stored with its figures and their basis as they stood on the day it was generated, never re-counted.

Chargeback reports

Formal, reproducible records of what the estate cost and who consumed it — generated on demand or on a monthly schedule, and frozen so the copy you send stays the copy they read.

Build a report Investigate in Analytics

Reports heldcounted

documents on this organization's record

one page

Ready to opencounted

complete, with their figures frozen

1 not finished

Schedules runningcounted

monthly run generating on its own

0 sponsors named in Settings

Types not builtcounted

named with the reason, rather than hidden

one kind is built

Saved views none yet on Chargeback reports

Why this workspace keeps none

This is the illustrative organization — it is never written to, so there is nothing here to save. In your own tenant, naming a filter set keeps it for everyone who can open this workspace, and answers it with the numbers as they stand each time somebody opens it.

Generate a report

Choose the period and scope, and freeze today's counted figures into a document that keeps them.

counted

No filter applied Showing: every month Aristo holds (6) All departments All productsChange

No filter applied Showing: every month Aristo holds (6) All departments All products

Monthly department chargeback — covering April 2026 – September 2026, scoped to Every department.

What this report contains, and what generating actually does

What the estate cost, which teams consumed it, how much of what they hold is being used, and what waits for a user — with every figure carrying the word for how it is known.

Generating freezes today's figures onto a document and stores the scope above with them. Opening that document later re-reads those figures — it never recomputes them, which is what makes the copy you send still the copy they read next quarter.

Source: The counted chargeback composition behind the Overview and Analytics workspaces As of: 24 September 2026

Report library

Every report this organization has generated, newest first. A report is a record: opening one re-reads its frozen figures and never recomputes them.

In the library (5)Archived (0)Everything held (5)

Scroll sideways for the remaining columns.

Every report generated for this organization, newest first, with its type, the period it covers, the reader it was prepared for, the format it was asked for in, who generated it, its state, and the fingerprint of its frozen figures. The scope each one covers is under its name.
Report	Type	Period	Audience	Format	Generated	By	Status	Figures	Actions
Monthly department chargeback — April 2026 – September 2026 Every department	Monthly department chargeback	April 2026 – September 2026	Executive	In Aristo	24 September 2026	A leader here	Complete	2f1cc32f9e4e	Open Scope Actions Open the reportThe frozen document, in Aristo. This is the link a colleague who can sign in should get.Print / save as PDFOpens in print layout. Aristo has no PDF renderer, so your browser writes the file.
Monthly department chargeback — July 2026 Every department	Monthly department chargeback	July 2026	Executive	In Aristo	21 September 2026	Aristo, on a schedule	Complete	e94037b0c983	Open Scope Actions Open the reportThe frozen document, in Aristo. This is the link a colleague who can sign in should get.Print / save as PDFOpens in print layout. Aristo has no PDF renderer, so your browser writes the file.
Monthly department chargeback — June 2026 (Engineering) Engineering	Monthly department chargeback	June 2026	Executive	In Aristo	24 August 2026	A leader here	Complete	4c484761561d	Open Scope Actions Open the reportThe frozen document, in Aristo. This is the link a colleague who can sign in should get.Print / save as PDFOpens in print layout. Aristo has no PDF renderer, so your browser writes the file.
Monthly department chargeback — May 2026 Every department	Monthly department chargeback	May 2026	Executive	In Aristo	21 August 2026	Aristo, on a schedule	Complete	7182611c4ef1	Open Scope Actions Open the reportThe frozen document, in Aristo. This is the link a colleague who can sign in should get.Print / save as PDFOpens in print layout. Aristo has no PDF renderer, so your browser writes the file.
Monthly department chargeback — April 2026 Every department	Monthly department chargeback	April 2026	Executive	In Aristo	24 July 2026	A leader here	Failed	—	Actions Every take-away formatThis report has no frozen figures, so there is nothing to open, print, export or share.
The directory read that supplies the per-team headcount was not authorized when this run happened, so the department sections had nothing to divide by. Nothing was half-written: the run stopped and this row is the record of it.

The Figures column is each report's fingerprint. Two reports carrying the same one carry the same figures — unless the evidence itself changed, which is the case where the newer report is the stronger one.

Schedules

A monthly run that generates the report on its own, at the scope chosen above.

Every month on day 1, covering the most recent month Aristo holds, on its own, scoped to Every department.

The period is worked out on the morning it runs, never stored — a schedule carrying fixed months would generate the identical report every month for the rest of the tenancy, and each run would look perfectly correct on its own.

Scroll sideways for the remaining columns.

The report schedules on this organization's record, when each next runs, and what its last run produced.
Report	Runs	Covers	Next	Last run	Audience	Action
Monthly department chargebackEvery departmentReference: Illustrative enterprise monthly close · read-only	Day 3 of each month	the most recent month Aristo holds, on its own	3 October 2026	21 September 2026 Complete	0 sponsors
Monthly department chargebackEvery departmentReference: Illustrative finance cut · paused · read-only	Day 15 of each month	the most recent month Aristo holds, on its own	Paused	21 August 2026 Complete	0 sponsors

In-app delivery. A scheduled run generates the report, files it in this library, appears in Notifications for every leader, and rings the bell. Its audience is the 0 sponsors named in Settings when it runs. Nothing is emailed and nothing is posted to Teams.

Why email is not wired, and what the audience count resolves to

Since slice 11 a run also appears on Notifications and on the bell in the top bar, which is what in-app delivery looks like when it is real rather than promised. Nothing is emailed and nothing is posted to Teams. Why not, precisely: this product's one piece of outbound machinery is the weekly sponsor digest — an adaptive card, sent to the sponsors named in Settings, on a per-tenant daily send budget, behind the organization's quiet-mode gate — and riding a report into it needs three things that do not exist. A card design for a report (the digest card is built around the weekly reading and has no shape for a document). A decision about whether a report competes for the same daily send budget every nudge is metered against, or gets its own — nobody has made it, and guessing would mean a monthly report silently suppressing somebody's activation nudge. And an answer for what a person does with a card about a document they must leave Teams to open. A schedule here will never promise a message that does not arrive. The audience column is the 0 sponsors named in Settings: a count resolved when the run happens, never an address book stored on the schedule, so removing somebody in Settings removes them here with nothing else to remember.

Report types Aristo today does not have

Named with the reason, because a missing feature that is explained is a boundary and a hidden one is a hole. 8 of them.

Quarterly executive summaryBudget variance reportCost optimization reportAnnual true-up reportFinance allocation detail and department leader summariesDetailed license analysisCopilot usage analysisA PDF Aristo writes itself

Why each of these 8 is not built

Quarterly executive summary. The executive summary is a live workspace rather than a filed document: it reads the current counted run and moves with it. Freezing a QUARTERLY one needs a composition over three months, which Aristo holds for no tenant yet — so it would be this chargeback report with a wider date on it and a different heading.
Budget variance report. Variance against a BUDGET needs departmental budgets, which this product does not yet hold — the variance section in this report compares months, runs and the consumption cap, which are the endpoints that genuinely exist.
Cost optimization report. The optimization workspace is live and is where these recommendations are read; this report already carries the same ranked list inside it. A separate document would be a second copy of one composition, which is how two surfaces start disagreeing about the same money.
Annual true-up report. A true-up compares what was charged against what was consumed across a full contract year. Aristo keeps every month it measures and does not yet hold a year of them for any tenant, so the report would be mostly labeled estimates wearing an annual title.
Finance allocation detail and department leader summaries. A report now records who it was prepared for, so a library of two hundred documents can be sorted by reader and a leader can answer which one went to the board. What it does not do is re-cut the FIGURES for that reader: an allocation detail and a leader summary are different documents over the same money, and issuing them today would mean three copies of one composition with only a cover page between them.
Detailed license analysis. A per-SKU analysis needs each product's bought-and-assigned figures over time, and no document in this store carries a SKU name and a period key together: the license record is a single CURRENT snapshot, and the persisted run keeps aggregate seat counts with no per-SKU breakdown. The report would have one real column and a row of months it could not fill.
Copilot usage analysis. What every run persists is aggregate: how many seats were active, how many were ready to activate, and the activation share. There is no per-person or per-feature usage record behind them, and there deliberately never will be one that this product would print — team figures are reported at a five-person floor and below it they are merged. A usage analysis in the ordinary sense is a person-level document, which is the one thing the covenant does not permit.
A PDF Aristo writes itself. Every other take-away format on this page is produced here: the workbook and the flat file are written from the report's own frozen figures, and the deck is the existing License Report. A PDF is the one that is not, because producing one on the server means a headless browser or a PDF library — a new dependency with a running cost, which is an owner's decision rather than a page's. What ships instead is the honest half: Download PDF opens the document in print layout with the chrome gone, and the reader's own Save-as-PDF writes a file carrying exactly the frozen figures. Every control that offers it says that in those words.