On most new build sites, the trades are organised by package. Groundworks, scaffold, brickwork, roofing, fall protection and external works each have their own subcontractor, their own programme and their own definition of finished. The places where one package ends and the next begins are interfaces. And on a busy site, interfaces are where programme weeks quietly disappear.
A scaffold contractor hands over to a roofer. The scaffold meets handover standard at the moment of inspection. By the time the roofers arrive five days later the boards have shifted, the kick rail is loose at one bay, and the lift below the eaves no longer offers safe working. The roofers stop, raise an RFI, wait for the scaffolder to attend and lose two days. Multiply that pattern across forty plots on a phased site and the cumulative drift becomes a material commercial number.
The same dynamic shows up between groundworks and external works, between roofing and rainwater goods, between scaffold and brickwork loading. None of it is any one trade’s fault in isolation. Every package signs off to its own checklist. The problem sits at the joins, not inside any single contract.
Interface management is the discipline of making sure each handover leaves the work in the condition the next trade actually needs, rather than the condition that satisfied the outgoing one. It means designing the sequencing at programme level, briefing both sides ahead of the handover and inspecting jointly rather than sequentially. Done properly, it converts what would have been an RFI into a thirty minute conversation on site.
Most developers and principal contractors recognise the issue. Fewer have a clean way to solve it when every package is procured from a different supplier. The contractor who won the scaffold package has no contract to deliver in a way that protects the roofer. The roofer has no leverage to influence how the scaffold goes up. The principal contractor sits in the middle and absorbs the friction in the programme.
This is one of the operational reasons multi-discipline groups exist. When scaffold, roofing, civil engineering and fall protection are all delivered by businesses under shared ownership, the interfaces become internal rather than contractual. The scaffolder knows the roofing programme because it is the group’s own roofer arriving. The fall protection installer plans clearance against the same scaffold drawings, not a separate set. The civils team understands what condition the formation needs to be in for the next package because both teams report into a shared programme review.
The commercial result for developers is fewer pause points, fewer RFIs sitting open and a tighter weekly output. None of it shows up dramatically. It shows up as a programme that holds its dates without intervention.
Interface management does not disappear inside a group, but the cost of getting the joint conversation to happen drops significantly. Trades coming from outside the group still need joint inspections, joint method statements and properly sequenced handover. The point is that the friction of arranging those conversations falls away when the parties already share an operating language.
For developers running phased schemes, interface management is also where pre-construction value engineering pays back. Decisions taken at design stage about which packages are bundled, which subcontractors carry which scope and where the handovers sit are the decisions that determine whether the live site runs efficiently or chases its own tail. Once those decisions are baked in, changing them mid-programme is costly.
It is also where developers see the clearest reason to look past the headline rate on any single package toward an integrated procurement model. The lowest unit cost on any one trade rarely turns out to be the largest cost on a scheme. The cost of a disrupted programme is.
Talk to the Globe Group To discuss interface management across trades on your scheme on your scheme, contact the Globe Group on 01223 890727 or email enquiries@theglobegroup.co.uk.
