Why Agency Change Orders Never Get Signed (And What It Costs You)
Short answer: Almost every agency has a change order process on paper and almost none of them use it consistently. The reason isn't discipline — it's friction. When a client asks for something extra on a Tuesday call, papering it properly means opening a separate signing tool, building a document, sending a link, and then chasing it. That's twenty minutes of work and an awkward follow-up to protect four hours of scope. So it doesn't happen, the work gets done unpaid, and it shows up later as a margin problem nobody can trace.
The moment it goes wrong
You're on a call. The client says "while you're in there, could you also…"
It's small. Saying yes feels good, costs little, and keeps the relationship warm. So you say yes.
Three of those in a month is most of a day. Over a quarter it's a meaningful share of your delivery capacity, given away without a record. And the client isn't being unreasonable — from their side, nothing was ever framed as additional. It was a conversation on a call.
Scope creep isn't usually a client problem. It's an agency documentation problem where the documentation step costs more than the scope being documented.
Why "we should just paper everything" doesn't work
Every agency knows the answer is to document scope changes. Most have tried enforcing it. It fails for reasons that aren't about willpower:
The friction is front-loaded and the payoff is deferred. The cost of papering it lands now; the benefit shows up at invoicing, weeks later.
It requires leaving the conversation. The scope change is agreed in a call or a thread. Documenting it means switching to a different tool with a different login.
It's socially expensive. Turning a friendly "sure, we can do that" into a formal document sent for signature feels like a downgrade in the relationship, especially for small items.
Then you have to chase it. The client doesn't sign, you follow up twice, and now you've spent more effort on the paperwork than the work.
Per-seat signing tools discourage volume. If signatures are metered or seat-limited, small change orders feel not worth spending one on.
The realistic response to all of that is to do the work and say nothing. Which is what happens.
What this actually costs
Three separate costs, and the first is the smallest.
The unbilled hours. Direct, and usually the only one anyone counts.
The invoice disputes downstream. When undocumented scope does eventually get billed — because someone noticed the overrun — the client has no record of agreeing to it. From their side the invoice contains a line they never approved. That dispute was created weeks earlier by the missing paperwork, not by the invoice.
The precedent. Every unpapered extra teaches the client that extras are free. By month four, "while you're in there" is a standing expectation rather than an occasional ask, and re-establishing the boundary is now a difficult conversation instead of a routine one.
What actually fixes it
The fix isn't a better template or a stricter policy. It's making the documentation step cheaper than the work being documented.
Three properties matter:
1. It has to happen where the conversation is
If the scope change is agreed in the client's portal or thread, the change order should be created and signed there. Every tool switch is a place the process leaks.
2. Signing has to be one action for the client
Not "check your email for a link, create an account with a third party, verify, then sign." The more steps between agreement and signature, the more change orders die in the gap.
3. It can't be metered
If each signature has a cost or consumes a seat, people ration them — and they ration exactly the small ones that add up. A process only works if using it for a two-hour change order feels free.
The documents this applies to beyond change orders
Change orders are the highest-frequency case, but the same friction affects everything:
The initial services agreement — sent as a PDF, signed weeks later, sometimes after work has started
Statements of work per project or phase
NDAs at the start of a relationship
Deliverable sign-off — formal acceptance that a phase is complete, which is what prevents a client reopening finished work
Renewal and rate-change acknowledgements
That fourth one is worth dwelling on. Most agencies have no formal acceptance step, which means "done" is a matter of opinion, and a client can reopen a completed phase months later. A signed acceptance closes it.
How this works in BluOps
BluOps includes document signing on every plan — not an add-on, not a higher tier, and not metered per signature.
Upload a document and toggle signature required. Contracts, SOWs, change orders, NDAs, acceptance forms.
Assign it to the client, and optionally to specific people. If you don't name individuals, it goes to every available member for that client.
Signing captures a timestamp and IP address.
Both parties receive a signed copy.
It lives in the client's portal — the same place as their projects, files, messages and invoices — so the signed record sits alongside the work it governs.
Being straight about what it isn't: this is not a full contract lifecycle platform. There's no drag-and-drop field placement, no template library with merge fields, no complex multi-party routing. If you're running high-value negotiated contracts with legal review cycles, you want a dedicated tool and probably your counsel's preferred one.
What it's built for is the routine, high-frequency document work agencies actually do — where the problem was never capability, it was that the process had too much friction to use.
On legal enforceability: requirements for electronic signatures vary by jurisdiction and by document type, and the stakes scale with contract value. For routine change orders and acceptance forms most agencies are comfortable with a straightforward signed record. For high-value agreements, ask your own counsel what they require — this article isn't legal advice and BluOps doesn't offer any.
A process you can actually hold
Set a threshold. Anything above it gets a change order. Two hours is a common line. Below it, absorb without ceremony — that's goodwill, and it's fine as long as it's a decision rather than a default.
Create it during the conversation, not after. "Happy to do that — I'll send a quick change order so it's on record" said in the moment is normal. Said two days later it's awkward.
Keep the document short. What, how many hours, what it costs, what it does to the timeline. Four lines. Length is friction.
Get acceptance on completed phases. A signed sign-off is what stops finished work being reopened.
Review quarterly. Count the change orders raised against the extras actually delivered. The gap between them is what your process is still leaking.
Frequently asked questions
Why don't agencies document scope changes?
Because the documentation costs more than the scope being documented. Papering a two-hour request means leaving the conversation, building a document in a separate tool, sending it, and chasing the signature. The rational response in the moment is to do the work and say nothing.
What should be in an agency change order?
What's being added, the estimated hours, the cost, and the impact on timeline. Four lines is enough. Longer documents get read less and signed slower, and length is the friction that stops them being raised at all.
Do I need DocuSign for agency contracts?
For high-value negotiated agreements with legal review, a dedicated contract platform is worth it. For routine agency documents — change orders, SOWs, NDAs, acceptance forms — the constraint is usually friction and cost per signature rather than capability, which is a different problem.
How do I stop scope creep without damaging the relationship?
Set a threshold below which you absorb requests without ceremony, and above which you raise a short change order in the moment. Doing it during the conversation reads as professional; doing it days later reads as retroactive.
Should clients sign off on completed work?
Yes, and most agencies skip it. Without formal acceptance, "done" is a matter of opinion and a client can reopen a finished phase months later. A signed sign-off closes the phase and is also useful evidence if the work is later disputed.
Does BluOps document signing cost extra?
No. It's included on all plans and isn't metered per signature. Signing captures a timestamp and IP address, and both parties receive a signed copy.
The short version
Change orders don't go unsigned because agencies lack discipline. They go unsigned because documenting a small scope change costs more effort than the change itself, so the rational move is to absorb it. Do that fifteen times and you've given away real capacity and taught the client that extras are free.
Set a threshold, raise it in the moment, keep it to four lines, and make signing cheap enough that using it for small items feels free.
See how documents and signing work in the portal — 7 days of full access is $1.