Insights article
Project planning detail / licensed stock image
On this page
A cabling proposal is a description of work, not only a number. The lowest total can be the most expensive choice if it leaves out containment, termination, testing, labeling, making good, or the access arrangements needed to complete the job.
The aim of comparison is not to find the longest document. It is to confirm that each proposal is answering the same question and that the differences are visible.
Compare the scope
Check the quantities and the boundaries. How many outlets, devices, cabinets, or areas are included? What type of cabling is proposed? Is containment included, or is it assumed to be existing? Are terminations, labeling, testing, and handover part of the work?
- The areas and quantities covered by the price.
- The cabling and containment specified.
- Termination, labeling, testing, and documentation responsibilities.
- What happens at the edges of the scope: making good, access, and disposal.
Look for assumptions and exclusions
Every proposal makes assumptions. The useful ones say so. Look for statements about existing conditions, available routes, access hours, other trades, and what will happen if the site differs from the drawings. An exclusion is not automatically a problem; an unstated exclusion is.
Check the deliverables
What will exist at the end that did not exist at the start? A working connection is the minimum. Clear labeling, an updated record of outlets or cabinets, and any agreed test information make the installation easier to maintain. The exact deliverables should match the project's needs, not a generic package.
Ask how changes are handled
Existing buildings change. A proposal should explain how additional work is priced, who authorises it, and how it is recorded. A clear change process protects both sides from surprises.
Check the schedule and responsibilities
Compare the proposed sequence, not just the duration. Who supplies equipment? Who coordinates access? Who is responsible for other trades? What happens if the space is not ready? A proposal that assumes perfect conditions may be less reliable than one that names the dependencies.
A short comparison checklist
- Are the quantities and areas clearly stated?
- Are containment, termination, labeling, and testing included?
- Are existing conditions and access assumptions explicit?
- Are exclusions named rather than left unstated?
- Is the handover information defined?
- Is there a clear change process?
- Do the schedule and responsibilities match the wider project?
A good proposal does not need to be complicated. It needs to make the work legible enough that you can compare it with confidence and know what you are approving.
Further reading



