The practices
| Practice | Who does it | Evidence (source, year, finding) | Verdict for our form | How on our form |
|---|---|---|---|---|
| Read the filer's own document to fill the form | TurboTax (photo or PDF import), Onfido and Persona (ID scan), Wise and Revolut (document capture) | TurboTax, import or enter a W-2, read 2026: a photo or PDF fills the return on its own. Onfido Smart Capture, read 2026: real-time blur and glare checks raise capture success | Apply later: needs OCR reading; the strongest 2025 to 2026 shift to plan for | Let the filer upload the launch licence, or a photo of it; the helper reads it the way it reads public sources today |
| Write the form so an AI agent can fill it too | Google Gemini auto-browse in Chrome, Perplexity Comet, ChatGPT Atlas | eesel.ai, Chrome auto-browse, 28 January 2026: Gemini's Chrome agent now fills forms across sites unattended | Apply now: costs nothing; a filer's own agent reads the same labels a screen reader does | Keep every field's visible label, id and autocomplete token matched; never rename a field without renaming its label |
| One click reuses a saved identity | Stripe Link | Stripe, payments revenue uplift, 2023: Link lifts conversion over 7 percent for returning users, one case 34 percent | Apply later: waits on operator accounts, same gate as save-and-resume | Once accounts exist, a returning operator's saved profile fills the launching-State and operator block in one click |
| Address lookup as you type, not a text box | Stripe Address Element, Google Maps Places | Stripe, Address Element, read 2026: built-in autocomplete cuts checkout time and validation errors | Apply now: the operator address field is still free text | Wire the operator address field to a live place-lookup; keep the typed fallback for an unlisted address |
| The draft saves itself, no save button | Notion, Linear | Figma blog, the Linear method, read 2026: speed and clarity come from removing manual steps, saving included | Apply now: a stronger version of the save-and-resume link already planned | Write the draft to storage on every change, not only when the filer clicks a save link |
| Format the value while the filer is still typing it | Stripe Elements, card and phone fields | Stripe Elements, read 2026: formatting while typing catches a shape error before submit | Apply now: extends the on-blur check the form already has | Group and case-correct the designator and pattern fields live; keep the on-blur plain-word check as the backstop |
| A chat panel that still writes into the real fields | Lemonade, the Maya assistant | getperspective.ai, Lemonade case study, read 2026: Maya carries a quote to a bound policy in under 90 seconds | Apply later: a bigger build, but the direction for the existing helper | Let the filer type a correction or a question to the helper in words, not only accept or reject its filled value |
| Name the verification method next to the field it touched | Revolut, Monzo, N26 | Craft Innovations, banking onboarding, read 2026: naming the check inline builds filer trust before upload | Apply now: one line of text, no build | Name the source next to any field the helper filled and next to any proof the filer uploads |
| A passkey instead of a password for a return visit | Apple, Google, any FIDO-based account | FIDO Alliance, State of Passkeys 2026, May 2026: passkeys succeed in 93 percent of logins against 63 for passwords | Apply later: same gate as accounts and save-and-resume | Offer a passkey instead of a password the day operator accounts exist |
| A command box that jumps straight to a section or field | Linear, Superhuman, Raycast | Superhuman, speed up with shortcuts, read 2026: a keyboard command box removes friction for a repeat expert user | Apply now: small addition, fits a filer who returns once or twice a year | A Cmd or Ctrl+K box that jumps to any of the six sections or any field by name |
| Speak one sentence, fill several fields at once | Voice-form widgets such as TypelessForm | TypelessForm, 2026: one spoken sentence fills several matched fields at once | Not for us: a designator or an orbit number is easy to mishear | Kept as typed and scanned entry; no microphone added |
| Cut every field the data does not strictly need | General ecommerce and lead-form advice | CXL, should you reduce form fields, read 2026: cutting the wrong fields once cost one test 14 percent | Not for us: twenty fields are the legal record, not a lead form | Kept at twenty; effort goes into guidance, not into deleting required fields |
Where the private sector is ahead
Reusable identity
Stripe Link and passkeys let a person prove who they are once, not on every visit; a registry filer should not retype the same operator block twice a year.
The document does the typing
TurboTax's photo import and Onfido's document scan read the filer's own paper; a registry still asks the filer to copy numbers out of it by hand.
Losing a draft is a bug, not a risk
Notion and Linear save on every change; a public form that only saves on a click still loses work to a closed tab.
The newest browsers fill forms unattended
Gemini's Chrome agent and similar tools now act on a page for the person; only a form with honest labels survives being driven by one.
An address is confirmed, never retyped free-hand
Stripe's Address Element looks an address up as the person types it; most public forms still hand over a blank text box.
What the private sector does that a public registry must not copy
- Countdown timers and "others are booking this now" urgency, common on travel and retail checkouts; a professional filer has no reason to be rushed.
- Pre-checked marketing consent or paid add-ons at checkout; a registry asks for nothing beyond the filing itself.
- Collecting more personal data than the task needs, to build a marketing profile; a registry keeps only what the law requires.
- A forced account before the person can even see the form, common in SaaS sign-up; the twin lets a filer see and start the form first.
- Confirmshaming the decline path ("No thanks, I don't want to save time"); every choice on a registry form is worded the same plain way, whichever way the filer answers.
The twin's form against this list
- A named helper that states its source per value, in the spirit of Lemonade's Maya, though not yet a two-way conversation
- Typed, searchable lists instead of a scrolling dropdown, the same fix Baymard and Google Maps both reach for
- Sensible defaults already filled in, in the spirit of Google Flights' pre-set departure airport
- Validation in plain words on leaving the field, close to Stripe Elements' live field feedback
- A conditional reveal at work, the same progressive disclosure Airbnb uses on its own sign-up form
- No live address lookup; the operator address is still a plain text field
- No document or photo upload that the helper reads to prefill fields
- No autosave without a click; a closed tab still loses work until save-and-resume is built
- No stored, reusable operator identity across filings, the gain Stripe Link is built around
- No passkey or password-free return sign-in
- No inline naming of the verification method next to a proof or upload field
- No command box to jump between the six sections
- Not yet checked against an AI browser agent filling it on the filer's behalf
Read next: the state of the art in form design, and the rules this evidence feeds into, in how a form is built here.