A gardening site visit should do more than produce a quick list of requested tasks. It is the point where a small contractor can compare the customer's expectations with the actual garden, access, working space and likely resources. A structured visit reduces the risk of arriving for the job with the wrong assumptions, while giving whoever schedules or delivers the work a clearer brief.
Start with the result the customer wants
Ask what the customer is trying to achieve rather than immediately converting every comment into a task. A request to tidy a garden, improve a border or reduce maintenance can mean different things to different people. Clarify priorities, areas in scope and any parts the customer specifically wants left alone. This creates a better basis for deciding what work should actually be proposed.
Walk the site before discussing the final approach
Inspect the relevant areas and note practical conditions that affect delivery. Access width, steps, gates, working space, existing planting and the route for moving tools or waste can all shape the job. Where work raises arboricultural, structural, electrical, chemical or other specialist considerations, identify the need for appropriate competent assessment rather than making unsupported conclusions during a general gardening visit.
Separate visible facts from assumptions
Record what can be observed and distinguish it from anything that still needs checking. For example, the position of a bed or damaged fence is visible; the cause of a plant problem or the condition of something hidden may not be. This discipline helps the business avoid turning a first impression into a promise that later proves difficult to support.
Discuss materials and disposal before they become surprises
If the proposed work is likely to require plants, soil products, aggregates or other materials, establish who is expected to supply them and how choices will be confirmed. Likewise, clarify the agreed approach to green waste and other job waste. The final quotation or job scope should reflect the arrangement rather than leaving the operative to negotiate it on arrival.
Record access and customer constraints
Note agreed access arrangements, relevant timing restrictions and practical requirements such as keeping a gate secured or protecting an area from routine traffic. Keep records proportionate and use the business's normal job system rather than relying on a worker's private messages. The crew needs useful operational information, not unnecessary personal detail.
Turn the visit into a job brief someone else can use
Photographs, measurements and notes are valuable only when they explain the work clearly enough for scheduling, pricing or another team member. Label information so it can be connected to the correct area and proposed task. If a decision remains open, mark it as unresolved instead of allowing the next person to assume it has already been agreed.
Check the final scope against the original conversation
Before work is booked, compare the proposed job with what the customer actually prioritised. Remove accidental extras, make exclusions clear and identify choices that still require confirmation. A good site visit produces a practical bridge between enquiry and delivery: the customer knows what is being proposed, and the gardening team knows what it is expected to achieve.