Approved on WhatsApp, Built on Monday, Invoiced Never
· 7 min read · Written by Faceela Research & Editorial Team
Reviewed by Ahmed Hassan Algammal — Founder and Enterprise Systems Consultant
The client walks the site on Thursday. He wants the shelf 200 millimetres lower and the drawer front changed to match the island.
The foreman says no problem. He means it — it is genuinely no problem, it is two hours in the workshop and a new front, and saying no to a client standing in his own apartment is not a thing a foreman is equipped to do. He sends it to the workshop on WhatsApp. It is built on Monday.
Nothing about that is unusual and nothing about it is wrong, except that it never becomes money.
That is the mechanism this article is about: the change entered the business as an instruction and there was no route by which it could ever become an invoice. Not because anybody decided not to bill it. Because the only person who knew it happened was measured on delivering it, and the only record of it was a message in a chat that scrolled away.
Unbilled approved variations run at 8–12% of contract value in this trade. That is the largest single leak in a joinery or fabrication business, and it is larger than most of the efficiencies people buy software to chase.
The chain, and the link it usually starts at
There is a chain that turns a client's request into money, and it has five links: the client asks, the change is priced, the client accepts the price, production is instructed, and it reaches an invoice.
In most workshops the chain begins at link four.
Production is instructed. That is the first link with a document behind it, because a cutting instruction has to exist for the item to be made. Links one, two and three happened — the client did ask, somebody did decide it was fine, the client did agree — but they happened in a conversation, and a conversation is not a link. It is a memory of a link.
The chain
Five links, and the chain starts at the fourth
1. The client asks
On site, to the foreman, in a voice note or across a half-built kitchen. Move the tall unit, change the handle, add a shelf, take the carcass to the ceiling.
Evidence it produces: A request, with a date and a person attached to it
Where that evidence lives: A phone, until the phone is changed or the chat is cleared
In most workshops: Happens. Is not recorded
2. The change is priced
Extra material, extra hours, a second delivery, a second install visit, and sometimes a panel already cut that is now scrap. All of it knowable in an hour, by somebody who has the job open.
Evidence it produces: A priced variation against the contract
Where that evidence lives: Nowhere — this is the link most often missing entirely
In most workshops: Usually skipped
3. The client accepts the price
Not the change — the price. This is the only link that converts goodwill into money, and it is the one people are most embarrassed to ask for.
Evidence it produces: An acceptance, against a number, before the work
Where that evidence lives: Nowhere
In most workshops: Usually skipped
4. Production is instructed
The cutting list changes, the machine list changes, the material is drawn. This link never fails, because a factory that ignored it would stop.
Evidence it produces: A revised cutting list and a material issue
Where that evidence lives: The workshop, reliably
In most workshops: Always happens
The chain habitually starts here
5. It reaches an invoice
The variation appears on the next application, priced, with its acceptance behind it. It cannot, because links two and three do not exist to carry it there.
Evidence it produces: An invoice line
Where that evidence lives: The accounts, if it ever arrives
In most workshops: Usually never
By link four the change is already built
Links one to three cannot be created backwards. A price agreed after the work is a negotiation; an acceptance obtained after delivery is a favour. This is why unbilled variations in this trade are worth 8–12% of contract value and most workshops bill none of it — not because anyone was cheated, but because the chain was entered three links in.
The message is not the problem. The deletion is
There is a lot of advice in this trade that amounts to "stop using WhatsApp". It is not going to happen and it does not need to.
The message is not the problem. The message is the best evidence in the business: it is timestamped, it names the person, it usually contains a photograph of the actual thing, and the client sent it himself. No variation form ever produced has that much authority.
The problem is that the evidence lives in the personal phone of a site foreman who may not work here in eighteen months, in a chat with four hundred other messages, and it is deleted the day the phone is replaced. By the time the final account is being argued, the strongest document in the case has been overwritten by holiday photographs.
So the fix is not a ban. The fix is a route: a way for that message to become a record inside the business, in under a minute, from the site, by the person who received it. Anything longer than a minute will not happen and anything that requires going back to the office will not happen either.
Where the evidence lives, and how long it survives
| Where the change was agreed | What survives of it | How long it lasts |
|---|---|---|
| Voice note from the client | The strongest evidence in the business | Until the phone is replaced |
| Message in a site group | Timestamp, sender, often a photo | Until somebody leaves the group |
| Said out loud in a site meeting | Whatever two people remember | Weeks, and they remember differently |
| Marked-up print left on site | A drawing with no revision letter | Until the site is cleaned |
| Email to the project manager | A real, dated document | Until he is on another job |
| Note in the foreman's own phone | The only account of why it changed | It leaves with him |
| A recorded variation against the job | Request, price, acceptance, instruction | As long as the business does |
Six of those seven rows are evidence held by a person. The seventh is evidence held by the company, and it is the only row on which a final account can be argued.
The foreman is measured on delivery, not on margin
Be clear about the incentive, because process documents usually are not.
A site foreman is judged on whether the job is finished, whether the client is happy, and whether the handover happens without a list. He is not judged on margin, he is not given a price list, and he is frequently not told what the item was sold for. Asking him to defend commercial value is asking him to do a job nobody gave him.
So when a client asks for a change, the foreman evaluates it against the only measure he has: can we do it. The answer is nearly always yes, and he gives the answer that keeps the job moving, which is the answer the business actually wants from him on every other subject.
Fixing this by telling foremen to be more commercial does not work and has never worked. What works is giving him an action that takes less effort than not doing it: record the change, attach the client's own message, and let somebody whose job is pricing do the pricing. He is not being asked to say no. He is being asked to say "noted" in a place that is not a chat.
The refusal that works
There is exactly one control that closes this, and it is structural rather than cultural.
A change instruction cannot reach production unless a variation exists against it.
Not a priced variation, and not an accepted one — that would stop the job, and stopping the job is how controls get bypassed within a fortnight. A variation record, with the request on it and the client's message attached, in whatever state it is in. Priced later. Accepted later. Invoiced later.
What that refusal does is move the capture point from link four to link one, at zero cost to the programme. The item still gets built on Monday. It simply cannot get built without existing, and once it exists somebody can price it, and once it is priced the conversation with the client is a conversation about a number rather than about whether it happened.
The same logic, on a contracting scale, is most variation money is lost before anyone argues about price, and its financial shadow is work that was done and never billed.
What to make a vendor show you
On a live system, on a real job, not on slides.
- Raise a variation from a phone, on site, with a photograph attached, in under a minute.
- Attempt to instruct production for a change with no variation record, and show the system refuse it.
- Show that refusal surviving an override, with the override leaving a record naming who did it.
- Show the variation carrying the client's own message and the date it was received, not a retyped summary.
- Price the variation and show it against the job's margin before anybody accepts it.
- Produce every variation on a job that is built, priced, and not yet accepted by the client.
- Produce the same list across every live job, oldest first, with a value on it.
Item 6 is the one that decides it. Every system can raise a variation and most can invoice one. A system that can show you the changes that are already physically built and not yet agreed is showing you the money that is currently leaving the business, this week, before it becomes a final-account argument you will lose.
Item 7 is that same figure for the whole company, which is the number the owner has never once seen.
The short version
Approved changes that never get invoiced are worth 8–12% of contract value in this trade, and they are not lost to disputes. They are lost to never having been written down.
The chain from request to invoice has five links, and in most workshops it starts at link four, because instructing production is the first step that requires a document to exist.
The WhatsApp message is not the failure — it is the best evidence anybody has, timestamped and sent by the client himself. It fails only because it lives on a personal phone and is deleted when the phone is replaced.
The foreman who agreed to it is measured on delivery and has no price list, so he answers the only question he was equipped to answer. The repair is not to make him commercial. It is to make recording the change take less effort than not recording it, and to refuse production to a change that has no variation behind it.
What that looks like built is Flow, on the joinery, steel and fabrication page. Nearby: the approval gate that decides whether a change is billable at all, what the site did to the installation price, and why the estimate never learned from the job. If you want the size of the leak before you fix it, the cost of chaos calculator is the shortest route to a number.