How to Apply and Audit Uniclass Codes in BricsCAD BIM Models

Uniclass provides a consistent classification structure for built environment information. In BricsCAD BIM V26, a classification system can be imported through BIMPROPERTIES, assigned to BIM elements through the Properties panel, and exported with classified elements to IFC. A dependable workflow therefore needs four controls: choose the appropriate Uniclass table, state the Uniclass release adopted by the project, apply codes consistently, and validate assigned values against the authoritative NBS dataset.

This guide shows a practical, repeatable approach for How to Apply and Audit Uniclass Codes in BricsCAD BIM Models, including property creation, consistency rules, reporting, exports, and a step-by-step audit method to catch missing or incorrect tags.

Why Uniclass Matters in UK BIM, and Why BricsCAD Users Should Care

Uniclass is a unified classification system maintained by NBS. NBS states that it can be used to structure specifications and manage project information, that its structure complies with ISO 12006 2, and that it supports ISO 19650 information management processes. NBS updates Uniclass quarterly. As of 14 August 2026, the latest published update is dated 21 July 2026.

BricsCAD V26 includes a supplied classification system named “UniClass2015”. Octave documents that this classification can be imported into the Classification System namespace, although the classification code help page does not identify which NBS quarterly release the bundled data represents.

In practical terms, controlled Uniclass classification can support:

• Consistent classification and filtering of model information
• Classification based schedules and data extraction
•  Model checking for missing, inconsistent, withdrawn or invalid codes when model data is compared with the agreed NBS release
• IFC exchange of assigned classification systems and codes

Uniclass basics (what you’re applying, and what “good” looks like)

Uniclass is organised into tables that classify different kinds and scales of built environment information. In a building model, the appropriate table depends on what is being classified and on the project information requirement.

• Ss (Systems) classifies collections of products brought together to operate as a system
• Pr (Products) classifies individual products used across the built environment
• SL (Spaces and locations) classifies spaces and locations
• EF (Elements and functions) classifies general construction elements and functions
• Other tables, including En (Entities), may also be required depending on the information being classified

Picking the right table: classify according to the information requirement

Table choice should be defined by what is being classified and by the project’s information requirements. It should not be reduced to a simple “what it is” versus “what it does” rule.

• Use Pr when classifying an individual product
• Use Ss when classifying a collection of products operating together as a system
• Use EF for general elements or functions, including where a more detailed system has not yet been defined
• Use SL for spaces and locations
• Use En for recognisably independent entities such as buildings, bridges or tunnels

Good Uniclass classification should be:

• Consistent: equivalent information is classified using an agreed approach
• Complete: objects required by the information requirements have a classification
• Valid: the exact code exists in the project’s agreed NBS Uniclass release and its status has been checked
• Appropriate: the chosen table and classification depth suit the object and the information exchange

Where to store Uniclass in BricsCAD so it remains structured and exportable

BricsCAD BIM V26 provides a dedicated Classification System namespace for standard construction classification codes. For official Uniclass classification, use this native classification mechanism rather than making a custom User property set the primary classification record.

Open BIMPROPERTIES, select Import, and load the approved classification XML. BricsCAD V26 includes “UniClass2015” among the supplied classification systems. After import, BricsCAD adds the classification system to the Classification System namespace, creates the associated property set and attaches the classification code property.

Select an element and choose its classification code from the classification property in the Properties panel.

Current NBS examples include:

• Pr_30_59_24: Doorsets
• Ss_25_30_20_25: Doorset systems

The example “Pr_30_59_25_24” should not be used as the current NBS classification for Doorsets.

If additional project governance metadata is required, create separate User properties such as:

• UniclassRelease, for example “July 2026”
• ClassificationStatus, for example “Provisional”, “Checked” or “Approved”
• ClassificationSource, where the project needs to record how the value was assigned

Keep these project audit fields separate from the official classification code.

Step-by-step: add Uniclass codes to BIM objects in BricsCAD BIM

Use BIMPROPERTIES to import the approved classification system XML into the drawing. In BricsCAD V26, choose Import and select the required classification file, such as the supplied “UniClass2015” file or another project controlled XML.

During setup:

• Confirm the classification appears in the Classification System namespace
• Define the BIM element categories to which the classification system applies

• Record which NBS Uniclass release the project has adopted
• Use the same controlled classification definition throughout the project

BIMPROPERTIES can also export the active namespace to XML so that the same definition can be imported into other drawings.

2) Assign a classification code to BIM objects

Select the required element and open the Properties panel. The imported classification system and its classification code property should be available. Use the classification code dropdown to select the required code.

3) Use filters and multiple selection for repeated assignments

BricsCAD’s Filter panel can create and save property based selection rules. The Properties panel can display and modify properties shared by multiple selected entities.

A controlled batch workflow can therefore:

• Select candidate objects using Filter panel rules
• Review the resulting selection before editing
• Assign the shared classification value through the Properties panel where the classification property is available to all selected objects
• Run the classification audit after the edit

