Commercial

Change orders prepare reviewed scope changes.

This commercial module prepares scope changes against an existing agreement and approved playbook. A signed change returns as an amendment candidate for review. It does not accept work on behalf of a counterparty or overwrite the current baseline automatically.

Change order · scope adjustmentFictional sample

CO-2 · adds one landing page per month

  • Monthly fee6,500 → 7,100
  • Term endunchanged

A change order is prepared from the current confirmed terms and returns for amendment review once signed.

Interactive preview · fictional sampleA change-order draft mapped to agreed scope and routed back as an amendment candidate.

01

Extra scope is mapped to agreed scope.

The user describes the proposed change and compares it with confirmed agreement scope. Missing approval, price or dependency details remain unresolved.

Change order · scope adjustmentFictional sample

CO-2 · adds one landing page per month

  • Monthly fee6,500 → 7,100
  • Term endunchanged

A change order is prepared from the current confirmed terms and returns for amendment review once signed.

The draft compares proposed scope with the current agreement record.

02

Commercial changes are prepared for review.

Fees, dates and affected obligations are drafted from approved inputs and deterministic calculations. The draft still needs human review before export or signature.

Proposal · Alder Works design retainerFictional sample

Proposal-V1 · from approved inputs

Monthly fee
USD 6,000
Initial term
12 months
Scheduled fees
USD 72,000 (6,000 × 12)
Exclusions
Advertising spend, additional development

Refused: “guaranteed 30% sales growth” — not in the approved inputs.

Drafts use approved inputs; unsupported claims are refused. Signed terms then link to the agreement record.

Approved inputs constrain scope, price and dependency changes.

03

Playbook differences do not become universal risk scores.

The module can compare a proposed clause with the user's approved positions. It labels source-supported differences and uncertainty, not a universal legal-risk score.

AGR-0142 · Design retainer — Alder WorksFictional sample

Design retainer — Alder Works

CustomerStatement of workMaya Okafor

Governing sources

  • SOW-S1 (signed, 21 Sep 2026)
  • Amendment A1 (signed, 15 Mar 2027)
  • Schedule 2 (attachment, not governing)
Amendment A1 § 3
Either party may give notice not to renew at least ninety (90) calendar days before the end of the term.

Confirmed by Maya Okafor on 18 Mar 2027, based on Amendment A1 § 3.

Record context shows source-supported differences without legal scoring.

04

Signed changes enter amendment review.

A completed change order is imported and reviewed as an amendment candidate. A confirmed effect can then supersede affected future actions, as Amendment A1 does in the sample.

Amendment A1 — Alder Works retainer · Review what changedFictional sample

Imported 15 Mar 2027 · effective 1 Apr 2027

Candidate · B1 still governs
FieldBefore (SOW-S1)ChangeAfter (A1)
Monthly feeUSD 6,000USD 6,500
Notice period60 calendar days90 calendar days
Initial term end30 Sep 2027unchanged

Effect on the notice date

1 Aug 2027 → 2 Jul 2027

30 Sep 2027 − 90 calendar days. 5 pending reminders would be superseded; sent ones stay in history.

Scheduled initial-term fees

USD 72,000 → USD 75,000

12 months, no proration, tax or early termination modelled.

New terms need review. The prior confirmed schedule remains visible; do not assume it reflects this amendment.

The amendment review confirms what the signed change actually changed.

How it works

How it works.

New agreements enter the same register as the ones you already had, with the same owners, dates and reminders from day one.
  1. 01

    Start from an existing confirmed record

    The flow uses the current agreement, sources and owner as context.

  2. 02

    Describe the proposed scope change

    Missing commercial terms, dates or dependencies are flagged for review.

  3. 03

    Review and export the change order

    A person approves the version before any signing process.

  4. 04

    Import the signed change

    The signed copy becomes an amendment candidate, not an automatic baseline change.

What it does not do.

Focused by design. These stay out of scope so the product stays sharp.

  • It does not send counterparty messages, accept work or approve scope autonomously.
  • It does not provide a universal legal-risk score or legal advice.
  • It does not overwrite the current agreement baseline until a signed change is reviewed and confirmed.
  • It does not include procurement, invoicing, accounting or project delivery management.

Common questions.

Start with your agreement platform.

Start a 7-day free trial, explore the fictional sample, and see how source-backed agreement work stays connected.