How do I stop rebuilding the same status deck every week?

Turn it into a routine: a schedule, a generation step, and a revision published to the same URL. Stakeholders bookmark one address and always see the current week, so there is no assembly step and no 'is this the latest?' thread.

Can a report pull from several dashboards?

Publish each dashboard export as its own report and link them from a summary, or generate one combined HTML page. Either way the recipient gets working charts rather than pasted screenshots with the axes cropped off.

Does leadership need accounts to read it?

No, and they are never billed. Pricing is per publisher, so a report read by thirty people costs the same as one read by two.

How do I know whether anyone read it?

Comments are the honest signal — a report with anchored questions on it was read; a deck attached to an email was not. Audit log is an Enterprise feature if you need access records specifically.

Can an AI agent assemble the digest?

Yes. An agent can generate the summary and publish it over REST or MCP, and read the comment threads afterwards so the next edition addresses what was asked.

One link instead of a weekly deck

The weekly status report is the most-repeated, least-loved artifact in engineering management. Every Friday: open six dashboards, screenshot four of them, paste into slides, write the same three paragraphs in a slightly different order, attach, send. Next Friday, again.

Two things are wrong with it, and only one is the time.

The other is that a deck of screenshots is dead on arrival. The axis is cropped, the tooltip is gone, nobody can drill into the number they're questioning, and the email thread that follows is people asking for the context that the screenshot removed.

Make it a routine

A recurring report is a schedule plus a generation step plus a revision at the same address:

Every Friday at 16:00, pull this week's delivery metrics, write the summary,
and publish it as a revision of report weekly-eng-status — same report id,
not a new one. Flag anything that moved more than 20% week over week.

Now the report regenerates itself, stakeholders bookmark one URL, and the current week is always at that URL. The revision history is the trend: what you said in week 3 is still there, next to what actually happened by week 8.

See routines, scheduled HTML reports, weekly analytics digest and monthly compliance digest.

Put the real artifacts in it

Whatever you were screenshotting can be published intact and linked:

Grafana · Metabase · Superset · Looker Studio · Power BI · Tableau
Quality signals: coverage · Lighthouse · SonarQube
Delivery evidence: test runs · incident reviews

Charts stay interactive because scripts run inside a sandboxed iframe. A VP who wants to know why a number moved can hover it instead of emailing you.

Questions land on the number

The main reason status reports generate follow-up meetings is that the question and the number get separated. Anchored comments keep them together: someone highlights the cycle-time figure and asks there; the answer lives there; the next person reads both. See commenting on HTML.

This also gives you something a read receipt never did — evidence that the report is actually used.

If an agent writes the first draft

An agent with a scoped token can assemble the digest, publish it, and then read the comment threads so the following week's edition answers last week's questions. See where agents publish and letting an agent respond to comments.

Keep the agent on reports:write and, if it should reply in threads, comments:write. It does not need the sharing scope.

Worth knowing

Readers are free. Pricing is per publisher; a leadership audience costs nothing.
Start private, widen once. A status report often carries headcount and customer names — see sharing & access control.
One report, many revisions. Ten links for ten weeks is the problem you are trying to solve. Don't rebuild it with a new report id each Friday.
Enterprise adds teams and folders, a custom domain, SSO, and an audit log if access records matter for you.

Try it

Comma is free — unlimited reports, unlimited commenters, unlimited revision history.

Start free → · See routines →