Use required fields only where they are truly necessary

Which form fields must truly be completed?

A field only becomes mandatory if the current process cannot be continued without this information for technical, business, or legal reasons. Internal data requests, values ​​that can be collected later, and sensitive early queries remain optional or are omitted; labeling and validation must express the same mandatory rule.

Essential processing

• Essential processing – Without this value, the current process cannot be meaningfully accepted and continued from a professional, technical, or legal perspective.

• No available alternative – The information cannot be reliably derived from existing data or obtained only in a suitable later step.

• Declared commitment – Field labels and help text clearly indicate which information is required and why sensitive values ​​are necessary before input.

No available alternative

1. For each mandatory field, jointly review the specific reason for termination if a value is missing with the relevant department, data protection officer, and processing team.

2. Make inferable, premature, or merely desirable information optional, collect it later, or remove it entirely from the process.

3. Implement mandatory labeling, browser validation, error messages, and internal processing with empty and borderline entries.

Test case: "CRM completeness"

A contact form requires a phone number and company size, even though inquiries can be processed via email. Both fields should be made optional, while the email address remains mandatory for the desired response. An upload is only requested later, once its purpose in the specific case is clear.

Declared commitment

• Proportion of mandatory fields with a documented, compelling processing or legal reason in the current process step.

• Number of form abandonments and support cases resulting from unexpected, sensitive, or unnecessary mandatory fields.

CRM completeness

• CRM completeness Internally requested fields become mandatory, even though a request could be processed or qualified later without them.

• Mandatory due to design Asterisks, legend, and the technical required property contradict each other and only generate unexpected errors upon submission.

• Sensitive Early Enquiry – Phone number, date of birth, or documents are requested before purpose, trust, and the necessary process step have been established.

What to Check Before and After "Consistently Limiting Required Fields"

"Consistently Limiting Required Fields" Building Navigation Based on User Tasks Instead of the Company Organizational Chart raises an important follow-up question: How do you translate user tasks into navigation instead of displaying the organizational chart?

Those who want to delve deeper into "Consistently Limiting Required Fields" from the perspective of the "Conversion & B2B Lead Systems" cluster will find further information in Qualifying Project Requests with a Few, But Crucial Fields .

If you want to practically implement "Consistently Limiting Required Fields," you can refer to Robust Website Systems . The focus there is on "Form Scope, Input, and Error Handling" and "Essential Processing."

Conclusion: Consistently Limit Required Fields

A requirement is a process necessity, not a wish list. The earlier or more sensitive a piece of information is, the more clearly its current need must be demonstrated.

Sources and Further Information

These primary sources are authoritative for platform behavior, terminology, and validation limits regarding "Consistently Limiting Required Fields."

• Understanding Labels or Instructions — W3C WAIThe WCAG explanation requires clear mandatory, format, and input instructions when users have to enter data into a form.

• Question Pages — GOV.UK Design SystemGOV.UK requires that only truly necessary information be requested, that optional fields be explicitly marked, and that mandatory fields not be marked with an asterisk.

• Collecting Personal Information from Users — GOV.UK Service ManualThe guidelines support the restriction to necessary and proportionate personal data and require a justification for its collection.