Practical guides

How to Approve Scope Changes Before Invoicing

Separate a client request from billing approval, price the change, document the decision, and carry the reference onto the invoice.

Free text file with blank fields and a filled example. No signup required.

InvoiceAgent includes a 7-day free trial. No credit card required.

Illustrative example

From request to invoice line

Original project
USD 12,000 website
Request
Reporting dashboard
Proposal CHG-07
USD 1,200 / delivery moves three days
Approval
Authorized sponsor confirms CHG-07
Invoice line after acceptance
Dashboard change CHG-07 / USD 1,200

Fictional fixed-fee change. Approval and the billing trigger are recorded as separate events.

See the recorded product workflow

Quick context

Section

Practical guides to scheduling invoices, writing reminders, and managing recurring client billing.

Best for

Consultants and agencies handling extra work during a fixed-price or capped engagement.

Outcome

Use this page to move from general research into a calmer, more repeatable invoicing process.

Action plan

Work through the billing decision

Classify the request

Compare it with the agreed deliverables. Clarify whether it is included work, a correction within scope, or additional work. Explain the distinction using the specification rather than assuming every new comment is billable.

Present the price and trade-off

Use a fixed fee or an agreed hourly basis with a cap. Identify the acceptance condition and any effect on delivery. Give the authorized approver a clear choice: approve, decline, or request clarification.

Carry evidence through delivery to billing

Save the actual decision against the change ID. When the agreed billing trigger occurs, include that ID and the approved charge in the handover. Keep pending changes outside the ready amount.

Editable resource

Preview the review checklist

Replace the bracketed fields with your client’s details. The download also includes the filled example shown on this page.

SCOPE CHANGE CHECKLIST
[ ] Request compared with original scope
[ ] Added deliverable and exclusions written
[ ] Price basis / currency / cap stated
[ ] Timing and acceptance condition stated
[ ] Authorized approver identified
[ ] Actual decision saved with change ID
[ ] PO / budget implications checked
[ ] Delivery or acceptance evidence recorded
[ ] Invoice line references approved change
Requested / approved / delivered dates: [details]
Common pitfalls

Where teams usually lose momentum.

Avoid this

Hiding a change inside a milestone

A larger milestone invoice without a change reference is hard for the client to reconcile. Show the original stage and approved extra separately.

Avoid this

Ignoring cumulative caps

Several small approved changes can exceed a purchasing cap or budget. Review the running approved total and any required PO amendment before billing.

Related topics

project billingapprovalsscope changes

Find more guides and practical tools in the resources below.

FAQ

Questions people usually have before changing the workflow.

What if the extra work is urgent?

Offer a bounded approval with an amount or time cap and document who authorized it. Urgency alone does not tell the invoice owner what can be billed.

What if the client says it was included?

Compare the request with the agreed scope and clarify the difference before charging. If it remains disputed, keep the issue out of routine reminder escalation while it is reviewed.

Should I rewrite the original project price?

Keep the original agreement and a traceable approved change. You can show a revised project total for reconciliation without erasing the original price.

Useful tools

Browse the free tools for help with dates, totals, and reminder planning.

Decision pages

Compare software by the delivery, payment, and follow-up features you need.