Is this form structurally capable of converting well?

• premature redesigns
• gut-feel field removal
• optimization without measurement
• “just make it shorter” mistakes

• Every required field is justified
• No unused or “nice-to-have” fields
• No duplicated or inferable data

• Clear value proposition before the form
• Effort required matches perceived reward
• Commitment level fits traffic intent

• Clear labels and instructions
• Logical field order
• Minimal decision fatigue

• Inline validation
• Helpful error messages
• No data loss on errors

• Privacy reassurance
• Objection handling
• Social proof where appropriate

• Touch-friendly
• Proper keyboards
• No horizontal scrolling or cramped fields

• Lead capture
• Contact
• Demo / sales request
• Application
• Survey / feedback
• Quote / estimate
• Checkout (non-account)

• What happens after submission?
• Which fields are actually used?
• What qualifies as a “good” submission?
• Any legal or compliance constraints?

• Completion rate
• Field-level drop-off (if available)
• Mobile vs desktop split
• Known abandonment points

• 3 fields → baseline
• 4–6 fields → −10–25%
• 7+ fields → −25–50%+

• not used
• not acted upon
• not required legally

• Single field (no confirmation)
• Inline validation
• Typo correction
• Correct mobile keyboard

• Single “Name” field by default
• Split only if operationally required

• Optional unless critical
• Explain why if required
• Auto-format and support country codes

• Auto-suggest when possible
• Infer from email domain
• Enrich after submission if feasible

• Dropdown if segmentation matters
• Optional by default

• Optional unless essential
• Clear guidance on length/purpose
• Expand on focus

• Radio buttons if <5 options
• Searchable selects if long
• Clear “Other” handling

1. Easiest first (email, name)
2. Commitment-building fields
3. Sensitive or high-effort fields last

• Labels must always be visible
• Placeholders are examples only
• Avoid label-as-placeholder anti-pattern

• Default to single column
• Multi-column only for closely related fields

• 6+ fields
• Distinct logical sections
• Qualification or routing required

• Progress indicator
• Back navigation
• Save progress
• One topic per step

• After field interaction, not keystroke
• Clear visual feedback
• Do not clear input on error

• Specific
• Human
• Actionable

• “Get My Quote”
• “Request Demo”
• “Download the Guide”

• Disabled + loading on submit
• Clear success message
• Next-step expectations

• Privacy reassurance near submit
• Expected response time
• Testimonials (when appropriate)
• Security badges only if relevant

• ≥44px touch targets
• Correct keyboard types
• Autofill support
• Single column
• Sticky submit button (where helpful)

• Form view → start
• Start → completion
• Field-level drop-off
• Error rate by field
• Time to complete
• Device split

• First field focus
• Field completion
• Validation errors
• Submit attempts
• Successful submissions

• Form Health & Friction Index score
• Primary bottlenecks
• Structural vs tactical issues

• Issue
• Impact
• Fix
• Priority

• Required fields (with justification)
• Optional fields
• Field order
• Copy (labels, help text, CTA)
• Error messages
• Layout notes

• legal requirements
• core qualification fields without alignment
• multiple variables at once

1. What is the current completion rate?
2. Which fields are actually used?
3. Do you have field-level analytics?
4. What happens after submission?
5. Are there compliance constraints?
6. Mobile vs desktop traffic split?

• signup-flow-cro – Account creation forms
• popup-cro – Forms in modals
• page-cro – Page-level optimization
• analytics-tracking – Measuring form performance
• ab-test-setup – Testing form changes