The crew knows its job, the site is running, and still the phone rings three times a day. When are you coming back? How much longer? Does the sand have to stay there? These calls rarely express mistrust. They happen because something is going on at the property that the customer cannot interpret, and because nobody told them beforehand what normal looks like. Every one of those calls costs site management time it does not have. This article sets out the questions that come up again and again during a build, how to answer them once in writing, and how your website can take over part of that job without anyone picking up the phone.
Key takeaways
- During a build, customers essentially ask four questions: when are you coming, how long will it take, what happens when it rains and where does the material go. Answering these in writing beforehand removes the reason for most calls.
- A one-page briefing note sent before work starts, covering contact person, duration in working days, working hours, storage area and a weather rule, is the cheapest measure available: written once, adapted per project in minutes.
- State durations in working days with a stated buffer rather than a calendar date for completion. Frost, prolonged rain and delivery times move schedules, and a date once mentioned stays in the customer's head.
- Delay turns into conflict when it goes unannounced. Report a postponement on the day you decide it, with the reason and a new date, instead of waiting until the customer stands in front of an empty site and calls.
- Changes agreed verbally are the most common point of dispute in the final invoice. Confirm every additional item in writing with scope and price before it is carried out, even if it is only a short message and a reply.
The four questions that keep coming up
Anyone who collects callbacks from live sites over the years sees the same pattern: it is almost never technical. Customers do not ask about compaction of the sub-base or the grading of the bedding layer. They ask about presence, duration, weather and space. These four topics account for the large majority of all calls during execution (project experience). Everything else is a one-off that could not have been anticipated anyway.
The reason is simple. A private garden is rebuilt once or twice in a lifetime. The customer has no benchmark, no experience and no idea that two days can pass between excavation and paving with nobody on site and nothing going wrong. What the crew sees as a normal sequence looks like a standstill from the kitchen window.
That points to the real lever. You do not need to communicate more during the build, you need to communicate earlier. Answering the four questions before the first site day shifts the communication out of the hectic phase into a calm one. Half an hour in the office replaces a series of calls that would otherwise be taken on site or in the van in the evening.
- When are you coming? Not only the start date, but also which days, from what time, and who gets in touch if something moves.
- How long will it take? This means the time until the surface is usable, not until the last snagging item. The two often differ by days.
- What happens when it rains? Which works pause in which conditions, and whether the end date moves as a result.
- Where is the material stored? The area, the duration, the access route, and whether the lawn or driveway will suffer.
- An extra question in established gardens: who is liable for existing plants, service lines and surfaces inside the working area.
Why the telephone is the most expensive channel
A call during working hours interrupts two people: not the customer, but site management and in effect the crew, because questions are passed on. It leaves no record that can be read back later, and it rarely arrives at a convenient moment. What remains is information that is documented nowhere and has to be given again at the next callback.
The structure of the sector adds to this. Landscape gardening is dominated by small businesses (BGL, the German landscaping and sports ground construction association), and in many firms costing, site management and customer contact sit with the same person. Full order books alongside tight staffing are widespread across the trades (ZDH). Under those conditions the attention of site management is the scarcest resource in the business, not machine hours.
The phone still matters, but as the exception rather than the default channel. The task is to reduce the share of pure information calls and to bundle the rest. Written channels have a side effect that is often underrated: they create a trail. If it later becomes unclear when which date was given, it can simply be read back.
| Channel | Strength | Limit |
|---|---|---|
| Call from site management | Immediate, personal, settles queries directly | Interrupts the work, leaves no record |
| Short message with a photo | Fast, gets read, shows the current state | Private devices, nothing filed in the business |
| Email to the customer | Readable later, filed, several recipients | Not opened every day by everyone |
| Briefing note before the build | Answers the standard questions in advance | Only as good as how current it is |
| Notice at the site fence | Also reaches neighbours and passers-by | No return channel, very limited space |
| Information page on the website | Available around the clock, same for all projects | Explains the general case, not this project |
The briefing note: write it once, use it for years
The briefing note is a one-page document sent to the customer seven to ten days before work starts, by email or on paper with the date confirmation. It contains nothing contractual, only the practical sequence. The contract and the quotation govern scope and price; the briefing note governs expectations. Mixing the two makes the document long and legally delicate.
Eight points belong in it: contact person with a direct number and hours of availability, duration in working days, usual working hours, the phases of the project in keywords, storage area and access, the weather rule, how changes are handled, and a note on when you will get in touch unprompted. Cover those eight and most questions are answered before they arise.
The effort occurs once. After that only the entries in square brackets change per project, which takes a few minutes. What matters is that one person in the business owns the sending and that it is tied to a fixed point in the workflow, such as the date confirmation. Otherwise the note stays a good idea and is the first thing dropped in the busy season.
Dear [name],
we expect to start with you in week [no.] and have allowed
[number] working days for the works. So that you know what to
expect, here is the sequence in brief.
Contact
[Name], [phone number], available on working days 7 to 8 am
and 4 to 5 pm. Outside those hours, email is best.
Working hours
Monday to Friday from [time] to [time]. On individual days the
crew will not be on site because material has to cure or a
delivery is awaited. That is part of the sequence.
Phases
1. Excavation and removal of soil
2. Building and compacting the sub-base
3. [Main works]
4. Edging, cleaning, handover
Material and storage
We store material on [area] and use [access route].
The area will be occupied from [date] for around [duration].
Paths and lawn are protected with [measure].
Weather
In prolonged rain or frost, [works] pause. We contact you the
same day if this moves the overall schedule.
Changes
We are glad to take on additional wishes during the build. We
will send you a short note with scope and price first and only
start once you have confirmed it.
We will get in touch [rhythm] with a brief update. If anything
is unclear in between, please call.
Kind regards
[Company]Weather and delay: explain the rule before it rains
Weather is the most frequent cause of postponement in landscaping and at the same time the worst explained. For the business it goes without saying that you do not lay paving in frost and do not move soil in prolonged rain, because the surface gets churned up and the compaction will not hold. To the customer it simply looks as if the crew is somewhere else.
The remedy is a weather rule in the briefing note that names which works pause in which conditions and who gets in touch when that happens. Two or three sentences are enough. What matters is that the rule is known before the first wet day. After that, the same explanation sounds like an excuse even though it is technically unchanged.
Equally important is how dates are stated. A calendar date for completion sticks in the mind even when the word expected preceded it. More robust is a figure in working days with a named buffer and an explicit statement of what the buffer depends on. If you already explain your time frames publicly through seasonal planning, you can keep the individual project note shorter.
Report delay on the day you decide it
Material, machines and space on the property
The second big reason for calls is space. A pile of aggregate on the driveway, a skip in front of the garage, pallets of slabs in the front garden: all of it is technically necessary and all of it surprises the customer when it arrives unannounced. In works such as terraces, sand-set slabs or cisterns, of the kind carried out by Viktor Waldbauer Garten- und Landschaftsbau in Nordstemmen, material arrives in quantities that visibly change a private plot.
So settle four points before work starts: which area will be occupied, from when, for how long, and how paths, lawn and kerbs will be protected. Access belongs with it: whether a lorry with a trailer fits into the street, whether it has to manoeuvre, whether a neighbouring plot will be used briefly. Agreeing that in advance avoids the call on delivery day when the driver is already in the entrance.
A photo helps more than any description. A sketch or an image of the planned storage area, attached to the quotation, prevents misunderstandings about size and position. The same shots are useful later for documentation. How to take usable site photographs with a phone is a topic of its own, and it pays off for the website and for the project file alike.
Name the area
Which part of the plot will be occupied and roughly how large it is. A hand sketch or a photo with a marked outline is entirely sufficient.
State the duration
From when material will be there and until when. Saying one week and occupying three costs trust that will be missing elsewhere.
Settle access
Does the lorry fit into the street, is manoeuvring needed, is a parking restriction required. Such points belong before delivery, not on the day.
Protect surfaces
Trackway boards, fleece or boards over lawn and paving. Naming the measure shows that the risk of damage was thought through.
Record the condition
Photos of driveway, lawn and facade before starting, with a date. That protects both sides if a scratch is discussed later.
Think of neighbours
A brief note to the neighbourhood removes the reason for complaints, particularly around deliveries, noise and blocked parking spaces.
Who gets in touch and when: ownership and rhythm
The most common cause of calls is not missing information but a missing promise about when information will arrive. Someone who knows a short update lands on Friday afternoon waits until Friday. Someone who knows nothing asks on Wednesday. A fixed rhythm is therefore more effective than being reachable at all hours.
Ownership matters just as much. If the customer does not know whom to address, they address whoever they can see: the machine operator, the apprentice, anyone in the crew. Those conversations produce commitments nobody costed. A named contact with stated hours relieves the crew and protects it from having to talk about prices or dates.
The rhythm has to match the size of the project. With three days on site, two messages are enough, one at the start and one at the end. With three weeks, a weekly summary is appropriate; on multi-month projects, a fixed weekday. Too much communication tires people just as much as too little, and a daily report with no new content stops being read very quickly.
Name a contact
One person per project, with name, number and two windows in the day when they are reliably reachable. That detail goes into the briefing note and the signature.
Promise a rhythm
Decide when you will get in touch unprompted: daily on short sites, weekly on longer ones. Name the weekday, not just the frequency.
Keep the format small
Three lines and two photos are enough: what was done, what comes next, whether the schedule holds. Anything beyond that will not be written consistently.
Relieve the crew
Instruct the team to pass questions about price and dates politely to site management. One sentence does it, and nobody has to feel awkward.
Review after handover
Note which questions still came up. Anything that appears twice belongs in the briefing note next time. The template then improves on its own.
The website as a quiet channel during the build
Much of what customers ask during a build is the same on every project. Exactly that part belongs on the website rather than in every individual letter. A page titled how a project runs with us can explain phases, typical durations, weather rules, handling of storage areas and handover in a few paragraphs. The briefing note links to it and stays short as a result.
That page works twice. It reassures current customers and it works before the order is placed, because prospects can see that the process has been thought through. Use of smartphones and digital channels is firmly established in Germany (Bitkom), and most people look for an answer online before they call. Those who find it there get in touch less often and better prepared.
Technically it stays manageable. One additional page, a reference from the enquiry form and a link from the portfolio are enough. What matters is upkeep: what the page says has to match what actually applies in the business. We offer ongoing care and hosting from 39 euros net per month, and that is precisely what website maintenance is for, so such content does not go stale.
What belongs on the process page
Variations and changes during execution
Wishes arise during a build. The terrace could be half a metre wider, a step would work well in that corner, an edging stone would look good after all. Such changes are often welcome for the business because the crew is on site anyway. They only become a problem at the final invoice, when customer and site management remember differently what was discussed.
The remedy is unspectacular: carry out nothing without written confirmation. It does not have to be a formal variation order. A short message with the scope, the price and a note on the effect on the schedule, plus the customer's reply, is sufficient in most cases. The order is what counts: confirmation first, execution second. The other way round produces a discussion about work already done.
The effect on time is often forgotten. Every change costs not only money but days, and a customer who orders an extra item and still expects the original completion date will predictably be dissatisfied. State both in one sentence. Prices for construction work have moved considerably in recent years (Federal Statistical Office), which is a further reason to give variation prices in writing and with a validity period.
An additional item confirmed in writing before it is carried out costs two minutes. The same item, appearing for the first time on the final invoice, costs a conversation, a deduction or a public review.
Legal context: deadlines, notices, documentation
What you communicate during a build has legal implications without having to turn into a project. Under works contracts governed by the German Civil Code, the business owes a result, not a particular number of working days; a date becomes binding only when it is agreed as such. That is precisely why the distinction between an expected time frame and a promised completion date is more than a matter of wording.
Where the German construction contract procedures (VOB/B) are incorporated, which mainly happens with public and commercial clients, separate rules apply to notices of hindrance and deadlines. Failing to give notice of a hindrance can forfeit claims. In the private sphere the VOB/B is usually not agreed. Which rules apply in a given case follows from the contract and should be checked where there is doubt; this article does not replace legal advice.
In practice, documentation matters more. Photos of the condition before starting, a brief site diary with date, weather and works carried out, and a filed record of messages about changes: in total that is a matter of minutes per day, and in a dispute it is the difference between recollection and evidence. Personal data from that file should be deleted once retention obligations have expired.
Write factually, have the individual case checked
The final week: handover, snagging, aftercare
The end of a site is the phase with the highest volume of calls and at the same time the least prepared. The customer sees an almost finished surface and does not know whether the remaining items were forgotten or planned. A message two days before the expected completion, proposing the handover date and naming the open items, takes the tension out of this phase.
At handover itself, a short list helps. What is inspected together, what is still outstanding and by when, who carries out the remaining work: three lines, confirmed by both sides. That documents the transition from build to warranty cleanly, and the final invoice meets no open points that would turn into a delayed payment.
The last element is aftercare. Newly laid turf, freshly planted shrubs, jointing material and timber surfaces need particular treatment in the first weeks. A short guidance sheet prevents complaints that are not really complaints, and it works long after handover. The same content can sit on the website and be linked from the portfolio gallery, where matching projects are already on show.
- Briefing note sent seven to ten days before the start, with contact person and hours
- Duration stated in working days, buffer and what it depends on explained explicitly
- Weather rule described before the first wet day arrives
- Storage area, duration, access and protective measures agreed in advance and photographed
- A fixed update rhythm promised and kept throughout the project
- Every change confirmed in writing with scope, price and effect on the schedule before execution
- Handover date proposed two days ahead, outstanding items recorded in writing
- Aftercare guidance handed over and published on the website