Competence assurance often looks heavier than it is. Read the Building Safety Act, glance through a few standards, and the whole subject can feel like a job you were meant to have finished long ago.
That perception stops many capable firms before a single competence record is written. What matters here is simpler than it seems: you do not need a complete system to make a lawful, defensible start.
One clear move leads to the next, and a working rhythm follows. Thirty days is enough to build a solid competence assurance foundation.
It also gives contractors a practical starting point for construction competency management without creating an overly complex process.
What the Duty Actually Requires On Site
Under the Building Safety Act 2022 and Part 2A of the Building Regulations, the obligation is to demonstrate and evidence competence, not simply to possess it. That duty covers all building work, not only higher-risk buildings, which is the point most contractors underestimate.
Two layers sit underneath it:
- Individual competence: whether each operative, supervisor and manager can carry out their specific role safely and in accordance with the Building Regulations.
- Organisational capability: whether the business has the systems, processes and resources to plan, manage and monitor that work.
Both need a paper trail behind them.
The SKEB Model in Plain Terms
Competence across the built environment is defined through SKEB: Skills, Knowledge, Experience and Behaviours. A qualification alone does not settle it.
A CSCS card confirms a baseline, yet it says nothing about whether the holder can deliver the task in hand. On-site conduct weighs as heavily as any ticket.
The Mindset That Keeps the Work Proportionate
Two principles carry the month. Start from where you stand, and reuse what you already hold. Most firms sit on far more evidence than they think: card records, QA logs, method statements, appraisals, toolbox talk registers and inspection sheets.
For a smaller contractor, a clear spreadsheet paired with role profiles is a legitimate first system. You are collating proof, not building it from nothing.
The 30-Day Competence Assurance Plan
Here is how the four weeks break down.
| Week | Focus | Output by end of week |
| Days 1 to 7 | Map roles, people and existing evidence | A clear picture of your starting position |
| Days 8 to 14 | Assess people against role profiles using SKEB | A first-pass competence matrix |
| Days 15 to 21 | Close the highest-risk gaps first | Every gap has an owner and a date |
| Days 22 to 30 | Set the review cycle and ownership | A living process, not a one-off audit |
Week One: Map Your Ground
List your roles, then the people filling them. For each role, write a short profile setting out what someone must do competently and safely. Keep it to a page.
This is how to create a competence framework without turning the exercise into a long consultancy project. Start with the work people actually perform, the risks involved and the standard they must meet.
Pull every scrap of existing evidence into one place so that, by day seven, you can see your true position rather than guessing at it.
Week Two: Assess Honestly
Measure each person against their role profile through the SKEB lens. Where does the proof sit, and where are the holes? Flag anything resting only on someone’s own word, since self-assessment on its own falls short. Sound competence decisions need oversight, whether that is supervisor sign-off, record checks or a second opinion.
Week Three: Close the Obvious Gaps
Gaps are not equal, so rank them by risk. Book the priority training, arrange CPD where knowledge has slipped, and capture evidence that already exists but was never logged. Carry the same thinking into your supply chain, because the duty follows the work down to every subcontractor.
Week Four: Turn It Into a System
A snapshot decays fast. Use these final days to decide who owns competence going forward, set a review cycle, and feed your records into the golden thread of building information.
Treat the evidence as live Building Safety Act competency records, not documents that are completed once and forgotten. Update them when roles change, qualifications expire, new risks appear, or further assessment is needed.
On higher-risk work, the Building Safety Regulator can examine competence arrangements. A living process stands up to that scrutiny far better than a folder thrown together under pressure.
Where the Foundation Leads Next
Day thirty is a base to build on, not a finish line. Competence now becomes something you review rather than rebuild. A sensible next step is mapping your evidence to a recognised common assessment standard, letting one body of proof answer many prequalification questions.
Steer clear of the usual traps too: over-engineering the paperwork, leaning on self-assessment, ignoring behaviours, and forgetting the firms you subcontract to.
Turning Thirty Days Into a Working Habit
Thirty days will not make you flawless, and it does not need to. It gives you an evidence-based, defensible start you can stand behind and improve steadily.
Competence assurance stops looking like a mountain the moment you treat it as a sequence of ordinary steps taken in order. Set out your roles, gather your proof, be honest about the gaps, and build a rhythm that keeps it current. Open a blank sheet, mark today’s date at the top, and take the first step while it is fresh.
