Change Order Template: The One Page and When to Send It

A client asks for a second version of the landing page, for a different market, on a Tuesday afternoon. The work starts on the Wednesday. The change order gets written the following Monday, after the file has gone out, because by then it feels like paperwork rather than a question. That sequence is the one this page is about, and every line of it can be accurate and still arrive four days too late.

The four days are the whole problem, and the reason is mechanical rather than personal. Say the purchase order behind the job reads $6,000 and the finished job invoices at $7,400. In Coupa the amount you are allowed to type is capped by what is left on the PO line, so the larger invoice cannot be raised against that order at all; where a system does take an over-PO invoice, it tends to sit on a tolerance hold, which is the status meaning the invoiced amount differs from the PO by more than the buyer allows without manual approval. Either way the money is now waiting on a purchase order amendment that somebody on the client's side has to raise, approve and re-send, and that queue has nothing to do with whether the work was any good.

Nobody has disputed anything. The document was written after the only moment at which it could have done any work.

What the page is actually for

A change order is not proof that you did extra work. The email thread already proves that, and the thread is usually better evidence, because it has the client's own words in it.

The document exists to move a number inside a system you cannot see. It has two readers. The first is the person who asked for the change, who already agrees with you and does not need convincing. The second has never spoken to you, sits in accounts payable or procurement, and makes exactly one decision: does the authorised amount for this vendor match the amount on this invoice. That second reader is who the page is written for. Everything on it should be checkable by somebody with no memory of the project.

What the federal version puts on the page

The most detailed publicly available specification for this document is not a freelance template. It is the change order machinery in the Federal Acquisition Regulation, which governs contracts between the US government and its suppliers. None of it applies to your agreement with a marketing director in Ohio. It is worth reading anyway, because it was written by the party that gets billed most often, and it shows what that party wants a change to say.

Four points survive the translation, all read at eCFR on 28 August 2026:

• Changes are made by written order, within the general scope of the contract (48 CFR 52.243-1(a)). Written comes first, before the price is even discussed.
• Where a change affects cost or time, the adjustment is made to the price, the delivery schedule, or both, and the contract is then modified to match (52.243-1(b)). Time is not an afterthought in the federal version.
• The contractor must assert its right to an adjustment within 30 days of receiving the written order — though the same paragraph lets the contracting officer receive and act on a proposal submitted any time before final payment, if the facts justify it (52.243-1(c)). A clock, then, with a named way of missing it. That is the shape of the whole problem: late is a different document, not a closed door.
• If the two sides cannot agree on the adjustment it becomes a dispute, and nothing in the clause excuses the contractor from proceeding with the contract as changed (52.243-1(e)).

Then there is the structural point, in the administration rules at 48 CFR 43.204(a): when a change order is not priced up front it takes two documents, the change order itself and a later supplemental agreement recording the adjustment. When the price and the schedule can be agreed in advance, only one document is needed. Two paragraphs down, the same section tells contracting offices and contract administration offices to establish suspense systems adequate to ensure prompt definitization of unpriced change orders (43.204(b)(3)) — definitization being the regulation's word for finally pinning the price down. That is a bureaucracy putting in writing that unpriced changes drift unless somebody is chasing them.

That is the whole argument for the one-page version. Price it before the work starts and you write one page. Price it afterwards and you are running the two-document route with no contracting officer whose job it is to close the loop.

Ten lines, and the two nobody writes

The two that go missing are the delivery date and the running total. The date matters because a change adding three days of work to a fixed deadline is not free; it is a fee paid in weekends. The running total matters for a reason that only shows up later, on the fifth change order, when the question is what the job now costs in full and the only way to answer it is to add up an email thread.

One more line is worth borrowing from the federal file. When a change order is finally settled, the regulation recommends a release: in consideration of the modification agreed as a complete equitable adjustment for the proposal, the contractor releases the government from further adjustments attributable to the facts giving rise to it, except for anything listed (48 CFR 43.204(c)(2), read on 28 August 2026). In freelance form that is one sentence: this change order settles the additional work described above and nothing else. It stops a client treating one agreed change as payment for everything that has drifted since.

Before, during, after: the same page, three different jobs

Before the work starts. The document authorises. It is short, it is priced, and the sentence carrying it is some version of happy to do this, here is the page, send a yes and I will start tomorrow. This is the only version where you still hold something the client wants.

