A homeowner wants to build a two-storey rear extension. Before contacting an architect, she wants to know whether she will need planning permission, how long it will take and what it will cost. She messages an architecture practice at 10pm. The practice's website has a portfolio but says nothing about planning. She moves on to one that explains its process clearly.
Planning questions are the first step in many architecture projects. Answering them carefully wins clients.
What homeowners ask
Homeowners usually ask whether their project needs planning permission, how long applications take, what drawings are needed, what building regulations approval involves, whether the architect submits the application, what happens if permission is refused and how much the architect charges for each stage.
Where the line sits
Whether a specific project needs permission depends on the property, its location, any restrictions and the design. An architect's website must not judge a specific project. It can explain the general process and capture the project details for the architect.
Example conversations
These scripts use information an architecture practice might publish. Your answers should come from your own pages.
Homeowner: Do I need planning permission for a rear extension? Assistant: That depends on your property and the design, so the architect needs to look at it. The process page explains how the practice assesses projects and handles planning applications. Could you share your address, what you'd like to build and your timeline, so the architect can advise?
Homeowner: How long does planning take? Assistant: The page explains the typical stages and timescales involved, and that the architect will give you a more specific timeline once they know your project.
Homeowner: Do you handle the application? Assistant: Yes, the services page explains that the practice prepares drawings and manages the application on your behalf.
Explaining the stages
A clear explanation of the stages, from feasibility to design to planning to building regulations, helps homeowners understand what they are paying for.
Fees by stage
Many clients want to know what each stage costs. Explaining how fees work, even as ranges, reduces uncertainty. Professional services face similar fee questions, as described in what clients ask before choosing a solicitor and how financial advisors use chatbots to answer client questions.
Proactive answers
Answering planning questions on the website before clients ask is a form of proactive support, described in proactive support answering questions before customers ask.
Neighbours and party walls
Homeowners often ask what they need to tell their neighbours and whether shared walls raise extra steps. An architect's website can explain in general terms that some projects involve notifying neighbours, and that the architect will explain what applies at consultation. It should not tell a homeowner what applies to their property. Capturing the question means the architect can come prepared.
Conservation areas and listed buildings
Properties in conservation areas or listed buildings often face extra considerations. Explaining that the practice has experience with these, if it does, reassures owners of older homes.
Building an FAQ
The AI FAQ generator can help you draft general answers about your process.
Data and trust
Clients sharing their address and plans want to know their details are handled responsibly. Security questions are covered in AI chatbot security questions to ask a vendor.
Answering at any hour
SpideyChat for architecture practices answers process questions from your own pages at any hour and captures project details for the architect. It does not judge whether a project needs permission.
A process page
Write a plain-language page explaining your stages, fees and how planning works in general. Try SpideyChat on your own site, or read about capture on the features page.