Direct answer
Name one decider in writing, and let no change move the work until it is a dated, priced change on the job record.
The job starts with one brief and one person who approved it. A week later a colleague joins the calls, then a manager, then someone from another team, and each of them arrives with a small adjustment: a different audience, an extra section, a new priority. None of them thinks they are changing the brief, because each change is small and each person assumes the others agree. You are the only one who sees the total, and by the time the delivery is judged, it is judged against a brief that exists in five heads and matches none of them. The goalposts do not move because anyone is dishonest. They move because the job has many voices and no single decider, and no record of which version of the brief counts. The fix is structural, and it is set once, in writing: one named decider whose word settles the brief, every change from anyone else treated as a note until the decider adopts it, and every adopted change landing on the job record as a dated, priced change before the work moves. This page gives you the rule, the exact reply for when a change arrives, and the clause that stops the pattern on the next job.
Updated November 20, 2026. First published November 20, 2026. The records quoted below are real and public, read back from the live service on November 20, 2026.
Step 1. See the real problem: many voices, no decider, no version that counts
A brief is a decision, and a decision needs an owner. When three people can each adjust the brief, the brief is whatever the last person said, and the delivery is measured against whichever version the judge happens to remember. The symptoms are familiar: feedback that contradicts last week's feedback, approval from one person reversed by another, and a final review where the work is marked down for missing something that was removed by someone else in week two. Arguing about who said what cannot fix this, because every party is honestly reporting their own conversation. What fixes it is agreeing, before the next change lands, on two things: the name of the one person whose instruction changes the brief, and the place where the current version of the brief lives, open to both sides, so that the version that counts is a page and not a memory. Everything else on this page is machinery for holding those two agreements.
Step 2. Name the one decider in writing, and say what everyone else's input is
The decider is named in one short written exchange, ideally at the start of the job and workable at any point: so the work stays on one track, changes to the brief come through one person. Name the decider, and name what happens to input from everyone else: it is welcome, it is read, and it lands as a note for the decider to adopt or set aside, not as an instruction that moves the work on its own. This is not a demotion of the other voices, and it should not be framed as one. Colleagues keep full sight of the job and full ability to argue their case to the decider; what they lose is only the ability to move your work directly, which most of them never knew they had. The decider, for their part, gains the thing busy clients actually want: one place where the state of the brief is true, and no surprises at delivery time about which version was built. If the client cannot name a decider, the job is not ready to start, and a smaller first stage is the honest shape until they can.
Step 3. Land every adopted change as a dated, priced change on the job record before work moves
Adoption is a visible act, not a mood. When the decider takes up a change, it goes on the job record the same day, in one line that carries four facts: what changes, the date it was adopted, what it does to the price, and what it does to the delivery date and the remaining steps. Work moves only after that line exists. This single habit ends most goalpost disputes before they form, because the argument later is never about whether a change was agreed; the record shows the change, its date, and its price, accepted by the named decider. It also protects the client: a change nobody priced cannot quietly become a larger invoice at the end, because the price effect was stated and accepted on the day the change was adopted, or the change was adopted at no change to the price, which the same line says. Small changes get the same treatment at smaller weight: a one-line record entry takes a minute, and a month of one-line entries is the complete history of how the brief grew, readable by anyone the client adds next.
Step 4. Keep the brief version both sides can open as the one that counts
The record only settles arguments if both sides are reading the same record, which is why the brief lives on the job record itself rather than in a thread either side can fork. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), created by Brennan Zambo, and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show the decision states a job moves through:
Accepted: the decision is on the record
- Status: accepted, decided_by client, decided_at 2026-10-16T14:31:51.146Z, release_hint ok_to_release.
- Steps: 4 steps total, 4 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
Pending: checked, and still waiting on a decision
- Status: pending, release_hint hold.
- Steps: 5 steps total, 5 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
Read the accepted record as a brief state made visible: status accepted, decided_by client, decided_at 2026-10-16T14:31:51.146Z, release state ok_to_release, 4 steps checked. A decision has a decider and a date, and anyone added to the job later can open it and see exactly what was settled and when. The pending record shows the other state: 5 steps checked, release state hold, still waiting on its decision, which is exactly what a change looks like before the decider adopts it: noted, visible, and not yet moving the work. Run the brief this way and a new voice joining in week three is an onboarding task of ten minutes, open the record and read the current brief and its change history, instead of a fresh negotiation conducted from memory.
Step 5. Answer every change with what it moves: price, date, steps
The reply to any proposed change, from the decider or relayed from anyone else, has one shape: Happy to do it. Here is what it moves. The change adds [work] to step [n], moves the delivery date from [date] to [date], and adds [amount] to the fee, or, where true, it fits inside the current scope at no change to price or date. Confirm and I will record it and start on it today. Notice what the shape does: it never refuses, it never complains about the number of voices, and it never starts the changed work on the strength of the message alone. It prices the change while the change is still a proposal, which is the only moment pricing it is easy, and it routes the confirmation to the decider, so a colleague's enthusiasm cannot commit the client's budget. When the decider confirms, the change lands on the record as in step 3 and the work moves. When nobody confirms, the brief stands as recorded, and the delivery is judged against it, which is the whole point.
Honest limits
This page is general information about running a brief, not legal advice: what counts as an agreed change under an existing signed agreement is set by that agreement and by local rules, and a large or regulated engagement deserves advice for your situation. Naming a decider organises instructions; it cannot make a client organisation agree internally, and where the decider themselves keeps reversing settled points, the priced-change record is what keeps the cost of each reversal visible and fairly shared. A verifiable receipt proves the saved result was not changed since it was saved; it does not prove a change was wise, which is why the decider accepts the change itself, in words, on the record, before the work moves.
Step 6. Put the one-decider rule in the next agreement, so the pattern never starts
Two short lines in your standard terms settle this before the first call: brief changes are instructed by the named decider only, and each instructed change is recorded with its effect on price and delivery date before work on it begins. With those lines agreed in advance, adding people to the job becomes harmless, because every new voice already knows the route their input travels, and the decider knows the record is where their decisions live. Clients with genuine multi stakeholder work are usually relieved by the rule rather than resistant to it: it gives them one internal conversation to have, with you out of the middle of it, and a delivery that matches the brief their own decider settled. The goalposts stop moving not because anyone is pinned down, but because the posts are now written on a record both sides can open.
Frequently asked questions
My client keeps adding new people who change the brief after we have started. How do I stop the goalposts moving?
Stop them structurally, with two written agreements. First, name one decider: changes to the brief come through that one person, and input from everyone else is treated as a note for the decider to adopt or set aside, never as an instruction that moves the work on its own. Second, land every adopted change on the job record before work moves, as one dated line stating what changes, what it does to the price, and what it does to the delivery date and steps. The brief version both sides can open is the one that counts, so a new voice joining later reads the current brief and its change history instead of renegotiating from memory. Answer every proposed change with what it moves, price, date, steps, and start the changed work only when the decider confirms.
What do I say when someone who is not the decider asks for a change?
Welcome it, write it down as a note, and route it to the decider without starting it. The working reply is short: noted, thank you, I will add it to the record as a proposed change for [decider] to settle, and here is what it would move on price and date if adopted. That shape respects the person, keeps their idea visible, and holds the line that only the decider's adoption moves the work. Most non deciders accept this instantly once it is explained as protecting their own side from contradictory instructions, because many of them have been on the receiving end of exactly that problem inside their own organisation.
Should every small change be priced, even tiny ones?
Every change is recorded; not every change carries a price. The record line states the price effect honestly either way: adds a stated amount, or fits inside the current scope at no change to the fee. Recording no-cost changes matters as much as pricing costly ones, because the dispute at delivery is usually about scope, what the brief finally was, not about any single charge. A month of dated one-line entries, priced and unpriced, is the complete growth history of the brief, and it is what lets you show, calmly, that the delivered work matches the brief as last settled by the decider.
What if the decider keeps changing their own mind?
Then the record earns its keep in a different way: each reversal is a change like any other, dated, with its effect on price, date, and steps stated before work moves, and accepted by the decider in words. A decider who can see the running total of what reversals have moved, in money and in days, usually settles quickly, because the cost of changing course is visible at the moment of deciding rather than discovered at the invoice. If reversals continue, the honest conversation is about the pattern itself, held with the record open: here are the six changes this month and what they moved, and here is the shape, fewer larger decisions, a freeze date before delivery, that would serve the work better.
How does a job record help when the brief keeps changing?
It gives the brief one home that both sides can open, with a decision history instead of a pile of threads. When the work runs through Zambo, built by Brennan Zambo, every job lands on its own record with a verifiable receipt for each step under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, so the current brief, each dated change with its price and date effect, and the acceptance state of each step sit on one page the decider and every added colleague can read. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. For $0.99, run your next multi stakeholder job on one record, so the next new voice reads the brief instead of rewriting it: get the Day Pass. A Day Pass is unlimited for 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month, $19 a month for $ZAMBO holders, or Lifetime at $250 one time.
Related
- The contract for AI and freelance work, with delivery both sides can check
- My client keeps asking for more revisions. How do I stop endless revisions?
- My client will not give feedback and my deadline is passing. Should I keep working or stop?
- Should I give a client a discount for paying the whole fee upfront?
- My client disputes the hours I billed them for. How do I prove the time I worked?
- Start with your problem: every problem in this directory, routed to its page