# Comma by Role — Who Sends Reports, and What Breaks for Them

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

> Consultants, QA, data scientists, security teams, SREs, freelancers, maintainers. The same problem — an HTML report nobody else can open — arrives differently in each job. The workflow for yours.

# Comma by role

The mechanics are the same for everyone: an HTML report gets a URL, people
open it without an account, their comments anchor to the paragraph or number
they're about, and a revision lands at the same address.

What differs is the wall each job hits first.

A consultant's problem is the **record** — three rounds of feedback scattered
across email with no way to show what changed when. QA's problem is
**expiry** — the artifact that proved the regression is gone in 30 days.
A security team's problem is that the obvious fix, _make it public_, is the
one thing they can never do. A freelancer's problem is that the client
genuinely cannot open a zip.

Pick the one that sounds like your week.

## Delivering to people outside your company

- **[Consultants](/for/consultants)** — deliverables a client opens without a
  login, and a revision history that survives the engagement.
- **[Agencies](/for/agencies)** — many clients, one workspace, and the
  separation that keeps one client's audit out of another's link.
- **[Freelance developers](/for/freelance-developers)** — handing work to
  someone non-technical who will never run `npm install`.

## Delivering inside engineering

- **[QA engineers](/for/qa-engineers)** — Playwright, Cypress and Allure runs
  that outlive the CI artifact and land in the PR as a link.
- **[SRE and incident teams](/for/sre-teams)** — postmortems and incident
  timelines with the graphs still in them.
- **[Engineering managers](/for/engineering-managers)** — a weekly digest at
  one address instead of a deck of screenshots.
- **[Open-source maintainers](/for/open-source-maintainers)** — benchmark and
  coverage pages contributors can open from an issue thread.

## Delivering findings and analysis

- **[Data scientists](/for/data-scientists)** — notebooks and charts that stay
  interactive for the stakeholder who asked.
- **[Security teams](/for/security-teams)** — scan and pentest findings that
  are private by default and stay that way.
- **[Technical writers](/for/technical-writers)** — doc builds an SME can
  review before the merge, not after.

## The parts that don't change

Whatever the role, four things hold:

1. **Readers need nothing.** No account, no extension, no VPN. See
   [sharing & access control](/docs/sharing).
2. **Comments anchor.** Feedback stays attached to the number it's about —
   see [commenting on HTML](/comment-on-html).
3. **Revisions reuse the address.** The link you pasted in week one still
   works in week six, and shows what moved.
4. **Publishing is automatable.** From [CI](/ci), from a
   [routine](/features/routines), or from an [agent](/agents) over REST or
   [MCP](/mcp).

## Try it

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

**[Start free →](/login)** · **[See a live report →](/demo)**

### Related

- [What kind of report are you sharing?](/report-types)
- [Share an HTML report](/share-html-report) ·
  [Share a whole HTML folder](/share-html-folder)
- [Troubleshooting broken reports](/fix)
- [Glossary](/glossary) — the vocabulary behind publishing and reviewing reports