Volume vs Breadth Signaling

When an agency reads a consultation, it is trying to judge how widely a view is held. How many submissions arrive, and how varied they are, have long stood in for that. An agent can produce as many distinct-looking submissions as anyone wants, so neither count nor variety carries the weight it used to.

Many people still organize through shared campaigns and templates, so a near-identical submission can carry a view that is genuinely and widely held. Clustering and summarizing a large intake collapses those submissions into one. That is right for analysis and wrong for counting how many people hold the view, and the agency does both with the same automation.

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.

Design challenge

Find 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

9 shown

6.1 Emerging

Clustering and deduplication for high-volume submissions

Grouping a flood of submissions by what they argue, so a reviewer reads each distinct argument once instead of the same template ten thousand times. It keeps mass campaigns from inflating the record while giving reviewers and the public confidence that no substantive position was missed.

6.2 Emerging

Provenance and attribution for mass submissions

Recovering who stands behind mass submissions: which campaign, how large, who organized it, and by what route each entry was filed. Decision-makers can see which campaign produced a flood of comments and how many distinct people stand behind it.

6.3 Emerging

Opinion mapping by consensus and clustering

Mapping where genuine agreement sits across a consultation, by weighting positions on how widely they are shared across distinct groups rather than how often one group repeats them. A position's reported weight reflects how many different groups hold it, which volume alone can't counterfeit.

6.4 Frontier

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.

6.5 Frontier

Submitter nudges on template matches

Telling a submitter, before they file, that their text matches a known template and that their own experience would add weight. The consultation gains first-hand accounts.

6.6 Emerging

Alternative weighting mechanisms

Weighting participation by the intensity and persistence of support behind a position, not by how many submissions repeat it. A participant spends a limited budget of voice on what matters most to them, rather than being counted the same regardless of how strongly they feel.

6.7 Frontier

Submission processing that resists prompt injection

Protecting the integrity of a government agent that reads, summarizes, clusters, or ranks user submissions from adversarial content inside those submissions, through structural controls that hold regardless of how the injection is worded.

6.8 Frontier

Verified agent admission

Letting a legitimate agent prove it is a known, authorized agent at the moment it makes a request, the inversion of proving a human is present. A service can then admit and account for declared agent traffic instead of guessing an actor from its behavior.

6.9 Frontier

Declared agent welcome

A service stating, in machine-readable form on the channel itself, what agent traffic is welcome there and for what purposes. The declaration states the policy; confirming which agent is making a request is a separate duty.

Case studies that touch this territory

Case study

A consultation is flooded

A scenario following one consultation on a mandatory buyback in a flood-hazard zone: a resident disputes the boundary with her own elevation survey, while a campaign submits thousands of copies of one template opposing the buyback. The journey shows how what each step captures decides what the analysis can tell apart later.

Informs T1 · Provenance & IntentT5 · Rationing & FrictionT6 · Volume vs Breadth SignalingT7 · Representation & Equity