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

Write a fence brief that can be priced consistently

Give each contractor the same scope, dimensions and unresolved questions.

Hardwood Fencing material and appearance context

A clear brief describes the intended fence and the decisions still needed. It lets contractors respond to a shared scope and makes differences in their proposals easier to understand. Attach a labeled plan, representative elevations and a material preference rather than relying only on inspiration images.

Describe the outcome

Explain the privacy goal, principal views, preferred board orientation and access needs. Identify the property and label all runs and openings on the drawing. Include the selected gap mockup and indicate which dimensions still require confirmation. For a fence along a side path, describe the objects that must pass through the gate and the appearance desired from the patio. Separate these functional requirements from a preferred detail that the contractor may need to adapt.

Assign the open decisions

State who will verify the location, local requirements and field measurements. Ask the contractor to identify the proposed support and gate systems, board attachment method and product instructions. Mark any unresolved grade, access or boundary condition explicitly. Include removal and disposal requirements for an existing fence, protection of nearby surfaces and responsibility for finish work where applicable. A short list of unanswered questions is more useful than presenting uncertain information as a finished construction specification.

Compare like with like

Request a response tied to the same drawing revision and a clear list of included materials and work. Ask that alternatives identify the changed product or scope and their effect on appearance or maintenance. Compare gate hardware, corner treatment, preparation and finishing as well as board quantity. Before work starts, incorporate accepted changes into the brief. Save that version with the project records so the installed result can be reviewed against a clear agreement rather than remembered conversations.

Evidence & scope

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