Facade Management Software: What It Must Prove

Facade Contractors Are Now in the Evidence Business

Facade management software used to be a productivity purchase: fewer spreadsheets, tidier photos, faster reporting. The Building Safety Act 2022 changed the brief. UK facade and envelope contractors now face three evidence demands at once — prove your people were competent, prove the carbon position of what you installed, and prove compliance through a golden thread of building safety information. Each demand lands on the same desk: the commercial manager signing the subcontract, the design director signing the details, the MD signing the company's name to the job.

This guide sets out what facade contractors actually have to evidence post-BSA, the feature checklist that separates real facade management software from generic project tools with a folder structure, and an honest way to reason about return on investment — without invented statistics.

What You Have to Prove Now

Competence

The BSA's dutyholder regime, delivered through amendments to the Building Regulations, requires that anyone carrying out building work has the skills, knowledge, experience and behaviours to do it, and that organisations have the capability to deliver their role. For a facade contractor that means being able to show, for any element of the works, who installed it, what qualified them to do so at the time, and who checked it. Third-party schemes matter here: FIRAS certification for fire-protection installers, CSCS records, manufacturer system training for the curtain walling or rainscreen system being installed. The question is no longer "do we hold the certificates somewhere?" but "can we connect the certificate to the person, the date, and the panel?"

Carbon

Carbon has become a commercial demand before it is a regulatory one. Main contractors and clients increasingly ask envelope bidders for embodied-carbon information at tender: Environmental Product Declarations for the systems offered, material take-offs that support whole-life carbon assessments, and evidence of what was actually installed rather than what was specified. Some planning authorities, notably in London, already require whole-life carbon assessments on larger schemes. A facade contractor who can produce installed-material records by elevation and package answers those questions from the record; one who cannot rebuilds them from delivery notes and emails.

Compliance and the Golden Thread

For higher-risk buildings — broadly, buildings at least 18 metres or seven storeys with two or more residential units — the Act requires a golden thread of building information: accurate, digital, accessible, structured and transferable records of how the building was designed and built. Gateway 2 requires Building Safety Regulator approval before construction starts; Gateway 3 requires evidence at completion before occupation. The facade package sits at the centre of both, because the external wall is where fire performance, testing evidence (CWCT sequences, BS 8414 system tests), and as-built change control converge. The envelope contractor's slice of the golden thread — what was installed, by whom, to which detail, with which approved change — has to be handed up the chain in a form the principal contractor and accountable person can actually use.

One caution on claims you will hear in sales conversations: no software product makes you Building Safety Act compliant. The duties sit with dutyholders — with people. What software can honestly do is build and keep the evidence behind those duties, so the proof exists when it is demanded.

Why the Spreadsheet Stack Fails

Most facade contractors run competence in one spreadsheet, QA in another, photos in WhatsApp, decisions in email, and drawings in a folder tree that only one person understands. Each tool works on its own. The failure happens at the joins — and the joins are exactly where evidence demands land:

• Nothing is anchored to the building. A photo of a firestop is worthless as evidence if nobody can say which floor, which elevation, which opening.
• Nothing is dated and signed in a way that survives scrutiny. A spreadsheet cell can be edited silently; an evidence record should not be.
• Competence lives apart from the work. The training matrix says the operative was qualified; nothing connects that status to the panels they installed that week.
• Handover becomes reconstruction. At Gateway 3 or practical completion, someone spends weeks rebuilding a record that should have been built as the work happened.

The alternative is one living record, built as the work happens and anchored to the building — not a document dump assembled at the end.

The Feature Checklist: Evaluating Facade Management Software

When you assess platforms, test them against the evidence demands above rather than the demo script. Six capabilities matter most:

