Competence Records
Role Framework
47
Active scopes
186
Evidence claims
12
Expiring Soon
3
Blocked scopes
NameRoleQAPlantHSEInduct
MK
Mike Kelly
✓
✓
!
✓
✓
JP
James Parker
✓
–
✓
✗
–
SC
Sarah Chen
✓
✓
✓
✓
!
!
Evidence review due
Mike Kelly - Plant scope
✗
Scope blocked
James Parker - major gap
Decision issued
Conditional pass
iHasco synced
Training evidence
12 expiring
Next 30 days
XO-Comp

Competence records that prove who did the work.

The Building Safety Act's competence regime asks every dutyholder the same question: who did the work, and what qualified them to do it? XO-Comp keeps the answer in one living record — role requirements, evidence, assessor decisions, and validity — ready the day someone asks.

Not a training matrix in a spreadsheet, rebuilt the week before an audit. Competence lives alongside the site records, timesheets, and programme it governs — so eligibility is checked before work is assigned, not at the gate.

See XO-Comp in ActionExplore Features
Role frameworks
Competence evidence
Assessor decisions
Site eligibility
Part of BrieXO FIELD

This app is one surface inside the FIELD bundle. Use this page for product-specific detail, then compare bundle tiers when you are ready to buy.

Explore FIELD See FIELD Pricing
Roles
Framework requirements
Matrix
Gap visibility
CPD
Training evidence
Verify
Proof on demand
The Problem

The Building Safety Act asks who did the work — and what qualified them

Under the BSA competence regime, every dutyholder must be able to show that the people doing the work were competent to do it — with tighter scrutiny again on higher-risk buildings. A training matrix in Excel, certificates in folders, and assessor emails assembled at handover cannot carry that weight.

A certificate is not competence

The BSA expects skills, knowledge, experience, and behaviours matched to the actual work — requirements that differ by role, product, and risk. A card list in a spreadsheet cannot model that.

Evidence without a trail is not proof

Training files, cards, CPD, and assessor notes only count when you can show where they came from, whether they were valid at the time, and who reviewed them. The decision trail is what turns documents into proof.

Checks happen too late

If a competence gap only surfaces at the gate, the programme pays for it. Planning and time capture should see who is cleared before work is assigned, not after someone has travelled to site.

Capabilities

Competence records you can act on — and prove

XO-Comp turns workforce competence into defined requirements, reviewed evidence, accountable decisions, and live readiness status — one record per person, built as the work happens.

Frameworks and packs

Create versioned competence frameworks with provenance, jurisdictions, languages, sectors, risk tiers, and default validity — or import a standard framework pack in one step.

VersionsPack importRisk tiers

People scopes and matrix

Assign users to framework versions, profiles, functions, typologies, products, risk presets, jurisdictions, and threshold overrides, then see gaps by person or matrix.

ScopesProfilesGap cells

Evidence and decisions

Store evidence artefacts, map claims to scopes and competency items, run verification attempts, and issue pass, conditional, or fail decisions with validity windows.

ClaimsReviewsDecisions

Training plans and CPD

Manage training catalogue entries, plans, plan items, completion evidence, CPD records, and iHasco training compliance sync where configured.

CataloguePlansiHasco

Verification links

Create tokenised public, internal, or partner verification links with disclosure controls, expiry, revocation, credential IDs, integrity tokens, and access logging.

TokensDisclosureAccess log

Eligibility signals

Feed allow, warn, and block decisions — with reasons and remediation steps — to XO Time and XO Prog, so eligibility is checked where work is assigned and time is captured.

Allow/warn/blockStatus feedsRemediation
Features

From requirement to readiness decision

XO-Comp models what each role requires, what evidence exists, who reviewed it, and whether the person is ready, conditional, expired, blocked, or needs remediation.

Build governed competence frameworks

Model competence around the work your teams actually perform: role profiles, function requirements, product or system experience, qualifications, capabilities, validity rules, and risk presets.

  • Taxonomies and role profilesFunctions, typologies, products, role templates, qualifications, capabilities, and profile-level requirements
  • Versioned frameworksFramework versions carry source, provenance, language, jurisdiction, sector, risk, validity, and measurement settings
  • Framework pack importBring in standard framework packs with built-in validation and a full audit trail — safe to re-run when a pack is updated
  • Policy defaults and risk presetsSet coverage rules, expiry windows, grace periods, and stricter presets for higher-risk buildings (HRBs), with scope-level overrides
