Chris M.25 August 2026

Design management is a dependency problem, not a document problem

Any single discipline getting something wrong is recoverable. The costly case is structural assuming one thing, MEP assuming another, and nobody finding out until the contractor does.

What were the answers to the previous five questions?

1. Why is design management a harder problem for AI than project management?

Because project management is largely sequential and design management is parallel. Dozens of disciplines generate interdependent information at once, and the failures live in the relationships between documents rather than in any one of them.

2. What is the difference between a clash and a dependency, and which is more dangerous?

A clash is two elements occupying the same space, which is geometric and detectable. A dependency is one discipline relying on an assumption another has quietly invalidated. Dependencies are more dangerous because nothing intersects, so nothing is flagged.

3. A client moves a wall by one metre. What are the second order effects, and why do they matter more than the first?

First order: structural resize, ceiling zones, duct rerouting. Second order: fire strategy assumptions, construction sequence, procurement lead ins, and possibly a gateway re-submission. The second order effects consume the programme, and they are the ones nobody costs at the point of agreeing the change.

4. What information does a system need before it can say anything useful about buildability?

The contractor's actual planned construction sequence, real site constraints including access and existing structures, temporary works requirements, and logistics such as crane capacity and delivery routes. Without those, buildability analysis is guesswork dressed as analysis.

5. What can AI not tell you about Building Regulations compliance, however good the retrieval is?

How the body reviewing it will interpret your approach. Regulations are applied through judgement and interpretations differ, and for a higher-risk building there is no choice of body and no informal conversation at all. What AI can do is align the disciplines' assumptions and expose where they diverge, so the question you put is precise rather than open.

What does the design manager actually have to hold in their head?

On a medium project: structural, architectural, mechanical, electrical and public health, civils, specialist packages such as lifts and fire safety, client requirements, regulatory compliance and contractor buildability input. Forty to fifty documents produced or revised in a month, each carrying a status code and a revision under BS EN ISO 19650, still widely called suitability on site, all interdependent. Note that status and revision answer two different questions: the status code says what the information may be used for, and only the revision says whether it is current.

The traditional response is coordination meetings, design check meetings, an RFI system, specification reviews, mark ups, and the stage sign offs the RIBA Plan of Work 2020 requires at each information exchange. All necessary. All producing more information, which is the recursive part of the problem. The distinction that matters is between Stage 3, where geometry gets coordinated, and Stage 4, where design intent meets contractor's design and specialist design and separate parties' assumptions first have to be true simultaneously. A project that signs off Stage 3 because nothing in the federated model intersected, and calls that coordinated, has the failure below waiting for it.

What fails is rarely a discipline being incompetent. Structural allows half a kilonewton per square metre to the soffit for services and finishes. MEP hangs a chilled water run and a fan coil unit. Architecture adds a ceiling with an acoustic layer. Fire adds protection to the duct. Every discipline sits inside its own allowance, the aggregate does not, and nobody owns the aggregate. Nothing clashes, because nothing intersects.

That is the general shape of it. Clash detection tests nominal geometry. The dependencies that cost money live in tolerance, deflection, aggregate load, construction sequence and third party test evidence, none of which a model represents, and all of which are assumptions one discipline holds about another.

Where does AI actually help?

In three places, ordered by how much of the value they carry.

Task	What the system does	What it must not do
Revision intake	Compare the new set against the approved one: what changed, where, and which disciplines the change reaches	Decide whether the change is acceptable, or approve anything
Clash and tight condition detection	Identify conflicts and near misses, state clearance required against provided, and map each to the responsible party using the design responsibility matrix	Resolve the clash, decide which party moves where the matrix is silent, or rank consequence without the design manager confirming it
Change cascade	Trace a proposed change through every discipline and back, with the sequence in which revisions must happen to avoid rework	Commit to a duration, or treat compliance implications as settled

Cascade is the one that changes the conversation with a client, because it converts a request into a costed consequence before anyone agrees to it.

