The three families
| Framework | Scope | Nature |
|---|---|---|
| CCTB | Wallonia and the French Community | reference-by-citation document |
| Flemish building framework | Flanders, the most used basis | full transcription of articles |
| Federal framework | Buildings Agency, bilingual | own use for its own contracts |
Private coding systems are added, distributed by software vendors and by practices, together with a Dutch methodology that some Belgian tools can integrate. Their status depends on the contract that invokes them.
None of these families is meant to absorb the others. They coexist, and a professional working across regions encounters all of them.
The structural difference: citation or transcription
This is the most important point in this article, and the one everyday vocabulary conceals. The frameworks do not rest on the same updating mechanism.
The CCTB is a reference-by-citation document. A project's particular specification does not copy the prescriptions: it cites the framework and states only the clarifications, additions and derogations specific to the contract. The project document stays short, and the technical content lives in the framework.
The Flemish building framework does not work that way. It is not a citation document: the articles relevant to the project are transcribed in full into the particular specification, starting from the most recent version of the framework. The project document becomes self-contained, and far longer.
The consequences are not symmetrical.
| Citation document | Full transcription | |
|---|---|---|
| Size of project document | limited | substantial |
| Updating of content | carried by the framework | frozen at date of transcription |
| Principal risk | ambiguous reference version | transcribed text gone stale |
| Necessary check | which version applies | is the text current and complete |
The two methods therefore expose users to different errors. Under citation, the error concerns identifying the version. Under transcription, it concerns maintaining the copied text, which falls entirely to its author.
What the absence of unification costs
Three concrete effects, regularly reported by practitioners. They touch comparability, drafting and checking.
Exchanging bills is laborious. A bill structured under one coding system and one structured under another do not align automatically. Reconciling them requires manual correspondence work, item by item, with scope for error at every line.
Comparing offers becomes harder. Two contractors responding on different bases produce documents whose apparent gap owes as much to structure as to prices.
The move to BIM suffers. A model produces quantities that must be attached to items. Without a common coding system, that attachment is redone on every project.
This is not an outsider's opinion. The Belgian industry has itself called for years for a single working methodology, covering specification texts, bills of quantities, the organisation of drawings and BIM classification, pointing to the confusion arising from exchange between divergent systems.
Why the situation persists
Three reasons combine, and none amounts to negligence. They relate to institutional history, devolved powers and tooling.
Competence is divided. Public procurement rules are federal, but the technical frameworks were developed by regional and community bodies, each for its own scope.
The frameworks have distinct histories. They were not born at the same moment nor for the same purpose: one aimed at a general framework, another at social housing, a third at the federal estate.
None is mandatory everywhere. Each applies within its own scope and remains optional beyond it, which makes unification hard to decree.
What this means for a professional
Four practical rules.
Identify the framework before reading a bill. That question precedes all others, including quantities.
Never assume an identical item in two bills covers the same work. Division and inclusions vary by framework.
Under full transcription, check the date of the copied text. A Flemish particular specification based on an old version does not say so.
Under citation, check which version applies. That question is covered in the article on the annual update.
The articles in this branch
The article on the CCTB covers its exact scope, its status and its update cycle. Its scope and status are set out there.
The article on the Flemish framework covers full transcription and its consequences. Its own mechanics are explained there.
The article on the federal framework and private coding covers how bills circulate between systems. Their articulation with the regional frameworks is covered there.
The article on comparing a Walloon and a Flemish bill gives the reconciliation method. The comparison is made there item by item.
This article reflects the position of professional frameworks at the date of checking and serves as orientation. It does not constitute legal advice and does not replace assessment of the individual case.