Selection similarity is a productivity aid, not proof that all selected elements require the same Uniclass classification.

4) Use reusable content carefully

Reusable BIM content can reduce repeated data entry, but the official Uniclass assignment should remain compatible with the controlled Classification System namespace used by the destination model.

For reusable components:

• Ensure the destination model contains the approved classification definition
• Verify the classification value after the component is inserted
• Do not require a custom PSET_Classification_UK merely to duplicate the native classification code
• Treat any automatic transfer of classification data as something to be verified by the project audit rather than assumed

Where additional project metadata is required, keep it in separate User properties.

Implementation & checking (distinct workflow section focused on doing and verifying)

This section is only about implementation and checking, how to put controls in place, run checks, and fix issues. It is intentionally separate from the Uniclass overview and the COBie/IFC export discussion.

Implementation checklist

1. Record the NBS Uniclass release adopted by the project
2. Define which Uniclass table and classification depth are required for each information purpose and stage
3. Use a controlled BricsCAD Classification System definition throughout the project
4. Define which model objects require classification at each information exchange
5. Keep project review status and other audit metadata separate from the official Uniclass code
6. Define the schedules, data extractions and exchange checks that will be used for auditing

Avoid rules such as “Doors = Pr”. A doorset system can be classified in Ss, while a doorset product can be classified in Pr, depending on what the information requirement asks you to classify.

Uniclass code validation rules

Formatting checks are useful, but they do not establish that a Uniclass code is valid. Validation should include both syntax and authoritative NBS checks.

Syntax checks:

• The code starts with the appropriate two letter Uniclass table identifier
• Numeric parts use the Uniclass hierarchy of two digit groups, with the number of groups depending on the table and classification level
• The code field does not contain free text or placeholders such as TBC or ???
• Required objects do not have a blank classification
• Authoritative checks:
• The exact code exists in the project’s agreed NBS Uniclass release
• The code’s status is checked to determine whether it is current, withdrawn or replaced
• The official NBS title corresponds with the code
• The chosen table and level of detail meet the project’s information requirement
• The project records the Uniclass release against which the model was checked

A correctly formatted code can still be nonexistent, withdrawn or inappropriate for the object being classified.

How to check missing Uniclass codes

1. Use a schedule, the Properties and Filter panels, or DATAEXTRACTION to report relevant model properties such as:

• Object identifier or Handle
• BIM or IFC object type
• Classification system
• Classification code
• Project audit status, if a separate User property is used
• Adopted Uniclass release, if recorded in the model or audit dataset

1. Filter or query the result for objects where the required classification code is blank.
2. After the completeness check, run a separate validity check comparing populated codes with the project’s agreed NBS Uniclass dataset.

DATAEXTRACTION can export selected entity properties to CSV or TXT, which provides a practical dataset for this second validation step.

Classification consistency check

Grouping similar model objects by their assigned classification is a useful way to identify outliers, but multiple codes are not automatically an error.

Review the model by:

• Grouping objects by BIM type or other agreed type identifier
• Listing the distinct Uniclass classifications within each group
• Investigating differences against the information requirement and the official NBS definitions

For example, a doorset system can legitimately be classified as Ss_25_30_20_25, while a doorset product can be classified under Pr_30_59_24. Different classifications can therefore be correct when the objects are being classified at different levels or for different purposes.

Standardise classifications only where the objects have the same classification purpose, required table and applicable NBS classification.

Fix incorrect Uniclass assignments (controlled correction workflow)

To fix incorrect Uniclass assignments safely:

1. Correct the source first (library/template) if the error is systematic
2. Batch-correct instances in the model (selection/filter)
3. Update ClassificationStatus to “Rechecked”
4. Re-run the audit report and archive it as evidence

Tip: Keep a simple change log: “Changed Pr code for door family X from A to B on 14 August 2026” (use your real dates). This supports accountability during reviews.

Auditing Uniclass in BricsCAD BIM

A robust audit BIM classification approach combines model checks, reports, and a light governance routine.

A reliable classification audit should test more than whether a field is populated.

A four part audit approach

1. Object level completeness

• Every object required to carry a classification has a value

1. NBS validity and release control

• Every populated code exists in the agreed Uniclass release
• Withdrawn or replaced classifications are identified
• The official NBS title and code correspond

1. Semantic and model consistency

• The selected table and classification are appropriate for the object and information requirement
• Unexpected differences between equivalent objects are investigated

1. Delivery level verification

• Required classification information is checked after IFC or other project data exchange

An audit report should include:

• Classified and unclassified counts
• Invalid, withdrawn and replaced code findings
• Semantic or consistency queries
• Documented exceptions
• The Uniclass release used for validation
• Exchange verification results where IFC or another structured deliverable is required

Uniclass and COBie: treat classification mapping as a separate deliverable

NBS publishes COBie mappings for Uniclass classifications. For example, the current NBS pages identify COBie mappings for Pr_30_59_24 Doorsets and Ss_25_30_20_25 Doorset systems.

