Process

Change Order Ethos.

Changes are normal. Confusion is optional. This is how changes are handled without destabilizing the site.

Change handling

Clean control, not conflict.

A change order protects the project: scope clarity, cost clarity, and schedule clarity.

Qualifies as a change

Outside original scope.

  • Added / removed / substituted scope.
  • Revisions after sign-off.
  • Design/engineering changes.
  • Unforeseen conditions requiring new work.
Contains

Defensible detail.

  • Description + affected areas.
  • Cost breakdown (labour/material/subtrade).
  • Schedule impact (days added/removed).
  • Assumptions and exclusions.
Workflow

How it runs

  1. Identify the change and stop ambiguity.
  2. Document (short written scope + photos as needed).
  3. Price (fixed or T&M as appropriate).
  4. Approve in writing before execution.
  5. Execute and record completion.
  6. Close with updated records.