Change requests and version control

Change requests let you scope out-of-scope work, get approval and billing terms, and then invoice separately.

When to use

When a client asks for something outside the original scope — a new section, extra revisions, a different feature — create a change request instead of adding it to the original project.

The flow

  1. Draft — list what's being added and any new deadline or cost.
  2. Send to client — they review and accept or decline.
  3. Upon approval — the work becomes a new billable project.

Billing

Each change request has its own estimate and line items. When approved, you invoice it separately so the client sees the original scope and the additions.

This keeps projects clean and invoices clear about what was original vs. what was added.

Was this article helpful?