The variation register is empty and the job is half built
What's been instructed, what's been priced, what's been agreed - nobody can say.
What's happening?
Half the job is built and the register that should be tracking its change is empty, or lives in one surveyor's head. Instructions are scattered across emails, meeting minutes and conversations; some were confirmed in the contract's form, most were not; and nobody can answer the three questions a variation account stands on: what has been instructed, what has been priced, what has been agreed.
The damage is monthly, not just at the end. Change that is not on a list does not make it into the application, so every cycle quietly undervalues the job, and the longer the register stays empty, the more the eventual reconstruction depends on other people's memories and goodwill. A register built mid-job is a sweep of the record as it stands, instructions captured and numbered, each with a status; kept from there, every new change gets confirmed, priced and carried into the month it belongs to.
The solution
The register built now, and kept as the job runs.
