A construction website enquiry form should collect enough information to decide who should respond and what to ask next. For many contractors, that means a name, email, type of work, approximate location and short project description. Company, telephone and timeframe can be useful, but their importance depends on the work and the people making contact.
The first submission is usually the start of qualification, not a completed tender return. This guide helps construction companies and specialist contractors choose useful fields, distinguish required details from optional ones, and plan the process behind the form. Two example field sets below can be adapted to your business; neither is a universal construction form.
Ask what the receiving person needs to decide
“Name, Email, Message” can work when visitors already know what to send. It is less helpful if the inbox regularly receives “Can you quote?” with no location or indication of the service. A small amount of structure can remove a predictable first round of questions.
Start with recent enquiries. Which missing detail repeatedly prevents the team from deciding whether a project fits? Ask for that detail explicitly. Do not add fields simply because the information may become useful later in the estimating process.
Equally, an enormous tender form can ask too much before a visitor knows whether you are available or suitable. Detailed quantities, procurement terms and complete drawing sets may belong in a subsequent exchange. Keep the public form aligned with the first decision your team actually makes.
Make identity and contact fields proportionate
Name and email are a practical starting point. Ask for company where the business relationship matters. A specialist working exclusively for main contractors may reasonably require it; a contractor serving homeowners should not force someone to invent a company name.
Include telephone when a call is genuinely useful, with optional status unless it is necessary to handle the enquiry. Explain why if it is required. A visitor researching between meetings may prefer an email response and may not yet want an immediate call.
Where different buyer groups need different handling, offer a short choice such as main contractor, developer, property manager or homeowner. Include an appropriate fallback. You do not need this question if all answers receive the same response and the description already supplies the context.
Collect the project details that establish fit
Service and project type
Use service names that match the website. Distinguish commercial and residential work if that changes eligibility or routing. Avoid making visitors choose between internal department names. If “project type” and “service required” would produce the same answer, combine them.
Location
A town or postcode area may be enough to check coverage. Ask for a full site address only when it is needed at this stage. State coverage beside the form or on the linked service page so people can assess suitability before typing. Allow uncertainty where the site has not yet been finalised.
Timeframe and project description
A broad timeframe is often more useful than a compulsory exact start date. Options might distinguish early planning, work expected within a few months and an agreed tender deadline, with “Not yet confirmed” available.
Give the description a visible prompt: explain the work, the current stage and any important constraint. Leave enough room for a few paragraphs. If a character limit is necessary, show it in advance and avoid a small limit that cuts off the information you asked for.
Use budget questions only when they help
An approximate budget can help qualify a direct client’s defined refurbishment. It may be less useful for a subcontract tender where the buyer wants your price against a specification. A compulsory budget question can produce a guess rather than reliable qualification.
If ranges are useful, base them on the jobs your business considers and explain what the figure covers. Does it mean the whole project or your work package? Include “Not yet established” and consider making the question optional. Do not copy arbitrary ranges from another contractor’s form.
Where a minimum project size is a genuine commercial boundary, state it clearly in the service information. Asking visitors to reveal a budget is an indirect way to communicate a requirement you already know.
Example: a simple construction company website
For a contractor handling a limited set of services, start with the following field set. The required fields assume that location and work type determine whether the enquiry is suitable.
- Name (required): who should receive the response.
- Email (required): a dependable reply route.
- Company (optional): useful for commercial enquiries without excluding homeowners.
- Telephone (optional): for visitors who would welcome a call.
- Type of work (required): a short service list with an “Unsure” option.
- Project location (required): town or postcode area, rather than a full address.
- Approximate timeframe (optional): including an unconfirmed option.
- Project description (required): a few sentences about the requirement and stage.
This example leaves budget and uploads for a follow-up. If the service is already clear from the originating page, preselect it visibly and allow the visitor to change it. Do not make them repeat information the website can carry forward accurately.
Example: a more complex specialist contractor
A specialist receiving enquiries from main contractors, consultants and developers may need more context. Build on the simple set where each addition affects routing or the initial response.
- Name, company and email (required): appropriate for this example’s exclusively business audience.
- Telephone (optional): with a preferred contact method if the team uses it.
- Your role (optional): main contractor, developer, consultant or another relevant role.
- Specialist service or package (required): choices matching the actual offer.
- Project type and location (required): enough to assess technical and geographical fit.
- Project stage (required): early advice, tender, appointed or unsure.
- Expected timing / tender deadline (optional): with an explanation of which date to provide.
- Scope summary (required): what you are being asked to design, supply or install.
- Package budget (optional): only if the estimating team uses it.
- Documents (optional): only through an agreed file-handling process.
Conditional questions can keep this manageable: show a tender deadline when someone selects tender stage, for example. Ensure hidden fields do not remain compulsory and that the form still makes sense to keyboard and screen-reader users. Additional behaviour needs testing as part of the website scope.
Decide whether uploads belong in the first step
Drawings, photographs and briefs can clarify a requirement, but upload functionality changes both development and ongoing handling. Agree accepted formats, size limits, private storage, authorised access, retention and how potentially unsafe files will be checked. Explain limits before submission.
Ask the website supplier to validate files on the receiving system, rather than relying only on restrictions shown in the browser. The OWASP file-upload guidance describes why file types, access and storage need several safeguards. This is a scoped feature, not simply an extra visual field.
If drawings are confidential or large, an initial enquiry followed by your established document-sharing process may be more appropriate. Our construction website cost guide explains why these requirements should be identified before comparing proposals.
Keep privacy information clear and collection limited
Collect personal information needed for the enquiry and provide a clear link to the relevant privacy information beside the form. Explain who uses the information, why and how long it is kept, with the remaining details appropriate to your process. The ICO’s guidance on privacy information and data minimisation provides the starting point. This is practical planning guidance, not legal advice.
Agree the appropriate lawful basis and handling arrangements for your business. Keep optional marketing choices separate from the project enquiry. Do not collect extra personal details merely because a form builder offers the fields.
Test the form on a phone, including failures
Use a single-column flow, persistent labels and visible optional or required wording. Give text fields enough width, use suitable email and telephone input types, and avoid oversized dropdowns containing every possible construction activity. Test with enlarged text as well as a narrow screen.
Errors should identify the field and explain how to correct it while preserving the other answers. Check slow connections, failed uploads and repeat taps on Submit. Spam protection should work without making the legitimate visitor solve unnecessary obstacles; review real spam and delivery problems before adding more friction.
Display success only after the submission has been accepted. State what happens next and offer another contact route if sending fails. Promise a response time only where the receiving team can meet it.
Measure usefulness after the enquiry reaches the business
Assign an owner, a monitored destination and a fallback for absence. If services route to different people, test each route and preserve a central record so messages do not disappear between teams. Send trial enquiries before launch and confirm receipt through the real process.
Where analytics is appropriately configured, measure accepted submissions rather than button clicks, respecting applicable consent choices. Keep names, email addresses, descriptions and uploaded documents out of analytics events. Compare the count with received enquiries; browser tracking is not the inbox.
Review missing information, unsuitable requests and time spent on clarification. Compare your own periods with similar traffic and note other changes; there is no universal construction conversion benchmark used here. The wider website enquiry guide helps diagnose problems before the form, while the contractor website checklist covers the surrounding content.
Our construction website service starts with that real journey. The useful form is the one that helps your team respond properly to a suitable project without demanding the whole job brief before the first conversation.