app.briexo.com/comp/matrix
Framework Matrix
Facade package - as-of today
v3 active
PersonRoleQAPlantHSEInductGaps
Mike Kelly
✓
✓
!
✓
✓
✓
James Parker
✓
–
✓
✗
–
✓
Sarah Chen
✓
✓
✓
✓
!
✓
Covered
Expiring
Blocked
N/A
47 active scopes
as-of status view

Review evidence and issue accountable decisions

XO-Comp connects evidence to the scope it supports, lets assessors record review outcomes, and keeps lifecycle status, reasons, validity, activity, and audit events visible.

  • Evidence artefacts and claimsReference XO Docs revisions, store issuer and validity dates, and map evidence to functions, scopes, and competency items
  • Assessment methodsTrack test, interview, assignment, and scenario methods with required evidence and linked artefacts
  • Validation lifecyclePass, conditional, and fail decisions carry reasons, issuer, effective status, validity windows, and transition logs
  • Operational audit trailEvery change to scopes, assessments, evidence, and training is logged with who, what, and when — the trail exists before anyone asks for it
app.briexo.com/comp/evidence/review
Evidence Review
3 scopes require decision
Assessor queue
✗
Plant operator scope
James Parker - major gap requires review
BLOCK
!
Facade QA scope
Mike Kelly - conditional evidence accepted
CONDITIONAL
!
HSE lead scope
Sarah Chen - new CPD evidence attached
REVIEW
Decision logged
audit event created

Connect competence to live delivery

Once competence has been assessed, the answer travels: planning, time capture, and site induction see who is cleared to work, while the evidence and decisions stay governed inside Comp.

  • XO Time eligibilityClock-in checks can show the decision, any blockers, what clears them, and the evidence behind the answer — before punch or kiosk start
  • XO Prog readinessPlanners see competency blockers and awaiting-competency constraints while assigning work — not after the programme slips
  • Field induction policySite induction requirements resolve from a person's active scopes and published XO Field templates, with safe fallbacks if a connected module is unavailable
  • Controlled verification linksTokenised verification links disclose only the fields you choose and log every successful access — proof for clients and partners without handing over the record
app.briexo.com/comp/people/mike/readiness
Readiness Signals
Mike Kelly - facade installer
ALLOW
XO Time
Clock-in check clear
XO Prog
No competency blocker
XO Field
Induction policy resolved
Verifier
Disclosure link active
One governed record
Other modules see status, blockers, and what clears them. The evidence and decisions behind the answer stay governed inside XO-Comp.
Verified link
selected fields only
More Capabilities

What one living competence record holds

The detail matters, but it is easier to understand in four buckets: govern requirements, assess evidence, develop people, and prove status.

Govern

Taxonomies, framework versions, role profiles, competency items, risk presets, org defaults, and one-step framework pack import.

Assess

People scopes, evidence artefacts, evidence claims, verification attempts, assessment methods, assessor decisions, lifecycle logs, and audit events.

Develop

Training catalogue, plans, plan items, completion evidence, optional CPD records, and iHasco training compliance sync where configured.

Prove

Tokenised verification links, credential IDs, integrity tokens, disclosure controls, expiry, revocation, access logging, activity feeds, and controlled status sharing.

Integrations

Competence signals where the work happens

XO-Comp owns the competence record. Other BrieXO modules read live status — eligibility, blockers, induction, evidence references — where configured, so one record answers everywhere.

XO-Time

Eligibility checks can carry Comp decisions, blockers, remediation, and supporting evidence details into punch and kiosk starts.

XO-Prog

Planners can see competency blockers, validation summaries, and awaiting-competency constraints while assigning work.

XO-Field

Site induction requirements can use Comp scope context, and evidence packs can include Comp source references.

XO-Docs

Evidence artefacts can reference controlled document revisions without turning XO-Comp into a document repository.

Ready to prove who did the work — and what qualified them?

See how compliance managers, assessors, planners, and site teams work from one living competence record. One tool, one record — no more spreadsheets.

Book a DemoStart Free Trial