FAQs for Commercial Systems Maintenance

Question 1

Do we have to take the ongoing arrangement?

Accepted Answer

No. It is optional, only offered after a set-up, and every system is handed over built to be run without me. Handover is real: the system is documented in plain language, the team runs it without me before I step back, and nothing about the build assumes a retainer behind it. The monthly arrangement exists because systems drift, not because the system needs me inside it. People leave, jobs change shape, the tools update themselves, and six months of small unnoticed changes can undo a good build; the check catches that drift while each piece is still one conversation. Some firms take it for the life of a job, some run the first few months and then carry it themselves, some never take it at all, and all three are using it as intended. It is a fixed monthly amount, agreed in writing, and it stops at the end of any month with nothing further owed, so the decision is never a trap either way.

Question 2

What does the monthly check actually look at?

Accepted Answer

The month itself: what the systems produced against what the job or the business actually did, so drift is caught while it is one conversation. The check is a comparison, not an inspection. On a project it reads what the systems captured against what the month actually contained: the instructions given against the instructions recorded, the changes that happened against the variation record, the CVR against the position being reported. At business level it reads the month-end the same way: what rolled up on its own against what got re-keyed, where the pack matches the jobs' records and where a number was reshaped by hand on its way to the board. Alongside both sits a check on the tools themselves, because features move and settings reset without asking. The output is deliberately small: a short list of what drifted, each item fixed with the person it belongs to rather than filed in a report, so the check stays a working habit instead of a document nobody reads.

Question 3

Can we stop the retainer and come back later?

Accepted Answer

Stop at the end of any month; nothing further is owed. Coming back later starts with an honest look at how far things drifted. Stopping is a month-end decision and nothing more: no notice period, no exit fee, no unwinding, because the systems are built in your own licences and stay yours whether or not I am checking them. Restarting after a gap is welcome but honest: drift does not pause because the check did, so a return usually begins with a short reading of where the systems now stand, priced in writing like everything else, before the monthly rhythm picks back up. A gap of a month or two is usually trivial; after a year, with new people and changed tools, the reading matters more. None of that is a penalty for leaving. It is the same rule the whole practice runs on: I do not keep something honest without first knowing what it currently is.

Question 4

Will you support systems you did not build?

Accepted Answer

Not directly. Upkeep of a system I have not built starts with a review, because I will not promise to keep something honest without knowing what it is. The monthly arrangements are only offered after my own set-up, and the reason is responsibility rather than salesmanship: a retainer is a standing promise that the record can be relied on, and I cannot make that promise about a system I have never read. A system built elsewhere, whether by your own team or by someone else, is not turned away; it starts with a review like anything else, which reads what is actually there, what it captures, where it drifts and what it would take to bring it onto a supportable footing. Sometimes the honest finding is that it is sound and needs only small changes, and the write-up says so. What I will not do is inherit a black box and invoice monthly for watching it, because the month something went wrong, the promise would turn out to have been decoration.

Question 5

What happens when the tools change under us?

Accepted Answer

That is half the reason the arrangement exists: the monthly check absorbs what the software changed rather than leaving it to break the routine. The tools underneath a commercial system now change every few months whether anyone asked them to: features move, defaults reset, something is renamed, an update quietly switches a behaviour the workflow depended on. Left alone, each of those is a small breakage that somebody works around, and the workarounds are how a clean system decays into the spreadsheet it replaced. The monthly check treats the tools as part of the month: what changed, what that breaks next month if ignored, and what needs adjusting so the team keeps working the same way. Most months that is nothing or nearly nothing; occasionally it is real work, and catching it inside the month is the difference between an adjustment and a rebuild. The team's routine is the thing being protected; the software is allowed to churn underneath it.

FAQs for Commercial Systems Maintenance, Quantity Surveying

Frequently asked questions

Running the arrangement

Do we have to take the ongoing arrangement?

What does the monthly check actually look at?

Can we stop the retainer and come back later?

Will you support systems you did not build?

What happens when the tools change under us?