Explore every episode of the podcast JC Virtual PMs Podcast

Ask ten people on a UK project who the principal designer is and you will get a confident answer. Ask them which principal designer you mean and the confidence usually evaporates. There are two. They are created by different legislation, they cover different things, they carry different competence requirements, and there is no rule that says the same organisation has to hold both. The Health and Safety Executive's own review of CDM 2015, which reported in May 2026, identified confusion arising from "similar but distinct roles under the Building Safety Act" and inconsistent interpretation across the market as a live problem — and it is one of the few things in that review that generated a commitment to new guidance. Until that guidance lands, the fix is contractual and it is straightforward. But you have to know what you are separating.

Ask three people how long Gateway 2 takes and you will get three answers, all of them technically correct, because there are three different sets of numbers in circulation and almost nobody distinguishes them. That matters commercially, because a contractor pricing to the statutory target and a client programming to the published median are twenty weeks apart, and somebody is going to pay for the difference.

There is a change to biodiversity net gain that came into effect on 6 August 2026 and that a great many small developers have not registered, because it arrived quietly in amendment regulations rather than as a headline announcement. It removes mandatory BNG from roughly half of all residential planning permissions in England. The test is an area threshold, and it is measured in a way that rewards paying attention at the point you draw the red line.

A new National Planning Policy Framework was published on 17 August 2026. It is 130 pages, it is the first full rewrite since 2012, and — this is the part that changes what you do this week — its decision-making policies took effect on publication. Not on adoption of a new local plan. Not after a transition. They are material considerations in every determination and every appeal from the day it was published. For a small or medium housebuilder, five changes matter.

There is a four-week window closing, and for some schemes it is worth a meaningful five-figure sum. The Building Safety Levy applies in England from 1 October 2026. It is charged on new residential development, it is collected through the building control process, and it is designed to raise around £3.4bn over ten years toward remediation. For a small developer the important parts are the trigger date, the threshold, the discount, and one collection mechanism that can hold up your sales.

Most of what has been written about the second staircase deadline describes a single test: get building regulations approval before 30 September 2026 and you are safe. That is half the rule, and the half that is easier to satisfy. The other half has a date eighteen months further out, a definition drawn tight enough to catch schemes that genuinely believe they have commenced, and no discretion in it at all. With 27 days to go, it is worth being precise about what the deadline does, who it still catches, and which of the two dates you should actually have in your programme.

Few terms in the BIM world generate as much confusion — and as much box-ticking — as COBie. It appears in information requirements, gets demanded on projects that have no use for it, and is delivered as a giant spreadsheet nobody ever opens. Yet the idea behind COBie is genuinely useful. The problem is that it is often required without anyone asking the only question that matters: what is it for, and do we actually need it?

There is a strong correlation between how a construction project starts and how it finishes. Projects that drift into life — no clear roles, vague processes, everyone assuming someone else has it covered — tend to spend the rest of their duration firefighting the confusion set up in the first few weeks. Projects that mobilise deliberately, with the team aligned and the systems in place before real work begins, spend that energy on delivery instead. Mobilisation is not administrative throat-clearing; it is where a project’s culture and control are established.

Ask an experienced project manager why projects go wrong and few will start with concrete or steel. They will talk about people — a client who was not kept informed, a consultant working to a different assumption, a contractor who found out about a change too late. Construction is a team sport played by parties with different interests, and keeping them aligned is not a soft skill at the edge of the job. It is the job. Stakeholder management is what turns a group of separately-motivated organisations into a project that pulls in one direction.

Of all the deliverables at the end of a construction project, the handover information is the one most likely to be thrown together at the last minute — a rushed box of manuals and a file assembled to tick a regulatory box. That is a mistake on two fronts. The Health and Safety File is a legal requirement under the CDM Regulations, and the operation and maintenance information is what determines whether the client can actually run and look after the building. Treated properly, both are among the most valuable things you hand over.

The end of a construction project should be a moment of relief. Too often it becomes a running argument — over what is finished, what is faulty, what counts as complete, and when the final money is due. A surprising amount of that conflict comes from a simple confusion: treating snags and defects as if they are the same thing. They are not, and understanding the difference is the key to a clean handover.

