Hardwood FencingGARDENS · SCREENS · BOUNDARIES(844) 237-3175
Planning

Lay out the boundary as a sequence

Turn a long boundary into named runs, openings and transition points.

A horizontal wood garden fence with a matching framed gate beside a paved path.
Illustrative context

A horizontal wood garden fence with a matching framed gate beside a paved path.

Architectural visualization. It does not set privacy, spacing, support, hardware or local approval requirements.

Begin with a measured plan showing where the fence changes direction and where people must pass through it. Panel appearance follows those decisions. A useful layout makes each run identifiable so a designer, supplier and installer can discuss the same location without guessing.

Name the runs

Assign letters to straight runs and numbers to their panels. Record endpoints against stable, identifiable features on the plan. Separate measured distances from approximate ones, and mark the date of the measurement. Include paths, doors, utility equipment, planting beds and places used to move bins. For a side yard with two gates, draw both gates before arranging the infill; otherwise the final panel may inherit an awkward leftover dimension.

Choose visible priorities

Identify the view that matters most, such as the approach from the street or the outlook from a terrace. Use it to decide where a centered bay or consistent top line deserves priority. Then inspect the less visible end of the run for a sensible adjustment zone. Do not distribute a measurement discrepancy casually across every panel. Show where variation is acceptable and where a specific alignment is part of the design.

Make the drawing buildable

Add clear opening dimensions, swing directions and a simple elevation for each different condition. Keep proposed support locations subject to the project-specific installation design. Record which dimensions still need field confirmation before cutting. Photograph the labeled endpoints and store those images beside the drawing. The finished planning package should let someone identify run B, its corner and its gate immediately, while keeping unresolved site questions visible instead of burying them in a board count.

Worked example: reconcile one run before dividing it into bays

A 30-foot run, reconciled
Hypothetical plan-length example. The bar shows length allocation, not fence construction.
Five consecutive zones total 360 inchesFrom left to right: start transition, 6 inches; infill A1, 144 inches; gate zone G1, 48 inches; infill A2, 156 inches; end transition, 6 inches. Numbers correspond to the ordered dimension schedule below.12345

6 + 144 + 48 + 156 + 6 = 360 inches. The two infill zones total 300 inches, or 25 feet. The gate zone and two end transitions account for the other 5 feet.

These allowances are invented for this arithmetic example. They are not post sizes, hardware clearances, support spacing or approved gate dimensions. The gate zone includes its unresolved interfaces; it is not a 48-inch clear passage. Confirm those from the actual project before assigning cutting lengths.

Consider a fictional 30-foot straight run measured between two named endpoint marks. The sketch reserves 4 feet for a gate zone and 6 inches at each end for unresolved transitions. The remaining planning length is 30 − 4 − 0.5 − 0.5 = 25 feet. That is the length left to coordinate, not 25 feet of cut boards. The gate zone is a reserved envelope, not a promised clear opening; posts, hardware and clearances still need to be resolved.

Worked example: reconcile one run before dividing it into bays
Segment in orderPlanning lengthWhat must be resolved
A-start transition0.5 ftEndpoint, return and support relationship
A1 infill zone12 ftBay division and support design
G1 gate zone4 ftRequired clear passage, leaf, supports and hardware
A2 infill zone13 ftBay division and final adjustment location
A-end transition0.5 ftConnection to the next run or termination
Total A30 ftMust agree with the endpoint measurement

The two infill zones total 25 feet, but neither is an approved unsupported span. Their internal supports and the actual board lengths belong to the project-specific assembly design. Keep the zone boundaries visible until that design is agreed. Dividing the full 30 feet by a preferred panel width would erase the gate and end conditions from the arithmetic.

Use the same measurement references throughout

Write down what each dimension measures: endpoint to endpoint, post center to post center, face to face, or clear passage. These are different distances. A gate opening measured between finished obstructions cannot be substituted for a center-to-center support dimension. Mark the references on the plan and repeat them in the schedule.

For a sloping run, identify whether the recorded length follows the ground or is the horizontal plan distance. Keep elevations in a separate column. A stepped top, a sloped top and a level top can share plan endpoints while requiring different board cuts and bottom-edge decisions. Record the intended condition rather than letting a photograph decide it implicitly.

  • Give every run two identifiable endpoints and a measurement date.
  • Show each gate separately, with its required passage and swing area.
  • Mark corners and returns where the next run begins; do not count the same transition twice.
  • Keep approximate measurements visibly provisional until checked.

What changes when a field measurement disagrees?

Suppose a later check makes the fictional run 29 feet 10 inches rather than 30 feet. Keep the original value in the revision history and record the 2-inch difference. If the gate and both end zones stay fixed, the combined infill allocation becomes 24 feet 10 inches. Do not quietly narrow the required gate passage or spread the difference across board gaps.

Choose an adjustment location, then check its effect on the visible rhythm, support positions and cut lengths. If the agreed design depends on equal bays, recalculate that portion of the layout and reissue its schedule. If the new measurement uses different endpoints, resolve the reference mismatch before changing the design. A revised total alone is not enough information for someone holding the earlier cutting list.

A layout handoff someone else can use

  • Plan: labeled endpoints, run order, openings and neighboring features that affect access.
  • Elevations: top and bottom intentions, changes of level, and where each gate sits.
  • Schedule: measurement references, measured versus provisional values, and unresolved transitions.
  • Revision note: what changed, which runs are affected, and which earlier drawing is superseded.
  • Release check: resolve boundaries, required clearances, services and assembly requirements before treating a visual layout as a construction instruction.

Use the site’s Design Studio to compare the visual decisions after these locations are established. Then review corners and returns and property boundaries for the next coordination questions. A convincing rendering helps evaluate appearance; the measured run schedule explains what the rendering represents.

Evidence & scope

Original planning guidance. References support their stated technical scope; examples and workflows do not establish product approval.