Retaining Walls on Sloped Properties: What to Document

Begin with a safe, wide observation

Photograph the full visible setting from a safe and permitted position. Include the slope, wall line, ground above and below, paths, driveway, stairs, building edges, fences, trees, drains, and neighbouring surfaces where relevant. A wide view gives each close-up a location and helps another person understand what could not be seen.

Record the date, weather context, camera direction, and vantage point. If the area is steep, wet, overgrown, behind a gate, or otherwise difficult to approach, do not enter or move barriers to obtain a better image. Write down the limitation and leave the unseen area as unknown.

Describe the slope and wall position

Explain where the wall sits in relation to the slope. Note whether the ground appears to rise behind it, fall away from it, meet a driveway, support a path, border a garden, or connect to another wall. Use fixed references such as a fence, stair, building corner, curb, or property feature rather than guessing an angle or height from a photograph.

If you record approximate dimensions, identify how they were obtained and which portion they describe. State when vegetation, shadow, an irregular top edge, limited access, or a changing grade makes the reading uncertain. A rough dimension is documentation, not a wall design, structural measurement, or final scope.

• Wall location in relation to the slope and fixed property features
• Approximate visible length or height, with method and limitations
• Ends, corners, returns, transitions, and areas hidden from view
• Whether the observation is direct, reported by someone else, or unknown

Map the retained area and nearby structures

Record what is above, beside, and below the wall without deciding what load or responsibility those features create. Note visible patios, driveways, paths, stairs, sheds, fences, decks, building edges, utility covers, landscaping, parked areas, or other structures. Identify whether each item is directly observed, shown in an older record, or reported by another person.

Show how people and vehicles approach the area. A wall beside a driveway, accessible route, stair, or shared path raises different questions about safe observation and access than a wall in a planted area. Keep those differences in the notes without prescribing a layout or construction response.

• Features visibly above, beside, and below the wall
• Driveways, paths, stairs, structures, utilities, and landscape elements nearby
• Access, shared-property, boundary, or responsibility questions
• Records or reports that need confirmation by an authorized party

Record visible water without explaining its cause

Photograph visible water context from a safe vantage. Note drains, downspouts, wet ground, staining, sediment, flow marks, ponding, exposed gravel, saturated-looking soil, or places where water appears to meet the wall or slope. State whether the image was taken during rain, after rain, or in dry conditions.

Trace only what is visible and stop when the route disappears behind vegetation, below a cover, into a pipe, or across another property. Do not remove covers, dig behind the wall, enter a ditch, or disturb the ground to follow a suspected path. Mark unseen portions as unknown.

• Visible drains, outlets, low points, wet areas, and flow marks
• Weather and surface conditions at the time of the observation
• Where a visible water path disappears or cannot be checked
• Questions to refer rather than answer from photographs

Document visible changes and reports carefully

Use neutral descriptions for visible changes such as a gap, crack, shifted-looking cap, leaning appearance, bulge-looking area, missing material, erosion-looking edge, or change in alignment. Take context views before close-ups. Avoid labels that imply a structural conclusion, cause, severity, or required repair.

Separate direct observations from reports. ‘I observed’ describes what was visible from the permitted vantage. ‘A resident reported’ or ‘a manager reported’ identifies information received from someone else. ‘Unknown’ identifies something not visible, measured, confirmed, or within the observer’s role.

• Current direct observations with date, location, and view
• Older records and reports labelled by source and date
• Features that cannot be viewed, measured, or confirmed
• Any access or safety limitation that shaped the record

Prepare a referral and site-question packet

A referral packet should include the property context, wide and close photographs, a simple location key, approximate visible dimensions, slope and wall position notes, nearby structures, water observations, access constraints, and the unknowns list. Identify who owns or manages the area and who is authorized to arrange further review.

Ask the receiving professional or responsible authority what additional information is needed and which questions belong to another discipline. The packet can request an observation-based review or referral; it should not ask a photograph to provide a diagnosis, design, repair method, or authority decision.

• What additional view or record would clarify the observed condition?
• Which questions require a qualified structural, geotechnical, drainage, or other professional?
• Which property, boundary, access, or authority questions need a responsible party?
• What remains unknown because the area was unsafe, restricted, covered, or not measured?
• What should be reviewed before anyone discusses a construction scope?

Keep the record open to site-specific review

Do not reduce a sloped property to wall height or one close-up. Keep the slope, retained area, nearby use, water context, access, visible changes, records, and unknowns together. This makes it easier for a qualified reviewer to understand the question without treating an incomplete image as a complete site record.

Use a short evidence key: observed directly, measured approximately, reported by another person, shown in an older record, not visible, or unknown. Add the source and date wherever practical. A careful record can support a referral even when it cannot answer the technical question.