Landscaping Planning Guide: Site, Soil, Plants & Water

Planning answer: Begin with a property-specific site record, not a generic shopping list. Write down how each area is used, where people and equipment move, what must remain accessible, which views or activities matter, and what problems you are trying to address. Mark doors, gates, downspouts, drains, slopes, low spots, existing trees and beds, paved areas, utilities you know about, irrigation zones, lighting, and any area where water collects or soil washes away.

Observe the site at different times rather than assuming one visit tells the whole story. Note sun and shade, wind exposure, runoff after rain, seasonal wet areas, compacted paths, pet or play areas, and access needed for maintenance. Record measurements and photos, but do not use a web guide to decide a property boundary, drainage right, utility location, or structural condition. Those questions need the responsible records and qualified people for the property.

Separate the project into required functions and optional preferences. A functional scope might address access, drainage observations, erosion exposure, irrigation coverage, screening, shade, or a usable activity area. Preferences can then cover planting character, color, texture, lighting, seating, or future phases. This distinction helps written proposals respond to the same problem instead of presenting unrelated packages.

Use the Landscaping Installation Cost Calculator only after you have described the scope and entered your own assumptions. Its output is an input-derived planning scenario, not a contractor quote, an observed offer, or proof that a particular design is suitable for the site.

Soil and water conditions shape what questions belong in the project scope. USDA NRCS explains that Web Soil Survey provides current official soil information for a user-defined area of interest. It can help a homeowner review mapped soil context and generate a soil map, but it does not replace an onsite evaluation, a property survey, laboratory testing, or a drainage or structural design.

Use that official context as a starting point. Ask what soil preparation is proposed, how existing compaction or fill will be handled, where runoff is expected to move, whether water will be directed toward neighboring property or a building, and who is responsible for any drainage design. If the plan includes walls, major grade changes, concentrated discharge, or work near a foundation, have the responsible local official or qualified professional define the needed review rather than inferring an answer from a map.

USDA describes native plants as plants that can conserve water, help protect soil from erosion, and support wildlife habitat. Treat that as a reason to consider locally appropriate native species, not as evidence of suitability for every yard. Match candidates to the site's light, moisture, soil, mature size, root behavior, exposure, and maintenance constraints, and use regional extension or other responsible local guidance when selecting a species.

For every proposed plant, request the botanical name, supplied size, expected mature dimensions, placement, soil preparation, establishment instructions, replacement terms, and maintenance responsibility. Keep alternatives in the written scope so a substitution does not silently change mature size, water needs, or the intended function of the design.

Irrigation planning should begin with plant needs, soil and slope context, existing equipment, pressure and coverage observations, and the way water moves through each zone. Document which areas will be irrigated, which will not, how trees and new plantings are separated from lawn zones, and how runoff, overspray, broken components, or low spots will be identified during testing.

EPA explains that WaterSense labeled controllers use weather-based or soil-moisture-based information to help reduce overwatering. That supports asking whether a controller is WaterSense labeled and how its sensors, schedules, seasonal adjustments, and manual override will be commissioned. It does not establish the water use or savings for a particular property; those outcomes depend on the site, plants, irrigation design, weather, settings, and maintenance.

Ask the written scope to identify controller and sensor models, valve and zone changes, emitter or head types, coverage goals, pressure assumptions, backflow responsibilities, wiring, trench restoration, initial programming, and the test used at handoff. A plan should also state who corrects leaks, runoff, blocked spray, or coverage gaps discovered during commissioning.

Pair irrigation decisions with plant grouping and soil preparation instead of treating the controller as a stand-alone upgrade. Request a simple zone map and initial schedule at closeout, then adjust from observed plant and soil conditions within applicable local watering rules. Do not adopt a universal schedule from a national guide; climate, rainfall, soil, exposure, plant maturity, and local restrictions vary.

Excavation can affect buried utilities even when the visible work looks minor. PHMSA's 811 guidance says to contact 811 before an excavation project. Follow the notification and marking process applicable to the job, respect the marks and tolerance requirements communicated for the site, and resolve conflicts before digging. An 811 request does not locate private lines, establish a property boundary, or approve the proposed work; ask which private irrigation, lighting, drainage, fuel, septic, or other lines also need to be identified.

