The brief changed and nobody wrote it down
Six weeks into the project, on a status call about something else, the client says it is obviously mainly for the sales team now. Then they move on, because as far as they are concerned they have not said anything. The brief, signed in March, says the audience is customers. Nobody is lying and nobody notices.
That is how briefs change. Not by amendment, which would be a document and a conversation and possibly an invoice, but by erosion: a sentence at a time, each one entirely reasonable, none of them announced. By the end you are delivering against a brief that exists in one person's head and was never written down anywhere.
Nobody ever says the brief has changed
There is a reason for that, and it is not carelessness. Saying the brief has changed opens a conversation about money and time, in front of colleagues, with somebody who is under their own pressure. Saying it as a clarification opens nothing at all. So the change arrives dressed as a clarification, every time, and the vocabulary is so consistent you can learn to hear it: obviously, just, I assumed, we always said, to be clear.
It arrives in four shapes. Somebody new joins on the client side, carrying a set of assumptions nobody has ever read out. The audience moves, usually inwards, from the people who buy the thing to the people who have to sell it. A constraint appears late — legal need to see it, it has to work in the old system, the budget for the third phase went. Or a date moves, which almost never shortens a phase; it deletes one, quietly, and the phase it deletes is usually the one where the thinking happened.
There is an asymmetry underneath all of this that is worth holding on to, because it stops the whole subject curdling into a story about difficult clients. The person who says it is mainly for the sales team is not making a change. They are describing the project as they now understand it, and they have understood it that way for a fortnight, in meetings you were not in. From where they sit they are being helpful. The change happened somewhere you could not see it, and the sentence is only where it surfaced.
Five places a brief is kept, none of them current
The reason this is hard to catch is not that the changes are hidden. It is that there is no single document the changes could be applied to, because by week six the brief is distributed across five things that disagree with each other.
| Where a version lives | What it holds | How current it is |
|---|---|---|
| The signed brief | The audience, the deliverables and the budget as they stood at the start | Right on the day it was signed and untouched since |
| The kickoff conversation | The assumptions underneath all of that, almost none of which were written | Still exactly right, if anybody kept it |
| Six status calls | Every change that has happened, scattered through six hours of other talk | Entirely current and entirely unusable without a way to search it |
| The client's head | What the work is for now, and what they will actually judge it against | The only complete copy, and the one you cannot read |
| The project channel | About half the constraints, each in the middle of a different conversation | Current, unordered, and never read back by anybody |
Read down that last column and the shape of the problem is obvious. The only complete version is the one in somebody else's head, and the only version anybody signed is the one that is furthest out of date. Everything in between is either an hour of talking or a channel, and neither of those is a document. The work will be judged against the copy you cannot read, by somebody who is not aware they are holding a different one.
The kickoff is the part worth keeping
The signed brief records what was agreed. The kickoff conversation records what the work is for, what it is instead of, and what everybody in the room took for granted without saying — and that second set is where every later argument comes from. Record it and you have it: the hour itself in text, a summary in proportion to it, and the decisions standing clear of the discussion they came out of. That is Meeting Notes doing an ordinary job on an unusually valuable hour.
The last ten minutes are the part to stay for. Agendas end and then people relax, and it is in that stretch that somebody says what they are actually worried about, or who they will have to show it to, or what the last agency got wrong. None of that will reach the brief document. All of it will be used to judge the work.
Noticing a change while it is still cheap
- Record the kickoff, and stay to the end of itThe formal half tells you what to build. The ten minutes after somebody says "anyway, that's probably everything" tell you what it is being measured against. Both are the same recording, and only one of them was ever going to make it into a document.
- Say the line the brief does not containBefore the call ends, read one sentence back: who this is for, and what it is instead of. Twenty seconds. If it is wrong you find out immediately, and if it is right it is now in the transcript in the client's own agreement rather than in your interpretation.
- Ask the record before each phase, not after itOne question at every gate: has anything been said since kickoff that changes who this is for? Two minutes, before the expensive work starts, and it is the only step here that reliably saves a fortnight.
- Raise it as a question with a date attached"On the 14th you mentioned it is mainly for the sales team now — is that a change to who we are designing for?" A date makes it specific. A question makes it answerable. Between them they turn an accusation into an agenda item.
- Send the amendment to whoever holds the moneyOne paragraph, the same day, to the person on their side who owns the budget rather than the person who said it. Not to build a case: so that the change is on the record as a change while it still costs a conversation instead of a phase.
Finding the sentence
Sooner or later you will be sure the brief moved and unable to say when. Ask Ona answers from the calls you have recorded and carries the source along with the answer — which call, and where in it — so you can read the ten seconds either side and see the words in context. Often the context is the whole finding: a change delivered as an aside reads nothing like one delivered as a decision.
Knowing the date is for you, not for them. Almost no account has ever been improved by being shown a transcript, and a studio that starts doing that has traded a client relationship for a case file. What the date actually buys is the confidence to raise it as a question instead of a complaint, and to raise it in week three instead of week nine.
We found the exact sentence. It was nine seconds long, in the middle of a call about something else, and everyone on our side had heard it and filed it as chat. Nobody was at fault. We just had no way of noticing that the job had quietly become a different job.
Lucia F., Producer, animation studio
The rest of what a studio argues about
A brief is one of several documents everyone agrees are important and nobody keeps up to date. The others — the change list, the review notes, the thing that was decided on the phone and never typed anywhere — go the same way for the same reasons, and they are taken up on Ona for creative professionals.
Where this stops being a records problem
Knowing exactly when the audience changed does not get you paid for the three weeks it cost. That is a conversation about money, with a person, and it is the same conversation it has always been. A record moves it earlier and makes it specific, which helps more than it sounds like it should, and it does not make it any easier to have.
It does not settle whether a change was a change, either. Two people can read the same nine seconds and disagree in good faith about whether it amended anything, and both of them can be reasonable. What you get is a shared object to disagree about instead of two competing recollections, which is far more useful than being proved right and a good deal less satisfying.
A good deal of it happens where there is no conversation at all. A comment left on a file at the weekend, a forwarded email with two lines added at the top, a change of job title on the client side that nobody mentions for a month. Ona holds conversations and nothing else, so anything that arrived in writing is outside all of this and stays your job to gather.
And the hardest case is the one where there is no sentence to find. Plenty of briefs drift because the thing was never stated in the first place: nobody said who it was for, because everybody assumed that was already settled. A transcript of a conversation in which nothing was said is a transcript of nothing being said. The answer there is not a record at all; it is asking the question at kickoff, out loud, so that there is something to keep.
When the work is already half-built
Not to name it, and naming it late is still much better than delivering into it. Find the moment if you can, then put one paragraph in writing describing what the brief seems to say now against what it said in March.
Send it as a question about direction rather than as a claim about cost. The cost conversation is easier once both sides are looking at the same two descriptions.
Then the habits are what carry it, and most of them need no software. Read the one-sentence line back at the end of kickoff. Ask the direction question at every phase gate. Put the amendment in writing the same day.
The part you give up is finding the nine seconds afterwards, so compensate by writing sooner. A short note after each status call, sent to them the same day, is the closest substitute there is.
No, and the difference is why it goes unnoticed for so long. Scope creep is more work, and more work is visible in a schedule.
A brief change is often the same amount of work pointed somewhere else. The budget looks fine, the plan looks fine, and nothing at all looks wrong until the day the work is judged against a standard nobody wrote down.
Catch the next change while it is still a sentence
Record your next kickoff, stay for the last ten minutes, and read one line back about who the work is for before anybody hangs up.