# One Link Instead of a Weekly Deck — Reporting for Engineering Managers

Canonical: https://commareports.com/for/engineering-managers
Published: 2026-09-11

> Assembling the weekly status from six dashboards into a slide deck is a recurring tax on your Friday. Make it a scheduled report at one URL that regenerates itself.

# 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:

```md
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](/features/routines),
[scheduled HTML reports](/features/routines/scheduled-html-reports),
[weekly analytics digest](/features/routines/weekly-analytics-digest) and
[monthly compliance digest](/features/routines/monthly-compliance-digest).

## Put the real artifacts in it

Whatever you were screenshotting can be published intact and linked:

- [Grafana](/share-grafana-dashboard) · [Metabase](/share-metabase-dashboard) ·
  [Superset](/share-superset-dashboard) · [Looker Studio](/share-looker-studio-report) ·
  [Power BI](/share-power-bi-report) · [Tableau](/share-tableau-dashboard)
- Quality signals: [coverage](/share-coverage-report) ·
  [Lighthouse](/share-lighthouse-report) · [SonarQube](/share-sonarqube-report)
- Delivery evidence: [test runs](/for/qa-engineers) ·
  [incident reviews](/for/sre-teams)

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](/comment-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](/agents/scoped-tokens-for-ai-agents) 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](/agents) and
[letting an agent respond to comments](/agents/let-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](/docs/sharing).
- **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 →](/login)** · **[See routines →](/features/routines)**

### Related

- [For data scientists](/for/data-scientists) ·
  [For SRE teams](/for/sre-teams) · [For QA engineers](/for/qa-engineers)
- [Stop screenshotting reports](/stop-screenshotting-reports)
- [Share an HTML report in Slack](/share-html-report-in-slack) ·
  [in Teams](/share-html-report-in-teams)