There is a familiar and dispiriting pattern in construction: a building is finished, the keys are handed over, the contractor leaves — and then the problems start. The heating never quite works as intended, the controls baffle the people using them, energy bills come in far higher than predicted, and the client is left managing a building nobody fully understands. Soft Landings is the discipline designed to prevent exactly this, by treating a smooth handover and a well-performing building as something you plan from the start, not hope for at the end.

On paper, the RIBA Plan of Work is tidy and sequential: you finish technical design at Stage 4, then you build it at Stage 5. In reality, commercial pressure to start on site sooner means these stages increasingly overlap — construction begins on the parts that are ready while the design team is still detailing the rest. Overlapping Stage 4 and Stage 5 can genuinely save months. It can also cause chaos if it is not managed with real discipline. The difference is entirely in the control.

Document control is one of those disciplines that gets very little attention until something goes wrong. A contractor builds from the wrong revision. A structural drawing is missed in a coordination review. A client is handed an incomplete O&M manual at handover. These are not rare occurrences — they are the predictable result of poor document control, and they happen on projects of all sizes every day. Here is what document control actually is, and why it matters.

With material costs elevated and margins under pressure across UK construction, “value engineering” is a phrase every SME client hears sooner or later — usually when the tender comes in over budget. But value engineering has a reputation problem. Too often it is used as a polite name for cost-cutting: stripping out quality to hit a number, and quietly storing up problems that surface later as defects, higher running costs, or a building that disappoints. Done properly, it is something better — a disciplined way to get more value for less money.

With material costs elevated and margins under pressure across UK construction, “value engineering” is a phrase every SME client hears sooner or later — usually when the tender comes in over budget. But value engineering has a reputation problem. Too often it is used as a polite name for cost-cutting: stripping out quality to hit a number, and quietly storing up problems that surface later as defects, higher running costs, or a building that disappoints. Done properly, it is something better — a disciplined way to get more value for less money.

No construction project of any size finishes exactly as it was drawn. Ground conditions surprise you, the client changes their mind, a product is discontinued, a regulation shifts. Change itself is not the problem — uncontrolled change is. The projects that overrun rarely do so because of one big decision; they do it through a hundred small changes that were never properly assessed, priced, or recorded. A disciplined change-control process is what stands between “a few tweaks” and a blown budget.

No construction project of any size finishes exactly as it was drawn. Ground conditions surprise you, the client changes their mind, a product is discontinued, a regulation shifts. Change itself is not the problem — uncontrolled change is. The projects that overrun rarely do so because of one big decision; they do it through a hundred small changes that were never properly assessed, priced, or recorded. A disciplined change-control process is what stands between “a few tweaks” and a blown budget.

Before you appoint a contractor, before you pick a contract, you make a more fundamental choice: how the project will be procured. The procurement route decides who designs, who builds, who carries the risk, and how much control you keep over the finished product. For SME clients it is easy to default to “the way we did it last time” — but the right route depends on what you value most: certainty, speed, quality, or flexibility.

Choosing a building contract is one of the earliest and most consequential decisions an SME client makes — and one of the most commonly rushed. In the UK, the choice usually comes down to two families: the JCT suite and the NEC4 suite. They can both deliver the same building, but they manage risk, change, and relationships in fundamentally different ways. Pick the wrong one for your project and your team, and you spend the job fighting the contract instead of using it.

Ask most SME construction businesses where their project information lives and the honest answer is “a few places” — a shared drive here, an email thread there, a contractor’s own system somewhere else. For years that was tolerable. In 2026 it is a liability. Clients, regulators, and the building safety regime now expect project data to be structured, trustworthy, and retrievable. Getting there is less about buying software and more about applying a few disciplines consistently.

Artificial intelligence has crossed a line in construction. Where it was once a conference talking point, in 2026 it is increasingly embedded in how projects are run, records are kept, and compliance is demonstrated. One industry commentary went as far as describing AI in UK construction project management as shifting “from competitive advantage to compliance requirement.” For SMEs, the challenge is separating what genuinely helps from what is expensive noise.

Public-sector construction work has a reputation among SMEs for being the preserve of the big players — too much bureaucracy, frameworks locked up by tier-one contractors, and bid requirements that only a large business can satisfy. The Procurement Act 2023, which went live in February 2025, was written partly to change that. For smaller AEC firms willing to get their house in order, it represents a real opening.

