# Form Completion and Validation Optimizer

Redesign a form around user intent, data necessity, validation timing, privacy, and recovery to improve accurate completion.

## Prompt

You are a form UX specialist who optimizes completion, comprehension, validation, and data quality.

Inputs:
1. Form purpose, users, and business outcome: {{form_context}}
2. Current fields, steps, labels, and help text: {{current_form}}
3. Validation rules, dependencies, and downstream use: {{data_rules}}
4. Analytics, errors, abandonment, and support evidence: {{performance_evidence}}
5. Platform, accessibility, privacy, and legal constraints: {{constraints}}

Do the following:
1. Audit every field for user value, business necessity, collection timing, sensitivity, answerability, and whether the data can be derived or requested later.
2. Reorganize retained fields into a logical sequence with clear labels, input types, defaults, optional markers, grouping, and conditional disclosure.
3. Define validation timing and messages for missing, malformed, inconsistent, duplicate, and system-rejected data, preserving user input and explaining exactly how to recover.
4. Address keyboard flow, screen readers, autofill, localization, mobile input, progress, save-and-resume, privacy explanation, and final review where appropriate.
5. Produce a field decision table, revised form structure, validation-message library, interaction notes, measurement plan, and test scenarios. Do not use deceptive defaults or remove required disclosures to improve completion metrics.

## Best for

Designers and product teams improving registration, checkout, application, intake, or data-entry forms without sacrificing accuracy or consent.

## Compatible tools

- Claude
- ChatGPT

## How to use

- Include every current field and its downstream use.
- Provide abandonment and validation evidence.
- Name data that is sensitive or legally required.
- Test the revised form on mobile and with assistive technology.

## Customization tips

- Explain why sensitive information is requested.
- Preserve input after every recoverable error.
- Use examples for unfamiliar formats.
- Track correction success as well as abandonment.

## Example input

Form: Mobile insurance claim intake with 27 fields across one long page. Users: policyholders after minor vehicle damage. Evidence: 38% abandon at incident details; support reports confusion about incident date versus report date. Rules: policy number can be looked up after email and postcode; photos may be added later; injury questions trigger specialist routing. Constraints: German and English, WCAG 2.2 AA, sensitive-data notice required, and drafts retained for 30 days.

## Example output

The redesign removes manual policy-number entry after verified lookup, separates incident and report dates with examples, and moves optional photo upload after claim creation. Injury routing remains early but uses neutral, explicit language. Inline validation appears after field exit, while cross-field date conflicts are explained at review. The plan includes draft recovery, mobile date controls with text alternatives, bilingual expansion checks, and metrics by field error rather than completion alone.