How do I describe the information users need before starting an online process?
Quick answer
Put a short readiness section before the first step or form field. List only requirements confirmed by the service owner, distinguish required items from optional ones, and explain any confirmed formats or timing limits. Give a time estimate only when it has been verified, and say what it covers. Use clear labels, and tell readers what to do if a requirement is unclear or unavailable.
The question, the details, the next step.
How do I describe the information users need before starting an online process? I want people to know whether they are ready before they open a long form.
Add a brief “Before you start” section immediately before the first form page or action. It should answer three practical questions: What must I have? How long should I allow? What materials or information should I prepare?
Use only details confirmed for this specific process. WAI guidance recommends providing relevant overall instructions before a form, including required or optional inputs, formats, and timing limits; it does not identify what any particular service requires. [S1] Confirm the list with the service owner rather than inferring it from an old form or a similar service.
Keep the section scannable. Mark each item “Required” or “Optional,” state the format where relevant, and avoid implying that an optional item is necessary to continue.
What should I include under requirements, estimated time, and materials? How do I avoid making guesses sound official?
Separate the categories and label uncertainty clearly:
- Requirements: List confirmed prerequisites for starting or completing the process. Make clear whether each is required or optional. Do not add eligibility rules or documents unless the service owner has verified them.
- Time: Give an estimate only if the person responsible for the process can support it. State what the estimate covers—for example, “time to complete the form”—and use a placeholder until confirmed: “[verified estimate].” Don’t present an unverified guess as a promise.
- Materials or information: Name only items users actually need. If a format matters, specify the confirmed format in plain language, such as “[accepted file format].”
Ask only for information needed to complete the process. WAI’s tutorial gives that as a general form-design principle, but it does not establish which information this particular process needs. [S2]
Can you show me a copyable layout that makes the distinction clear without knowing the details of my service?
Use this as a draft, replacing every bracket with information confirmed by the service owner. Remove any line that does not apply; don’t leave placeholders in published copy.
Before you start
- Required: [verified prerequisite or information]. If a format matters: [verified format].
- Optional: [verified optional item], if applicable.
- Have ready: [verified materials or details needed to complete the process].
- Time: Allow about [verified estimate] to [define what the estimate covers]. This is [a planning estimate / other verified description].
- Before continuing: If you are unsure whether [specific item] is required, [verified next step or support route].
For example, a writer could draft “Have ready: [confirmed item]” while checking the requirement, but should not replace the placeholder with a plausible-sounding document name. Put important instructions before users begin, and repeat a detail beside the relevant field when useful. WAI recommends overall instructions before a form and relevant instructions in or alongside field labels. [S1]
How should I check the section before publishing, especially if the process has several pages or the details change?
Treat the pre-start section as a summary of current, verified process information—not as a substitute for instructions on each page. Check the requirements, formats, optional items, time estimate, and support route with the person responsible for the process. If a detail is not confirmed, omit it or leave it for internal follow-up rather than presenting it as fact.
Compare the summary with the form itself: remove requests for information the process does not need, and make sure any important format instruction appears near the relevant field as well as, where useful, in the opening guidance. WAI discusses instructions, validation, notifications, and progress for multi-page forms as form-design topics, but its general guidance does not verify a particular service’s prerequisites or timing. [S2]
A useful final test is whether a reader can decide what to prepare and whether to proceed without mistaking optional items for required ones.
A practical checklist
Place a concise readiness section before the first process step or form page.
Confirm every prerequisite, format, optional item, time estimate, and support route with the responsible service owner.
Label requirements and optional items distinctly; omit unverified details.
Explain what a time estimate covers, and use a placeholder until it is confirmed.
Repeat important format instructions beside the relevant field when useful.
Remove draft placeholders and check the summary against the actual process before publishing.
A few more useful answers
Should I list documents users might need just in case?
Only list materials confirmed as needed for this process, and label any confirmed optional item as optional. A plausible guess can mislead users about what is required.
What if nobody can confirm how long the process takes?
Do not invent a duration. Omit the estimate or say that a verified estimate is unavailable, if that wording is appropriate for the service.
Is a pre-start checklist enough for a multi-page form?
It can help users prepare, but it may not replace instructions beside individual fields. Keep relevant format or entry guidance near the field where users need it.
Sources
References used for this guide.
- [S1] Form Instructions — WAI Forms Tutorial w3.org · Checked
- [S2] Forms Tutorial — WAI w3.org · Checked