Why IT and security projects run late, and how to prevent it.

Projects rarely slip because of the technology. They slip because of everything around it.

Common causes

• Unclear scope. Different people expect different things.
• Site not ready. Power, civil work, ceilings, conduits and access are not finished when engineers arrive.
• Long lead times. Specialist equipment, imports and approvals take weeks.
• Late decisions. Colour, position, brand or user lists are agreed after work starts.
• Missing approvals. Landlord, fire, statutory or customs paperwork.
• Dependencies on other trades. Electricians, interior teams and civil contractors.
• Change without control. Extras added without adjusting the schedule.

Controls that work

1. A written scope and a bill of materials with named alternates.
2. A site readiness checklist signed before mobilisation.
3. Early ordering of long-lead items.
4. A decision log with dates and owners.
5. Weekly progress reviews with a short risk list.
6. A change process that states cost and time impact before work proceeds.
7. Phased handover so areas go live as they finish.

For multi-site programmes

Standardise the design, stage equipment centrally and run installation in waves, with every site tracked on a visible board.

The honest conversation

A good supplier tells you early when something threatens the date, and offers options.