Rewriting the Brief Mid-Job
A change agreed and recorded keeps the specification governing the work; the same change issued as a direction quietly replaces the specification with you.
Reads as a businessReads as employmentCuts both waysDepends where you are
Four factors, and no total. Every bar is the same length: the side is the claim, the size is not. The heaviest factor in most tests, and the easiest one to give away by accident.
Changing what was asked for is entirely normal. The mechanism is what matters: a change agreed and written down keeps the specification governing the work, and a change issued as a direction quietly replaces it with you.
The management distinction in “Rewriting the Brief Mid-Job” matters when software turns a brief into a continuous stream of instructions. Teams considering explore the provider’s implementation page for cognitive offloading should define the outcome being measured, limit access and preserve the contractor’s ability to organise the method where the agreement requires it.
Most engagements that end badly contain half a dozen of the second kind and none of the first.
For another operational perspective on “Rewriting the Brief Mid-Job”, consult ProofHub project-management articles. Compare it with the actual statement of work, jurisdiction and supplier relationship before adopting a general practice.
What a change actually is
Any difference between what the work was described as and what it is now expected to be. New requirements, removed requirements, a moved date, a different standard, a constraint that has appeared.
Not every change is large. The size is irrelevant to whether it gets recorded; the point of recording is that the description keeps matching reality, and small undocumented changes destroy that as effectively as large ones.
The two-line version
Nobody needs a formal variation process for most work. Two lines in a message, acknowledged, does the job:
Change agreed 14 March: the export also has to handle the Irish entity. Estimate moves from six days to eight. Everything else unchanged.
That is enough to re-establish what is being delivered, what it costs and what the date is. A minute's work, and hardly anybody does it.
Why the cost conversation has to happen
A change that nobody prices is a change the supplier absorbs. Done once, that is goodwill. Done repeatedly, it is a buyer who has discovered that this supplier will not push back, and a supplier who is quietly subsidising the engagement.
The supplier's eventual responses are to raise the rate, decline the next job, or deliver the change badly. All of them are worse for you than the conversation.
The change that reduces the work
These exist and buyers rarely raise them, which is a mistake. If a requirement has been dropped, saying so is how the supplier knows not to spend three days on it.
It is also the cheapest credibility available in a commercial relationship. A buyer who adjusts the scope in both directions is treated differently from one who only ever adds.
When the change is really a new piece of work
There is a point at which adjusting the specification stops making sense and the honest answer is that this is a second engagement.
The signals are familiar: the estimate has more than doubled, the original deliverable is no longer recognisable, or the change was requested by somebody who was not part of the original conversation. Treating it as a new piece keeps both the description and the pricing clean, and gives both sides a decision point.
The accumulation nobody sees
A single engagement with fourteen small undocumented changes has no specification left. Ask two people what the work is and you get two answers, both sincere.
At that point every instrument in this collection has gone. You cannot reject against a document nobody agrees on, you cannot say the work is late against a date that moved three times, and the only remaining way to manage is to tell somebody what to do.
Keeping the record somewhere other than a thread
Message threads are where changes go to be lost. They are searchable in theory and unusable in practice, and they vanish when somebody leaves.
A single dated list per engagement, appended to, is enough. It does not need a system. It needs to exist and to be somewhere other than one person's mail.
Who is allowed to change it
Worth deciding before it matters. In many businesses the person who agreed the work is not the only one talking to the supplier, and changes arrive from three directions with nobody reconciling them.
A supplier receiving conflicting direction from several people in your business will either follow the most recent or the most senior, and whichever they pick you will have an argument about it later.
The change that arrives as an opinion
Not every change is phrased as one. A comment in a review, a remark that something would be better the other way, a forwarded message from somebody senior — each of these lands on a supplier as instruction whether or not anybody meant it that way.
Suppliers generally act on them, because declining to act on a buyer's stated preference is commercially awkward. If you did not mean it as a change, say so in the same breath; if you did, it is a change, and it belongs on the list with everything else.
What to do with the ones already lost
For a long-running engagement with no change history, there is a repair that costs an hour: write down what the work is now, send it, and ask the supplier to confirm or correct it.
That does not recover the history and it does not need to. It re-establishes a shared description from today, which is the thing every subsequent instrument depends on.