Form Labels and Help Text
Say what the field wants, why it is needed, and what format is acceptable, before the reader gets it wrong.
Definition
Form copy covers the label, the help text, the format hint and the reason a field exists. It is the difference between a form people complete once and a form people fight.
Expert heuristic. A review criterion developed by practitioners. Useful and widely taught, but evaluated by judgement rather than measurement.
On this plate
Reach for this when
- Designing or auditing any form.
- One field shows much higher drop-off or correction rates than the rest.
- Support keeps answering the same question about what a field means.
Common mistakes
- Placeholder-only labels.
- Rules revealed only on failure.
- Help text written for the legal team rather than the reader.
- Writing hint text for the fields that are obvious and leaving the one genuinely ambiguous field unexplained.
The same field, three ways
| Weak | Better | Best | Why the last one wins |
|---|---|---|---|
| Name | Full name | Full name, as it appears on your ID | Removes the ambiguity that causes the correction request later. |
| Phone | Mobile number | Mobile number, for delivery updates only | Answers the unspoken question, which is why you want it. |
| Password | Password (8+ characters) | Password, at least 8 characters with one number | States every rule up front instead of revealing them on failure. |
| Date | Start date | Start date, DD/MM/YYYY | Names the format where ambiguity is genuine rather than assumed. |
| Company | Company (optional) | Company, if you are buying for a business | Explains when to fill it rather than only that it can be skipped. |
Where the words go
Do
- Keep a visible label above the field, always.
- Put format and constraint text under the label as persistent help, not inside the field.
- Mark optional fields rather than required ones when most are required, and the reverse when most are optional.
- Say what happens to sensitive data at the field that asks for it, not in a privacy page nobody opens.
Do not
- Do not use the placeholder as the label. It disappears exactly when it is needed, fails contrast in most implementations, and is unreliable for assistive technology.
- Do not hide the password rules until the password is rejected.
- Do not write help text that restates the label: 'Email' with 'Enter your email'.
- Do not use asterisks without a legend.
Words that cause support tickets
- Internal jargon: entity, record, instance, workspace slug.
- Legal phrasing in an everyday field, which reads as a warning.
- Labels that differ from the words used in the confirmation email for the same thing.
- Ambiguous dates: 'Date' on a form with both a start and an expiry.
Labels, hints and the reason a field exists
Do
- Put the format requirement above the field, not in the error after it.
- Say why you are asking for anything that feels intrusive, at the field.
- Keep the label visible while the field is being filled.
- Mark optional fields rather than required ones when most are required.
Do not
- Use the placeholder as the label.
- Explain a field in a tooltip, which touch users will not see.
- Write a hint longer than the field it explains.
- Ask for something you do not use, then justify it in the hint.
In practice
- i.
Explaining a suspicious request
A checkout asking for a date of birth without explanation reads as data collection. The same field labelled 'Date of birth, required to verify age for alcohol delivery' is completed without complaint, because the reason is where the question is.
- ii.
Why do you need my date of birth
Explaining a suspicious requestA single line saying the date is used to confirm eligibility, and is not shared, measurably reduced abandonment at that field. The field did not change. The reason for it became visible.
Local chart
WRT·009 · Region III · Grid F1
This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.
Continue from here
Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.
Depends on
Get these right first, or this one will not hold.
- Labels and InstructionsA11Y·017 · Accessibility
A visible label is both a writing decision and a WCAG requirement.
Check your work
Review passes that test whether this was done properly.
- Form UX ChecklistCHK·001 · Checklist
Related concept
Connected closely enough to change how you apply this.
- Text InputCMP·003 · Component
- AuthenticationPAT·023 · Pattern
- Input ValidationPAT·007 · Pattern
- Payments and CheckoutPAT·024 · Pattern
- Error MessagesWRT·002 · UX writing
- MicrocopyWRT·001 · UX writing
- Tooltips and Inline HelpWRT·015 · UX writing