Key takeaways
- HIB 3.0 is the technical guideline of the Dutch Central Government Real Estate Agency for ICT housing and cabling, and it shows how detailed the assessment of digital infrastructure can be.
- An
IT-Label audit can recognise and check relevant technical principles from HIB 3.0 without becoming a shortened copy of that handbook. - The strength of
IT-Label lies in the translation: from technical requirement to audit point, and from audit point to an understandable delivery level ranging from IT1+ PREMIUM to IT5 SHELL. - Documentation and management deserve extra attention, because
well-built infrastructure without registration can still be difficult to hand over to a new user. - An
IT-Label does not replace HIB 3.0 and does not mean a building complies with HIB 3.0; it assesses the actual digital delivery level for the user.
The Dutch Central Government Real Estate Agency works with an extensive technical guideline for the digital infrastructure of its buildings: the Handbook for ICT Housing and Cabling, in the version known as HIB 3.0. The document describes how ICT rooms, cabling, connection points, redundancy and management should be designed and realised in government buildings. It is written for technicians and project managers, not for investors or brokers.
Still, HIB 3.0 is interesting for anyone involved in the digital quality of real estate. Not because commercial property should meet the same level as a government office, but because the handbook illustrates a principle: digital infrastructure can be designed, standardised, documented and
The central question of this article is therefore not whether
What HIB 3.0 does and does not cover
HIB 3.0 focuses on the passive,
What matters is what does not automatically fall within scope. HIB 3.0 covers housing and cabling, not the active ICT equipment an organisation installs itself, nor
Anyone reading HIB 3.0 will notice how systematically responsibilities and boundaries are recorded. That makes the handbook not just a collection of technical requirements, but also an example of how to organise scope and transferability. That last point in particular is valuable for an audit that ultimately needs to be readable for a broad audience.
From technical requirement to audit point
The temptation is great to shorten the hundreds of requirements in HIB 3.0 into a checklist and simply tick them off during an inspection. That would be a mistake. The result would be a technical exam that a tenant or investor cannot read. The task for an
A useful approach is to ask three questions for each relevant component. What is technically relevant and why? What can an auditor objectively establish during a building inspection? And what does that ultimately mean for the user? Two examples make this concrete.
Fibre-optic backbone and redundant routes. Technically, this concerns the number of connections and their physical separation. The auditor can check how many connections are present, how they enter the building and what expansion space is available. For the user, this translates into: how dependent am I on a single connection, and what happens in the event of a fault?- Structured data cabling. Technically, this revolves around category, age, connection points and patch facilities. The auditor assesses type, condition, coverage and documentation. For the user, this becomes: can I connect my workstations immediately, or do I first need to invest in new cabling?
That common thread, from technical requirement to audit point to delivery level to meaning for the user, is where the translation happens. It is also what distinguishes
A user does not want to read a handbook of hundreds of requirements. They want to know what the building can handle digitally and what that costs.
A possible audit matrix
To make the principles from HIB 3.0 workable, an audit can group relevant checkpoints into categories. What follows below is a proposal for further development, not an established methodology. The goal is structure, not completeness.
Connectivity and internal infrastructure
The first question is what enters the building: fibre optics, other fixed connections, the number of available providers, capacity and the physical entry points. The second question is how data is subsequently carried through the building and the rented space, via backbone, copper and
ICT rooms, redundancy and smart readiness
ICT rooms require attention to location, accessibility, physical security, available space, power supply and climate. Redundancy and continuity revolve around dual connections, separated routes and identifying single points of failure, a topic we covered extensively earlier in redundancy explained. For smart readiness, one distinction is crucial: can the infrastructure support sensors, access control, PoE and building management systems, or is the application actually present? These are two different things.
Documentation and management
This component deserves extra attention.

Curious about your building's IT-Label ?
Discover how your property scores on digital infrastructure.
Request an IT-LabelFrom hundreds of requirements to a few understandable performances
To keep the audit readable, technical checkpoints can be brought together under a limited number of performance categories. This too is a possible direction, to be critically tested against both HIB 3.0 and the existing
- CONNECT. How well is the building connected externally?
- DISTRIBUTE. How well can data be distributed internally?
- CONTINUE. How robust and redundant is the infrastructure?
- SECURE. What physical and digital security provisions are present?
- SCALE. How easily can the infrastructure grow along with demand?
- SMART. To what extent is the building prepared for
smart-building technology? - MANAGE. How well are infrastructure, documentation and responsibilities organised?
The advantage of such performance categories is that they bridge the technical depth of HIB 3.0 and the simplicity a real estate professional needs. They translate dozens of checkpoints into a handful of questions everyone can follow. The current methodology assesses six areas: connectivity, infrastructure, performance, scalability, integration and smart building.
The translation table
The following table shows how a technical world, an audit point and a real estate translation come together. Each row ends with the question the user actually asks.
| Technical world | Real estate translation | User's question | |
|---|---|---|---|
| Fibre optics and backbone | Check presence and capacity | Connectivity | Can my company function digitally here? |
| Redundancy | Check connections and routes | Continuity | What happens in the event of an outage? |
| Data cabling | Assess type, condition and coverage | Plug and play | Can I connect my workstations? |
| ICT room | Check space, power, climate and security | IT housing | Where will my equipment be placed? |
| Scalability | Assess spare capacity and expansion | Digital growth capacity | Can my company grow here? |
| Documentation | Check registration and drawings | Manageability | Does anyone actually know what is there? |
| Smart readiness | Assess supporting infrastructure | Can this building become smarter? |
From audit to classification
The outcomes of an audit can ultimately contribute to the existing classifications. Importantly: an IT1+ PREMIUM does not simply mean that a building meets all HIB 3.0 requirements.
- IT1+ PREMIUM and IT1 HIGH PERFORMANCE. A very complete, respectively
high-quality digital ecosystem, with strong continuity, scalability and manageability. With IT1 HIGH PERFORMANCE, only limiteduser-specific optimisations are needed. - IT2 PLUG & PLAY and IT3 READY. A strong foundation that allows a user to become operational quickly, or a situation in which the essential provisions are present but a substantial part of the
fit-out still rests with the tenant. - IT4 CORE and IT5 SHELL. Mainly basic connections present, with the user realising a large part themselves, or a digital
shell-and-core situation. We explained what that means in concrete terms in what IT4 CORE or IT5 SHELL means for your building.
This creates a logical and traceable chain: from technical standard to audit, from findings to label, and from label to a delivery level that a user understands.
Curious about your building's IT-Label ?
Discover how your property scores on digital infrastructure.
Request an IT-LabelThe demarcation list as the final piece
One of the strongest lessons from professional technical projects is careful demarcation. An audit should ideally not only state what is present, but also provide insight into who is responsible for what. That requires distinguishing between
The classification does not automatically determine who is legally or contractually responsible. That is recorded in a demarcation list, which aligns with the agreements between tenant and landlord and with the question of who is responsible for IT in the lease agreement. The label makes the situation transparent; the demarcation list makes the agreements binding.
Your next step
From technical requirement to audit point, from audit point to delivery level, from delivery level to IT1+ through IT5. Because ultimately, a user does not want to read a handbook of hundreds of requirements. They want one question answered: what can this building handle digitally, and what does that mean for my organisation? If you would like to know how an audit works for your property, read more about how the
How does your building score?
Do the free
This article was written by the
Stay up to date with our knowledge articles
Receive our new articles on digital infrastructure in real estate in your inbox. No spam, unsubscribe at any time.
Almost done
We have sent you an email. Click the link in that email to confirm your subscription.