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.
As AI agents make it easy to file a campaign template at scale, more participants will submit text identical to thousands of others without knowing it will be grouped and weighed as a single argument rather than counted one by one. A person who would have added their own experience, had they understood how submissions are read, instead files volume that carries little distinct weight.
The challenge is to let a submitter learn this at the point of submission, so they can choose to add a personal perspective, without pressuring anyone or blocking the template route.
Government needs the submissions it receives to carry distinct argument rather than repeated template text, so a reviewer can weigh what a person actually contributes, while a participant keeps the right to send a template unchanged. That means a submitter should learn, before filing, that their comment matches a known template and that a unique argument carries more analytical weight, without being prevented from submitting as written.
Template-match nudges risk deterring low-literacy participants, so the nudge must never be coercive: it explains why a personal perspective helps, applies plain-language and accessibility standards, and always preserves the right to submit the template as-is.
A soft inline banner that detects a template match and tells the submitter their own experience adds weight ('this matches a known template; adding your own experience adds weight'), with the primary submit action still fully available. It informs the submitter without preventing a template submission.
No surface has been built yet; the approach above is the brief for one.
Frontier (no production implementation of a submitter-facing template-match nudge found; the conceptual basis is strong)
UK Government Duplicate-Entry Prevention. The "Growing Up in the Online World" consultation survey included "duplicate-entry prevention and questions designed to detect and deter automated (bot) responses." While primarily aimed at bots, this represents a submitter-facing intervention in the submission flow.
Regulations.gov Bulk Comment API Transparency. GSA's updated API requires identity verification for bulk submitters and introduces transparency about the source of automated comments. While organization-facing rather than individual-facing, it establishes the principle that the system should signal when submissions are part of a coordinated campaign.
Beth Noveck / Transparency Advocacy. Noveck has argued that data science tools and methods have evolved to deal with voluminous, duplicative, and fake comments, "yet neither agencies nor the regulations.gov administrator are using them in a substantial way," pointing to a gap in submitter-facing feedback mechanisms.
Concept: Real-Time Template Detection. No major consultation platform currently provides real-time feedback to submitters saying "your comment matches a known template — consider adding your own perspective." This is an open design problem. The pattern would combine NLP similarity matching with a nudge interface, preserving the submitter's right to submit the template unchanged while informing them that doing so adds volume but not breadth.
High in principle; the design is jurisdiction-agnostic. Implementation requires care: the nudge must not be coercive or discourage participation. Accessibility and plain-language requirements apply. The nudge should explain why adding a personal perspective matters, because agencies weigh unique arguments, not counts.
By nudging toward substance over volume at the point of submission, the pattern works against the volume-as-mandate dynamic; its central safeguard is that it never gates participation behind a literacy or effort threshold.