Public-service forms are written by institutions for institutions, and it shows: dense clauses, cross-referenced sections (“see Annex 3, unless the applicant falls under Section 4(b)”), and jargon that assumes you already understand the process you are trying to learn. Reading one cold, under time pressure, is where people either give up or guess — and guessing on a residency application, a benefits form, or a business registration can cost weeks of resubmission or worse.
A model is a genuinely good reading partner for this kind of text: it can take a wall of instructions and turn it into a plain checklist of what is actually being asked for, field by field. What it cannot do is tell you whether you qualify for the thing the form grants, what the current deadline is, or whether your specific situation meets a legal threshold — those questions belong to the issuing authority, not to a language model that has no access to the current version of the rules, your file, or the discretion the authority applies case by case.
Never ask a model to determine your eligibility, confirm a deadline, interpret your legal status, or state what benefit or entitlement you qualify for — and never let it auto-fill or submit a form field on your behalf. Forms and eligibility rules change, an out-of-date model response can describe a superseded process with total confidence, and only the issuing authority can confirm what applies to your specific case. Use the model to translate wording into a checklist; use the authority’s own current published source, or a direct call to their office, for anything that decides an outcome.
Step 1: Start from the official source, not from memory
Locate the form and its instructions on the issuing authority’s own site — not a summary blog, not a forum thread, not the model’s own recollection of “how this form usually works,” which may reflect an outdated version. Note the exact URL and the version or publication date printed on the document itself; forms get revised, and a checklist built from last year’s version can send you chasing evidence the current form no longer requires, or missing a field it added.
Official source URL: [paste]
Form name / number: [paste]
Version or publication date printed on the form: [paste]
Date you retrieved it: [today's date]
Step 2: Paste the actual instructions and ask for a field-by-field translation
Copy the form’s own instruction text (not a description of it) and ask the model to work only from what you pasted.
Here are the official instructions for [form name], copied directly
from [official URL], version dated [date]: [paste instructions text].
Working only from this text, list every field the form asks for, in
plain language, in the order they appear. For each field, note: what
it is asking for, any evidence or document it says is required, and
whether the instructions state a condition (e.g. "only if you are
self-employed") for that field. Do not add fields, requirements, or
conditions that are not in the text I gave you, and do not guess
what a vague field is asking for — mark it "unclear, needs
confirmation" instead.
Illustrative shape:
Field 4 — "Household composition": lists everyone in the applicant's
household as of the application date. Evidence required: a signed
declaration if household size changed in the last 12 months.
Field 7 — "Supporting documentation, Annex 3": unclear — the
instructions reference "Annex 3" but Annex 3 was not included in
the text provided. Needs confirmation from the authority or the
full document.
This only works if the model is translating text you gave it, not filling gaps from its own training. If a field references an annex, a schedule, or a linked page you have not pasted, treat the output for that field as incomplete rather than asking the model to infer what the missing section probably says — go back to the official source and get the actual text first.
Step 3: Build the evidence checklist, tied to the exact wording
Turn the field-by-field list into a document checklist, keeping the form’s own wording alongside your plain-language note so you can double-check later that nothing drifted in translation.
From the field list above, build a checklist of every document or
piece of evidence mentioned, in the exact wording the form uses,
next to a plain-language note of what it means. Group items by
whether they apply to everyone or only under a stated condition.
Government forms often ask for national ID numbers, income figures, health information, or household composition details — some of the most sensitive data you can put into a chat tool. Redact identifying numbers wherever the exercise does not require them (you are checking wording and evidence lists, not filling in your actual answers), and never paste your completed, filled-in form for “review” unless you are using a tool your authority has explicitly approved for that purpose.
Step 4: List what is genuinely uncertain, and take it to the authority
Any field marked “unclear,” any condition that seems to reference something outside the text you have, and any question about whether you personally qualify goes on a separate list for a real person at the issuing authority — a phone call, an in-person appointment, or an official email, not a follow-up chat message.
From this checklist [paste], list every item marked unclear or
needing confirmation, plus any question about whether my situation
meets a stated condition. Phrase each as a specific, answerable
question I can ask the authority directly. Do not attempt to answer
these questions yourself.
Common pitfalls
- Letting the model fill a gap with a plausible-sounding answer. A model under-informed about your specific form will still produce fluent, confident text — the wording alone will not tell you it is guessing.
- Working from a summary instead of the form’s own instructions. Even a well-meaning explainer article can describe an older version of the process; the official source with its version date is the only reliable anchor.
- Treating the checklist as proof of eligibility. A completed evidence checklist means you know what the form is asking for — it says nothing about whether you will be approved.
- Auto-filling or submitting through a connected tool. A browser agent that fills form fields for you removes the one checkpoint (your own read of the final answer) that catches transcription errors before they become official.
Validation and fallback
Before you submit anything, re-read the completed form yourself against the checklist and the original instructions, field by field — do not trust a model’s confirmation that “everything looks complete.” If a required field’s wording is ambiguous even after this process, call the authority rather than submitting your best guess; a short delay for a clarifying call is nearly always cheaper than a rejected or contested submission.
Prepare your next form
Pull the official instructions, verify the version date, and run the translation and evidence-checklist prompts above using the official form preparation sheet. If the form comes as a long, dense PDF, reading long documents, contracts, and PDFs covers the underlying three-pass method, and AI vs. Google is worth a look before you trust any search result about “how this process works” over the authority’s own page.