Create a separate list for work that may involve walls, steps, fences, decks, patios, drainage structures, electrical circuits, gas, plumbing, pools, protected trees, easements, or changes near a building. The necessary review depends on the jurisdiction, property, scope, and adopted rules. FEMA advises contacting local officials before spending money on repair work because local codes and floodplain rules can apply. Use that as a prompt to verify requirements with the responsible local offices, not as a claim that one permit rule applies nationwide.

Ask who will verify permits, inspections, utility coordination, access limits, material staging, equipment loads, erosion controls, and protection for existing surfaces and plants. If engineering, drainage design, arborist review, electrical work, or another specialty is needed, the written proposal should identify who provides it and what document controls the work.

Before signing, make sure the plan shows what is being removed and retained, limits of disturbance, access routes, protection measures, and restoration responsibilities. Resolve ambiguous lines on a concept sketch before crews and equipment arrive; a decorative rendering alone is not a construction or approval document.

FTC consumer guidance recommends checking licensing and insurance, comparing multiple written estimates, and putting the agreed work terms in writing. Verification methods and contract requirements vary by state and locality, so confirm the legal business name and any required credential through the responsible authority. CostSignals does not vet, rank, endorse, or certify a landscaping contractor.

Make proposals comparable by giving each contractor the same site record and asking for the same scope structure:

• plan version, measured quantities, work limits, and exclusions;
• demolition, hauling, disposal, grading, soil preparation, and drainage work;
• exact plant names, supplied sizes, quantities, locations, and substitution process;
• hardscape or structure materials, base preparation, edge details, and finish;
• irrigation equipment, zones, commissioning, and restoration;
• utility coordination, permits, inspections, specialty review, and owner duties;
• protection, access, cleanup, establishment care, and closeout documents;
• schedule dependencies, payment milestones, and written change control.

An estimate should make allowances and unknown conditions visible. Ask how unsuitable soil, concealed utilities, drainage conflicts, unavailable plants, weather, or an official review will be documented and priced before additional work proceeds. Do not authorize an open-ended change from a verbal description.

Read the controlling contract, cancellation terms, payment terms, warranty documents, and dispute provisions before signing. Confirm which commitments come from the contractor, manufacturer, designer, nursery, or another party. The calculator scenario can help organize your own assumptions, but replace those assumptions with the quantities, scope, and terms in the actual written documents before making a decision.

Define completion before work begins. A useful closeout walk-through checks the agreed plan against installed locations and quantities, tests irrigation zones and controls, records plant and material substitutions, reviews drainage observations, identifies unfinished restoration, and assigns each punch-list item to a responsible party and date. Do not treat installation as evidence that drainage, plant establishment, or irrigation performance has been approved for every future condition.

Keep the signed scope, plan version, approved changes, permit and inspection records where applicable, utility documentation, product identifiers, plant list, irrigation zone map, controller instructions, photos, receipts, warranty documents, and care instructions together. The FTC's written-contract guidance supports preserving the agreed work terms; the actual contract and product documents control their respective obligations.

Ask for an establishment and maintenance handoff that states who waters, adjusts irrigation, replaces failed plants under any written term, controls weeds, refreshes mulch, prunes, cleans hardscape, and reports a leak or drainage problem. USDA's native-plant guidance can inform plant-selection questions, while actual care must follow the selected species, local conditions, and supplied instructions. EPA's controller guidance can inform controller questions, while settings still need observation and adjustment at the property.

Revisit the site after irrigation tests and meaningful weather, documenting ponding, erosion, overspray, leaks, settlement, access issues, or plant stress without assigning a cause from this checklist. Send the observation to the responsible contractor, designer, official, or specialist when it affects the agreed scope, safety, a structure, utilities, or neighboring property. A maintained project file makes that follow-up specific and keeps future work grounded in the decisions and documents that actually apply to the site.