Plan Verification, Technical Audit, Contrôle Technique: What Each One Actually Does in 2026

TL;DR. Plan verification is the upstream review of construction documents against codes, owner requirements, and standards, performed before construction begins. Technical audit is a broader diagnostic exercise — typically retrospective or due-diligence in nature — that looks at the state of a building or a project's documentation. Contrôle technique is the regulated mission defined by the Loi Spinetta of 1978 and now codified at articles L125-1 to L125-6 of the Code de la Construction et de l'Habitation, performed by an agréé contrôleur technique to prevent technical hazards affecting structural soundness and occupant safety. The three are not interchangeable, and on most French projects two or three of them coexist.

On any French construction project of meaningful scale, three terms get used in the same sentence and treated as if they meant the same thing: vérification des plans, audit technique, and contrôle technique. They do not. They describe three different services, performed by different parties, at different moments in the project, under different legal regimes. Conflating them produces real operational problems: scopes get duplicated, gaps get missed, and the maître d'ouvrage ends up paying twice for partial coverage of work that needed to happen once, completely.

This article disambiguates the three. We define each one against its actual legal and operational scope, lay out a comparative table, and describe where Freeda's service sits within the ecosystem.

What contrôle technique actually is (and isn't)

Contrôle technique is the most narrowly defined of the three because it is the only one with a dedicated legal regime. It was created by the Loi n°78-12 du 4 janvier 1978 — the Loi Spinetta — and its application decree, the Décret n°78-1146 du 7 décembre 1978. After the 2020–2021 recodification of the CCH (Ordonnance n°2020-71 du 29 janvier 2020 for the legislative part and Décret n°2021-872 du 30 juin 2021 for the réglementaire part), the regime is now codified at articles L125-1 to L125-6 of the Code de la Construction et de l'Habitation, with the obligatory cases at articles R125-17 to R125-21.

The mission of the contrôleur technique, per article L125-1, is to contribute to the prevention of technical hazards encountered during the construction of works. The opinion delivered to the maître d'ouvrage covers, in particular, structural soundness and the safety of persons. The activity is subject to ministerial agrément and is legally incompatible with any conception, execution, or expertise activity on the same project — the independence requirement is structural, not optional.

Contrôle technique is mandatory for a defined list of construction categories at article R125-17, including: établissements recevant du public (ERP) of the first to fourth categories; immeubles de grande hauteur (IGH) with a floor more than 28 metres above the highest ground level accessible to fire services; buildings with cantilevers over 20 metres, beams or arches over 40 metres, deep foundations, or significant underpinning works; and buildings in seismic zones or other defined risk areas. On these projects, signing a contrat de contrôle technique with an agréé firm is not a service choice — it is a legal precondition for permits and insurance.

The mission begins at conception, continues through construction, and ends at réception. The deliverables are well-defined: an initial rapport initial de contrôle technique on the design, then periodic reports during execution, then a rapport final at handover. The scope is set by the contract between the maître d'ouvrage and the contrôleur technique, drawing on the missions defined by the AFNOR standard NF P 03-100 (L for solidité, S for sécurité des personnes, F for sécurité incendie, and so on through the alphabet of standardised missions).

What technical audit actually is

Audit technique has no equivalent legal regime. It is a broader, market-defined service that describes any diagnostic review of a building's technical state or a project's technical documentation, usually performed independently of the parties responsible for the work being audited. The audit can be physical (a survey of an existing building) or documentary (a review of plans, specifications, calculation notes, or compliance evidence). It can be commissioned for due diligence ahead of an acquisition, to substantiate a dommages-ouvrage claim, to assess remaining service life, or to verify that work already done meets a defined standard.

The key difference from contrôle technique is timing and orientation. Contrôle technique is mandatory, prospective, regulated, and concerns specific risk categories. Technical audit is voluntary, often retrospective, market-priced, and concerns whatever the client asks it to concern. The auditor is rarely the same firm as the bureau de contrôle on the same building, because the conflict-of-interest rules that govern contrôle technique do not govern audit work — but the audit firm is still expected to be independent of the parties whose work it is reviewing.

What plan verification actually is

Plan verification — vérification des plans — is the most general of the three terms and the one most often used loosely. In its operational sense, it refers to the systematic review of construction documents (plans, technical specifications, descriptive notes, owner requirements) against an external reference: a building code, an accessibility regulation, a fire safety standard, a brand book, a programmatic brief. The deliverable is a structured report of conformities and non-conformities, located in the documents and ranked by impact.

Plan verification overlaps with both contrôle technique and audit, but is not identical to either. Contrôle technique includes a documentary review of plans as one of its activities, but its scope is restricted to the missions defined in the contract (typically L, S, F, and a handful of others) and to the categories of risk the regime exists to prevent. A bureau de contrôle reviewing a 600-page DCE will not typically check every drawing against every applicable code; it will sample, focus on its contracted scope, and produce its opinion on the basis of that sample. Audit, similarly, will check what the client asks it to check, against the standard the client specifies, at the depth the client commissions.

Plan verification as a standalone service exists to fill the gap between these: an upstream, full-coverage review of every construction document against every applicable rule, before construction begins and before the contrôleur technique's sampling-based review.

Comparative table

Where Freeda sits

Freeda is a plan verification service. We are not a bureau de contrôle and we do not perform contrôle technique missions in the regulatory sense. On a project where contrôle technique is mandatory, the maître d'ouvrage still contracts an agréé bureau de contrôle — Freeda does not displace that role, and the partnership we announced with SOCOTEC in January 2026 is explicitly built around extending the capacity of contrôle technique firms, not replacing them.

Where Freeda operates is the upstream zone. We read the full set of construction documents — plans, CCTP, descriptive notes, brand and owner requirements — and check them against the applicable codes (CCH, ERP regulations, accessibility under the arrêté regime, fire safety, RE2020 where relevant) and against the maître d'ouvrage's own technical reference. Our team of architects, engineers, accessibility specialists, and fire safety experts validates every finding. The report identifies non-conformities with their location in the documents and a remediation step for each. The turnaround is 48 hours.

The point of doing this upstream is asymmetric economics. A non-compliant corridor width caught on a plan costs the architecte minutes to redraw. The same corridor caught during contrôle technique's review costs days to a few weeks of design rework. The same corridor caught on site after construction has begun costs months of delay and the kind of figures every Director of Projects has seen on an internal post-mortem.

How the three services typically coexist on a French project

On a residential project of around 100 units submitted for a permis de construire, the typical sequence is: an upstream plan verification phase before depositing the permit (catching errors against the CCH, the PMR regulation, and the local PLU); a contrat de contrôle technique signed with an agréé bureau before construction starts (covering at minimum the L and S missions, often F and others depending on the project); periodic contrôle technique review during execution; and, if the project is sold or refinanced later, a technical audit at the point of transaction.

The three are sequential, not substitutable. Skipping the upstream verification on the assumption that the bureau de contrôle will catch everything is a common pattern and a costly one — the contrôleur technique's mission is to prevent specific categories of risk, not to perform an exhaustive code check. Conversely, treating a plan verification report as if it were a contrôle technique opinion misrepresents both. The maître d'ouvrage who understands the distinction commissions each service for what it actually delivers.