DEV Community

OpsPack
OpsPack

Posted on

A 5-line change order that stops scope creep

Scope creep usually starts with one innocent "could you also..." and ends with you working for free. A change-order habit fixes it without a fight.

The 5-line change order

  1. What was asked: one sentence describing the new request.
  2. What it affects: deliverables, timeline, or both.
  3. Cost: a fixed number, not an hourly guess.
  4. New date: the delivery date if approved today.
  5. Approval: "Reply YES to approve and I will start."

Rules that help

  • Say "happy to, here is the change order" within 24 hours of the request.
  • Never start the extra work before the YES is in writing.
  • Keep a short list of what is in scope in your original contract so the comparison is easy.
  • Small favors are fine, but name them as a courtesy once so they do not become the baseline.

Free template

The exact wording is in this free change order template: https://opspack.vercel.app/change-order-template

Contract, payment-terms and invoice chase kits: https://opspack.vercel.app

Top comments (1)

Collapse
 
__d03cc26214f3 profile image
איתמר וענונו •

The "in writing within 24 hours" part is the one that matters most. The verbal "could you also..." is where scope creep starts, and the request is easy to lose once it is buried in a chat thread. A short list of what is in scope, kept next to the contract, makes the comparison easy when the next request comes in.