Ultra PatternsAI interface patterns with receiptsULTRA project

Pattern 02 · An app that adapts · Interaction pattern

View

Pre-filled form with review

Tested (pilot) · 6 participants The same comparison with sixteen or fewer participants. Indicative, too small to test a hypothesis.

Practice view. What to build, the words on screen and how to measure it. Switch to Research for why it should work, the framework properties and the references.Research view. The research side is shown below the card: why it should work, the properties it targets and the references. Switch to Practice to hide it.

The AI fills in all fields from the source text and the user reviews, edits and submits.

WhyFor verifiable facts it removes typing; whether it also saves time there is the hypothesis for a factual-field study. For judgement content it anchors people to the default and shifts them from authoring to checking. In the VAIA pilot with six participants, pre-filling cut the alternatives viewed from a median of 11 to 6.5 fields.
WhenFactual fields the system can verify, such as dates, codes, prices and names copied from a source.
Not whenDescriptions, summaries and anything a person should author; there use on-demand suggestions instead.

The user stays in chargeCase: VAIA FormFlow

Done right, done wrong

Schematic screens, not real products. Click a screen to enlarge it.
Right. Factual fields filled from the source, each marked as AI-filled, with one Review step before submit.
Wrong. A judgement field filled with a plausible paragraph; the user accepts it without considering alternatives.

The receipt

CaseCourse registration form for an AI training platform (VAIA)
ComparedPre-filled form with review vs. On-demand suggestions per field · Within-subjects, counterbalanced order
Participants6 Course providers familiar with the platform
Main resultAlternatives viewed (fields) median 6.5 vs 11 lower with pre-filling
Read asFewer alternatives viewed means more anchoring on the default. For verifiable facts that is fine; for judgement content it is the risk.
SecondaryNon-top suggestion chosen: median 1 vs 2
SecondaryPreference: 2 of 6 chose pre-filling
SecondaryOne participant kept pre-filled text after noticing a better alternative
Methodsinteraction logs · eye-tracking · think-aloud · post-task interviews
HonestlySingle site, single domain, small sample. Indicative. Pilot. The anchoring effect is consistent with the literature but not yet replicated.
SourceVan den Bossche and Abdul Khalil (2026), From Pattern Libraries to Practice, IUI Companion, which reports this pilot · doi.org/10.1145/3742414.3794714 · study run 2025-12 · ULTRA case

A receipt is the result of one test, printed on the card: the case, what was compared, how many people took part, the main result, the methods, and what we do not know. The plan written before the analysis is the study card. How a pattern earns its label.

In practice

Pre-filling is the default in most AI form tools because it looks fast. The VAIA pilot shows the cost. When every field arrived filled, participants read the text, corrected small things and moved on. They viewed fewer alternatives and more often kept the first suggestion, even when a better one was one click away. One said they simply continued with what was there. Use pre-filling where the system can verify the value against a source, and mark each filled field so people know where to look.

Words on screen

"Filled in from your text. Check before you submit.""Review""Change""Clear and write it myself"

Obligations to keep in mind (AI Act, GDPR)

  • Mark every AI-filled field as AI-filled, so users know what to check. (O1, IUI 2026, Table 1)
  • Do not pre-fill judgement content: defaults anchor people and reduce alternatives considered. (O4, IUI 2026, Table 1, VAIA pilot)

Design considerations, not legal advice or a conformity assessment. What O1 to O5 mean.

Build it

Illustrative signatures, not a published library: the names below are suggestions to adapt to your stack. Thresholds are examples to tune on your own data.

States: extracting, filled, reviewing, edited, cleared, failed

Component: <PrefilledForm fields={fields} source={text} onReview={fn} onClear={fn} />

Prompt snippet: Extract the value of each factual field from the source text. Return null when the source does not contain it. Never invent a value.

Output schema: { "fields": [{ "id": "string", "value": "string | null", "evidence": "string" }] }

Measure it

How often users follow the AI · from logsFaster, fewer errors · from logsPlan your testTen minutes per participant is the usual budget: pick the two or three cards that fit.

Same idea, other names

Shape of AI: Auto-fillMicrosoft HAX: G9 Support efficient correction

All the libraries we build on

Applied by: nobody yet · Replicated by: nobody yet · Used this pattern? Tell us and get listed

Research side · why it should work · framework v0.2

Why it should work

A filled field is a default, and defaults anchor judgement; reviewing a plausible text invites a verification stance in which people look for errors rather than alternatives, which is the mechanism behind automation bias.

Properties targeted

Reliance · Cognitive load · Efficiency · Axes: type: autofill, format: text, interaction: review · Vocabulary bridge

Notes

Why it should work for facts and fail for judgement: a factual field has one right value, so anchoring costs nothing and verification is the right stance. A judgement field has many acceptable values, and the anchor removes the search for them. The VAIA pilot shows the second half of that sentence with six people; the first half is the hypothesis for a factual-field study.

Relations

  • Efficiency rises for verifiable fields; reliance rises for all fields, which is the risk for judgement content.
  • Marking AI-filled fields should direct attention in review; whether it lowers cognitive load is not yet measured.

Across contexts

ContextUsersStateResult
VAIA course formscourse providersTested (pilot)2 of 6 preferred; 6.5 vs 11 alternatives viewed
Your contextBring your case

References

  1. Tversky and Kahneman 1974, Judgment under uncertainty: heuristics and biases (anchoring).
  2. Parasuraman and Manzey 2010, Complacency and bias in human use of automation.
  3. Van den Bossche and Abdul Khalil 2026, From Pattern Libraries to Practice, IUI Companion.

Editors

Practice: Abasin Abdul Khalil · Science: Ivania Donoso-Guzmán · card v1.0 · 2026-09-02