Recent chats
ASKGEEZ Q&A GUIDEWriting & communication

How do I explain why a form asks for a particular piece of information?

Quick answer

Name the specific task the information helps with, then say what the person should enter and any relevant format. Keep the explanation beside the field, and make it no longer than needed to answer the likely question. Before saying how information is used, stored, shared, or required, verify that statement with the responsible source; if the reason is unknown, do not guess. Review whether the field is needed at all.

LET’S WORK THROUGH IT

The question, the details, the next step.

Question

How can I explain a field’s purpose without making the form feel more complicated?

Geez

Use one short note that answers the reader’s likely question: “Why are you asking me for this?” State the specific step the detail helps with, in ordinary language, and put the note next to the field so it is easy to connect to the request. If the expected answer or format is not obvious, include that too. Form guidance recommends identifying the expected input and giving enough instructions to complete the task without confusing or unnecessary detail. [S1]

A useful pattern is: “We ask for [detail] to [verified purpose]. Please enter [what to provide or format].” The words “verified purpose” matter: use a reason confirmed by the person responsible for the form, not a plausible-sounding guess. If you cannot confirm the reason yet, leave a placeholder in the draft rather than publishing an invented explanation.

Follow-up question

What if people might assume the detail is being collected for a different reason?

Geez

Address the likely misunderstanding only when you can confirm the facts. First ask the form owner what the information is needed for and whether any statement about its use is accurate. Then explain the confirmed purpose narrowly. Don’t add claims about storage, sharing, deletion, confidentiality, or whether the field is mandatory unless those details have also been checked.

For example, suppose a draft event-registration form asks for an organization name. The reason below is illustrative, not a claim about any real form: if the owner confirms it helps staff group registrations by organization, a note could say, “We ask for your organization so we can group registrations for this event.” If that reason is not confirmed, do not use it. Ask the owner to supply the wording instead. General form guidance supports asking for information needed to complete the process, but it does not establish why a particular organization requests a particular detail or how it handles that information. [S2]

Follow-up question

Can you give me a template I can adapt for one field?

Geez

Copy this into your draft and replace each bracketed part only after checking it:

“[Field label] [We ask for this detail to [confirmed purpose].] Please enter [specific answer or format]. [Optional: [verified clarification that addresses a likely misunderstanding].]”

Example with placeholders: “Preferred contact time. We ask for this detail to [confirmed purpose]. Please enter [a time and time zone, if needed]. [Add a clarification only if the form owner confirms it.]

Delete the purpose sentence if nobody can verify it; don’t turn an unknown reason into a confident claim. You can still make the field easier to complete by clearly stating what answer it expects, provided that instruction is accurate. Keep any optional clarification short and directly related to the field.

Follow-up question

How do I check whether the note is ready to publish?

Geez

Read the field label and note together as if seeing the form for the first time. Check that the note explains the request in context, says what to enter where necessary, and does not introduce a second question or an unverified promise. Then ask the responsible form owner to confirm the purpose and each statement about data use. If the purpose cannot be confirmed, leave it out and request clarification rather than inventing one.

A final edit can be simple: remove words that do not help someone understand why the detail is requested or what to enter. Form guidance recommends requesting only information needed to complete the process and providing instructions that help people understand individual controls. That guidance is general; it cannot determine whether a specific field is necessary or establish its business purpose. [S2]

A practical checklist

  • Name the exact field and the question a reader may have about it.

  • Ask the responsible form owner to confirm the reason for requesting the detail.

  • State the purpose plainly and only as specifically as the verified facts allow.

  • Add the expected answer or format if it is not self-evident.

  • Verify every claim about how the information is used before including it.

  • Remove unsupported claims and any instruction that does not help complete the form.

A few more useful answers

What should I write if no one can explain why the field is there?

Don’t invent a reason. Ask the responsible form owner to confirm the purpose; until then, omit the purpose claim or keep a bracketed placeholder in the unpublished draft.

Should every field have a purpose note?

Not necessarily. Add one when the reason or expected answer may not be obvious, and keep it focused; general form guidance favors instructions that help completion without unnecessary detail. [S1]

Can I say a detail is required or will not be shared?

Only if the relevant statement has been independently confirmed by the responsible source. The field’s wording alone does not establish its requirements or data-use practices.

Sources

References used for this guide.

  1. [S1] W3C WAI: Understanding WCAG 2.2 Success Criterion 3.3.2, Labels or Instructions
    w3.org · Checked
  2. [S2] W3C WAI Forms Tutorial
    w3.org · Checked

YOUR QUESTION. YOUR DETAILS.

Let’s work through your situation.

Get a tailored answer or help with your next task. Starts at $1, with a quote before you pay.

Ask your own question
← Back to Geez at Work