Write clear boundaries for a revegetation scope

A scope boundary is more than a line around bare soil. It also defines where one party's responsibility ends and another begins. Many disputes arise because the quoted area is clear but preparation, watering, damage repair or acceptance is not. This HAUSE checklist helps an owner turn a general request into a reviewable project brief. It is a planning tool rather than legal drafting advice. Material contract terms and regulated work should be reviewed by the appropriate professional and governed by the actual agreement.

Define the physical boundary and its measurement basis

Provide a current drawing with treatment polygons, exclusions and held areas. Identify whether quantities are measured, estimated or provisional. State the agreed method for slopes and irregular ground where relevant. Mark paths, beds, retained vegetation, drains and surfaces that must remain untreated. A property area, aerial outline and actual application area can differ substantially, so do not use the terms interchangeably.

Give each polygon an identifier that appears in the quote, release record and completion information. Record who can approve a boundary change. If a neighbouring strip or future garden is added during the site visit, revise the quantity and drawing before it becomes an informal expectation. A readable marked photograph can be suitable for a small project if it clearly shows the limits and is accepted by the parties.

Assign preparation and soil responsibilities

List clearing, debris removal, soil supply, placement, grading interfaces, compaction assessment and final preparation separately. Identify which tasks are included and who accepts them. Alberta's Alberta Transportation — topsoil and subsoil placement specification specification illustrates that soil placement has its own scope. It is not automatically applicable to every site, but it shows why a seed-application contract should not quietly inherit all responsibility for another contractor's soil work.

State how unsuitable or unknown conditions will be handled. The USDA NRCS — Critical Area Planting, Code 342 standard supports investigating factors that could limit vegetation establishment. Do not use a general “prepare as required” phrase to conceal a known drainage or soil uncertainty. Define what is known, what remains an assessment and who authorizes the resulting work. Where buried services or structural issues are involved, keep the appropriate approval and locate processes separate.

Describe the application as identifiable work

Record the intended plant community, seed description, relevant material requirements and any product-specific protection system. Clarify whether the material schedule is specified by a designer or proposed for review by the contractor. Define how substitutions are approved and documented. A scope saying “hydroseed all areas” does not establish which mixture, preparation condition or treatment is intended for different zones.

Include access, water used for application, equipment staging and cleanup of excluded surfaces where relevant. Identify other construction activities that could delay or damage the work. If phasing is expected, state the number or basis of releases rather than assuming unlimited return visits. Keep application water logistics separate from the continuing water supply needed for establishment.

Make establishment tasks explicit

A task marked “by owner” should still be described well enough for the owner to understand the obligation. Written instructions are a deliverable; providing the labour to carry them out is a different service. Do not call both arrangements maintenance included.

Work through a responsibility-gap example

Imagine a 1,200 m² commercial project where one contractor places soil, another applies seed and a third maintains the site after occupancy. The project brief should identify who accepts the prepared surface, who tests irrigation and when the maintenance contractor takes responsibility. Without those handoffs, every party may reasonably assume that someone else will respond to an early dry patch.

Use a dated release form and handover acknowledgement. Record remaining irrigation defects and held areas instead of signing a blanket completion statement. The City of Calgary — park development guidelines and acceptance forms page provides municipal examples of separate construction-completion and final-acceptance forms. Their existence illustrates staged decisions; it does not impose those forms or their terms on a private Canadian contract. Define the actual project milestones in its own documents.

Check exclusions and acceptance before release

Read exclusions against the task list. An exclusion is useful when it tells the owner what must be arranged; it is unhelpful when it merely removes an essential operation without naming a next step. Resolve conflicts between the quote, drawing and specification. Preserve the final revision and approval trail so field staff receive the same scope the owner selected.

Walk the boundary with the person responsible for neighbouring work before releasing it. Mark ambiguous corners on the drawing rather than relying on a verbal gesture across an open site. If the edge follows a future fence or path, identify whether its final position is confirmed. Record who must notify the planting team when that reference changes, because an accurate application inside yesterday’s boundary can still be wrong for the finished project.

State what application completion demonstrates and how later vegetation acceptance will occur if required. Avoid creating a new coverage threshold or warranty after the work is installed. Keep unknown conditions, weather dependencies and future construction risks visible without treating every uncertainty as an automatic excuse for poor work. Continue with bid comparison, change records and inspection and acceptance.