Myrus Build

A lot of the construction industry is still treating competence management as a data exercise. More dashboards. More matrices. More AI-generated “insights”. More colourful reporting. But none of that answers the question that actually matters: “Can you defend your competence decisions under regulatory scrutiny?” Because when a project hits Gateway 3 - or worse, an investigation - nobody is going to care how good the dashboard looked. They’ll care about: - who was approved to do what - against which criteria - using what evidence - who signed it off - whether reassessment happened - whether competence aligned to building risk - and whether the organisation can prove all of it retrospectively That is not workforce analytics. That is organisational accountability. The market is starting to split into two very different categories: Systems that report competence activity and Systems that provide defensible competence assurance Those are not the same thing. Training records are not assurance. Course completion is not competence. Visibility is not governance. AI summaries are not evidence. Other regulated industries went through this shift years ago when scrutiny around competence intensified. Construction in the UK is now entering the same phase. The organisations that succeed over the next few years will not be the ones with the best-looking dashboards. They’ll be the ones that can evidence, defend and govern competence decisions at scale. Especially at Gateway 3.

Most organisations in construction do not have a competence problem. They have a competence visibility problem. They cannot clearly answer: - Who is competent? - Competent for what? - Based on whose assessment? - Against which standard? - Under what level of supervision? - And how is that competence maintained over time? That becomes a serious issue under the Industry Competence Committee and Building Safety Regulator expectations, because competence is no longer something organisations can assume. It has to be actively managed, evidenced, reviewed, and governed. The challenge is that many systems across the industry were built for administration, not assurance. -Training records are treated as proof. - Qualifications are treated as capability. - Experience is treated as competence. But none of those things automatically demonstrate that someone can safely and consistently perform a role in practice. The organisations that adapt fastest over the next few years will not necessarily be those with the biggest frameworks. They will be the ones that can clearly connect: - roles - responsibilities - risk - capability - assessment - and accountability into one coherent operational system. That is where competence moves from paperwork into governance. #BuildingSafetyAct #Competence #BuiltEnvironment #Governance #ConstructionHR #RiskManagement

There’s a useful illusion in construction that competence can be “proven” through training records, qualifications, and compliance paperwork. The recently published guidance from the Industry Task and Finish Group (ITFG) challenges that assumption directly. What it makes clear is that competence under the Building Safety Act framework is not a documentation exercise. It is a systems issue. It sits in procurement decisions, organisational structure, supervision models, and accountability chains. In other words: it is designed into how work is governed - or it fails. This matters because most organisations are already “doing competence”. They have frameworks, matrices, training logs, and sign-off processes. But the gap the guidance exposes is uncomfortable: You can be fully documented and still not be demonstrably competent in practice. That shifts the question from “Do we have evidence?” to “Does our system reliably produce competent outcomes?” And that is a fundamentally different standard for HR, leadership, and delivery teams to operate against. At MyrusBuild, we are focused on that gap between compliance and reality - where competence is assumed on paper, but not consistently assured in practice. Because in the current regulatory environment, that gap is no longer theoretical. It is where risk actually sits. The question now is simple: Are your systems designed to record competence — or to produce it? #BuildingSafetyAct #Competence #Governance #BuiltEnvironment #RiskManagement #OrganisationalCapability