Structured intake that resists volume-padding
An intake built from constrained, verifiable fields instead of free narrative, tying assessment to data rather than to how the application reads.
The impact of agents
As agents make it costless to generate lengthy, plausible-sounding narrative, an assessment system that weighs volume or detail of supporting narrative starts rewarding whoever's agent writes most persuasively, not whoever's circumstances are most genuine. Free-text forms are trivially padded this way, meeting surface-level quality thresholds without reflecting genuine human circumstances.
What must be verified
Government needs to assess an application on verifiable data tied to external sources, not on the volume or fluency of supporting narrative, so that an agent's ability to generate plausible prose does not raise an applicant's apparent merit.
Protecting access
Structure excludes at its edges. The user whose circumstances don't fit the predefined categories is often the user facing the most complex hardship. The form pushes them to misdescribe their situation or abandon it entirely. The same fields that resist padding cause this exclusion.
Keeping the path open
- Put a 'my situation doesn't fit these options' escape hatch on every structured intake.
- Route that hatch to a human rather than to a rejection, and treat it as a first-class outcome of the form rather than an error state.
- Make every field operable by keyboard and assistive technology; date pickers and conditional branching are classic screen-reader traps.
Response surface
Constrained fields and links to existing records carry the assessment, and a case that does not fit them goes to a person.
Hardship assistance application
Answer only the questions that apply to you. The assessment uses your answers and the records you link. Writing more does not make an application stronger.
Your answers and the linked records are assessed against the hardship criteria.
The assessment draws only on the linked records the person can see and contest. It never draws on guesses from what they left unsaid or how they said it.
Maturity
- Established
As a form design principle.
- Emerging Headline
As a deliberate anti-AI-padding strategy.
Precedents
The ATO business activity statement. Financial regulators and planning authorities have long used constrained fields, drop-downs, bounded numeric ranges, and mandatory document attachments, because they are harder to fabricate than narrative. The activity statement reports tax through defined numeric labels, G1 for total sales, 1A for GST on sales, 1B for GST on purchases, each tied to records the agency can check. A field that must reconcile against a source is not padded by writing more.
What carries over to agent use
Structured intake is highly transferable but requires careful design:
- Field constraints (drop-downs, date pickers, document-upload requirements) create verifiable data points that are harder to fabricate than free text.
- Conditional logic (showing questions based on prior answers) makes bulk template generation harder because the path through the form varies.
- Evidence requirements tied to external data sources (tax file number, Medicare record, employer) shift verification from narrative to data.
- Risk: Over-structuring intake can itself become sludge for people whose circumstances do not fit neatly into pre-defined categories.
Where things go wrong
The failure mode is an automated process drawing adverse inferences from data the person could not contest. Anchoring assessment to verified external data and providing a human-review escape hatch prevents that. An agent can still game the fields that remain, selecting real but misleading combinations of the constrained options to steer toward a favorable outcome rather than an accurate one. Structured fields verify that the data exists; they don't verify that the applicant chose the fields that describe their actual circumstance.
Sources
1 reference
The instrument, the operating deployment, or the official record itself.