Structured intake with process metadata
A guided composition environment with sectioned fields, a non-blocking paste-disclosure prompt, and quietly captured session metadata, sitting beside a one-field free-text escape hatch.
Conventional submission forms capture what was submitted but not how it was prepared. A 2,000-word consultation response looks identical whether it was personally drafted over a week, generated by an AI in thirty seconds, or circulated as a form letter by a campaign organization. Decision-makers need process metadata to interpret submissions appropriately.
Decision-makers need to interpret how a submission was prepared, not just read its final text, so they can weigh a week of personal drafting differently from a thirty-second generation or a circulated form letter. Government needs that preparation signal to be reliable enough to act on while costing the submitter little or no extra effort to produce.
Structured forms are slower than free-text boxes and can feel like bureaucratic interrogation, and multi-section forms are harder to navigate with assistive technology, so time-poor or frustrated citizens may abandon them. Always allow a free-text alternative alongside the structured intake, and treat the simple path as equivalent (just with less process metadata available), never as a disadvantaged submission.
Because the preparation signal should come from the workflow itself rather than from an extra disclosure burden, the response is a guided intake that records timing and paste patterns as the submitter works, and offers a paste-detection prompt ('looks like you pasted from another source; want to note where it came from?') that the submitter can answer or skip. The information is gathered as a byproduct of building the submission, never as a gate the submitter must clear.
No surface has been built yet; the approach above is the brief for one.
- Emerging Headline
The building blocks (session analytics, paste detection, structured forms) are mature, and the tax software audit trail offers a strong analogue.
- Frontier
Capturing how a submission was prepared as a byproduct of intake — no government consultation platform currently records preparation method as structured data.
Tax preparation software audit trails. Consumer tax software (TurboTax, H&R Block, Xero Tax) records every interaction during preparation: which questions the user answered, which fields were auto-populated, which calculations ran automatically, and where the user overrode a suggested value, a complete provenance chain from raw inputs to filed return. The audit trail is invisible to the user during preparation but available to the tax authority on request. The key insight: process metadata is captured as a byproduct of the structured workflow, not as an additional disclosure burden. See Axiom Studio and Cobbai.
Collaborative document edit history. Google Docs automatically records who wrote or edited every passage, with timestamps and color-coded attribution. The "Show Editors" feature reveals the edit provenance of any highlighted range, and version history preserves every state, recording per-passage authorship as a byproduct of collaborative editing. See Google Workspace Updates.
Consultation platform analytics (Citizen Space / Delib). Purpose-built platforms capture submission metadata including timing patterns, completion rates, and session data, with AI analysis on the 2026 roadmap and all AI outputs required to be traceable to original submissions. But current platforms capture metadata about the submission event (when, from what IP, session length) rather than the preparation process. See Delib.
Agentic AI UX patterns for audit and accountability. Smashing Magazine's 2026 pattern catalog includes "Action Audit & Undo" and "Explainable Rationale and Confidence Signal" patterns, concrete designs for a human-legible record of what an AI system did and why. These assume the AI tool records its own actions; the challenge for submissions is extending this to tools the agency does not control. See Smashing Magazine.
High transferability for the design principle; medium for implementation. The tax software model is the strongest analogue: a structured workflow that captures process metadata as a natural byproduct. A government consultation platform could implement this through a structured composition environment (sectioned guidance rather than a single free-text box, capturing timing and paste patterns per section), a non-blocking paste-detection prompt that creates a natural disclosure moment, and session metadata (duration, edit count, sequence, typed-to-pasted ratio) treated as behavioral rather than content analysis.
The critical limitation is that process metadata from the submission platform captures only the final-mile activity. If a citizen drafts in Word, refines with ChatGPT, and pastes the result, the platform sees only the paste event. The tax software model works because preparation happens inside the tool; consultation submissions are typically prepared externally.
Structured intake records how a citizen prepared a submission, not how an agency reached a decision, so it does not catch a decision-side failure. Its design principle still transfers: capturing a complete provenance chain from raw inputs to final output, as a byproduct of the workflow, is exactly the auditability that an opaque calculation pipeline lacks.