Turning extra requests into paid, approved work

What a change order does

A change order is a short, agreed document that captures a new request, its cost, and any timeline impact, approved before you start the extra work. Its job is to make the price of additional work visible at the moment it is requested, so the client decides knowingly and you are paid for what you do. It transforms scope creep from a vague drain into a series of explicit, billable decisions.

Recognize when one is needed

The trigger is simple: any request that falls outside the agreed scope warrants a change order, no matter how small it sounds. The phrases to listen for are "could you also," "while you're in there," and "just a quick change." Each is individually minor and collectively expensive. Routing every out-of-scope request through the same process, regardless of size, is what keeps the cumulative cost from disappearing into unpaid hours.

Keep the document light

A change order does not need to be a formal contract; it needs to be clear and fast to produce. A few lines stating the new request, the added cost, and any shift to the timeline is enough, sent for the client's approval before work begins. Having a ready template means you can issue one in minutes, which removes the friction that tempts freelancers to just absorb the work instead.

Anchor it to the original agreement

A change order reads most naturally as an extension of the work you already agreed to, so tie it back to the original scope. When your project starts from a clear agreement with a defined scope, a change order simply references what was in scope and notes that this request is beyond it. That framing makes the extra charge feel like normal procedure rather than a confrontation, because you are pointing to a shared document, not an opinion.

Get approval before you start

The single rule that makes change orders work is approval first, work second. Beginning the extra task before the client has agreed to the cost surrenders your leverage and invites a dispute about whether they ever authorized it. A quick written yes — even a one-line email reply — is enough, and it protects both sides by ensuring the client is never surprised by a charge they did not knowingly accept.

Log everything, even what you absorb

Record every change request the moment it arrives, including the ones you decide to do for free as goodwill. A written log means that when the cumulative weight of small requests becomes a problem, you can show the client the full list rather than relying on a vague sense that the project grew. Data turns a potentially emotional conversation into a factual one, and it helps you spot which clients routinely push scope.

Make it part of how you work

Change orders only protect you if they are standard practice rather than something you reach for when frustrated. When clients learn from the first request that extra work flows through a quick change order, they accept it as how you operate, the same way they expect a contractor to price additional work. Consistency, not confrontation, is what makes the process stick and keeps your margin intact across the whole project.

It helps to set the expectation for change orders during onboarding, before any extra request arises. A brief line in your kickoff — 'anything beyond what we scoped, I'll handle with a quick change order so you always see the cost first' — primes the client to treat the process as normal. When the first out-of-scope request comes, the change order is then a fulfillment of something you already explained, not a surprise.

Track the cumulative value of change orders on a project, because it tells you something useful about your original estimate and the client. A project that needs many change orders may have been under-scoped at the start, or may involve a client who routinely expands work. Either lesson improves how you scope and price the next engagement, turning the change-order log into a quiet source of estimating data.

FAQ

What is a change order?

A short, agreed document capturing a new out-of-scope request, its cost, and any timeline impact, approved before you start. It makes the price of extra work visible so the client decides knowingly.

When should I issue a change order?

For any request outside the agreed scope, no matter how small. Routing every out-of-scope request through the same process is what stops small additions becoming large unpaid hours.

How formal does a change order need to be?

Not very. A few lines stating the request, added cost, and timeline impact, sent for approval before work begins, is enough. A ready template lets you issue one in minutes.

Do I need approval before doing the extra work?

Yes. Approval first, work second. Starting before the client agrees to the cost surrenders your leverage and invites a dispute about whether they ever authorized it.

Should I log requests I do for free?

Yes. A written log of every request, including absorbed ones, lets you show the client the full picture when cumulative scope becomes a problem, turning an emotional talk into a factual one.

Related free tools

This article is general information for freelancers, not legal, tax or financial advice. Rules vary by country — confirm specifics with a qualified professional.