Compliance checking used to be the endpoint. A consultancy would review drawings, flag issues, and confirm that a project met the required standards before work progressed. That model worked well enough when regulation operated in the background, but the Building Safety Act 2022 changed the expectations placed on consultancies at a fundamental level. Under the current regime, firms working on higher-risk buildings are now expected to be involved far earlier and to stay involved far longer. The Building Safety Regulator has introduced a more structured approach to oversight, one that requires evidence, coordination, and clear lines of accountability at every stage from initial design through to occupation. Building control is no longer a box to tick toward the end of a project. What this means in practice is that consultancies are being asked to interpret risk, prepare documentation that can withstand regulatory scrutiny, support gateway approvals, and help clients understand their obligations in a way that goes well beyond traditional sign-off activity. The role has broadened, and the weight of responsibility that comes with it has grown considerably. What Has Changed for Consultancies The core shift is one of timing and scope. Consultancies are now expected to contribute earlier and more continuously across design, approval, construction, and occupation stages, rather than arriving at the end of a project to confirm that requirements have been met. That change is directly tied to the Building Safety Act 2022, the establishment of the Building Safety Regulator, and the heightened scrutiny applied to higher-risk buildings. Together, these developments have made it clear that building control is not a final checkpoint but an ongoing process with formal accountability at every stage. The practical implication is that consultancy work now includes risk interpretation, evidence preparation, coordination support, and the development of accountability frameworks. These are not extensions of the old sign-off function; they represent a genuinely different kind of professional involvement, one that begins earlier, carries more weight, and continues well beyond the point where a project was once considered complete. Why the Old Compliance Model No Longer Works The previous end-stage checking model became insufficient once regulatory scrutiny tightened, formal dutyholder roles were introduced, and approval gateways were restructured to require substantive evidence rather than retrospective confirmation. Understanding why that happened requires looking at where the pressure originated. From Grenfell to a New Dutyholder Regime The shift in how the industry approaches building safety did not happen in isolation. The Grenfell Tower fire in 2017 exposed systemic failures across design, construction, and oversight, and the subsequent Hackitt review made clear that the existing regulatory framework was too fragmented to prevent similar outcomes. The Building Safety Act that followed created formal dutyholder roles, placing legal responsibility on identifiable individuals and organisations at every stage of a project. The Health and Safety Executive, operating through the Building Safety Regulator, now expects documented evidence of competency requirements being met, not informal assurances or retrospective sign-off. Professional competence became a requirement that had to be demonstrated, not assumed. Why Gateway 2 Raised the Stakes for Advice Gateway 2 sits at the point where detailed design is submitted for regulatory approval before construction can begin. Under the official regulations, work cannot proceed until the Building Safety Regulator is satisfied that the design meets safety requirements, which means errors or gaps at this stage do not simply trigger a revision note. They trigger regulatory bottlenecks that can halt a programme, delay procurement, and force redesign work at the most expensive possible moment in the project timeline. This is where the old model of late-stage checking becomes genuinely unworkable. Identifying a compliance problem after a Gateway 2 submission has been prepared carries consequences that earlier involvement would have avoided entirely. How Consultancies Now Shape Projects Upstream The expansion of consultancy involvement upstream is one of the most significant practical changes to emerge from the current regulatory environment. Rather than waiting until a design is largely fixed, many firms are now embedded in projects from the earliest stages, when the cost of changing course is still low and the opportunity to influence outcomes is greatest. Advising During Concept and Early Design The point at which a consultancy joins a project has shifted considerably. Where involvement once began at the technical review stage, many firms are now embedded during concept development, when design decisions are still fluid and the cost of changing course is low. At this stage, the most valuable input tends to centre on fire safety strategy, Approved Document B interpretation, and the buildability implications of early design choices. Higher-risk buildings in particular require a level of regulatory literacy from the outset, because decisions made about means of escape, compartmentation, or structural form can define the compliance position of the entire scheme before a single detailed drawing is produced. Project teams increasingly rely on coordinated technical input before statutory submissions are fixed, and engineering consultancy services that extend into pre-application and early design phases are now part of the project team from the first substantive design conversations, rather than arriving once the architecture is largely settled. Preventing Redesign and Approval Delays The downstream benefit of that earlier involvement is a measurable reduction in redesign, rework, and the kind of programme disruption that a poorly prepared Gateway 2 submission creates. When building control requirements and fire safety standards are understood at concept stage, the detailed design can be developed around them rather than reconciled with them later. That distinction matters because late reconciliation almost always means change, and change at the submission or post-tender stage carries a cost that early coordination avoids. Compliance with Approved Document B is harder to retrofit into a design than it is to build in from the start. Consultancies working upstream help ensure that by the time a Gateway 2 submission is being prepared, the documentation reflects a design that was developed with regulatory requirements in mind, not one that has been adjusted to meet them. The Role Now Runs Across the Whole Lifecycle The upstream shift