Vienna’s mandatory electronic Bauwerksbuch shows how phased obligations, professional verification and lifecycle responsibility can improve building data. The article compares this safety and maintenance record with the EPBD Digital Building Logbook and identifies six lessons for Europe.
(Note: Opinions in the articles are of the authors only and do not necessarily reflect the opinion of the European Union)
Vienna’s mandatory electronic Bauwerksbuch creates a verified, continuously maintained record of building condition, inspections, defects and selected renovation measures. Although it is narrower than the Digital Building Logbook envisaged by Directive (EU) 2024/1275, the Vienna model offers practical European lessons on mandatory uptake, phased implementation, professional verification, lifecycle responsibility, data governance, and interoperability.
Europe’s renovation challenge is also a data challenge. According to the European Commission, 85% of EU buildings were constructed before 2000, 75% have poor energy performance, and the annual energy renovation rate remains at about 1%. Reaching a zero-emission building stock therefore depends not only on technologies and finance but also on reliable information about each building’s fabric, condition, legal history, and previous interventions.
The recast Energy Performance of Buildings Directive, Directive (EU) 2024/1275, reflects this need through energy performance certificates, renovation passports, smart readiness indicators, national databases and Digital Building Logbooks. These instruments are intended to support better decisions throughout a building’s lifecycle.
Vienna’s Bauwerksbuch — literally, 'building logbook' — approaches the data problem from a different starting point: building safety and maintenance. It establishes a mandatory electronic record, verified at key stages by qualified professionals and maintained by the owner or property manager.
The Bauwerksbuch is not the comprehensive Digital Building Logbook envisaged by the EPBD. Nevertheless, it demonstrates how legislation can establish responsibility for collecting, verifying and updating building information. It also exposes the important gap between an electronic document system and an interoperable building-data ecosystem.
Vienna introduced the Bauwerksbuch in 2014 for specified new buildings, extensions and conversions. A 2023 amendment substantially extended the instrument to parts of the existing building stock. Under section 128a of the Vienna Building Code, a Bauwerksbuch must be created for relevant new construction, extensions and conversions before the notice of completion is submitted.
For existing buildings, the rollout is phased:
The City of Vienna stated in May 2026 that the first deadline affects around 31,000 buildings and the second around 23,500. Allotment garden houses, allotment garden dwellings and buildings with a built-up area of no more than 50 square metres are exempt. The authority may also require a Bauwerksbuch for another building in a justified individual case.
For existing buildings, an initial inspection forms part of the process. The law combines defined professional qualifications with independence from the central project parties. The Bauwerksbuch must then be maintained electronically by the owner or, where a property manager has been appointed, by that property manager.
The Bauwerksbuch is not designed as a report that becomes obsolete once delivered. It assigns responsibility for keeping the record up to date throughout the building’s operation.
The statutory content extends well beyond a one-off condition survey. It includes:
The components concerned are those whose deterioration could endanger life or health. The legislation expressly mentions structural elements, the building envelope, railings and parapets without making that list exhaustive.
The City of Vienna’s official explanatory guidance confirms that no single prescribed document layout applies. It recommends a structure covering general building data, permits and plans, the construction and relevant components, inspection requirements, inspection results, defects and remedial measures.
In practical terms, the Bauwerksbuch records who must inspect what, at which interval, with which qualification, what was found and what action followed.
Vienna also established a municipal Bauwerksbuch database under section 128c of the Vienna Building Code. Registration has been available since 1 July 2024.
The distinction between the Bauwerksbuch and this database is essential. The registration process records the creation date and an electronically signed confirmation that the logbook was created. For the relevant existing buildings, it also records the date and signed confirmation of the initial inspection.
The complete Bauwerksbuch is not routinely uploaded. The City’s official registration page lists the prescribed confirmations as the required registration documents. The full electronic record remains with the owner or property manager and must be made available to the authority on request.
The municipal database is therefore a compliance register: it provides evidence that the required record and inspection exist. It does not centrally store the underlying permits, component information, inspection findings, defect history and maintenance documentation.
This design can limit unnecessary central data collection and leave operational responsibility close to the building. Its limitation is equally clear: digitising a registration process does not automatically make the underlying information structured, interoperable or reusable.
For German-speaking practitioners, a detailed implementation guide to Vienna’s electronic Bauwerksbuch and municipal registry explains this distinction in operational terms.
Article 2(41) of the recast EPBD defines a Digital Building Logbook as a common repository for all relevant building data. The definition expressly includes energy performance certificates, renovation passports, smart readiness indicators and life-cycle global warming potential data. Its purpose is to facilitate decision-making and information sharing among construction professionals, owners and occupants, financial institutions and public bodies.
Vienna’s Bauwerksbuch has a narrower legal purpose and data scope:
Primary purpose
Vienna’s Bauwerksbuch: Building safety, condition, inspection planning and maintenance documentation.
Digital Building Logbook under the EPBD: A common repository supporting decisions and information sharing across the building lifecycle.
Core data
Vienna’s Bauwerksbuch: Permits, relevant components, inspections, defects, remedial plans and specified renovation records.
Digital Building Logbook under the EPBD: All relevant building data, including EPCs, renovation passports, SRI and life-cycle GWP.
Architecture
Vienna’s Bauwerksbuch: Electronic record held by the owner or manager, plus a municipal compliance register.
Digital Building Logbook under the EPBD: Common, accessible repository or governed connections between relevant data sources.
Interoperability
Vienna’s Bauwerksbuch: No common machine-readable Bauwerksbuch schema is prescribed.
Digital Building Logbook under the EPBD: EPBD provisions link DBLs with renovation passports, building systems data and national energy-performance databases.
It would therefore be inaccurate to state that Vienna has already implemented the comprehensive Digital Building Logbook envisaged by the EPBD. A more precise assessment is that the city has created a mandatory electronic building record with several DBL-relevant governance features: assigned responsibility, phased coverage, professional verification, lifecycle updating and official registration.
Recent European work also emphasises that the next step is not simply to add more PDF files. The Digital Building Logbook Organisational Model identifies governance, interoperability, data sovereignty and secure data exchange as key implementation challenges.
Although Vienna’s Bauwerksbuch is primarily a safety and maintenance instrument, it has a direct point of contact with renovation. Section 118(3) of the Vienna Building Code requires specified individual building-component renovations and changes to technical building systems to be documented. Where a Bauwerksbuch exists, that documentation must be included in it.
The practical relationship goes further, although its effects have not yet been formally evaluated. Energy measures do not take place independently of a building’s condition. Façade defects can influence the timing and design of insulation. Roof damage may need to be addressed before insulation or photovoltaic systems are installed. Moisture, structural issues or unresolved approval questions can change the sequence, cost and feasibility of a renovation plan.
Article 12 of the EPBD requires renovation passport schemes based on a common European framework. Under Article 12(8), the renovation passport must be stored in, or accessible through, a Digital Building Logbook where one is available. Article 16 links available building-systems data to the DBL, while Article 22 requires national energy-performance databases to be interoperable and integrated with relevant administrative building databases and DBLs.
Verified condition and maintenance information can therefore complement energy-performance data. It does not replace an energy assessment or renovation passport. Conversely, an energy certificate does not replace a building-safety inspection. The value lies in making both information streams available to the professionals planning the next intervention.
Create adoption, not only a platform
Voluntary databases risk remaining incomplete. Vienna first created a legal obligation, identifiable duties and deadlines. This generates demand for the record before a comprehensive data ecosystem exists.
For other jurisdictions, the transferable principle is not necessarily to copy the same obligation, but to define the regulatory or service trigger that ensures information is actually created and maintained.
Phase the rollout according to capacity and need
Vienna did not impose a single deadline on the entire existing stock. It prioritised the oldest buildings and divided implementation into two tranches.
A phased approach gives owners, professionals and authorities time to build capacity, refine guidance and improve digital procedures. Other jurisdictions could phase by age, risk, renovation need, building type or transaction events.
Assign a lifecycle custodian
Data quality deteriorates when responsibility ends after the first report. Vienna places ongoing responsibility on the owner and, where appointed, the property manager.
A broader DBL framework likewise needs explicit rules for who may enter, update, verify and access each category of information.
Combine data collection with professional verification
Vienna links creation and the initial inspection to qualified, independent professionals and signed confirmations. This provides accountability for safety-relevant information.
For interoperable DBLs, professional verification must be complemented by common definitions, required fields, validation rules, provenance and version histories.
Distinguish the evidence layer from the data layer
The municipal register confirms compliance, while the detailed record remains with the owner or manager. This separation can support proportionality and data sovereignty.
However, policymakers should state clearly whether a system is a compliance register, document archive, common data environment or gateway to distributed sources. Each model creates different requirements for access, security, maintenance and reuse.
Design interoperability before unstructured files become the legacy
Electronic documents are a useful starting point, but “electronic” does not necessarily mean machine-readable.
A future-proof system needs persistent building identifiers, a minimum data dictionary, role-based access, audit trails, portable exports and governed interfaces to permits, cadastres, EPCs, renovation passports and technical-system data. Adding these elements after thousands of heterogeneous records have accumulated is considerably harder than designing for them from the outset.
Vienna’s model can be understood as three possible levels of maturity. The first is the electronic record maintained by the owner or property manager. The second is official registration confirming that the record and required inspection exist. The third would be governed interoperability: selected data becoming securely reusable for maintenance, renovation planning, energy assessment and policy without unnecessarily centralising every document.
The European Commission’s study defining an EU framework for Digital Building Logbooks identified consistent, reliable and accessible data as a prerequisite for better building management, investment and policymaking. Vienna demonstrates that legislation can establish uptake, responsibility and verified milestones. A comprehensive DBL must add common data structures, durable identifiers, controlled access and interoperable exchange.
These are potential development steps, not features already required by Vienna’s present legislation. That distinction matters. The city’s experience is useful precisely because it shows both what a mandatory electronic record can achieve and what remains unresolved when the detailed information stays in heterogeneous files.
Vienna’s Bauwerksbuch should neither be dismissed as a conventional document folder nor presented as a completed EPBD Digital Building Logbook. It is a mandatory electronic safety and maintenance record supported by professional verification, ongoing responsibility and an official compliance register.
Its European relevance lies in the governance choices it makes and the limitations it exposes. Clear deadlines, accountable custodians and verified information can establish adoption. Yet electronic records and registration confirmations alone do not provide the broad data scope or interoperability expected from a Digital Building Logbook.
Europe’s practical challenge is therefore not simply to digitise more building documents. It is to connect verified information about condition, energy performance, renovation and lifecycle impacts so that it remains useful, current, secure and proportionate. Vienna offers a credible starting point — and a reminder that a digital logbook becomes valuable only when governance and data architecture develop together.
