Mark De Lacey

Mark De Lacey, a Technical Director from Australia who flew over specifically to record this episode, brings decades of experience from steelworks apprentice in Wollongong through mines, a nuclear reactor, Hong Kong, utilities, and transport infrastructure. The centrepiece of the conversation is Interface Requirement Specifications, the mechanism by which a principal defines what is needed at every contract interface, and the two adjoining contractors then produce Interface Control Documents reflecting the detail, with both documents bound into their respective contracts. Mark illustrates the concept with a story of a crane that turned up to site but the embankment it needed to sit on had not been built, because nobody coordinated the interface between two separate contracts. The conversation drills into why the principal not understanding what they actually want is the root cause of project overruns, why gaps and overlaps in contract packaging are equally dangerous, and why changes always cost more than the original work. Andy pitches the idea of bite-sized methodology sequences as construction's equivalent of TikTok content.

Key Topics Discussed

• Interface Requirement Specifications. The principal writes what is needed at each contract interface boundary. The two contractors on either side then produce Interface Control Documents reflecting the engineering and construction detail. Both documents are bound into the respective contracts. This is the mechanism for coordinating multi-contract projects.
• Interface Control Documents. The practical detail documents produced by contractors in response to the principal's interface requirements. They describe exactly how two contracts will physically and programmatically connect, from structural loads to programme sequencing.
• Crane and embankment story. A crane arrived on site but the embankment it was supposed to stand on had not been built. Two separate contracts, no coordinated interface. A vivid example of what happens when interface management fails.
• Contract packaging, gaps and overlaps. Both gaps (nobody owns a scope element) and overlaps (two parties both own it, creating conflict) in contract packaging are dangerous. Getting the packaging right requires the principal to understand exactly what they want delivered.
• Principal understanding. The root cause of most project overruns is the principal not understanding what they actually want. If the brief is unclear, every downstream decision compounds the ambiguity.
• Leadership Development. Changes always cost more than the original work. Avoiding changes through better upfront definition is the single biggest lever on project cost.
• Contracts as last resort. "The moment you reach into that drawer and pull out the contract, ask yourself why." If you can avoid pulling the contract out, that is a fantastic outcome. Contracts should be a safety net, not a daily management tool.
• TikTok for construction. Andy proposes bite-sized methodology sequences, short, digestible content explaining construction methods, sequencing, and interfaces. The industry equivalent of TikTok content.

Notable Quotes

• "The moment you reach into that drawer and pull out the contract, ask yourself why."
• "If you can avoid pulling that contract out, that's a fantastic outcome."
• On project overruns: the principal not understanding what they want is the root cause.
• Andy: "TikTok for construction", bite-sized methodology sequences.

Guest Background

Mark De Lacey is a Technical Director based in Australia. His career started as an apprentice at the steelworks in Wollongong and has taken him through mines, a nuclear reactor, Hong Kong, utilities, and transport infrastructure. He is an expert in large project contract integration and interface specifications, the mechanisms that coordinate scope, programme, and risk across multiple contracts on major infrastructure projects. He flew from Australia specifically to record this podcast episode.