Published by LANDOVA Design & Planning. October 16, 2026.
The backyard design has been approved. What exactly should move from that review into conversations with the people who may build it?
Sending a beautiful rendering is a start, but a handoff needs more context. Someone receiving the information should be able to identify the current design, understand what it communicates and see which questions still require answers. The purpose is to create a shared reference for the next stage, not to imply that homeowner approval settles every technical or contractual matter.
State what the approval covered
Begin with a plain description of the decision. Was the household approving the arrangement of outdoor spaces, a material selection, a phase boundary or a particular design revision? Name the file and revision that were reviewed.
Avoid a broad label such as “approved plans” if it conceals several different statuses. A design visualization, a selection list and any separately required technical documents may serve different purposes. Ask the responsible professionals which materials can be used for estimating, which need further development and which are appropriate for construction.
Homeowner preference approval should remain distinct from any permit, engineering or other review that the actual project requires.
Assemble an index before sending a collection of files
Create a short index with the document name, date or revision, purpose and status. Include the current layout, relevant design views, selection information and the description of the scope being discussed. If some information is still provisional, label it that way.
Place superseded files in a clearly separate archive. Preserve them for reference, but do not mix them into the active package without an explanation. The recipient should not have to decide which of three similarly named PDFs reflects your current intent.
Check that the index itself points to accessible files. A folder full of shortcuts is not a useful handoff if the receiving person cannot open them.
Explain the scope in ordinary language
A scope note should describe the work being considered, the elements intended to remain and any future work outside the present discussion. Use the same feature names in the note and the drawings.
For a phased project, identify the area under discussion now and the later features shown for context. A future feature appearing in a rendering should not silently become part of the current pricing request. Conversely, leaving something out of one picture does not establish that it is excluded from the project.
Where proposals already exist, record their stated scope separately. Ask the issuing party to resolve differences between its proposal and the design package; do not rewrite the proposal yourself.
Make unresolved questions visible
Create an open-questions page. Each entry needs a question, the relevant drawing or location, the person being asked and the next review point. Useful entries are specific: “Who confirms the interface between the proposed paving and this retained edge?” is better than “Check hardscape.”
Separate missing information from disagreement. An item may be awaiting a product selection, a site assessment or a response about trade responsibility. Those are different reasons to keep it open and may involve different people.
Do not mark an item resolved merely because someone has been asked. Record the answer and identify where it appears in the updated documents.
Test the handoff with a fictional example
Imagine a household planning a dining terrace now and a garden structure later. The current rendering shows both, while the written scope names only the terrace. Without an explanation, a recipient could reasonably ask whether the structure belongs in the requested proposal.
A clearer handoff labels the structure “future concept, outside this pricing request,” describes the first-phase scope and lists any professional review needed to coordinate future intent. The document index identifies the terrace layout revision being used. The question is then about a defined project rather than competing interpretations of a picture.
This example illustrates organization only; it does not prescribe a construction sequence or assign responsibility to a particular trade.
Confirm the next action and its owner
Close the handoff with a small set of next actions. Ask recipients to confirm that they received the current documents and to identify the questions that prevent them from responding accurately. Confirm how revised information will be shared and who should receive it.
Keep the project’s actual agreements and professional roles in view. Design, estimating, technical review and construction are separate activities whose responsibilities need to be established for the project. Clear records support those conversations without replacing them.
Ready to organize the design decisions behind your outdoor project? Bring your current information to LANDOVA Design & Planning. Start Your Design.
