A client intake form should reduce uncertainty, not collect everything that might be useful someday. Start with the decision you need to make after reading it.
Name the decision
Write what you will do with the answers: quote, book, refer or ask a follow-up. Every field should support that decision.
Group the questions
Put contact details, the request and the constraints in separate blocks. A logical order reduces abandoned forms and confused answers.
Use plain labels
Test a label with someone outside the business. If they ask what it means, rewrite it rather than adding help text.
End with the next step
Tell the client what happens after submission and who will respond. A form that ends in silence creates unnecessary follow-up.
Intake fields
| Item | Example |
|---|---|
| Block | Fields |
| Contact | Name, email, preferred reply |
| Request | What do you need? |
| Constraints | Deadline, budget range, files |
| Next | Who responds and when |
What to watch for
- Collecting fields without a decision.
- Using internal jargon in labels.
- Ending without a response expectation.
A useful next step
Remove one field that does not change the next decision. A shorter intake form is usually easier to complete and easier to maintain. If a required field has no owner, remove it or assign the follow-up before sending the form. A question that nobody acts on is data collection without a purpose. If the request is urgent, make the deadline field optional and ask for it in the reply instead of blocking the form. If a field is not used in the first month, remove it before the next review. Use one required field for the decision owner; leave the rest optional. Test the form with one real request before sending it to a client.