1. Spatial anchoring. Every record — photo, QA check, decision, delivery — should attach to a location in a spatial model of the building: Building, Floor, Elevation, Location, Element. If the software organises evidence by folder or by form type instead of by where the work is, you will be doing the anchoring manually forever.
2. An audit trail you cannot quietly edit. Who recorded what, when, and what changed afterwards. Dispute resolution and regulatory scrutiny both turn on whether the record is trustworthy, not just whether it exists.
3. Evidence capture that works at the workface. Photo evidence with time and location metadata, QA and ITP checklists per system (curtain walling, rainscreen, fire-stopping), usable on a phone by an installer on a mast climber — not just by an engineer at a desk.
4. Competence records connected to the work. Installer tickets, training and eligibility visible at the point of sign-off, so the competence evidence and the installation evidence are the same record, not two spreadsheets to reconcile later.
5. Programme and labour on the same record. When progress, time and QA share the spatial structure, slippage and quality drift are visible per elevation and zone — and the as-built history writes itself.
6. Answers with a decision trail. The test of a living record is whether you can put a hard question to it and get an answer with the location and history attached. Try it in the demo: "Show me the QA sign-off, installer tickets and photo record for unit 214, west elevation, level 9." If the answer is a search box over file names, keep looking.

Finally, check the exit: can the platform export a structured, transferable evidence pack — golden-thread-shaped, not a zip of PDFs — when the principal contractor or building owner asks for your slice of the record?

Honest ROI Reasoning — Without Invented Numbers

Most ROI claims in this category are marketing arithmetic. A more honest way to build the business case is to price what your team already spends on the absence of a connected record:

• Reconciliation time. The hours each month spent matching the training matrix to the labour allocation sheet, the photo folder to the QA tracker, the delivery notes to the installed quantities. This is pure overhead created by the joins between tools.
• Handover assembly. The weeks at the end of a package spent rebuilding an O&M and evidence pack from fragments. Built-as-you-go records reduce this to an export.
• Dispute evidence. When a defect claim or final-account argument arrives two years after handover, a QA record with a photo, timestamp, location and signature is worth a great deal more than a recollection. It is impossible to put a universal number on this — one avoided dispute can pay for years of software, and some projects never have one.
• Rework caught late. Defects found at commissioning cost more than defects found at installation. Evidence captured at the workface pulls that discovery earlier.

The honest conclusion is that returns are project-specific: they scale with how much spreadsheet and email work the platform genuinely replaces, and with how exposed the business is to evidence-heavy demands — HRB packages, litigious clients, competence audits. Price your own reconciliation and handover time first; that number is usually persuasive on its own.

How to Choose

• Pilot on a live package, not a sandbox. Two elevations, one crew, four weeks. Real adoption at the workface is the single strongest predictor of value.
• Ask the awkward questions in the demo. Use your own project: a specific opening, a specific operative, a specific change. Watch whether the answer comes with location and history attached.
• Test the export before you sign. Ask for a structured evidence pack for a section of work and show it to whoever receives your handovers.
• Watch for red flags. A generic project tool with a "compliance module" that is a document library; no spatial model; audit trails that can be edited; and any vendor claiming their product makes you BSA-compliant.

Where BrieXO Fits

BrieXO is built around exactly this idea: one living record, anchored to the building, built as the work happens. The FIELD bundle is live today and covers the site side of the evidence problem — daily site records, QA/ITP checks and RAMS gates, governed photo evidence, record-linked threads and decisions, programme control, labour time, and competence management, with analytics and AI-assisted insight (EXOH) that answers questions from the record with the location and decision trail attached. Design-side capability — BIM coordination, specifications and carbon evidence — is part of the DESIGN bundle (on the roadmap), and cost and contract workflows sit in the COMMERCIAL bundle (on the roadmap).

To be clear about the claim: BrieXO does not replace your dutyholder responsibilities, and no software discharges Building Safety Act duties. What it does is keep the evidence behind those duties organised, anchored and exportable — one tool, one record, no more spreadsheets. If you are evaluating platforms for an envelope business, start with the BrieXO for facade contractors overview, and the deeper guides on Building Safety Act compliance software and golden thread software.

Related resources: CWCT testing evidence guide, Building Safety Act implementation guide, UK construction compliance software guide.