FoundStart

A one-page change request that keeps client work under control

A client asking for an extra page, new report or earlier deadline has made a request, not necessarily changed the contract. Write the requested difference against the agreed deliverable. Include who asked, when, and the version of the original scope. Avoid replacing the original brief with an edited copy that hides what changed.

Separate the request from the agreement

A client asking for an extra page, new report or earlier deadline has made a request, not necessarily changed the contract. Write the requested difference against the agreed deliverable. Include who asked, when, and the version of the original scope. Avoid replacing the original brief with an edited copy that hides what changed.

Record the impact before the price

Use five fields: requested change; work added or removed; dependencies; delivery impact; proposed fee. For example, adding a second language can require approved translation and another review round, not just another button. Mark estimates as estimates. If the change displaces another task, name that task instead of promising both deadlines.

Give the decision a clear owner

End with approve, decline or revise, plus the name of the person allowed to decide. A friendly chat reply such as sounds good can be unclear if it does not identify the fee and deadline it accepts. Refer to the numbered proposal in the approval. Keep the existing work moving only where it does not depend on that decision.

Keep a small change log

Example record: CR-04; add an Arabic summary; client supplies translation by 12 November; delivery moves two working days after receipt; fee awaiting approval. After acceptance, add the approval reference and new baseline version. This is an operating template, not legal advice or a promise that every message changes a contract.