After the ask, before you have gone far. Still fine, and more common than the tidy version. Say what has been done so far, price the whole change including it, and stop at a natural boundary rather than finishing on faith. A change order sent at 20 percent complete reads as project management. The same page at 95 percent reads as an invoice with a signature line on it.

After delivery. This is the version most people are searching for, and it is a different document. It confirms rather than authorises: past tense, named requester, actual date, delivered item, amount, and a direct ask to confirm by reply so it can be invoiced. Its weakness is that the client already has the value, so the only things making them sign are the record and the relationship. Its strength is that it still creates the paper the next stage of chasing needs.

The trigger for reaching for the page is not a feeling about scope creep. It is any request that does not match a line in the scope of work you already agreed, at the quantity and standard written there. If a request matches, do it. If it does not, it gets a page before it gets your afternoon.

The client's paperwork moves slower than the client does

The reason timing is unforgiving at larger clients has nothing to do with goodwill. The person asking for the change usually cannot authorise money, and the purchase order raised at the start of the job is a ceiling rather than an estimate. An invoice over that ceiling does not get queried. It gets bounced by software, which is the mechanism described in getting into a vendor portal so you can invoice.

So the change order at a corporate client has a job the wording never reveals: it gives your contact something to forward to procurement so the PO can be increased before your invoice arrives. That process has its own queue, usually measured in weeks. Ask for it directly on the page, in one line, and ask before you deliver rather than after. In the sequence at the top of this piece the change order and the invoice arrive on the same day, which means the amendment has not been raised and the invoice has nothing to match against.

Small clients paying from a bank account have none of this and can approve a change in an afternoon. The size of the client, not the size of the change, is what decides how much lead time the page needs.

The change that pushes a job over a statutory line

There is a second-order effect worth knowing before you write the page, because a small addition can arrive with a statute attached to it.

New York's and Illinois's freelance payment statutes both draw their threshold around the relationship rather than around a single invoice. New York's definition of a freelance worker reaches services provided for an amount equal to or greater than eight hundred dollars, either by itself or when aggregated with all contracts for services between the same hiring party and freelance worker during the immediately preceding one hundred twenty days (N.Y. Gen. Bus. Law section 1410(3), read 28 August 2026). Illinois sets $500 on the same rolling 120-day aggregation, in a single contract or across all contracts between the same contracting entity and freelance worker (820 ILCS 193/5, in the FindLaw republication of the section, read 28 August 2026).

So run the arithmetic before deciding the page is not worth writing. A $700 job in New York plus a $250 change order inside the same 120 days is $950 against a threshold of $800. Both definitions also carry exclusions — construction services and certain classifications among them — which is a separate question from the arithmetic and decides whether the statute reaches a given job at all. Where it does reach, the written contract requirement and the payment deadline come with it, and that is an argument for writing the change order rather than for keeping the paperwork quiet. What the contract then has to contain, and which agency a complaint goes to, is in New York's Freelance Isn't Free Act; Illinois runs its own version through the state labour department on different numbers.

When they won't sign it

Sometimes the page goes out and nothing comes back. The request stays live in Slack, the deadline does not move, and the silence is doing work.

Here the borrowed federal structure stops being useful, and the reason is worth naming. A federal contractor who cannot agree on the adjustment keeps performing the contract as changed and argues about the money afterwards, because that clause says so in as many words (52.243-1(e)). Nothing puts that clause in your agreement unless your agreement puts it there. So the step before deciding anything is to open the contract and look for two sentences: a disputes or continue-performance clause requiring you to keep working while a disagreement runs, and the amendment clause saying how a change becomes part of the deal. Client master agreements do sometimes carry the first. What either one means for the job in front of you is a question for a lawyer licensed where the agreement says it is governed.

What that leaves is a boundary rather than a confrontation. Keep delivering what the signed scope of work describes, on time, and hold the unsigned addition where it is. The message that does this best is short and contains no complaint: the original deliverables are on track for the agreed date, the second market version is on hold pending the change order sent on the 14th, and it can start the day that comes back. It states a position without making an accusation, and it gives the client's side something to act on rather than something to answer.

The thing not to do is the one that feels most reasonable in the moment, which is to finish it anyway and explain on the invoice. An invoice is not where a change gets agreed. It is where a change gets disputed, sixty days later, by somebody who was not on the call.

Before you rely on any wording above, the sentence that actually governs you is the amendment clause in the agreement you signed, read by a lawyer licensed where that agreement says it is governed. The page itself is the cheap part.