An intake form is often a customer’s first real interaction with a business. A good one feels quick and respectful. A bad one feels like paperwork — and people abandon paperwork.
These principles apply to any intake or request form, on paper or online.
1. Ask for less
Every question has a cost for the person answering it. Before adding a field, ask: will we act on this answer? If not, leave it out. You can always ask follow-up questions once someone has engaged.
Separate what you need now from what you need eventually. A service request needs to know who is asking and where the work is. The gate code, the pet’s name and the preferred visit day can often wait for a follow-up.
2. Set expectations before the first question
People are more likely to finish a form when they know what they’re getting into. Show:
- Who they’re submitting to — your organization’s name, clearly.
- What the form is for — one sentence.
- How long it is — the number of steps or sections.
A visible list of steps turns an open-ended task into a finite one.
3. Group related questions
Grouping questions into short sections — About you, Where is the work?, What do you need? — makes a form feel shorter than one long list. Keep each group to a handful of related questions and give it a plain-language heading.
On multi-step online forms, one group per step works well.
4. Order questions the way people think
Start with easy, familiar questions (name, contact details) and move to the specific ones. Within a group, follow natural order: street, then city, then postal code.
5. Use the right input for each answer
- Email and phone fields should check format, and on phones should bring up the right keyboard.
- Dates should use a date input rather than free text.
- A short list of options should be a choice, not a text box.
- Long answers get a larger text area.
6. Validate kindly, and early
Catch mistakes as they happen, next to the field, in plain language: “That doesn’t look like an email address.” Don’t wait until the end to report a list of errors, and don’t clear what someone typed.
7. Be honest about what’s required
Mark required fields clearly and consistently. If most fields are required, mark the optional ones instead. Never require a field you won’t use — people will enter placeholder text to get past it, which is worse than a blank.
8. Let people review before they submit
A review step — every answer in one place, with a way to go back and fix things — catches typos and reassures people that they’re sending what they meant to. It’s the single best defence against the “sorry, I typed my email wrong” follow-up.
9. Confirm clearly
After submission, tell people it worked and what happens next: when you’ll respond and how. A clear confirmation prevents duplicate submissions and anxious phone calls.
10. Keep paper and online in step
If you collect the same information on paper and online, make sure both ask the same questions in the same way. Otherwise you’ll spend time reconciling two versions of the same form.
Structuring a longer form
Some forms genuinely need many questions — applications, detailed assessments, onboarding. Structure carries them:
- Break into short steps, each with a clear heading, and show progress.
- Front-load the easy questions so people build momentum.
- Group by topic, not by which system the data goes into.
- Explain any question people might find intrusive — one short sentence on why you’re asking.
- Let people review everything before submitting.
Mobile considerations
A large share of intake happens on phones:
- Keep labels short so they don’t wrap awkwardly.
- Use input types that bring up the right keyboard for email, phone and numbers.
- Avoid wide tables and side-by-side fields that squeeze on small screens.
- Make tap targets generous.
- Test the whole flow on a phone before publishing.
Accessibility basics
An accessible form reaches more people and is usually clearer for everyone:
- Label every field with visible text, not placeholder text alone.
- Don’t rely on colour alone to show errors or required fields.
- Keep instructions next to the field they apply to.
- Make sure it works by keyboard, in a sensible order.
- Write plainly. Short sentences and everyday words beat formal phrasing.
Measuring and improving
Forms improve through iteration:
- Watch completion. If people start and don’t finish, look at where the form gets long or intrusive.
- Read the answers. Frequent blanks in an optional field suggest it isn’t needed; confused answers suggest an unclear label.
- Track follow-up questions. If you always have to ask one more thing, add it to the form.
- Remove what you never use. Every removed field speeds up every future submission.
Frequently asked questions
How many fields is too many? There’s no fixed number; relevance matters more than count. People will answer twenty questions they see the point of and abandon five they don’t.
Should I ask for a phone number? Only if you’ll use it. If email is your main channel, make phone optional.
Is a multi-step form better than one long page? For anything beyond a handful of questions, steps with a progress indicator usually feel shorter and are easier to complete on a phone.
Putting it into practice with Atlas
Stratosphere Atlas bakes several of these principles into its public forms: respondents see the organization’s name and every step listed down the side before they start, each section is one reusable data schema with its own formats and required markers, and every form ends with a review step before submission. Because printed and online forms come from the same schemas, paper and online stay in step. See Collect your form online with a public link.
