Record seeding changes before the scope drifts

A planting project can change because the owner adds an area, another trade damages prepared ground, a material becomes unavailable or the site reveals an unresolved condition. If those events are handled only through conversation, the final work can differ from the agreed scope without a clear record. This HAUSE change workflow is a practical documentation aid. It is not legal advice or a substitute for the signed contract's notice and authorization requirements. Its purpose is to make the requested decision concrete before additional work, cost or responsibility becomes ambiguous.

Identify the trigger and preserve the baseline

Start with the current approved drawing, scope and material schedule. Describe what changed and when it was observed. Keep the original baseline rather than overwriting it. A new garden exclusion, added slope, delayed release or damaged access strip should have an identifiable location. Record whether the request comes from the owner, contractor, designer or another authorized party.

The Public Services and Procurement Canada — change-order record record provides a federal example of identifying reasons for changes, including conditions, substitutions and timing. Its internal approval structure is specific to that system and should not be copied into a private project as if it creates authority. Use the actual contract process and identify who can approve the change. A site conversation with a person who lacks that authority may still leave the work unapproved.

Separate additions, defects and new disturbance

Describe the event without deciding blame prematurely. An owner-requested additional area is different from a concern about original installation. Damage from later construction is different again. Map the condition and retain photographs, dates and relevant records. If responsibility is disputed, record the technical work needed separately from the unresolved commercial decision so the site issue can be understood clearly.

A repair proposal should explain its cause assumptions and limits. Caltrans Construction Manual — Erosion Control illustrates connecting establishment inspections with repair decisions in a public project. Its specific payment provisions do not determine a Canadian contract's outcome. Do not assume that every bare patch is included warranty work or that every weather event automatically transfers responsibility. Review the evidence and governing terms through the appropriate project process.

Obtain the technical decision before pricing an unknown solution

If the change involves drainage, slope protection, uncertain soil or a different plant community, identify the competent reviewer. A price for “extra hydroseeding” does not settle whether that treatment is appropriate. Define any necessary preparation, reinstatement or protection before calculating an application quantity. Keep professional or regulatory approvals separate from ordinary commercial authorization where both are required.

For substitutions, compare the proposed material with the approved objective and requirements. Record the exact product or seed identity and the reason for the request. Check the applicable specification edition; the City of Calgary — current landscape specification editions index demonstrates how current and superseded editions are distinguished. A phrase such as “equivalent to current standard” should not hide an unreviewed technical difference or an unread document.

Use a change record that answers the main questions

Follow the contract for notice, emergency action and pricing. This table does not create new rights or waive existing obligations. Where the necessary decision cannot be made immediately, record the hold and any authorized interim protection instead of treating silence as approval.

Work through an added-area example

Imagine an original 700 m² application scope. After a fence is moved, the owner asks to add a 90 m² strip that has a different soil condition and no tested watering coverage. The change is not merely “add 90 m² at the old rate.” It may require preparation, a water arrangement, another material decision or a separate visit. Define those items before asking for a priced revision.

Record the new total only after the change is accepted. Preserve the original 700 m² baseline and identify the added polygon. If the strip is released later, keep its application and establishment dates separate. The example supplies no rate and does not imply that a unit price must or must not remain the same. That decision belongs to the actual agreement and the changed conditions.

Close the change into the final handover

Once authorized work is completed, update the as-installed map, material information, quantity record and maintenance plan. Keep the proposal, approval and completion evidence together. A change that affects care should be handed to the maintenance team, not only filed with the invoice. Explain held areas or unresolved issues that remain after the changed work.

Give each change a short identifier that appears on the drawing, quotation, approval and completion record. Where several proposals address the same issue, mark which revision replaces which. A rejected proposal should remain labelled rejected, while an approved portion should be described explicitly. This small discipline prevents a later reviewer from combining an obsolete price with a newer scope and mistakenly treating them as one approved instruction.

Review the final record for conflicting revisions and assumptions. If a change remains disputed, label it accurately rather than presenting it as approved or completed. Continue with scope boundaries, quantity reconciliation and maintenance handover.