Change order approval workflow

The specific sequence of steps — request, estimate, client approval, execution — a change order moves through from being flagged to being billable.

Example

1) PM flags an out-of-scope request in the project channel. 2) Lead estimates hours and cost within a day. 3) A one-page change order is sent to the client. 4) Work starts only after the client replies with written approval.

Why it matters for agencies

A slow or unclear approval workflow is often why change orders don't get used even when an agency has a template for them — if getting a change order approved takes longer than just doing the work, teams default to just doing the work, which is exactly how scope creep becomes normalized.