What is ADAC?
ADAC, short for Asset Design and As Constructed, is the IPWEA-QNT XML specification Australian councils and utilities use to receive as-constructed infrastructure asset data from developers. It covers stormwater, sewer, water, roads, and open space.
A submission is an ADAC XML file describing the constructed assets, together with the as-constructed CAD drawings of the same works. The council reviews both before the assets are accepted into the asset register and the GIS.
How a council uses it.
When a developer builds a subdivision, the roads, drainage, and water assets inside it eventually become the council's to operate. ADAC is how the description of those assets is handed across. One agreed structure means a council can take submissions from many developers and load them into the same asset register and GIS, rather than transcribing a different spreadsheet each time.
The review is the point at which quality is set. Each asset class carries mandatory attributes, coded value lists, and rules over the values themselves, such as invert levels and cover depths. The drawings have to agree with the file. Whatever passes review is what the council operates, maintains, and renews from for the life of the asset, which is why a wrong pipe length or a missing pit is expensive long after the developer has gone. See as-constructed drawings for the drawing half of the same handover.
ADAC submissions checked on the way in.
ADAC standards are held in Lunr as versioned configuration tied to a project. Turn ADAC validation on for a project, and everything loaded into it is checked against that project's standard: the schema, the mandatory attributes, the value lists, and the business rules over the values.
Lunr also reads the DWG geometry and reconciles it against the XML in real-world coordinates, so an asset missing from either side, a pit out of position, or a pipe length that disagrees is caught rather than assumed. Findings attach to the document as validation errors, drive the review workflow, and hold as-constructed status and asset handover until they are resolved.
See how ADAC validation worksKeep reading.
Validate the XML against your configured standard, cross-check it against the drawing, and hold handover until the findings clear.
The drawing half of an ADAC submission: the set updated to show what was actually built.
How the assets an ADAC submission describes are broken down and tagged once they reach the register.
The asset record, the inherited archive, and contractor handover, for a small council team.
Questions about ADAC.
- What does ADAC stand for?
- ADAC stands for Asset Design and As Constructed. It is an XML specification published through IPWEA-QNT, used across Australia so that asset data handed to a council arrives in one predictable structure rather than in whatever format each developer happens to use.
- What is in an ADAC submission?
- An ADAC submission is an ADAC XML file describing the constructed assets, together with the as-constructed CAD drawings of the same works. The XML carries the asset records and their attributes, and the drawings show the same network as it was built. The council reviews both before the assets are accepted.
- Which asset classes does ADAC cover?
- ADAC covers the infrastructure classes a council takes on from development works, including stormwater, sewer, water, roads, and open space. Each class carries its own set of asset types and mandatory attributes, so a stormwater pit and a road pavement are described in the terms that suit them.
Take ADAC submissions that are checked before they land.
Book a walkthrough and watch Lunr validate an ADAC XML file against your standard, reconcile it against the drawing, and hold handover until the findings clear.
10M+ documents under management · Hosted in Australia and the US · SAML · Full audit trail · Export anytime
- entity
- Lunr Labs Pty Ltd
- location
- Melbourne AU
- workspace
- documents.lunr.app
- rev
- 2026