October 9, 2026·7 min read

Landscape Architect Site Observation Report Template

A practical landscape architect site observation report template with field-tested sections, common mistakes, and tips for protecting your firm during CA.

Most site observation reports written by landscape architects are either so sparse they're useless in a dispute or so padded they take 45 minutes to write per visit. Neither extreme serves your firm. This article gives you a field-tested template structure, explains what each section actually needs to accomplish legally and professionally, and flags the mistakes that create liability after the fact.

Why the Report Format Matters More Than You Think

A site observation report is a legal document first and a project communication tool second. When a contractor claims they installed Quercus agrifolia at 24-inch box as specified and you approved the work, your report is the record that either supports or contradicts that claim. Vague language like "trees appear to be correct size" has cost firms real money in arbitration. "Seven (7) Quercus agrifolia, 24-inch box, 1.5-inch caliper minimum, installed per detail L-5.1" costs you an extra 30 seconds and eliminates the ambiguity entirely.

The format also affects whether your team actually completes reports consistently. A 4-page form with 60 blank fields gets skipped or half-filled. A structured one-page template with clear prompts gets completed every visit.

Core Sections Every Report Needs

Header Block

Project name, project number, contract number, date of visit, time of arrival and departure, weather conditions, and temperature. Weather matters — it determines whether concrete placement or planting was appropriate that day. Your report noting "overcast, 38°F, light wind" during a planting visit becomes important if plant establishment fails.

Also record who was present: contractor representative name and title, subcontractors on-site, owner representative if present. First and last names, not just company names.

Work Observed

This is the substantive core. Describe specifically what work was in progress or completed since your last visit. Reference specification sections and drawing sheet numbers. "Irrigation mainline installed in Zone 3 per drawing IR-2.1, Spec Section 328400" is useful. "Irrigation work ongoing" is not.

Group observations by trade or work area. If concrete flatwork, planting, and irrigation were all active simultaneously, separate them. It takes two extra minutes and makes the report navigable six months later.

Conformance Status

For each item of work observed, make a clear determination:

Conforming — work meets contract documents
Non-conforming — specific deficiency noted, action required
Unable to determine — work covered before observation, or insufficient information

Never skip this column. "Unable to determine" is a legitimate and protective answer when a contractor backfills before you can observe the subgrade. Document that you requested exposure or testing and whether the contractor complied.

Deficiency Log

Any non-conforming item gets its own numbered entry: deficiency number, date identified, description, specification reference, required corrective action, and resolution date. This log carries forward visit to visit until the item closes. A running deficiency log in your report series is far more useful than scattered notes across individual reports.

Contractor Requests and Verbal Directions

Record every verbal direction you gave on-site and every question the contractor asked, even if you answered verbally. If you told the superintendent to hold off on the decomposed granite installation until the irrigation pressure test passes, that goes in the report. Verbal directions that aren't documented might as well not have happened.

Next Scheduled Visit

Date, anticipated work scope, and any items you need the contractor to have ready for your review. Setting this expectation in writing reduces the "we didn't know you were coming" conversation.

Template Table: Deficiency Log Format

#	Date Identified	Location	Description	Spec/Drawing Ref	Required Action	Status	Date Resolved
D-001	2026-03-12	Zone 2 planting area	Agave americana installed at 5-gal, contract requires 15-gal	Spec 329300, Plan L-3.2	Replace with specified size or submit substitution request	Open	—
D-002	2026-03-12	Entry plaza	Concrete broom finish direction inconsistent with detail	Drawing A-4.1	Contractor to grind and re-finish or submit RFI for EOR review	Closed	2026-03-19

Keep deficiency numbers sequential across the entire project, not resetting each visit. D-047 on a large project is normal. It tells a story about the project's construction quality.

Frequency and Timing

How often you visit depends on your contract, but the minimum that provides meaningful protection during active construction is weekly during grading and hardscape, twice-weekly during planting and irrigation installation. Daily observation is a separate scope item with a different fee — make sure your contract is explicit about which you're providing.

The distinction between "site observation" and "construction inspection" is not just semantic. Observation means you're making periodic visits to determine general conformance. Inspection implies continuous on-site presence and a higher standard of care. Using the wrong word in your contract or your reports is a liability issue. The ASLA and most state licensing boards have guidance on this distinction. Use "observation" unless you've specifically contracted for and are providing continuous inspection services.

Photo Documentation Standards

Every report should reference photos by filename, not just attach them as a blob. "See photo 2026-03-12_D001_agave_size.jpg" is searchable and linkable. A folder of 200 unnamed photos from a project is nearly useless in a dispute.

Photograph non-conforming items from two angles: context (showing location on-site) and detail (showing the specific deficiency). For conforming work you're accepting, photograph enough to establish that you actually looked at it — not just one wide shot of the whole site.

Distribution and Timing

Send the report within 24 hours of the site visit. This is the professional standard and the practical one — your notes are accurate, the contractor can act on deficiencies while work is still accessible, and the timestamp matters if timing is ever disputed. Reports sent three days later raise questions about what was edited.

Copy the owner, contractor, and any subconsultants whose work was observed. Keep a distribution log. If a contractor later claims they never received a deficiency notice, your email distribution record answers that.

Common Mistakes Firms Make

1. Mixing observations with recommendations. "The contractor should consider adding a layer of mulch" reads as optional. If mulch depth is specified, write "Mulch depth observed at 2 inches; Spec Section 329300 requires 3-inch minimum depth. Non-conforming. Contractor to add material to achieve specified depth." Recommendations belong in meeting minutes, not observation reports.

2. Not referencing specification sections. Every deficiency should cite the specific spec section or drawing detail being violated. Without that reference, the contractor can argue about what was actually required. You shouldn't be having that argument in the field.

3. Using hedging language. "It appeared that..." and "it seemed like the trees might be..." are not protective — they're ambiguous. Write what you observed, factually. If you couldn't determine conformance, say so explicitly and document why.

4. Signing off on covered work. If a contractor backfills a drainage layer before you observe it, do not write "drainage layer assumed conforming." Write "drainage aggregate not observed prior to backfill. Contractor notified verbally that observation was required per Spec Section 334000. Contractor to provide compaction testing results." Then follow up in writing.

5. Letting deficiency items drop off the log. A deficiency that appears in report 7 and disappears without a resolution note in report 8 is a problem. Either the contractor fixed it and you didn't document the resolution, or you stopped tracking it. Both create exposure.

6. Treating the report as a formality rather than a record. Firms that rush through reports to check a contractual box end up with a document that looks like it was written in five minutes — because it was. A judge or arbitrator will notice. So will your E&O insurer.

How Phasewise Handles This

Phasewise includes a structured site observation report module that ties directly to your project's phase and task timeline, so reports are logged against the correct construction administration phase rather than floating as disconnected attachments. The deficiency tracking feature carries open items forward automatically from visit to visit, so nothing falls off the log between reports. If your team is currently managing this in Word documents and a shared drive, that's the specific workflow Phasewise replaces.