Clarification of Scope

Scope must be defined before price can be trusted.

Scope is not what someone assumes. Scope is what can be described, measured, accepted, priced, changed, and enforced.

What it is

Descriptive Scope

A general textual description of work without measurable boundaries, quantities, or completion criteria.

What it regulates
  • General intent of the parties.
  • Nature and type of work.
What it does not regulate
  • Scope quantity or extent.
  • Acceptance, completion, or performance criteria.
  • Basis for pricing, valuation, or change orders.
Where it is used
  • Small-scale or informal work.
  • Early project or pre-design stages.
  • Projects with high uncertainty or evolving scope.
Observed gap

Open to interpretation

Lack of measurable boundaries leaves scope open to interpretation.

Potential risk: disputes over included work, exclusions, and what constitutes additional scope.
Impact by role
Worker

Performs work beyond expectations without clear entitlement to extra payment.

Company

Bears risk of scope expansion and uncompensated work.

Client

No objective basis to verify completion or enforce performance.

Resolution mechanism

Contract interpretation · Statutory adjudication · Court

Status: in force. Sources: provincial contract law and CanLII descriptive scope jurisprudence.

What it is

Measured Scope

Scope defined by quantities, units, dimensions, areas, counts, locations, specifications, or measurable work items.

What it regulates
  • Quantity and extent of work.
  • Basis for unit pricing and valuation.
  • Measurement-based change orders.
What it does not regulate
  • Final outcome quality unless acceptance criteria are defined.
  • Performance responsibility beyond measured units.
  • Design adequacy or suitability of selected method.
Where it is used
  • Trade packages.
  • Estimating and tendering.
  • Unit-rate work and quantity-driven projects.
Observed gap

Measurement does not guarantee outcome

Measured scope controls quantity, but may not control result, quality, coordination, or completion standard.

Potential risk: paid quantity may be clear while acceptance remains disputed.
Impact by role
Worker

Can justify payment by measurable output, but may still face quality or acceptance disputes.

Company

Can price and control quantity better, but must define acceptance to protect margin.

Client

Can verify quantities, but still needs quality, completion, and acceptance standards.

Key understanding

Measured scope answers “how much,” not always “what result.”

Use measured scope when quantity matters, but add acceptance criteria to control outcome.

What it is

Result-Based Scope

Scope defined by the required final result, performance standard, completion criteria, or acceptance outcome.

What it regulates
  • Required final outcome.
  • Completion and acceptance criteria.
  • Performance expectations and deliverables.
What it does not regulate
  • Exact method of execution unless specified.
  • Detailed quantities unless measured scope is added.
  • Internal labour or productivity assumptions.
Where it is used
  • Performance-based work.
  • Design-build or outcome-driven agreements.
  • Projects where acceptance is more important than quantity alone.
Observed gap

Result may be clear, method may not be

Result-based scope can reduce acceptance disputes, but may create execution-method or cost-risk disputes.

Potential risk: contractor bears more delivery risk if method, exclusions, and assumptions are not defined.
Impact by role
Worker

May be judged by outcome, even where time, materials, or dependency conditions are unclear.

Company

Can sell certainty, but must price delivery risk and define exclusions.

Client

Gets a clearer acceptance basis, but must understand that certainty usually has a price.

Key understanding

Result-based scope controls acceptance.

It is strong when the desired outcome is defined clearly and risk allocation matches the promised result.

What it is

Hybrid Scope

A combined scope structure that defines description, measurable boundaries, result expectations, exclusions, acceptance criteria, and change rules.

What it regulates
  • Nature and type of work.
  • Quantities, limits, inclusions, and exclusions.
  • Acceptance criteria and change mechanisms.
What it does not regulate
  • Unexpected conditions unless allocated.
  • Market volatility unless contract mechanism exists.
  • Client changes unless documented and priced.
Where it is used
  • Professional construction contracts.
  • Projects with pricing, risk, and acceptance sensitivity.
  • Work requiring both quantity control and outcome control.
Observed gap

Requires discipline

Hybrid scope is stronger, but only works if changes, exclusions, acceptance, and dependencies are maintained during the project.

Potential risk: strong initial scope can fail if field changes are undocumented.
Impact by role
Worker

Clearer task boundaries, stronger basis for extra work claims, and less ambiguity.

Company

Better margin protection, change control, and reduced dispute exposure.

Client

Clearer verification, acceptance, cost control, and enforcement basis.

Best practice

Hybrid scope is the strongest practical model.

It combines description, measurement, outcome, acceptance, exclusions, and change rules into one enforceable structure.