Fill in these first
- Form purpose: [e.g. checkout for a clothing store, free trial sign-up]
- Fields in order: [for each, the label, placeholder, required or optional, input type and any helper text]
- Current error messages: [paste them, or "not known"]
- Device split: [e.g. 80 percent mobile]
- Known problems: [e.g. drop-off at the address step, people mistype phone numbers]
- What the business must collect and why: [e.g. phone for delivery updates]
Task
Review the form field by field and say exactly what to change so more people complete it without errors.
Output format
- | Field | Current label | Issue | Fix | Priority (high, medium, low) |
- Fields to remove, make optional or ask later, with the reason for each.
- Rewritten error messages: each says what went wrong and how to fix it, in under 12 words.
- Mobile checks: input type and keyboard per field, autofill attributes, tap target size.
- Layout notes: single column, label position, step count, and where the main button sits.
Rules
- Labels stay visible above the field; placeholders never replace labels.
- Validate after the person leaves a field, not on every keystroke.
- Never blame the user in an error message.
- Do not invent drop-off figures. Where no data was given, rate priority by how many people the field affects.
Example
Phone field: issue "rejects spaces and +91". Fix: accept any common format and clean it on the server. Priority high.






