T6

Volume vs Breadth Signaling

When an agency reads a consultation, a grant round, or a wave of objections, it is trying to read the weight of opinion behind the submissions. How many arrive, and how varied they are, have long stood in for that weight. Agents that draft fluent, distinct-looking submissions and file them at scale break the link between those two signals and the thing they measure. Sheer volume can now be manufactured, and so can the appearance of variety. Yet many people still organize through shared campaigns and templates, so a near-identical submission can carry a view that is genuinely and widely held. The same agency increasingly reads through agents of its own, clustering and summarizing what arrives, so the weight of opinion is judged partly by automation on both sides.

01 Policy challenge

An agency must act on the content of public submissions without being able to verify where any of them came from. Its duty to consider what was submitted still holds, but it can no longer assume that a submission was written by the person who filed it, that distinct-looking submissions came from distinct people, or that volume reflects breadth of support.

As automated filing grows, the agency also has to defend the resulting decision: it must be able to show which signals it relied on, how it judged their authenticity, and why the weight it gave them was sound.

02 Design challenge

Surface the signal an agency can trust in a set of submissions, however many arrive.

Let an agency see distinct arguments, real breadth of support, how strongly each position is held, and verified provenance, whether it receives a hundred submissions or a million.

Design on the assumption that automated submission at scale is the norm, so these signals can be told apart however many arrive.

Keep a path open for people who take part through a shared campaign or a template, so weighing breadth doesn't discount a view that many people genuinely hold.

Patterns in this territory

6 shown
6.1

Clustering and deduplication views for high-volume submissions

A reviewer console that groups semantically similar submissions into argument clusters with a visible distinctness ratio, each cluster expandable to the underlying submissions.

Emerging
6.2

Provenance and attribution for mass submissions

A submission-record view that collapses each campaign to a single representative entry, discloses how many submissions it represented and who organized it, and marks whether each submission arrived through a verified route. It reports provenance and size; it does not try to classify which submissions were machine-written.

Established
6.3

Consensus-and-clustering opinion mapping

A real-time opinion map that plots participants into clusters and surfaces consensus statements (broad agreement across clusters) separately from divisive ones.

Emerging
6.4

Distinct-voice weighting

A consultation results dashboard that renders three side-by-side figures (raw submissions, distinct arguments, and verified distinct submitters), with campaign responses labeled rather than hidden.

Emerging
6.5

Submitter nudges on template matches

An inline submission-flow nudge that detects template similarity and offers to help the submitter add a personal perspective, with a clear, non-blocking 'submit as written' path.

Frontier
6.6

Alternative weighting mechanisms

A prioritization interface that gives each participant a credit budget and shows the intensity-weighted result, with a plain-language explanation of how votes are weighted.

Emerging