A one metre wall move traced through first and second order effects. The first order effects are obvious and cheap. The second order effects are where the programme actually goes. On a higher-risk building in England, a change to compartmentation is likely to be a major change requiring the regulator's approval before work starts.

The output is not a duration. It is a structured consequence the design manager can put to a client with the uncertainty left visible: moving that wall reaches structural, architectural and MEP, and the design work has to happen in that order because MEP cannot resolve until the other two are fixed. It revises the fire strategy, which changes the core sequence and brings the shaft procurement decision forward. If this is a higher-risk building past Gateway 2, a change to compartmentation is likely to be a major change under the change control regulations, which means an application to the Building Safety Regulator and a decision before the work can start. I can give you the design effort. I cannot give you the regulatory date, and nobody who offers you one should be believed.

That is a materially better conversation than structural says it is fine but MEP might have issues, and it is better precisely because it does not end in a number. The value of the cascade is that it makes the shape of the consequence visible before anyone commits, not that it produces a duration the system is in no position to promise.

What is different about the risk here?

The consequences of a missed connection are higher, and the failures are quieter.

Implicit dependencies. Two details that never clash but where one assumption invalidates another. The system sees what is drawn, not what is implied.
Missing site context. An existing tree not in the model, an unrecorded utility, a neighbouring structure. The design works and cannot be built.
Interpretation divergence, and which regime you are in. For conventional work a local authority or a registered building control approver may reach different views on the same clause, and no retrieval predicts which. For a higher-risk building that risk changes shape rather than disappearing: building control is the Building Safety Regulator, there is no alternative body and no informal steer, and every question is a formal submission answered on the regulator timescale.
Specialist package constraints. Lift loadings, plant clearances and equipment access are often contractually or proprietarily defined. A geometric check will not see a contractual constraint.
Statutory triggers. On a higher-risk building in England, a material change of use to any part of the building is expressly a major change under the change control regulations. The client must apply to the Building Safety Regulator for approval of that change, and the work must not start until it is granted. A review scoped to technical compliance will not raise it, and it will not know that it did not.

What changes about the coordination meeting?

It stops being a search and becomes a resolution.

The traditional meeting opens with a question nobody can answer well: are there any clashes? The honest answer is usually yes, but I am not sure which ones matter. The assisted version opens with six critical clashes, four tight conditions and three sequence risks, each routed to the discipline that has to move, each with the clearance required and the clearance provided. The meeting spends its time deciding rather than discovering.

The design manager coordinates. They do not hold the design. Design intent sits with the appointed designers under their appointments, contractor's designed portions sit with the contractor and flow down to the specialists, and specialist packages sit with the specialists. A system that says MEP should move has expressed a preference, not a determination: which party moves is answered by the design responsibility matrix and the appointments, not by the model.

Surfacing an issue by machine transfers no design responsibility either. What it changes is the record. Before, an unnoticed dependency failure turned on whether reasonable skill and care would have found it. After, there is a dated entry showing it was raised, and whether anyone acted. A flagged item left open is a materially worse position than one nobody ever saw, and that register is disclosable. Every flag needs a disposition with a name and a reason against it. See also what a good AI pilot looks like and MCP and the connected construction office.

Design decides what gets built. part 10, the most valuable AI on a project may save nobody any time, published Wednesday, 26 August 2026 deals with the discipline that has to prove what happened, months or years after it did.

What five questions should you be able to answer now?

Attempt these before tomorrow. Each has a defensible answer, and each is answered at the top of the next part.

Why is commercial management described as an evidence game rather than a numbers game?
What is a challenge function, and why might it save no time at all?
A CVR says a package is 74 per cent complete. What would you compare that against?
Why does a contemporaneous commercial record beat a reconstructed one, and what does that mean for final accounts?
What should happen when a commercial manager overrides an assessment, and what makes the difference between a strong and a weak position later?

Which sources is this part built on?

Every figure quoted above resolves to one of these. Each was checked before publication.