IA Library · Page pattern · Reasoned, not built
Enquiry, quote or booking page
“How do I ask, and what happens after I do?”
RequiredConditional on the briefCommon, not requiredLeft out for this briefYour content
Used by
Why this pattern works5 statements · 3 sourced · 1 untested or unknown
How sure we are
Worked out from research and real briefs. No site has been built from it yet, so treat it as reasoning to check, not a tested template.
What it answers
Its job Take the action with as little effort as the business can manage, then say clearly what happens next.
Its action: Submit the form. The other way to get in touch stays visible.
Use it when
- The action needs more than a phone number: a quote with photos, a booking request, a commission brief.
Not when
- A phone-led business whose customers just call. A form nobody answers is worse than a number.
- Booking handled entirely by a third-party system: link to it and say so.
What the research says
- GOV.UK’s question pages, check-answers and confirmation patterns are the best-sourced structure in this library. They are written for government transactions, so applying them to a three-field quote form is our own reasoning.
- The sources disagree: GOV.UK starts forms at one thing per page; NN/g says contact forms should be 3 to 5 fields. Short enquiries follow NN/g; long bookings follow GOV.UK.
- Attachments were asked for in 23 of the briefs we studied, quote requests in 17.
Common mistakes
- A long form for a short question, or a “contact us” with no idea of when anyone will reply. NN/g: 3 to 5 fields, and state the response time.
- Asking for a budget field before saying anything about prices.
What changes with the brief
| What should a ready visitor do? Ask for a quote | Quote form with photo upload; the steps say when the quote arrives. |
|---|---|
| What should a ready visitor do? Phone us | The page leads with the number and hours; the form becomes the second route. |