Step 4: Agree

Scope rarely breaks in one dramatic moment.

It expands through small messages: "Can we also add a lightweight dashboard?" Each one sounds harmless. Together they become unpriced delivery work and margin exposure. ScopeGuard compares the signed agreement with the message thread and flags potential drift - with evidence.

Runs in the browser. Deterministic rules. A human always makes the final call.

Who it is for

Agencies, studios and freelancers who deliver fixed-scope projects - and the account, sales and delivery leads who have to defend the margin when the thread drifts away from the contract.

Common triggers

  • "Quick extras" accumulate across weeks of messages.
  • The client remembers a promise the contract never made.
  • The dispute surfaces at invoice time, not at request time.
  • Nobody can show who agreed to what, when.

How it works

Load the source of truth, add the thread, review the evidence.

Add the source of truth

Load the scope document or initial order email, plus communication or work-record exports.

Run the analysis

Deterministic, configurable rules compare messages against scope items. No model guessing - the same input always produces the same findings.

Review the evidence

Each potential drift finding shows the message, the source and the scope basis it conflicts with, plus an estimate of delivery exposure in hours.

Decide what happens next

Mark it in scope, turn it into a priced change request, or reopen a previous decision. The trail stays shared and reviewable.

Open core

The rule engine is open source.

The repository contains the inspectable product core - the rules, the evidence model and the local app - so technical teams can verify exactly how findings are produced before trusting them in a client dispute.

Inspect the rules