Free tool · nothing is uploaded
Variation builder
A client rep asks for a change on site. It gets built, because that is what site people do. Six weeks later it is disputed and nobody wrote down who asked, when, or what it affected. This records it on the day, in a form that survives the argument.
The variation that gets built and never gets paid
The pattern is always the same. Someone with apparent authority asks for something on site. It sounds minor. The crew do it because stopping costs more than doing it. Nobody writes it down because it is small, and small things do not feel like variations. Then thirty of them add up, the job finishes, and there is no record of who asked for any of it. The fix is not a better argument at the end. It is two minutes on the day — who asked, when, what changed, and what it affects.
Questions
Does filling this in mean I get paid?
No. It means there is a record. Entitlement comes from the contract, and most contracts require formal notice within a short period. This does not replace that notice.
What if I was told verbally?
Record it as verbal, with who said it, when and who else heard it, then confirm it in writing to the person who instructed it. A verbal instruction that is confirmed in writing on the day is far stronger than a memory six months later.
Should I price it before I do it?
Where the contract allows the time, yes. Where it does not, record the instruction and the fact that pricing follows — but never let the absence of a price be the reason nothing is recorded.
Is anything uploaded?
No. It stays in your browser on your device.
Related free tools
Thirty small variations is where the margin goes
The Obras variation register captures each one at the moment it is instructed, against the work it affects, so the commercial position is current rather than reconstructed at the end.
