How To Run A Design Team Meeting That Actually Works

E20_How To Facilitate A Design Coordination Meeting That Resolves Issues, Not Just Records Them

Design coordination meetings are among the most common meetings on any construction project. They are also among the most commonly mismanaged. The difference between a coordination meeting that resolves issues and one that merely records them is the difference between a project that progresses smoothly and one that carries the same unresolved conflicts from week to week until they become construction problems. Most construction projects hold design coordination meetings regularly throughout the design and construction phases. In theory, these meetings should be the mechanism by which design conflicts are identified and resolved. In practice, they are frequently ineffective — producing minutes that record issues without resolving them, and consuming significant team time with little output. This article sets out a practical approach to facilitating design coordination meetings that actually achieve their purpose.

How To Run A Design Team Meeting That Actually Works

Design team meetings happen on every construction project. Whether they are productive is another matter entirely. The typical design team meeting — two hours, fifteen attendees, no agenda, no action log — is one of the most reliably wasteful experiences in the construction industry. It absorbs time and energy without producing decisions, and it creates the illusion of coordination without the substance of it. Yet most design team meetings are not as effective as they should be. They run over time, fail to reach decisions, produce action lists that are never followed up and are attended by people who do not need to be there. This article sets out the practical steps that make design team meetings productive rather than just regular.

Contractor Design Portions What They Are And How To Review Them Properly

Contractor Design Portions — commonly referred to as CDPs — are design packages that are transferred from the employer’s design team to the main contractor or a specialist subcontractor as part of the construction procurement. They represent one of the most significant areas of design risk on any construction project, and yet they are also one of the most inconsistently managed. When CDP submissions are reviewed properly, they protect the client’s quality and safety standards and reduce the risk of costly late-stage problems. When they are not, the consequences can be severe and difficult to recover.

How To Manage Scope Creep In The Design Stage Before It Reaches The Site

Scope creep is one of the most reliable ways to turn a well-planned construction project into an expensive, overrun one. It rarely arrives dramatically — it accumulates quietly, one apparently reasonable request at a time, until the project the client is building bears little resemblance to the project they budgeted and programmed. By the time the consequences are visible, the changes are already embedded in the design, contracted into the works or partially built. Scope creep in design typically starts with small additions — a client who wants an extra room here, a specification uplift there. Each change seems manageable in isolation. The problem is cumulative: by the time the project reaches procurement, the brief has expanded significantly, the programme has been eroded by the additional design time and the budget is under pressure. When the contractor is appointed, these costs crystallise — and the client is often surprised by the gap between the original estimate and the tender price.

Design Freeze- What It Is, When To Call It, And What Happens When You Don’T

Design freeze is one of those project management concepts that sounds straightforward in theory and proves remarkably difficult to enforce in practice. The idea is simple: at a defined point in the design process, the scope is fixed, the design is locked, and changes can only be made through a formal change control process. In practice, design freeze is routinely ignored, softened, moved or quietly abandoned — with consequences that range from programme delay to significant cost overruns and site-level rework. In practice, ‘design freeze’ is frequently misunderstood, poorly enforced, or simply not called at all. The consequences range from minor inefficiencies to serious contract disputes. This article explains what design freeze really means, when to call it and what happens on projects where it is never properly established.