What documents does a change order process actually need?

Four, and they do different jobs. A one-page change order that ties the request to the original SOW and states the fee. A log that tracks the cumulative budget impact across the project. An intake form so requests arrive in one place instead of scattered through email. And a signing step that produces a record you can hand to somebody later. Most studios have the first one and none of the others, which is why the third change of a project is the one that gets absorbed.

Do I need a tool, or will a template do?

A template is enough while you are writing one change order a month. The failure is not the document, it is the discipline of producing it under deadline pressure, which is when studios skip it. A tool earns its place at the point where you are skipping the paperwork rather than at the point where writing it is slow.

How does Stria fit into a change order toolkit?

You forward the client's email and Stria checks the request against the scope you locked, then drafts the change order with the clause it falls outside quoted back to you. It does not connect to your inbox and it does not act on its own — you choose what to forward and you approve what gets sent.

Change Order Toolkit: The Four Documents a Studio Needs Before the Next Small Change

Every studio has a change order template somewhere. Almost none of them have a change order process, and the difference shows up on the third request of a project rather than the first.

The first "small change" gets documented, because it is early and nobody is behind yet. The third arrives in week six, on a Thursday, when two other projects are also live — and it gets absorbed, because finding the template, filling it in, and having the money conversation costs more attention than the change appears to be worth. The template was never the bottleneck.

So this is a list of four documents rather than one, ordered by how much of that friction each removes.

1. The one-page change order

The strongest pattern is a single page that ties the request directly to the original statement of work and states the fee impact before any work starts. One page is deliberate: a document that runs to three pages invites the client to re-negotiate the project instead of approving an addition.

The elements that matter are unglamorous — a reference to the governing contract and its date, a plain-language description of what is being added, the fee as a line item, and a short acceptance window so the document cannot sit unanswered indefinitely.

Asana publishes a free change order template if you want a starting point, and Forge's version shows the same one-page structure. Our own change order template for freelancers walks through the wording clause by clause, and the engagement letter and SOW templates cover the document this one has to reference.

2. The change order log

A single change order tells you what one request cost. A log tells you what the project cost, which is the number that decides whether you take similar work again.

Keep it boring: request date, one-line description, approved fee, running total. The running total is the whole point — three changes at $400 read as three small approvals in an inbox and as a 12% budget increase in a spreadsheet, and only one of those framings reaches you before you quote the next project.

3. An intake form for requests

If requests arrive in email threads, they arrive in the format most likely to get answered informally. A short web form does two things a thread cannot: it collects the same fields every time, and it moves the request out of the medium where "sure, no problem" is a single tap.

Cognito Forms has a change order form template with conditional logic if you want estimated fees calculated on submission. Stria's own version of this is the inquiry form walkthrough, which covers the same idea for the front of the engagement.

4. A signing step that produces a record

A signature is not the goal; the record behind it is. What you want to exist six months later is evidence of who approved what, on which version, and when — the thing you can forward once and end a dispute with, rather than reconstructing a thread.

The e-signature change order workflow covers how to sequence this so the client signs before you countersign, and Stria's e-signature alignment page maps the specific mechanisms behind ESIGN, UETA and eIDAS — including an explicit list of what Stria does not claim.

Where a tool earns its place

Standardising this process is measurably worth doing. The Project Management Institute's Pulse of the Profession reports that organisations with mature delivery practices experience scope creep on a materially smaller share of projects than low-maturity ones — the gap is process, not talent.

The honest version of the automation argument is narrow. A tool does not write a better change order than your template does. What it removes is the step where you decide whether producing one is worth the effort right now, which is the step that actually fails.

That is the part Stria takes: you forward the client's email, it checks the request against the scope you locked, and it drafts the change order with the clause the request falls outside quoted back to you. It does not connect to your inbox and it does not send anything on its own — you choose what to forward, and you approve what goes out. If you want to see the mechanics without an account, the free scope check runs the comparison on a pasted excerpt.

Pick at least one document from each of the four categories above and put them where you will actually find them. The next "just one small change" email is going to arrive on a Thursday, and the only thing that decides whether it gets billed is how much work it takes you to say yes properly.

If you would rather not assemble the toolkit yourself, start a 14-day Stria trial — the free plan covers one client and three deliverables a month, with no card.