An architecture practice’s first enquiry form should help the team understand a potential project without asking a prospective client to produce a technical brief before speaking to a professional. This UK-focused guide explains how to design an architect project enquiry form that captures the right details, treats planning uncertainty responsibly, protects uploaded drawings and moves suitable enquiries towards a discovery meeting. It is intended for practice owners and marketing teams, not as legal, architectural or planning advice.
For the wider acquisition strategy, read Marketing for Architects UK. For the later proposal stage, see architect fee proposal follow-up.
Why project-brief enquiries need a different form
An architect is not selling an off-the-shelf product. A homeowner may be unsure whether an extension is feasible; a developer may need a feasibility study before a funding decision; a commercial occupier may require a phased refurbishment while a building remains in use. A generic “name, email, message” form gives the practice little context. An exhaustive questionnaire, however, asks people to solve design and planning questions they have hired an architect to help with. The goal is a short, understandable first step that supports an informed conversation.
Treat the website form as an initial triage tool, not a planning application, professional appointment or substitute for a measured survey. Ask only what changes the next action. Explain what happens after submission, when a human will respond and whether an initial discussion is free or charged. A clear distinction between enquiry, consultation and formal appointment reduces misunderstanding.
Start with three different enquiry routes
Provide a simple route for residential projects, a separate route for commercial or developer briefs and a general route for people who do not yet know what service they need. The routes can share the same underlying form with conditional questions. Avoid forcing users to select a technical RIBA stage when they are describing a problem in everyday language.
For a homeowner, the useful first questions are the property location, whether the work is an extension, renovation, conversion or new build, the outcome they want, a broad intended timescale and how to contact them. For a developer, ask about site control, intended use, approximate scale, programme and who will make appointment decisions. For a commercial client, ask whether the building is occupied, whether phased delivery matters and what approvals or landlord permissions are known. Every field should have a reason.
A practical minimum field set
The first screen should usually request name, a reliable reply method, broad project type, postcode or town, and a short description. Ask for a full address only when needed to assess location-specific constraints, and explain why. Allow “not sure” for budget, planning status and timing. An uncertain answer is useful information, not a reason to reject a lead.
Make phone optional unless a telephone discussion is essential to the service. Avoid asking for date of birth, identification documents, detailed financial information or other sensitive information at first contact. Use a free-text box with a prompt such as “What are you hoping to change, and what would success look like?” rather than an intimidating blank field. Show a character guide only if it genuinely helps.
Budget questions without deterring serious clients
A budget field can prevent mismatched expectations, but a mandatory precise figure is a poor proxy for project readiness. Many clients do not know whether they are describing a construction budget, an architect’s fee or the total project cost including VAT and contingency. Label the question clearly: “Indicative construction budget, if known”. Offer ranges tailored to the practice’s work and a “not yet established” option.
Do not automatically mark a prospect as unqualified because they cannot give a number. Instead, route them to an exploratory call or a paid feasibility discussion. Where the practice has a genuine minimum project size, explain it in plain language before the form rather than surprising applicants after submission. Keep budgets as internal planning assumptions until scope and procurement conditions are understood.
Planning status: capture facts, not promises
Ask whether the client has already sought planning advice, submitted an application or received a decision. Offer “I don’t know whether permission is needed”. This is more reliable than asking “Does the project have permitted development rights?” because many applicants cannot determine that themselves. Separate planning permission from building regulations, listed-building consent and other approvals; they are not interchangeable.
The Planning Portal explains that pre-application advice can clarify local requirements and policy issues, and councils may charge for it. It is not a guarantee of permission. A form should therefore avoid language such as “Planning approval guaranteed” or automated feasibility verdicts based solely on a postcode. For England-specific advice, label the jurisdiction; Scotland, Wales and Northern Ireland have distinct systems and processes.
Ask about site constraints at the right moment
Location can affect the scope of work: a listed building, conservation area, flood risk, unusual access or shared ownership may call for specialist assessment. Rather than presenting a long legal checklist to every visitor, ask a single optional question: “Are there any known site constraints?” Offer examples and “not sure”. Follow up after the first review where the answer matters.
An uploaded sketch or photo can be useful, but the practice should not imply that a photo replaces measured drawings or a site visit. Provide an alternative to uploading, such as “I can email this later”. If documents contain addresses, occupants or commercially confidential information, explain how the practice will handle them. A clear upload policy can be more reassuring than a large drag-and-drop area.
Design a safe optional upload flow
Accept only file formats the team can open safely, such as PDF, JPG and PNG, and publish a sensible size limit. Tell users whether they can submit without an attachment. Consider malware scanning, server-side file validation, private storage, retention controls and restricted staff access. Never place uploaded drawings in a publicly indexed media directory merely because the form plugin makes that easy.
A successful upload should display a filename and an accessible remove option. Error messages should explain whether a file is too large, the format is unsupported or the transfer failed, without erasing the rest of the form. Test with a mobile camera photo, a multipage PDF and a slow connection. For complex CAD packages, use a separate secure transfer process after initial contact.
Create useful conditional questions
Conditional logic can reduce effort when it follows the user’s choices. A residential extension may prompt “Is the property detached, semi-detached or terraced?” while a commercial fit-out may ask whether the space is currently occupied. A new-build enquiry may need a site location and approximate plot area. Keep branches short and provide a way back if the user changes project type.
Do not hide required fields without updating their validation state. A hidden question must not block submission. Test every branch with keyboard navigation and screen readers, not just a mouse. Avoid making users answer the same question twice when a later page already has the information. If the form becomes longer than a short initial brief, consider a two-stage process with a clear progress indicator.
Write a confirmation that sets expectations
The confirmation page should acknowledge receipt without pretending that the practice has accepted an appointment. State the usual response window, the contact channel and what the team will review. If the practice offers paid consultations, explain that pricing and booking will be confirmed separately. Send a short confirmation email containing the project reference and a summary, but do not echo sensitive drawings or private details into insecure messages.
Provide an alternative route for urgent accessibility needs or anyone unable to use the form. An acknowledgement is not the same as a signed appointment, planning instruction or fee agreement. Internally, flag enquiries that require a specialist rather than promising all projects an immediate quotation. Clear expectations prevent repeated “Did you receive my form?” calls.
Route the enquiry into a useful CRM record
Capture project category, broad location, lead source where lawfully collected, date, status, owner and next action. A compact pipeline might be: received; needs clarification; discovery booked; feasibility or proposal requested; proposal sent; appointed; not proceeding. Record the reason for a lost opportunity in a small controlled list rather than a long free-text blame note.
Assign an accountable person and a service-level target. A residential studio might route extension enquiries to a project architect and commercial enquiries to a director. Do not automatically send every lead into an aggressive email sequence. The team should be able to distinguish a genuine prospective client from a supplier pitch, student enquiry or job application without exposing personal details unnecessarily.
Separate enquiry handling from marketing consent
A person asking about a project expects a reply to that enquiry. That does not automatically mean they want newsletters or promotional emails. If the practice offers optional marketing updates, make the choice separate, clear and unchecked by default where consent is the chosen lawful basis. Document the purpose and lawful basis for each processing activity; do not use a generic consent checkbox as a substitute for appropriate privacy information.
Collect the minimum data necessary for the initial conversation, restrict access and set retention periods appropriate to the practice’s needs. A short privacy notice beside the form should link to fuller information about processing, recipients, retention and rights. Consider whether enquiry records contain third-party details, tenant information or plans that require additional care. Review the Information Commissioner’s Office guidance when setting policy.
Accessibility and mobile quality checks
Use visible labels rather than placeholder-only instructions. Associate error messages with the relevant fields, maintain a logical focus order and ensure buttons have meaningful names. Users should be able to complete the form with a keyboard, at high zoom and on a narrow screen. Avoid time limits that unexpectedly delete a carefully written project description.
WCAG 2.2 is a useful testing framework, not a magic compliance badge. Test the actual form and its conditional states, not merely the page template. Check contrast, target sizes, required-field instructions, confirmation messages and upload controls. When possible, involve people who use assistive technology. Fix failures in the real workflow rather than relying on an accessibility overlay.
A worked residential extension example
Imagine a practice that receives 60 monthly enquiries: 30 extensions, 15 renovations, 10 new builds and five unrelated requests. The old form asks for a full specification and mandatory budget, so some early-stage homeowners abandon it. A revised version asks for project type, postcode, desired outcome and contact details, then optionally asks about timing and sketches. The team follows up with a short discovery call before preparing any fee proposal.
This example is illustrative, not a measured conversion claim. If 48 of the 60 enquiries are genuine, 24 reach a discovery call, 12 receive a proposal and four become appointments, the enquiry-to-appointment rate is 4 ÷ 60 = 6.7%. The more useful diagnostic measures are genuine-enquiry share, call-booking rate, proposal-to-appointment rate and time to first human response. A higher submission count alone may conceal poorer fit.
A worked commercial refurbishment example
A commercial practice receives an enquiry about a phased office refurbishment. Instead of requesting a full tender pack, the form captures location, approximate floor area, whether the building remains occupied, target handover date and decision-maker role. It asks whether the client already has measured plans, but does not require them. The confirmation promises an initial scope review, not a fixed fee.
The practice routes this to its workplace team, checks whether statutory approvals and landlord consents may be relevant, and offers a scoped discovery meeting. The CRM records the next action and dependencies. If the buyer cannot yet define the construction budget, the team can propose a paid feasibility stage rather than silently discarding the opportunity. The key is to identify the next responsible professional decision.
Measure lead quality rather than just form volume
Track form starts, successful submissions, valid project enquiries, discovery bookings, proposals and appointments. Define each event consistently and avoid recording personal project descriptions as analytics parameters. Use aggregate reporting and appropriate privacy controls. A useful weekly dashboard separates traffic sources from the project mix and actual appointment outcomes.
For example, 200 form starts and 100 submissions yield a 50% start-to-submit rate. If 70 submissions are relevant and seven become appointments, the submission-to-appointment rate is 7%, while the relevant-enquiry-to-appointment rate is 10%. Compare both before and after a form change. Segment cautiously: small numbers can fluctuate substantially, and a single large commission can distort short-term revenue comparisons.
A 14-day implementation plan
Days 1–2: review enquiry records with the project team, identify the questions that genuinely affect routing and agree a small set of project types. Days 3–4: draft the short form, plain-language labels and confirmation copy. Days 5–6: implement conditional questions and an optional secure upload. Days 7–8: connect CRM ownership, acknowledgement messages and retention rules.
Days 9–10: test mobile, keyboard, error states, upload failures and privacy text. Days 11–12: run a small live pilot and inspect actual enquiry quality. Days 13–14: fix friction, document the final workflow and set a monthly review. Keep a record of baseline metrics; do not declare success after a handful of submissions. The implementation sequence is illustrative and should adapt to the practice’s technology and risk.
FAQ: should the form ask for planning permission status?
Yes, as an optional factual question with an “unsure” choice. It can help route a conversation, but a website form should not determine whether approval is required or promise a planning outcome. Relevant professional and local authority advice remains necessary.
FAQ: should an architect require a budget?
Usually not as a precise mandatory figure at the first contact. Ask for an indicative construction budget if known, define what it means and offer a “not established” answer. The team can discuss scope and cost expectations during qualification.
FAQ: are drawings necessary before the first call?
Not always. A sketch or photograph may help a preliminary discussion, but making uploads mandatory can exclude early-stage clients. For confidential or large files, arrange a secure exchange after initial contact.
FAQ: what is the best success metric?
A useful primary metric is qualified enquiries that progress to an appropriate discovery meeting or appointment, supported by response time and proposal outcomes. Submission rate is a diagnostic measure, not the final business result.
Authoritative references and further reading
The RIBA guide to working with an architect explains project discussions and professional selection. The Planning Portal’s pre-application advice guidance explains the value and limits of early planning discussions. Elmbridge Council’s pre-application checklist illustrates why location plans and drawings may matter later. For accessible forms use WCAG 2.2, and for personal data see the ICO. These sources inform the recommendations; local rules and professional responsibilities must be checked for the individual project.