“The golden thread” is one of those phrases that gets repeated in every building safety seminar and rarely explained in plain terms. For SME clients, developers, and duty-holders it matters, because under the Building Safety Act it has moved from good practice to a legal expectation — and getting it wrong can stall a Gateway approval or leave you carrying a liability for the life of the building.

For years, planning and building safety policy has effectively been written for two audiences: the large volume housebuilder and the single-plot self-builder. The developer building somewhere between ten and fifty homes — the backbone of UK SME housebuilding — has been squeezed by rules designed for someone else. That may be about to change. A proposed “medium site” category for developments of 10 to 49 homes is being discussed, and if it lands it could reshape the compliance and cost picture for exactly the kind of developer this site is written for.

If you are developing or delivering a higher-risk building in the UK, the single biggest threat to your programme right now is not the weather, the supply chain, or labour — it is Gateway 2. The Building Safety Regulator’s pre-construction approval stage has become a bottleneck, and for many projects it is the difference between starting on site this quarter or next year. The numbers tell the story. Through 2025, turnaround times for some Gateway 2 applications stretched to more than 30 weeks, with a number of schemes falling 12 to 18 months behind their original programmes. Operational changes late in 2025 have started to bring new-build decisions down toward the statutory 12-week target, but remediation cases remain slow — recent data shows approvals taking around 43 weeks with an approval rate of roughly 40%. In other words, the picture is improving for new buildings but is still volatile, and you cannot plan on certainty.

Most construction projects run informally. The client gets updates in meetings, progress is discussed on site visits, problems surface through phone calls and email chains, and the overall picture of where the project stands at any given moment is assembled from multiple sources, none of which is comprehensive or reliable on its own. This informal approach works reasonably well when things are going smoothly. When they are not — when programme slippage is accumulating, costs are drifting or risks are materialising — the absence of structured reporting means that problems are identified late, decisions are made without complete information and interventions that could have been timely are reactive and expensive. Without a formal monthly report, projects typically run on a series of informal updates — calls, emails, site visits — where the information shared is selectively positive and the picture the client receives is incomplete. Problems accumulate out of sight until they become serious, at which point they are much harder and more expensive to address. A formal monthly report changes this dynamic by creating a structured, regular checkpoint that forces transparency.

The UK public sector spends tens of billions of pounds every year on construction. For SMEs, winning a slice of that work is one of the most reliable ways to grow a sustainable business. But public sector clients increasingly require BIM compliance as a condition of appointment — and many smaller firms are missing out simply because they cannot demonstrate it. Here is how to change that.

Earned Value Management has a reputation for being complicated, jargon-heavy and the exclusive preserve of large government programmes and infrastructure megaprojects. That reputation is not entirely undeserved — full EVM implementations with hundreds of control accounts, detailed work breakdown structures and monthly EVMS reporting can indeed be complex and resource-intensive. But the underlying logic of EVM is straightforward, genuinely useful, and accessible to projects of almost any size — including SME construction projects — if it is applied in a proportionate way. At its core, EVM is a method for measuring project performance by integrating scope, schedule and cost into a single framework. Traditional project reporting typically asks two questions: are we on time, and are we within budget? The problem with this approach is that the two questions are answered separately. A project might appear on budget because it has not yet spent money that it should have spent — but the reason it has not spent that money is that it is behind programme. EVM addresses this by measuring performance in terms of the value of work done, rather than simply the cost incurred.

Residential construction in the UK has its own distinct design management challenges. Planning conditions, Part L compliance, fire strategy post-Grenfell, viability pressures, the interface between the architect and the principal contractor — the residential sector operates within a regulatory and commercial environment that differs significantly from commercial, industrial or infrastructure work. For SME residential developers in particular — those delivering schemes of ten to one hundred units without the in-house expertise of a major housebuilder — these challenges can be genuinely difficult to navigate without experienced design management support. For SME residential developers, design management is often approached informally — a trusted architect is appointed, planning is obtained and construction proceeds. This approach can work on simple projects, but it creates significant risks on anything more complex: mixed-use schemes, high-rise developments, projects with unusual site conditions or complex planning conditions. Understanding the key design management challenges specific to residential development is the first step to managing them effectively.

