NBS published two Uniclass updates in the first half of 2026. The January release touched eight tables, including Activities, Products, Systems, Spaces/locations, Roles, CAD, Form of information, and Project management. It introduced 26 new classifications alongside 5 amended codes. The April release followed with changes across six tables, adding 12 new classifications and amending 40 existing codes.
That's 38 new classifications and 45 amendments in six months. For a system that governs how you structure your specifications, tag your BIM objects, and name your CAD layers, that represents a pace of change that most practices aren't tracking.
Every update also includes amended codes, which can be easy to overlook. An amended code might change the scope of what a classification covers, merge two previously separate entries, or refine the language that defines an existing category. If your specifications use the old wording or scope, they may still technically reference valid codes but describe something slightly different from what the current Uniclass definition intends.
One of the most telling additions in the January 2026 update is the extension of the Activities table to cover deconstruction. NBS added codes for the deconstruction of architectural components, mechanical services, and external works. Until now, the Activities table assumed construction and maintenance as the primary lifecycle phases. Deconstruction was an afterthought, if it was classified at all.
This matters because the UK's push toward circular construction means that buildings increasingly need to be designed with disassembly in mind. If you've worked on any project where the client brief mentions embodied carbon targets or material recovery, you'll recognise the gap. The specification data needs to reflect how components come apart from the earliest design stages, not just how they go together.
NBS has signalled that further codes accommodating re-use and alteration in construction are planned for future releases. This echoes what happened when BIM was first introduced. The practices that started structuring their data early didn't just avoid rework later; they became the firms that clients trusted to deliver properly managed project information.
Seven new surface water management codes landed in the Products, Systems, and Spaces/locations tables. These were developed in collaboration with the Environment Agency and are designed to improve asset mapping for drainage and flood management infrastructure. For architects working on projects with significant external works or sites in flood-risk areas, these codes fill a gap that previously required workaround classifications or generic codes that didn't quite fit.
Five new healthcare-specific codes were added to the Spaces/locations table, developed with the Royal Cornwall Hospitals NHS Trust. These cover clinical environments such as clean and dirty utility rooms that didn't previously have their own classifications. The April update refined this further, renaming the clean utility code to "Clean utility rooms" and adding a dedicated "Dirty utility rooms" code. New M&E codes also arrived in the April Products table, covering additional ventilation and pipework products that support more precise classification of mechanical services.
The CAD table received two new codes under the Boundaries subgroup, building footprint and gross external area, supporting standardised AutoCAD layer naming in alignment with ISO standards. Layer naming might seem like a minor administrative detail, but inconsistent layers create reconciliation work that someone has to do by hand on every drawing issue when your layers don't match the classification system your BIM coordinator is using. The Roles table expanded too, adding codes for quality managers and utilities consultants.
Many UK practices still use CAWS (Common Arrangement of Work Sections) for their day-to-day specification work. CAWS has been around for decades, and its familiarity is precisely what makes it comfortable. NBS Chorus still supports CAWS-structured specification libraries, and plenty of firms haven't felt the urgency to switch.
But CAWS hasn't been actively developed for years. Uniclass has absorbed and replaced its functionality while expanding far beyond what CAWS was designed to cover. Where CAWS dealt with work sections, Uniclass covers the entire project lifecycle from briefing through operation and demolition, across activities, spaces, systems, products, roles, and more. The quarterly updates that NBS publishes all go into the Uniclass tables. CAWS gets nothing.
If your practice is still primarily using CAWS, you're not wrong to do so on projects where it's established. But you are working with a system that's standing still while Uniclass moves forward. Every new code for circular construction, surface water management, or healthcare classification lands in Uniclass and nowhere else. The longer you wait to shift, the larger the gap between your clause library and the classification system the rest of the industry is converging on.
Uniclass follows a quarterly update cycle: January, April, July, October. Every quarter, NBS refines codes, adds new ones, and occasionally amends or deprecates old entries. The system has grown steadily since its 2015 overhaul, and the pace hasn't slowed. Current table versions tell the story: Activities is at v1.26, Systems and Products are both at v1.42, and Spaces/locations sits at v1.35.
Most practices don't track these changes. The spec writer who set up your clause library two or three years ago may have used codes that have since been amended or superseded. Your BIM objects might reference Products table entries that have been reclassified. Unless someone in your office is checking the NBS download page each quarter, you won't know until a project coordinator flags the mismatch during a BIM audit or a client's information manager rejects a deliverable.
The practical cost is real. Reclassifying specifications after they've been issued costs time your team doesn't have. Re-tagging BIM objects across a model because someone used a deprecated code creates rework that nobody budgeted for. On public sector projects where Uniclass compliance isn't negotiable, outdated codes can hold up information exchanges and delay stage sign-offs.
This is where the gap between what Uniclass specification standards require and what practices actually deliver becomes a genuine liability. Tools like Avoice are built to handle this kind of ongoing change, updating specification classifications as the underlying standards evolve rather than relying on someone to audit clause libraries by hand each quarter.
The UK's BIM mandate, now operating under the Information Management Initiative (IMI) Framework since its 2025 rebrand, requires Uniclass classification on all public sector projects. If you're working on government-funded buildings, your specifications, models, and deliverables all need to use current Uniclass codes aligned with ISO 19650 and ISO 12006-2. This isn't a recommendation. It's a contractual requirement.
What many architects overlook is that private sector clients are increasingly adopting the same expectations. Major developers, institutional investors, and facilities management operators have started mandating BIM Level 2 processes and Uniclass classification as standard, regardless of whether the project receives public funding. They want structured data because it makes their buildings easier to manage over a 30- or 40-year lifecycle.
Your specification workflow needs to produce correctly classified output as a default, not as an afterthought addressed during a pre-submission review. Avoice generates specifications classified under Uniclass, CAWS, NATSPEC, and CSI MasterFormat standards because classification accuracy can't be bolted on at the end of a project. It needs to be embedded from the start, grounded in your firm's own project data and the standards that apply to each specific job.
Two more quarterly updates will arrive before the year is out. Based on the January and April release notes, NBS has signalled continued expansion into circular construction classifications, and ongoing collaboration with bodies like the Environment Agency suggests that environmental and sustainability-related codes will keep growing through the July and October releases.
For your practice, the action is practical. Start by checking which version of the Uniclass tables your current specification templates reference. If you're still working from tables published before 2025, you're almost certainly missing codes that affect how your projects are classified and delivered. The NBS download page provides the latest tables for free, so there's no cost barrier to staying current.
Then consider whether your current workflow can absorb quarterly changes without creating a manual maintenance burden. If your spec writer is copying clause text from a static library and applying Uniclass codes by hand, every quarterly update becomes a task that rarely gets prioritised until something goes wrong on site or a submission gets rejected. AI-powered specification tools like Avoice take a different approach, ingesting a firm's existing documentation and structuring output around the latest recognised standards so that specifications stay current without someone cross-referencing clause libraries against the NBS changelog.
The question for 2026 isn't whether Uniclass specification standards matter to your practice. They clearly do, and their influence is growing quarter by quarter as more clients, both public and private, require classified project information. The real question is whether your tools and processes are set up to keep pace with a system that updates four times a year, or whether you're still treating classification as a static reference that someone configured once and forgot about. If you're ready to see how this works on a real project, Avoice is worth a closer look.
