Completed fictional example: Handle a mid-project scope change before work continues

All people, identifiers, amounts, outcomes, and internal evidence are fictional. This example demonstrates how to complete the record; it is not a client case or an account test.

Project / original accepted proposal and version

WEB-014 / proposal v2, demo acceptance A-02

Change ID / requester / date

CH-02 / Jamie / October 2, 2026

Request and difference from the baseline

Add a Contact page and form; original scope was one home page

Classification: correction / clarification / new scope

New scope

Deliverable impact and retained work

Contact page added; original home page retained

Price basis / tax treatment under the agreement

Illustrative fixed $600 addition; same tax treatment as the original proposal

Timing and required inputs

October 16 if copy arrives by October 12

Options and client reply

Keep the original scope and date, or add the page with the addition and delay; model wording in the article

Decision maker / answer / evidence / date

Jamie, designated decision maker in the demo agreement, explicitly accepts CH-02 October 5; demo reply A-03

Outcome and plan update / owner

Accepted; Casey updates tasks and timing referencing CH-02; original proposal retained

Two alternative outcomes for the same model

Declined: Jamie chooses the original scope and date on October 5. Mark CH-02 declined; Casey does not start the added work.

Conditional: “Add the page but keep the original deadline.” CH-02 remains open; Casey checks capacity by October 6 and submits a revised option for a decision. Do not infer agreement to the addition or date. These are alternative scenarios, not concurrent decisions.