Make a visual record, not a diagnosis

Walk the yard in daylight and take wide photos from the home, property edges, and access route. On a simple sketch, identify the house, patios, steps, walls, trees, poles, existing equipment, and areas the household wants to keep. Note where water collects after rain and which parts of the yard feel most exposed to wind or sun. Those are observations; they do not establish soil stability, adequate drainage, or a final pool location.

Ask which route people, tools, and materials would use from the street to the proposed area. A route that appears workable in a photo may include turns, gates, grade changes, obstacles, or access agreements that alter logistics. Do not remove vegetation, break concrete, or move utilities to “prepare” the site without responsible review.

  • Dated wide-view photos of the front, side, and yard.
  • A sketch showing existing features and areas to retain.
  • Approximate locations of visible meters, equipment, and access covers.
  • Notes about access, parking, and known time restrictions.

Turn preferences into reviewable questions

Bring priorities separately from assumptions: family use, sitting space, privacy, shade, access, or room for equipment. Explain what you do not want to lose in the yard. Ask each proposal to identify what was verified on site, what depends on drawings or the competent authority, and what still needs a specialist.

Physical site preparation belongs here. Permit preparation is different: do not assume a project is exempt or that a homeowner sketch is enough for an application. Keep those questions for the permit-preparation guide.

Table: Turn preferences into reviewable questions
InformationHow it helps the visitHonest limit
Photos and sketchFrames access and discussionNot a survey or design
Desired useOrders prioritiesDoes not determine technical capacity
Water observationsFlags questions to raiseDoes not prove cause or remedy

Finish with a summary that can be corrected

Write a one-page summary: private property reference, project goal, attached photos, observed access, open questions, and features to preserve. If someone makes a technical statement, ask which document, inspection, or professional it depends on. That keeps an early idea from becoming an implied construction promise.

Do not expect a seller to settle structures, buried utilities, drainage, or compliance by message. “This needs confirmation on site” can be the most useful answer.

Planning note

If there will be a visit, ask what should be accessible and what information would be useful to bring, but do not treat that list as a work order. Note whether neighbors, access rights, or community rules could affect entry and retain any response in your notes. The goal is not to anticipate a solution; it is to keep visible details from getting lost between conversations. When the project moves from an idea to a proposal, compare the initial sketch with the written scope again.

Clear record

If you share information with a site visitor, retain your original copy. A clear note about what was observed helps separate visible facts from expectations and reduces confusion in later proposals.

Frequently asked questions

Should I clear the entire yard before a visit?

Not necessarily. Clear only what can safely improve visibility; do not demolish, excavate, or alter utilities to get ahead of a decision.

Do photos show whether a pool will fit?

No. They help an early conversation, but the installed footprint also involves access, working areas, equipment, and conditions a photo cannot confirm.