SHEET S-10 / CLIENT VOICE
LANDSCAPE CLIENT COMMUNICATION
Send the update with the whole job in view.
A changed delivery, a crew note or an agreed variation can change what you tell the client. Bring those details together, then have the person responsible for the job check the update.
Context matters more than a polished sentence.
A client message can be accurate and still be wrong for the job if it forgets the decision behind the date. The latest site note may say the planting bed is ready. The supplier email may say the specimen tree is held for another week. The approved scope may exclude the extra drainage work. Client communication software should bring those records together and show a conflict rather than quietly picking one.
A variation, or change order in the US, needs more than a new line in an email. The agreed scope, price and date should be easy to find, along with the person who approved them. That makes the next client conversation easier to answer.
Fictional example: the update that waits for the missing fact.
In a fictional Cedar House project, the client asks whether planting can happen before a stone delivery. The foreperson's crew note says the access route is still occupied. A supplier message gives a later delivery window, while the signed scope says the planting sequence depends on finished edging. A useful draft gathers those three sources, names the conflict, and proposes a calm update with the decision still open.
The project lead checks the sources, chooses the wording, and approves the message. The client sees the agreed sequence, the next date to expect, and the question that needs an answer. The person who knows the client checks the note before it goes out.
A handover should leave the client with something usable.
A client-visible handover is more than a final thank-you. It can list the work accepted, the care notes agreed, the items still open, and who owns the next action. Ask whether those facts come from the job record and whether a person can edit them before they are shared. A principal should be able to explain every line at the final walk-through.
| Check | Ask before choosing |
|---|---|
| Sources | Can a draft show the site note, scope, and supplier fact it used? |
| Conflict | Does uncertainty stay visible until an owner resolves it? |
| Review | Can the responsible person edit and approve the wording before release? |
| Handover | Does the client receive accepted work, open items, and the next owner in plain language? |
The firm keeps its voice and its responsibility.
Lode is designed to relate the records around a job, prepare a client update for review, and preserve the decision that follows. It does not guarantee autonomous email, infer consent, resolve a source conflict silently, or send a promise under the firm's name without approval. The useful system makes review faster while leaving the relationship with the people who own it.
The plain-text quote and site handover checklist is a practical starting point for a team review. Add your own client language, approval roles, and care notes before comparing products.
Bring the message you nearly sent.
Request accessRead how the full office sequence works, compare the handoff with a CRM on the comparison page, or see the current scope on the private walkthrough page. For the programme, continue to landscape scheduling. For cost context, continue to landscape estimating and landscape job costing.
For established landscape firms delivering high-value work