In landscaping, the value of an enquiry is decided long before the site visit — in the moment someone fills in a form on your website. If all that arrives is „name, email, message“, the real work only starts afterwards: call back, ask questions, drive out there and find that someone wants a hedge trimmed while your crews are booked with paving work into late autumn. An enquiry form that qualifies moves that work to the right place: to the beginning, into a few taps, without anyone having to pick up the phone. This article shows which fields a landscaping form actually needs, which fields cost you enquiries, why the budget question deters people less often than expected, and how consent, purpose limitation and deletion periods are handled properly without the form looking like an official document.
Key takeaways
- Six answers carry a landscaping enquiry: trade, approximate area, location, time frame, budget range and optional photos — first contact needs no more, and anything less pushes you back to the phone.
- Keep required fields down to three: one contact channel, the trade and the location. Every additional asterisk costs enquiries without noticeably improving qualification (project experience).
- A budget range with predefined bands deters people less often than an empty input box, because it offers orientation instead of demanding a figure that private clients cannot realistically estimate.
- Processing an enquiry rests on Art. 6(1)(b) GDPR and needs no consent; consent is only required for uses beyond that enquiry, such as adding the person to a newsletter list.
- Without a defined deletion period the form inbox grows into an uncontrolled data store: put in writing when enquiries without an order get deleted, and keep them apart from quotes that carry their own retention duties.
What a form has to do before you call back
An enquiry form is not a letterbox, it is the first work step in your quoting process. Every enquiry passes through the same questions in your business anyway: which trade is this about? Roughly how large is the area? Where is the property? When should the work happen? And does the price expectation match what this service costs? Either the enquirer answers those questions in two minutes on screen — or you answer them in a phone call squeezed between two sites, with a scrap of paper on the dashboard and a crew standing by.
The difference becomes visible in spring. Most enquiries arrive between March and May, exactly when the office is at its thinnest because everyone is out on site. A form that supplies the basic answers decouples the flow of enquiries from your availability: you review twenty enquiries in a quarter of an hour in the evening, sort them into three piles and only call the ones where a call actually changes something. How that yearly rhythm carries across the whole site is covered in the article on seasonal planning for your website.
The most common worry is that more fields mean fewer enquiries. As a tendency that is true — but the statement is incomplete. What drops is not the number of enquiries evenly across the board, but above all the number that would never have fitted anyway: the enquiry from eighty kilometres away, the job for twelve square metres of lawn edging, the price expectation that is out by a factor of three. Whether that effect appears in your business depends on your catchment area and your range of services; it cannot be promised, but it can be checked.
Two minutes as a guide
The six answers that carry an enquiry
Practice narrows it down to six answers that separate a landscaping enquiry from a mere hello. They are not arbitrary: they mirror the criteria you use in the office anyway. Can we do this? Do we drive there? Will we have capacity then? And is the effort of a quote worth it? A form that supports those four decisions is a dispatching tool, not just a courtesy box at the bottom of the home page.
Order matters. Arrange the answers so that the easiest question comes first and the most delicate one comes last. Someone who has already picked a trade and typed a postcode abandons the budget question far less often than someone who meets it as the very first field. That small rule costs nothing and changes behaviour noticeably.
Trade
A selection rather than free text: private garden, paving, tree care, ponds, planting maintenance, fencing, winter service. This single answer decides who in the business picks the enquiry up.
Approximate area
Rough bands such as „up to 50 square metres“ or „200 to 500 square metres“ are enough. You do not need centimetres, you need an order of magnitude for material, machines and duration.
Location
Postcode and place name are sufficient. Street and house number belong to the site visit and only increase the amount of personal data in the form without adding value.
Time frame
A preferred month or part of the season instead of a calendar date. Someone ticking „as soon as possible“ lands somewhere very different in your schedule than someone ticking „autumn, no rush“.
Budget range
Predefined bands to tap, optional, with a „not sure yet“ option. The band positions the enquiry without forcing anyone to invent a figure.
Photos
Two or three pictures of the current state, optional and with no demands on image quality. They save follow-up questions about access, slope, planting and substrate.
Trade first: the switch that sorts everything else
The trade field is the most important field in the whole form, because it makes every following question meaningful. An area means something entirely different for paving than for planting maintenance, a time frame in tree work sits differently for horticultural reasons than in terrace construction, and a budget range can only be judged once it is clear what is being discussed. So the trade belongs at the top — as a selection with clear labels, not as an open text box.
The second advantage of a selection: it controls what you are offered in the first place. If you no longer offer winter service, take it off the list and write fewer declines. If paving is your core business, put it first and point to the matching service page — for example the page for paving work, where the reader has already learned what to expect. The form then becomes a continuation of the page it sits on rather than an interchangeable afterthought.
One technique has proved itself: preselecting the trade based on the page the visitor came from. If someone opens the form from the tree care page, „tree care“ is already ticked. That saves a tap, prevents wrong entries and keeps the enquiry aligned with what the visitor has just been reading. The selection naturally stays editable.
- Name the trades exactly as you name them internally — no marketing terms, no catch-all categories
- Only list trades you actually carry out; remove services you no longer offer
- No more than eight options, otherwise the list becomes unwieldy on a phone
- Add an „something else“ option with a short free text box so nothing gets lost
- Carry the preselection over from the originating page, but keep it editable
- Place the selection visibly at the top instead of hiding it behind a collapsed section
Area, location and time frame: the three scheduling filters
These three answers settle whether an enquiry fits your operating rhythm. They are comparatively harmless to answer, yet they deliver most of the sorting effect. The key is asking for bands rather than exact values. A private client does not know whether the terrace measures 34 or 41 square metres — they know it is „about the size of a room“. Force them into an exact number and you either get an invented figure or no enquiry at all.
For the location, postcode and place name are enough. That lets you check travel distance and catchment area without storing a full address you do not need for first contact. For businesses with a clearly defined radius, a note right at the field helps, such as „we work within roughly 40 kilometres of our yard“. Anyone outside that decides for themselves — and you save yourself the decline. Positioning the whole site regionally is the subject of the article on local visibility for landscapers.
The time frame is the most underrated filter. In landscaping it is not only whether a job fits, but when it fits. Someone ticking „autumn or next spring“ is not a worse client than someone choosing „as soon as possible“ — they simply belong in a different queue. Without that field both land in the same pile, and in May you chase an enquiry that could comfortably have waited until October.
| Field | Weak implementation | Solid implementation |
|---|---|---|
| Area | Required field for an exact square metre figure | Choice of four or five size bands, optional |
| Location | Street, house number, full address as required | Postcode and place, address only at the visit |
| Time frame | Calendar picker down to the exact day | Month or part of the season to tap |
| Trade | Open text box labelled „your request“ | Selection list with the services you offer |
| Budget | Empty number field with a required asterisk | Bands to tap, optional, with „not sure yet“ |
| Message | Required field with a minimum length | Optional box for anything unusual |
Why the budget field does not deter people
Hardly any field is as contested as the budget question. The objection is always the same: „people will drop out because they feel interrogated“. That worry is understandable but aimed at the wrong implementation. What deters is an empty required field asking for a figure the person does not know. A selection of predefined bands works differently: it does not interrogate, it positions — and it gives the enquirer a first sense of the order of magnitude their project sits in.
That is where the real benefit lies. Many private clients have no idea what a natural stone terrace, a rainwater cistern or a complete garden installation costs. If the lowest band starts at a realistic amount, that corrects the expectation before anyone books an appointment. The effect grows stronger when the service pages state price frames, as described in the article on pricing. Anyone who still enquires has already accepted the order of magnitude.
Two details decide whether this field succeeds. First, it has to be optional — a required asterisk here turns a positioning aid into an interrogation. Second, it needs a „not sure yet, please advise me“ option. That choice is not an evasion, it is valuable information: it flags people looking for advice, and in landscaping those are frequently the better clients, because they rely on your expertise rather than on a price comparison.
The budget range is an offer, not a credit check
A form that asks nothing shifts every question into a phone call — and every phone call into the time when the crew is waiting.
Photos: the field that saves the most driving time
No other optional field delivers as much information per tap as the photo upload. Two pictures of the current state show you in seconds what ten lines of description cannot: access to the plot, the slope, the planting, the existing surface, whether a digger can even get in and whether there is a wall in the background that has to come down first. In many cases this replaces the first site inspection and shortens the path from inbox to a reliable quote considerably.
For the field to work it has to be deliberately undemanding. Phone snapshots are fine, crooked and badly lit. Say so explicitly: „two quick snapshots are plenty, this is not about beautiful pictures“. Anyone who instead sets requirements for resolution or file format will receive no pictures at all. Technically the form should accept common phone formats, shrink large files on the server and give clear feedback while the upload is running — otherwise the process fails on a mobile connection without anyone understanding why.
Two points belong in the plan. First, phone photos often carry location data in their metadata; if you do not need it, strip it on upload. Second, uploaded images are personal data as soon as they show a property — they fall under the same deletion period as the rest of the enquiry. How to turn such projects into your own reference pictures later is covered in the article on photos for your website; for that you need separate permission from the owners in every case.
Uploads that do not break off
Fields that do harm
Just as important as the right fields are the fields you leave out. Many forms have grown over years: at some point somebody wanted the salutation, then came the question about how people heard of you, later a field for the preferred callback time. Each field made sense on its own; together they add up to a questionnaire that nobody completes on a phone.
The test question is the same for every field: does this answer change what you do next? If you would act identically regardless of the answer, the field does not belong in the form. The salutation changes nothing about processing. The company name changes nothing as long as you serve both private and commercial clients. „How did you hear about us?“ is interesting, but it belongs at the end and never in the required section.
- Salutation as a required field — it changes nothing about processing and only adds a hurdle
- Full address with street and house number at first contact instead of at the site visit
- Phone number as required, although many enquirers deliberately want to start in writing
- Puzzle captchas with distorted characters that cause drop-offs on phones
- A message box with a minimum length, which produces filler text instead of information
- A calendar with day-exact appointment picking, although the date gets agreed anyway
- Asking for the plot size in addition to the area of the actual project
- Several contact channels required at once, such as phone plus email plus callback window
Keep required fields to a minimum
The split between required and optional is the real lever. A form can have eight or nine fields without feeling off-putting, as long as only three of them are required: one contact channel, the trade and the location. Everything else may stay empty. That sounds paradoxical but it works, because optional fields get filled in more often than expected — people answer questions willingly when they can see the purpose and are not being forced.
Behind it sits a simple observation: forced answers are often wrong. Someone required to enter an exact square metre figure will guess. Someone required to give a phone number although they wanted to start in writing will occasionally mistype a digit. Wrong answers are worse than missing ones, because you trust them and calculate on that basis. An empty field is visible immediately; a guessed figure only shows up on site.
Part of keeping things lean is the feedback when something goes wrong. If a required answer is missing, the form should mark it directly at the field, in plain language, without discarding anything already entered. A form that comes back empty after submission with the message „please complete all fields“ loses the enquiry for good. How a well-considered enquiry form for landscaping businesses is structured in detail is shown on the corresponding service page.
| Answer | Status | Reason |
|---|---|---|
| Name | Required | Without a name no sensible reply is possible |
| Email or phone | Required, at least one | One reply channel is enough, the choice stays with the enquirer |
| Trade | Required | Controls responsibility and every following question |
| Place and postcode | Required | Decides catchment area and travel distance |
| Area, time frame | Optional | Improves classification without blocking submission |
| Budget range, photos | Optional | Highest information value, highest drop-off risk if forced |
Data protection: consent, purpose limitation, deletion
Every enquiry form processes personal data, which means the General Data Protection Regulation applies. The good news first: for handling the enquiry itself you generally do not need consent. Whoever sends you an enquiry wants a quote — that is a pre-contractual step under Art. 6(1)(b) (GDPR). An additional consent checkbox for the core purpose is therefore not only superfluous, it can mislead, because it suggests a voluntariness that is not required at this point.
You do need consent for everything beyond the enquiry: adding someone to a newsletter, later advertising, passing details to a partner business. Such purposes belong in a separate, non-preticked option with clear wording. And they must not be a condition for submitting the form at all. Under Art. 13 (GDPR) you also have to inform people at the point of collection who processes the data, for what purpose, on what basis and for how long — a clearly visible reference to the privacy notice right by the submit button covers that.
The third point is the one most often missing in practice: the deletion period. Enquiries that never became orders pile up in the inbox for years, complete with photos of other people's properties. Put in writing when that data is deleted — for instance six months after the decline (project experience) — and stick to it. Quotes and contracts carry their own commercial and tax retention duties and therefore belong in a separate place, not in the same mailbox.
- Legal basis for processing: pre-contractual step under Art. 6(1)(b) (GDPR), no consent required
- A separate, non-preticked consent solely for newsletters, advertising or passing data on
- A plain reference to the privacy notice directly at the submit button
- Record purpose limitation in writing: enquiry data does not migrate into a mailing list
- Define a deletion period for enquiries without an order and clear the inbox regularly
- Store quotes and contracts separately, because different retention duties apply there
- Implement spam protection without puzzles and without passing data to third parties
- Transmit the form only over an encrypted connection and keep the internal recipient list small
When health information enters the picture
From inbox to appointment: the process behind the form
A good form achieves little if nobody is responsible afterwards. Most lost enquiries are not lost at the form, they are lost in the days that follow: the message lands in a shared mailbox that only the office assistant opens, and she is away for two days. So every form needs a defined process with a named owner and a deadline within which someone responds.
Arrival and instant acknowledgement
The enquirer immediately receives an automatic acknowledgement summarising their own answers, a realistic response window and a phone number for urgent cases. That acknowledgement prevents duplicate enquiries and the follow-up call the next morning.
Daily review in the office
Once a day all enquiries are reviewed and sorted into three piles: book a visit, follow-up needed, decline. Because trade, location, time frame and budget range are already there, the review takes less than a minute per enquiry (project experience).
Follow-up or decline
If a single answer is missing, a short call is enough instead of a drive. If the enquiry does not fit at all, a friendly decline goes out with a pointer to the kind of business that can help. That costs two minutes and preserves your reputation locally.
Site visit and quote
For the remaining enquiries an appointment is arranged, ideally bundled by district to save driving time. The form answers and the photos go to whoever drives out, as preparation.
Follow-up and deletion
After the quote comes a fixed follow-up date. If no order results, the record moves into the deletion routine with the period defined earlier. That keeps the data store manageable and purpose limitation demonstrable.
Refine rather than rebuild
An enquiry form is never finished on the first attempt. After one season you know which fields get filled in reliably, which option nobody ever taps and where most enquiries break off. Those observations need no elaborate analysis: it is enough to read through a quarter's enquiries and count how often a field stayed empty and how often you had to phone despite the form.
Those two counts produce the adjustments almost by themselves. A field that stays empty again and again, and whose absence does not bother you, can go. A follow-up question you have to ask in every second case belongs in the form as a field. A budget band nobody ever falls into is cut wrongly. Form maintenance is business maintenance — and winter is the right moment for it, when there is time for organisation anyway.
One boundary matters here: audience measurement must not turn into tracking the behaviour of individual people. To judge whether a field works, anonymous totals are enough. And anyone who already manages enquiry data by purpose and deletion period has everything needed for that review at hand.