INSIGHT · PRODUCTIVITY & TECHNOLOGY
The Code is a dataset now,
and one edition has carried three versions.
The National Construction Code is published as machine-readable XML on data.gov.au under a Creative Commons Attribution 4.0 International licence. One edition of it, NCC 2025, has carried three dataset records in forty-seven days. The original, created on 6 May 2026, is now titled "National Construction Code 2025 - Superseded (Replaced June 2026)". Version 1.1, created 3 June 2026, is titled "Superseded (Replaced 22 June 2026)". Version 1.2 was created on 22 June 2026. The ABCB's instruction to anyone who took the data is explicit: download the latest version and replace what you saved.
Analysed 3 October 2026 · ABCB, Updated NCC 2025 dataset, published 24 June 2026 and updated 30 June 2026 · ABCB data resources page, no page date shown · data.gov.au records for NCC 2025, Version 1.1, Version 1.2 and NCC 2022, read through the CKAN API · ABCB September 2026 CEO update, published 30 September 2026 · all pages and records read 3 October 2026.
Key takeaways
- The instruction names a date, not an edition: The ABCB's news item of 24 June 2026, updated 30 June 2026, states: "The updated version corrects errors in the previously released dataset. If you have accessed the dataset since 6 May 2026, you should download the latest version and replace any previously saved or integrated data." The test is when you took the file, not which edition of the Code you were working to.
- Three dataset records exist for one edition: Read through the data.gov.au CKAN API on 3 October 2026, the ABCB publishes national-construction-code-2025 (metadata created 6 May 2026), national-construction-code-2025-v1-1 (3 June 2026) and national-construction-code-2025-version-1-2 (22 June 2026). All three records are live. Two carry "Superseded" in their titles. By our calculation, 6 May to 22 June 2026 is forty-seven days.
- The superseded record carries the plainest warning: The original record's description opens: "This dataset contains errors identified after publication and has been superseded by a corrected version published on 4 June 2026. Users should download and use the updated dataset".
- The corrections reach named clauses: Version 1.2's description lists "MathML Fixes - B1V1(5)(b) and J6D5(3)(a) updated to use correct rather than substitute symbols". A system that parsed formulae out of an earlier file parsed substitute symbols.
- We would store the dataset version separately from the Code edition: Our system-design recommendation: for every external dataset a system reads, hold the dataset identifier, the version label, the resource timestamp, the retrieval date and the licence. "NCC 2025" names an edition. It does not name a file.
01
What is actually published.
The ABCB's data resources page, read on 3 October 2026, states that the Board "has published some datasets to data.gov.au the central source of Australian open government data", and that "The National Construction Code (NCC) data is available for download in XML format. The data is machine-readable and suitable for a wide range of applications, including research, analysis and software development."
- Software development is a listed intended use: That sentence is the part worth reading twice. The Code is not only a document to be read by a practitioner; it is a file to be parsed by a system. Three datasets are listed: NCC 2025 XML data, NCC 2022 XML data, and the data behind the interactive climate zone map.
- The licence permits commercial use, with conditions: Creative Commons Attribution 4.0 International. The page sets out what that permits: "you are free to share, adapt, and build upon your work, even commercially, as long as you give credit the ABCB as the original author of the data, provide a link to the licence, and indicate if changes were made." It adds that attribution must not "suggest the ABCB endorses you or your use of the ABCB data".
- The publisher has done the hard part: The provisions are available in a form a system can consume, with a licence that permits commercial use. What follows is not a problem with that. It is the ordinary consequence of consuming anything by file.
02
Three records,
one edition.
The data.gov.au records for NCC 2025, read through the CKAN API on 3 October 2026.
All three are in the active state and all three are attributed to the Australian Building Codes Board under the CC BY 4.0 licence. The original record holds five XML resources, each with a resource timestamp of 6 May 2026: Volume One, Volume Two, Volume Three, the ABCB Housing Provisions and the Livable Housing Design Standard. Version 1.1 holds the same five plus an XML resource named "NCC Schema". Version 1.2 holds the five volumes plus a ZIP resource named "NCC 2025 Schema". A schema arrived at Version 1.1 and changed format at Version 1.2. For anyone validating input against it, that is a second moving part.
| Dataset identifier | Title as published | Metadata created | Metadata modified |
|---|---|---|---|
| national-construction-code-2025 | "National Construction Code 2025 - Superseded (Replaced June 2026)" | 6 May 2026 | 3 June 2026 |
| national-construction-code-2025-v1-1 | "National Construction Code 2025 (Version 1.1) - Superseded (Replaced 22 June 2026)" | 3 June 2026 | 22 June 2026 |
| national-construction-code-2025-version-1-2 | "National Construction Code 2025 (Version 1.2)" | 22 June 2026 | 22 June 2026 |
03
What each version
says it changed.
Version 1.1's description states, under the heading "Key Changes": "1. Dataset Consolidation - a. Transformed each volume into a single cohesive document, streamlining parsing and reducing the need for multi-file dependency handling - b. Reduced overall file size through optimisation and removal of redundancies - c. Improved overall data usability for downstream applications by ensuring unique identifiers across each volume. 2. Errata Fixes - a. Applied corrections to identified inconsistencies in structure and formatting". Version 1.2's description states: "Release Date: 2026-06-18 - Overview - This release focuses on improving the usability and accuracy of the NCC TPP XML dataset. - Key Changes - 1. MathML Fixes - B1V1(5)(b) and J6D5(3)(a) updated to use correct rather than substitute symbols - 2. Errata Fixes - Applied further corrections to identified inconsistencies in structure and formatting".
- Read Version 1.1 as an integrator: "Ensuring unique identifiers across each volume" means the identifiers in the first release were not unique across volumes. If a system stored a clause by its identifier and that identifier was not unique, the stored reference may not point where it was intended to point. "Reducing the need for multi-file dependency handling" means the file layout changed, which is a parser change, not a content change.
- Read Version 1.2 the same way: B1V1 is a Volume One verification method for structural reliability; J6D5 sits in the Volume One energy efficiency provisions. The description says their mathematical symbols were substitutes rather than the correct symbols. A person reading NCC Online would not have seen that. A system reading MathML would have ingested it.
04
The release
has four dates.
One correction, read across its own publishers, carries four dates.
None of these is wrong. They are four different events: a record being replaced, a release being dated by its author, a record being created on a portal, and an announcement being published and then revised. They are only a problem for a record that holds one field called "updated". The news item also merges two releases into one list: its summary puts the clause-level symbol fix under the heading "Dataset consolidation", while on data.gov.au the consolidation work sits in Version 1.1 and the symbol fix sits in Version 1.2. A reader of the news item sees one update. A reader of the portal sees two.
| Date | What carries it |
|---|---|
| 4 June 2026 | The date the superseded record names as when "a corrected version" was published |
| 18 June 2026 | The "Release Date" stated inside Version 1.2's own description |
| 22 June 2026 | The metadata creation timestamp of the Version 1.2 record |
| 24 June 2026 | The publication date of the ABCB news item announcing the update, itself updated on 30 June 2026 |
05
The link on
the download page.
The ABCB data resources page, read on 3 October 2026, states: "NCC 2025 XML Data - Download the NCC 2025 XML data from: https://data.gov.au/data/dataset/national-construction-code-2025". The same page carries, directly beneath it, "Recent update: We have updated the NCC 2025 dataset on data.gov.au to correct an earlier issue." That address is the record titled "National Construction Code 2025 - Superseded (Replaced June 2026)", as read on 3 October 2026.
The warning and the link both work as intended for a person: you read the note, you follow the link, you see the superseding notice at the top of the record and you move on to the current version. For a system, the two behave differently. A scheduled job that fetches a bookmarked URL reads the resource and does not read the title. The notice that a human relies on is prose in a description field. This is the ordinary failure mode of integrating by address rather than by version, and it is why the retrieval record has to be ours rather than the publisher's.
06
What this means
for a business's records.
- "Which Code?" and "which file?" are now two questions: A project record that says NCC 2025 answers the first. Nothing in it answers the second.
- An ingestion date is evidence: The ABCB's test is "if you have accessed the dataset since 6 May 2026". A business that cannot say when it accessed the dataset cannot apply that test to itself without re-downloading and comparing.
- Derived artefacts inherit the version: Checklists, templates, clause libraries, specification clauses and prompt contexts built from an XML release carry whatever that release contained. Replacing the source file does not replace what was generated from it, unless something recorded which release each artefact came from.
- Identifier-keyed references are the fragile ones: Version 1.1's stated improvement was unique identifiers across volumes. A reference stored as a bare clause identifier from the first release is a reference whose target was ensured to be unique only afterwards.
- A superseded dataset is still a lawful copy: The licence does not expire. Nothing stops a stored file from being read next year. The only thing that marks it as superseded is a record you kept.
NCC 2025 adoption dates by state · Schedule 2 referenced documents
What we would put in a system
The point of contact is the moment any external dataset is read by anything that keeps the result.
Where agents help is narrow. A document intelligence agent can watch a published dataset record, compare its version label, resource timestamps and description against the version last recorded as ingested, and draft a change notice: this record is now titled superseded; this resource timestamp is newer than the one we hold; these clause identifiers appear in the new release with different content. An integrations agent can draft the list of internal artefacts that were generated from the superseded release. A person decides whether to re-ingest, what to re-issue and who needs to be told. No agent decides that a project may continue to rely on an earlier file, and no agent determines whether anything meets the NCC. Those are matters for the practitioner, the certifier, the relevant authority and your advisers.
| Field | Why it is load-bearing |
|---|---|
| Dataset identifier | national-construction-code-2025 and national-construction-code-2025-version-1-2 are different records for one Code edition. The address is part of the identity. |
| Version label as published | "Version 1.1", "Version 1.2", or no label at all for the original. Taken verbatim, not normalised. |
| Resource timestamp | Each XML resource carries its own creation timestamp. It is the only field that distinguishes two downloads of the same-named file. |
| Retrieval date and time | The ABCB's own test is phrased as an access date. A system that does not store one cannot answer it. |
| Licence and attribution string | CC BY 4.0 requires credit, a link to the licence and an indication of whether changes were made. Anything derived from the data carries that requirement. |
| Downstream artefacts built from it | Which checklists, clause libraries and templates were generated from which release, so a replacement can be scoped rather than guessed. |
Questions worth asking
of your own systems
For a design consultant: if your practice holds a clause library, a specification template set or a checklist built from NCC 2025, can you say which dataset release it was built from?
The ABCB's test is an access date. If the library was built between 6 May and 22 June 2026 and no retrieval record exists, the answer has to be found by comparison rather than by lookup.
For a multi-entity construction group: how many systems in the group read the same external dataset independently?
Three entities that each ingested on their own schedule can hold three different releases of one Code edition while all three report working to NCC 2025. The reporting field is identical; the underlying file is not.
For a project or development manager: when a clause reference is quoted in a project document, does the document say where the text came from?
NCC Online, a volume PDF and an XML release are three artefacts of one edition, and the ABCB has published corrections to all three in 2026. A quotation with a source and a date can be re-tested. One without cannot.
For a building-product manufacturer: if your conformity documentation quotes NCC clause text, which artefact was it copied from and when?
The symbol fix at Version 1.2 reached two named clauses. Documentation that reproduces formula text has a provenance question that documentation citing a clause number does not.
For anyone running an AI assistant over code text: what is in its index, and when was it put there?
A retrieval index is a stored copy. The replacement instruction applies to it in the same terms as to any other saved or integrated data.
Questions people ask
about the NCC XML dataset
Is the National Construction Code available as data?
The ABCB publishes NCC 2025 and NCC 2022 as XML on data.gov.au, and states the data is machine-readable and suitable for research, analysis and software development. The licence is Creative Commons Attribution 4.0 International.
How many versions of the NCC 2025 dataset are there?
Three live data.gov.au records as read on 3 October 2026: the original created 6 May 2026, Version 1.1 created 3 June 2026 and Version 1.2 created 22 June 2026. Two of the three carry "Superseded" in their titles.
What did the ABCB say to do about the earlier dataset?
The news item of 24 June 2026, updated 30 June 2026, states that anyone who accessed the dataset since 6 May 2026 "should download the latest version and replace any previously saved or integrated data".
What changed between NCC 2025 dataset versions?
Version 1.1's description cites dataset consolidation, reduced file size and unique identifiers across each volume, plus errata fixes. Version 1.2's description cites MathML fixes at B1V1(5)(b) and J6D5(3)(a) and further errata fixes. These are the publishers' own descriptions; we did not compare file contents.
Can I still use a superseded NCC dataset?
The licence does not expire, so nothing stops a stored file from being read. Whether an earlier file is appropriate for any particular purpose is a matter for the practitioner, the certifier, the relevant authority and your advisers. What this reading describes is that only a record you kept marks the copy as superseded.
What this analysis
does and does not show.
As read on 3 October 2026
- Publication
- NCC XML on data.gov.au under CC BY 4.0, software development listed among intended uses
- Records for NCC 2025
- Three, all live; two titled as superseded
- ABCB instruction
- Accessed since 6 May 2026: download the latest version and replace any previously saved or integrated data
- Version 1.1 changes cited
- Dataset consolidation, reduced file size, unique identifiers across each volume, errata fixes
- Version 1.2 changes cited
- MathML fixes at B1V1(5)(b) and J6D5(3)(a), further errata fixes
- Download link state
- The ABCB data resources link resolved to the record titled "Superseded (Replaced June 2026)"
- Derived by us
- Forty-seven days from 6 May to 22 June 2026; five days from 1 May to 6 May 2026
- We did not download or parse the XML files themselves. Every statement about what changed is taken from the publishers' own descriptions of their releases, not from a comparison of file contents.
- Dataset metadata timestamps are as returned by the data.gov.au CKAN API on 3 October 2026 and are reported to the date only. Portal metadata timestamps and a publisher's own release date are different quantities, which is part of what this reading describes.
- "NCC TPP XML dataset" is quoted from Version 1.2's description. We did not find an expansion of TPP on the pages we read and have not inferred one.
- We did not establish whether the superseded records remain reachable indefinitely, nor whether the ABCB data resources link has since been changed. Both are page states as read on one day.
- Which edition of the NCC applies to a project is set by state and territory implementation arrangements and is a separate question from which dataset release a system holds. We did not review jurisdictional arrangements here.
- Nothing here is legal advice, a determination that any product, design or project meets the NCC, or a criticism of any publisher's processes. Cyberate does not provide certification or conformity assessment.
What to watch next
Only dates and intentions that publishers have themselves published.
- ABCB September 2026 CEO update, published 30 September 2026: Reports that the Board "Learned from International Code Council's AI Navigator tool development", and that its 2026 NCC User Survey found "the importance of making requirements easier to identify, navigate, understand and apply". Neither carries a date.
- Prefabrication certification scheme consultation: The same update reports that feedback from the consultation on the proposed National Voluntary Certification Scheme for Manufacturers of Prefabricated Construction is being reviewed and will "inform the next stage of the project".
- NCC 2022 carries the same question: The NCC 2022 dataset record on data.gov.au carries a metadata creation date of 5 May 2025 and includes a resource named "NCC 2022 READ ME.txt". A business holding NCC 2022 data has the same version question for the edition still in force in several jurisdictions.
Bring us one external dataset
your systems read.
Tell us which published dataset a system of yours consumes, and when it last took a copy. We will show you what a version record would have held, and which internal artefacts a change notice would have had to name.
This article is general information about published Australian Building Codes Board data releases and how records of them are structured. It is not legal advice, it does not interpret any provision of the NCC, and it does not determine whether any product, design or project meets the NCC. It describes dataset records and pages as read on 3 October 2026; those pages can change.
Sources
Suggested citation: ABCB NCC XML dataset records on data.gov.au and ABCB publication pages, as read 3 October 2026. Two figures are derived by date subtraction and are identified as ours in the limits above.
- ABCB - Updated NCC 2025 dataset: Published 24 June 2026, article updated 30 June 2026, read 3 October 2026. Government code administrator, news item.
- ABCB - ABCB data resources: No page date shown, read 3 October 2026. Government code administrator, data publication page.
- data.gov.au - NCC 2025, Superseded (Replaced June 2026): Metadata created 6 May 2026, modified 3 June 2026, read 3 October 2026. Australian Government open data portal, dataset record.
- data.gov.au - NCC 2025 (Version 1.1), Superseded (Replaced 22 June 2026): Metadata created 3 June 2026, modified 22 June 2026, read 3 October 2026. Australian Government open data portal, dataset record.
- data.gov.au - NCC 2025 (Version 1.2): Metadata created and modified 22 June 2026, read 3 October 2026. Australian Government open data portal, dataset record.
- data.gov.au - National Construction Code (NCC) 2022: Metadata created 5 May 2025, read 3 October 2026. Australian Government open data portal, dataset record.
- ABCB - September 2026 CEO update: Published 30 September 2026, read 3 October 2026. Government code administrator, news item.
RELATED READING
Other readings on the same records.
- The industry where being small means staying manual: The Productivity Commission's 53% and the innovation gap that follows firm size. (Productivity & Technology)
- A construction schedule template, and the day it stops being enough: The fields a programme needs to double as a payment record, and why a spreadsheet copy of this table is not the same as a dated one. (Productivity & Technology)
- A regulator's decisions now arrive by email, and the address is your obligation: The QBCC sends notices and decisions primarily by email from 1 February 2026. Contact details must be updated within 14 days, with 10 penalty units stated. (Licensing & Compliance)