Playbooks · Everyday tasks
Draft a scope change order with an agent, before the extra work starts
Written October 27, 2026 · Edited November 20, 2026
For a freelancer × a client asking for more than the signed scope × an agent drafting, ending with a one-page change order the client approves in writing — price, schedule impact, and sign-off line on one page — and no extra work started before that approval exists.
Before you start
You need the agreed scope in writing — the deliverables, the exclusions, and the acceptance criteria from the proposal or agreement, plus the client's responsibilities with dates (the assets and approvals the client owes, and by when) — plus the client's new request in their own words, your hourly rate or the flat fee you charge for this kind of work, and the current delivery date. The agent drafts and classifies; you decide the price and you send the order. A change order is a business form, not legal advice, and this workflow does not replace a lawyer's review of your base agreement. If you have no agreed scope in writing, write that down first: a change order cannot measure a change from a scope that was never stated.
The one rule the whole workflow rests on: no extra work starts until the client approves the change in writing. A verbal "go ahead" on a call, a thumbs-up in chat, and a "just do it and bill me" are not approvals. The work starts when the signed order exists, not when the request arrives.
What "done" looks like
At the end of one sitting you have a classified request, a one-page change order with the added work, the price, the schedule impact, and a sign-off line, a short client email carrying it, and a one-line entry in your decision log recording the outcome. If the client approves, the extra work has a price and a date before it begins. If the client declines, the signed scope stands unchanged, and the request is parked, not worked for free.
Steps
- Put the agreed scope and the new request side by side. Paste both into the agent's workspace: the scope as agreed, and the client's request quoted exactly as they sent it. Ask the agent for one thing first — a short statement of what is different between the two, in plain words, with no price and no draft yet. Read that statement against both texts yourself. If the agent describes the request as inside the scope when it plainly is not, the classification in the next step will be wrong, and everything after it will be wrong with it.
- Classify the request before pricing it. Use a three-color scale. Green is a swap of equal effort inside the existing hours: one deliverable out, one of the same size in, no change to price or date. Yellow is a small addition, no more than four hours of work, billed at your rate after written approval. Red is significant new work: a separate quote and a new timeline. Ask the agent to classify the request and to say, in one sentence, which part of the agreed scope the request goes beyond. If the request straddles two colors, it takes the higher one. A red request priced as yellow is the exact loss this workflow exists to prevent.
- Price the change from your own numbers, not the agent's guess. Give the agent your rate and your own estimate of the hours, or the flat fee you charge for work of this kind, and ask it to show the arithmetic: hours times rate, or the flat fee, plus the schedule impact in business days. Check both figures yourself before they go anywhere near a client: the agent does not know your rate unless you gave it, and it does not know how long the work takes unless you estimated it. A price the agent invented is a price you will have to defend or absorb.
- Draft the one-page change order. Ask the agent to draft a single page with six fields and nothing else: the project and the change-order number; what is added, in the client's words; what is removed or swapped, if anything; the price, with the arithmetic shown; the schedule impact, in business days added to the delivery date; and a sign-off line with a place for the client's name, signature or written approval, and date. Keep it to one page. A change order that needs a second page to explain itself will not be read in full, and an unread change order is not an approval.
- Write the client email from the order, not from the conversation. Ask the agent to draft a short email that carries exactly what the order says: what is being added, the price, the schedule impact, and one line asking the client to reply with approval or to decline. Do not let the draft apologize, discount the price, or offer to start early. The email's job is to make the choice easy: approve, decline, or ask a question. A client who replies "approve" in email has approved in writing; a client who replies with a question has not, and the work still waits.
- Send it, and stop work on the change until the reply arrives. Send the order and the email yourself. The original scope's work continues; the changed work does not start. If the client calls and says "just go ahead," the answer is the order: "Happy to — reply approve to the email and I start today." That sentence is not awkwardness; it is the whole point of the page you just drafted. Starting early to be helpful converts a priced change back into a favor, and favors do not get invoiced.
- Log the decision in one line, whatever it is. In a decision log — one note, one row per change — write the date, the request in a few words, the color, the price, the schedule impact, and the outcome: approved, declined, or parked for a later phase. A declined yellow request that the client asks for again in three weeks is a new decision, not a reopened argument, and the log is what makes that true. At invoice time, the log is the record of every change that was priced and approved, and every one that was not.
- If the client declines, park the request in writing. Reply once, briefly: the signed scope stands, the requested change is parked, and it can be revisited as a new change order later. Do not work on it in the meantime, and do not let it drift back into the project as a "small tweak" in a later revision round. Revision rounds are for the agreed scope; a declined change stays declined until a new order approves it.
Check the agent's work
- Check that the difference statement in step 1 quotes the request and the scope fairly. A statement that flatters the request into the scope is the first error, and it poisons the classification.
- Check the color classification against the scale: green means equal effort inside existing hours, yellow means no more than four hours, red means a separate quote. A request that takes the lower color without a reason is misclassified.
- Check the price arithmetic yourself: hours times your rate, or the flat fee you set. No figure the agent supplied without your numbers survives this check.
- Check that the change order fits on one page and carries all six fields, including the sign-off line. A missing sign-off line is a missing approval mechanism.
- Check that the client email says only what the order says, and that it asks for a written reply. An email that promises a start date before approval has already given the change away.
- Check that the decision log has one line for this request, with the outcome recorded, before you move on to other work.
What can go wrong
- Starting on a verbal approval. A call ends with "sounds good," the work gets done, and the invoice is disputed. Written approval is the rule because memory is not a record.
- Pricing a red change as yellow. A significant addition billed as a small one leaves the extra hours unpaid and the schedule blown. When a request straddles two colors, it takes the higher one.
- Letting the agent set the price. The agent has no access to your rate card, your costs, or the client's budget. Every figure in the order traces to a number you supplied.
- A change order with no sign-off line. A page that describes the change beautifully but gives the client nowhere to approve it is a memo, not an order. The sign-off line is what makes it binding.
- The declined change creeping back in. A parked request that reappears as a revision-round tweak gets worked for free. The log entry is the guard: declined stays declined until a new order says otherwise.
Limits
- This workflow prepares a business form; it is not legal advice, and it does not make a change binding on its own. Your base agreement, and a lawyer's review of it, decide what an approval means for your work.
- The color scale is a working classification for pricing and approval, not an industry standard. Green, yellow, and red mean what your agreement says they mean, and the scale should be stated in the agreement before the first change arrives.
- No fee, rate, or schedule figure on this page is a quote for your work. Every figure in a change order comes from your own numbers, checked by you before it is sent.
Related playbooks
- Draft clinic booking replies with an agent, without inventing times or fees
- Draft a repair-request letter from your own records, nothing invented
- Draft customer replies with ChatGPT, and send every one yourself
- AI freelance work pays more, in bigger chunks
Sources
Sources: JeffBullas — Red/Yellow/Green change scale and stop-work line, ScopeChange — change orders before unpaid work.
Back to: Everyday playbooks hub · Also: Write Upwork proposals with an agent, without inventing anything · Chase an unpaid invoice with an agent