A contact form can ask too much too soon. An owner may know the site address and intended use, but have no floor area, procurement route or construction budget yet. If the form demands a finished brief before anyone will speak to them, a worthwhile inquiry may never arrive. Let visitors start with what they know while collecting enough context to direct the request.
The page also needs to show visitors whether they have reached the right team and what will happen next. More submissions are not automatically better: vague requests that staff cannot answer can take time without leading to useful project conversations. The goal is less uncertainty on both sides.
Make the purpose and next step clear
Visitors should be able to tell where to send a new commission, a question about an existing project, a press request or a construction-related concern. Give different inquiries separate routes where the volume warrants it. A practice that manages occupied buildings, for instance, needs to distinguish a design inquiry from an urgent operational issue. Its general project form is not an emergency reporting channel.
State the service area and the work the team can assess, without implying that every project will be accepted. “Residential alterations and new buildings within the region” tells a visitor more than “All your design needs.” If public-sector work must enter through a formal tender process, say so; a contact form does not replace it.
Beside the form or contact details, explain what follows submission. A coordinator might review the request, identify the relevant discipline and reply to discuss scope or ask for missing information. Give a response timeframe only if the team can normally meet it, and clarify whether it excludes weekends or holidays.
Give visitors a route that fits their task
- New project: a short form asking for location, intended use and the assistance sought.
- Existing commission: a named project contact or agreed communication channel, where available.
- General or media inquiry: an email address or separate route without construction-specific fields.
- Urgent building issue: the appropriate property manager or emergency contact, if the organization is responsible for providing one.
Keep the choices understandable to someone outside the practice. “Discuss a new building project” is clearer than an unexplained department name. If the page covers several offices, say which geographical areas each serves rather than listing addresses without context.
Ask for enough information, not a finished brief
Early inquiries differ. A developer may have a defined site and a feasibility deadline; a homeowner may simply be asking whether an extension is plausible. Require what the team needs to reply safely and usefully, then leave the rest optional. A name, reply method, broad project location, inquiry type and open description are often enough for an initial review. The right fields depend on the practice and its services.
Use labels a non-specialist can answer. “Project location” might call for a city or postal area, not a full address. “What would you like help with?” leaves room for uncertainty; “Specify the planning application type” assumes knowledge the visitor may not have. If budget is genuinely needed to assess fit, offer ranges or “not established,” and explain why you ask. A missing budget does not make an inquiry unserious.
Optional questions can provide useful context: Does the visitor own or control the site? Is there an existing building? When is a decision expected? Are surveys or planning comments available? The answers can help staff prepare for a call, but they do not replace checks on title, regulations, site constraints or feasibility.
Use conditional questions sparingly
If someone selects “existing building,” a follow-up such as “Is the building occupied?” may help the team plan the first discussion and consider access. Too many branching questions, though, make an inquiry feel like an application. Keep a question only if its answer changes who responds or what they need to say; otherwise, ask later.
Leave room for work that does not fit a neat category. Mixed-use redevelopment, phased school refurbishment and medical fit-outs may defy a single dropdown choice. Offer “Other” with a text field rather than forcing an inaccurate answer to satisfy form validation.
Make contact options usable and trustworthy
A caller may need to discuss a time-sensitive decision. Someone else may need a written record or be unable to call during working hours. Offer only channels the organization monitors, such as a form, published email address or telephone number. State limited phone hours, and do not promise instant chat or rapid callbacks unless those services are consistently staffed.
Make the business identifiable through its practice name, relevant office location and consistent contact details. For teams working across regions, distinguish a registered address from a meeting office. A map should not suggest walk-in access if meetings are by appointment only.
Evidence near the contact route should address a practical question. A brief account of relevant building types or a link to verified project work may help a visitor judge fit; a sweeping testimonial without context is less helpful. Label project images accurately, too. A rendering of an unbuilt scheme should not look like a delivered facility. For choosing accurate visual material across a site, the post on visuals for architecture and property websites covers the broader decision.
Reduce friction on the form itself
Small interface faults can prevent a legitimate inquiry. Keep labels visible outside fields, mark required entries and explain formatting only when it matters—for example, whether a phone number needs a country code. Use an email input for email addresses, but avoid restrictive patterns that reject valid ones.
Put errors beside the affected field, say what needs fixing and preserve what the visitor has already entered. “Please enter a reply email address” is useful; “Invalid input” is not. The button should describe the action—“Send project inquiry,” for example—rather than promise a consultation that has yet to be arranged.
Try the form on a phone, not just a desktop. Check that the keyboard does not cover the active field, dropdowns are easy to use, the submit button is not hidden by a persistent banner and the confirmation is visible. Complete a test submission using only details a prospective client would likely know.
Design for different access needs
Keyboard operation, visible focus states, readable contrast and labels associated with their fields matter for visitors using assistive technology. Instructions cannot depend on color alone. If spam control requires verification, test it with a keyboard and screen reader and provide an accessible alternative if needed. Offering a phone number does not fix a form that someone cannot operate.
Show permitted file types and size limits before an attachment is uploaded, and confirm receipt of the file. Do not make drawings compulsory at first contact: a prospective client may not have them, and plans of an existing building may contain information that should not travel through an ordinary web form.
Be precise about privacy and sensitive information
Names, site details, business plans and information about an occupied property may all arrive through a contact page. Collect only what is needed now, explain how submissions will be used and point visitors to the applicable privacy information. Do not quietly turn a project inquiry into a newsletter subscription. Any marketing consent should be separate from sending the request.
Ask visitors not to place sensitive documents or personal information in free text. Medical, educational and public-sector work can involve confidential operational details; a broad description is usually enough for an initial inquiry. If supporting records are needed later, arrange a secure exchange. Handling requirements depend on jurisdiction, contract terms and the organization’s data policies.
Spam controls should save staff time without excluding clients. First check for server-side validation and suitable filtering, then watch for legitimate requests being blocked before imposing a demanding verification step. If submissions are stored in the website system as well as emailed, decide who may access them and how long they remain there.
Make delivery and follow-up dependable
A good form is little use if messages land in an unmonitored mailbox. Give incoming inquiries an owner and arrange cover for absences. Staff need a straightforward way to sort new commissions, existing projects, supplier messages, unrelated requests and urgent issues that need redirection. On a shared website, office routing should rely on something visitors can reasonably supply, such as project location, rather than an internal department name they must guess.
After submission, confirm on the page that the request was sent and state the realistic next step. An automated acknowledgement must not suggest that a person has assessed the project. Nor should it repeat the whole inquiry by email if the message may contain confidential site or operational details. Tell visitors how to reach the team if no acknowledgement arrives or they need another route.
Test the full path: send a sample inquiry, confirm that the right recipient gets the required fields, check attachments and read the visitor-facing confirmation. Repeat the test when form plugins, email settings or office routing rules change. An on-screen success message alone does not prove anyone received the request.
Measure whether the page improves conversations
Submission totals are a starting point, not a verdict. Look at how many inquiries receive a substantive reply, fit the practice’s scope and lead to an appropriate next discussion. Note common routing mistakes and missing details without making first contact a qualification hurdle. If callers keep asking whether the team serves a particular region, clarify the coverage on the page.
Review changes over a period that allows for shifts in traffic and project cycles. Removing three required fields could increase both genuine submissions and spam; a project-type choice might improve routing without changing volume. Check form errors, delivery failures, response delays and the share of requests staff must redirect.
Before changing a field, ask the staff who reply to inquiries what they use in that first response. If they never need the required “estimated floor area” but routinely need the project’s city, swap the fields. Then test a hypothetical occupied-building refurbishment: does the right team receive its location, broad scope and a safe way to reply, without demanding a completed design brief?