Do not make a custom PSET_Classification_UK the authoritative Uniclass record solely for COBie purposes. Keep the official model classification in BricsCAD’s Classification System namespace.

Where COBie is a project requirement:

• Define the project’s COBie generation and classification mapping method
• Validate source classifications against the agreed NBS Uniclass release before generating COBie
• Map the required classification information into the appropriate COBie output according to the project’s requirements
• Check the resulting COBie data against the source model after generation

The BricsCAD V26 sources used in this workflow directly document classification assignment, IFC export and DATAEXTRACTION to CSV or TXT. A COBie workflow should therefore be described separately from BricsCAD’s documented IFC classification export unless a specific COBie tool or mapping process has also been verified.

IFC classification mapping: verify classification as classification

Do not treat Uniclass solely as a custom IFC property set. BricsCAD documents that assigned classification systems and classification codes are included when the BIM model is exported to IFC.

IFC provides dedicated classification structures. A classification system is represented by IfcClassification, individual classification references by IfcClassificationReference, and associations between classifications and model objects by IfcRelAssociatesClassification.

After exporting IFC:

• Confirm the expected classification system is present
• Confirm classified objects retain their classification association
• Check the classification reference Identification against the expected Uniclass code
• Check the human readable Name or description against the official NBS classification
• Where edition information is required, verify that the agreed classification release can be identified

Testing a small exchange model early remains a useful way to verify the chosen export and receiving workflow.

BricsCAD and Revit Uniclass workflows: define the exchange requirement

Mixed authoring environments do not need identical native storage mechanisms. They do need an agreed classification requirement and a consistent exchange result.

In BricsCAD BIM, standard classification codes are managed through the Classification System namespace. Other authoring applications, including Revit, may use different native mechanisms.

For interoperability:

• Agree the Uniclass release to be used
• Agree which table and classification depth are required
• Agree whether classification applies to an occurrence, type, system or another information object
• Test the exchanged IFC rather than relying only on matching native property names
• Verify the IFC classification reference and its association with the intended object

Do not make interoperability dependent on both platforms having a custom property called PSET_Classification_UK.UniclassCode. The exchange requirement should describe the information that must be delivered, not require identical authoring software data structures.

Automation ideas: reduce manual classification work without treating automation as validation

BricsCAD provides documented tools that can reduce repetitive model data editing. The Filter panel can save property based filters and create selection sets, while the Properties panel can modify properties shared by multiple selected entities.

BIMAUTOMATCH can also propagate BIM data between similar elements based on recognised similarities and existing properties. However, Octave does not describe BIMAUTOMATCH as a Uniclass validity checker or as a tool that validates classifications against the current NBS dataset.

A controlled assisted workflow can therefore:

• Use saved filters to identify candidate objects
• Apply a classification to reviewed selection sets
• Use automation only where its behaviour has been tested for the project
• Run the NBS validity and semantic audit after automated or bulk assignments
• Record human review status separately from the official classification value

Automation can accelerate assignment, but it does not replace classification validation.

Building a Uniclass classification schedule and audit output

A classification report should expose the model’s authoritative classification data and the information needed to validate it.

Recommended model and audit fields include:

• Object identifier, Handle or other stable identifier
• BIM or IFC object type
• Building, storey or location where relevant
• Classification system
• Classification code
• Project Uniclass release
• Classification audit status, if maintained as a separate User property
• Official NBS title and current or withdrawn status, added or checked from the controlled NBS validation dataset

The report should identify:

• Missing required classifications
• Codes that do not exist in the agreed release
• Withdrawn or replaced codes
• Unexpected classification differences between equivalent objects
• Classifications requiring semantic review

BricsCAD’s DATAEXTRACTION workflow can export entity properties to CSV or TXT, allowing the model classification inventory to be compared with the controlled NBS dataset.

Common pitfalls (and how to avoid them)

• Storing codes in text notes rather than structured properties
  • Fix: store in property sets; reserve notes for human comments
• Different spellings/field names across models
  • Fix: one property schema; no variants
• Mixing tables without a rule
  • Fix: document table choice; apply consistently
• “Complete but wrong” classification
  • Fix: run consistency audits, not just missing-value checks
• Late auditing
  • Fix: audit at every milestone, not just pre-handover

Conclusion: a repeatable BricsCAD BIM Uniclass classification workflow 

A dependable Uniclass workflow in BricsCAD BIM should be based on four controls:

1. Use BricsCAD’s Classification System namespace for the official Uniclass assignment and control the classification definition used by the project
2. Record the NBS Uniclass release against which the project is being classified and audited
3. Apply classification rules that define the required table and level of detail for each information purpose
4. Audit completeness, NBS validity, semantic suitability and exchange preservation at agreed project stages

BricsCAD can store assigned classification codes, expose them through model properties and export classified elements to IFC. Schedules and data extraction can support model auditing. Where COBie or another structured deliverable is required, treat its mapping and verification as a separate project requirement rather than assuming that a custom property set guarantees compliant exchange.