In brief: most installation disputes trace back to something that wasn’t written down clearly at the start. A detailed scope of works, agreed before installation, prevents most of them.
The root cause
When an installation goes wrong, it’s usually because two people had different ideas about what was agreed. A clear scope of works closes that gap before work begins.
Why the wording matters
Compare “install CCTV as required” with “supply, install, configure and commission the listed cameras to provide the agreed fields of view shown on the system drawing.” Either could appear on a one-page quote. The first can mean almost anything. The second can be checked against what was delivered.
What a scope of works should include
- What’s included
- What’s excluded
- The assumptions behind the price: power, cable routes and access
- How the system will be tested and handed over
Assumptions and changes
Every quote rests on assumptions that don’t always survive contact with the site. Changes are normal. What matters is recording what changed, why, and who agreed it, so nothing is lost between a decision on site and the handover documents.
Simple, and often skipped
A detailed scope of works costs nothing to write and prevents most disputes. Yet it’s one of the most often skipped documents in a project.
Electronic security for over a decade, after an early career in IT networks.