Weighting distinct voices
Reporting consultation results so volume and breadth don't collapse into one number. A decision-maker citing the consultation can say how many people asked for something, separate from how many submissions said it.
The impact of agents
As AI agents make it cheap to mobilize or generate submissions in bulk, a raw count of how many arrived stops telling an agency how widely a position is held. The same total can mean a broad, independent constituency or a single campaign amplified at scale, and a report that shows only the count cannot tell the two apart.
What must be verified
When results are reported, government needs to read breadth of support rather than raw volume, so a campaign that mobilizes many people behind one position is not mistaken for many independent positions. That means the report has to distinguish how many submissions arrived, how many distinct arguments they contain, and how many verified distinct submitters stand behind them.
Protecting access
Legitimate mass participants are the group most at risk. If a distinctness metric is foregrounded in place of the raw count, a real constituency that mobilized behind one position can read as illegitimate. Their turnout looks manufactured.
Keeping the path open
- Report raw counts and distinct-argument counts together, never one instead of the other.
- Label campaign responses rather than hiding them.
- Write the dashboard's own labels in plain language, so a reader who has never met the volume-breadth distinction is informed by it rather than misled.
Response surface
Raw submissions, distinct arguments, and verified distinct submitters are reported together, so breadth reads as independent sources rather than as volume.
Breadth means distinct positions from independent sources. 4,213 submissions making 27 arguments from 1,388 people is a legible fact here. Presented as one number, it would have read as a city in near-total opposition.
Maturity
- Emerging
For reporting practices that separate campaign from distinct responses, which already exist.
- Frontier Headline
For a dedicated interface showing volume and breadth side by side, which has no established precedent.
Precedents
UK consultation response reporting. UK consultations routinely distinguish campaign responses, which are template-based and often organized by advocacy organizations, from detailed responses that are unique and substantive. The 'Growing Up in the Online World' consultation noted that campaign responses 'reflect the reach and mobilisation capacity of the organising group(s) rather than the independent views of a representative cross-section of the public', and reported the two separately.
The UK copyright and AI consultation. The report acknowledged that many responses 'either repeated or built upon a set of template letters, or template survey responses, that were created and distributed by interested organisations or individuals', and reported them separately from original responses. Separate reporting is established UK practice across at least two departments.
Coglianese and Balla on mass campaigns. Coglianese's research on e-rulemaking documents that in high-volume dockets the great majority of mass-campaign comments are near-identical and add little distinct substantive content, so raw volume is a poor proxy for breadth of views. Balla's analysis of 1,049 mass comment campaigns across 22 EPA rulemakings found the agency references mass campaigns in its responses but cites them at lower rates than unique comments. That is breadth weighting already happening, without being named or disclosed.
Parliamentary Joint Committee on Human Rights form-letter disclosure. In the freedom of speech inquiry, 418 accepted submissions were published while approximately 10,590 items were categorized as form letters, with one sample of each published alongside the count received. The count is disclosed, the campaign is not erased, and the substantive submissions stay findable.
What carries over to agent use
Moderate to high. The UK's practice of reporting campaign versus non-campaign responses is immediately transferable. Building dashboards that show distinctness metrics without appearing to dismiss mass participation is the part that does not.
Where things go wrong
If a dashboard reports only the raw count, an orchestrated campaign passes as a broad mandate, since nothing in it distinguishes one campaign from a thousand independent submitters. Presenting distinct-submitter and distinct-argument counts alongside raw volume closes that gap. The distinctness count can itself be gamed: an agent can paraphrase the same template into superficially different wording, and a similarity check tuned to catch identical text will register each rewrite as a separate distinct argument.
Sources
6 references
The instrument, the operating deployment, or the official record itself.
Writing about the subject rather than the framework itself, including vendor commentary.