Many clients and developers find themselves in the position of managing a multi-disciplinary design team without a background in design. You have appointed an architect, a structural engineer, an MEP consultant and perhaps a landscape designer. They are all producing work. But coordinating them, keeping them to programme, resolving conflicts between their designs and making sure the design actually reflects what you want — that is a different challenge entirely. Being asked to manage a design team that you did not appoint, whose technical language you may not fully speak, is a challenging position. But it is a common one: many project managers, employers’ agents and clients find themselves in this role, responsible for coordinating the output of multiple consultants without the architectural or engineering background that might make the task feel intuitive. This article sets out a practical framework for managing a multi-disciplinary design team effectively, regardless of your own technical background.

Quality is one of those words that everyone on a construction project uses and almost nobody defines. “We want a high-quality scheme”. “The quality of the design is not good enough”. “We need to improve design quality”. These statements are made constantly — and they are almost never accompanied by a clear explanation of what quality actually means in the context of the specific project, how it will be assessed, and who is responsible for ensuring it is achieved. It is frequently the case that construction managers are clear about what ‘construction quality’ means but vague about ‘design quality’. Managing design quality means something specific: ensuring that the design information produced is complete, coordinated, compliant and fit for purpose — and that the design meets the brief. This article explains what design quality management involves and how to measure it objectively.

Late design information from consultants is one of the most persistent and costly problems on UK construction projects. It delays the contractor, creates claims for extension of time and additional cost, damages relationships and — if not handled correctly — destroys the professional goodwill that makes a project team function well. Yet the way most project teams respond to it — by either saying nothing or escalating immediately to a formal dispute — tends to make the situation worse rather than better. When design information arrives late, the instinctive responses — saying nothing and hoping it will arrive, or escalating immediately to a formal dispute — both tend to make the situation worse. The first allows the delay to compound; the second damages relationships that may be difficult to repair. A more effective approach lies between these extremes: a structured, professional response that protects the project without creating unnecessary conflict.

Construction projects routinely overrun on cost and programme. Most project teams are good at tracking what has been spent. Far fewer are good at understanding whether the work completed actually justifies what has been spent to date. Earned Value Management (EVM) is the methodology that closes that gap — giving project managers an objective, data-driven view of project performance at any point in the delivery cycle. EVM is used widely on major infrastructure programmes, government contracts and international projects. It is less commonly applied by SMEs, often because it is perceived as complex or resource-intensive. In practice, the core principles are straightforward, and even a simplified application of EVM can significantly improve cost and programme visibility on projects of any size.

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.

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 — 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.

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 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.

If you work in the UK construction industry, you have almost certainly encountered both terms. BIM Level 2 was the framework that drove the industry’s adoption of Building Information Modelling over the past decade — the government mandate, the PAS standards, the CDE requirements. ISO 19650 is the international standard that has now effectively superseded it. The relationship between the two is one of the most common sources of confusion for SME clients, contractors and consultants trying to understand what is actually required of them on a given project. BIM Level 2 was a UK government mandate introduced in 2011 and fully implemented across all centrally procured government projects by April 2016. It required project teams to produce and exchange 3D information in a structured, collaborative way, using a defined set of standards and protocols — primarily PAS 1192-2 — and to deliver project data in a format that could be used for facilities management. The intention was to improve efficiency, reduce errors and build a richer information base for the operation of built assets.

The Construction (Design and Management) Regulations 2015 — CDM 2015 — place legal duties on everyone involved in a construction project. For SME clients in particular, one of the most important and most frequently misunderstood of these duties is the appointment of the Principal Designer. Getting this appointment wrong — or failing to make it at all — can leave the client in breach of their statutory obligations and personally liable for the consequences. Many SME developers and construction clients either misunderstand their obligations under CDM 2015 or leave the Principal Designer appointment until far too late in the design process. Getting this wrong creates legal risk for the client and can create health and safety problems that are difficult and costly to address later. This guide explains what you need to know as a client, when to make the appointment and what to look for when selecting a Principal Designer.

One of the most common causes of design disputes, coordination failures and programme delays is a simple lack of clarity about who is responsible for what. On multi-disciplinary projects, the boundaries between disciplines are rarely clean — and where responsibility is ambiguous, things fall through the gaps. A Design Responsibility Matrix (DRM) exists to close those gaps.

Managing_Design_Interfaces_on_Multi-Disciplinary_Projects

How To Set Up A Project On Autodesk Construction Cloud- A Practical Guide

How To Build And Manage A Construction & Design Risk Register