primoe.
FRLet’s talk about your project

Construction drawing approval: how to organise statuses and drawing flow

One document, one version, one explicit status: organising approval so that everyone involved knows which drawing to use and what action is still expected.

Read the guide 12 min read

By Alain Bonnetaud, founder of PRIMOE · Updated · published

A drawing may have been reviewed without being usable for fabrication or construction. It may also be technically sound but superseded by a new version that has not yet been issued. On site, these ambiguities lead to rework, waiting time and disputes over responsibility.

The approval protocol sets a common language for the contractors, the engineering consultants and the lead consultant. It specifies the documents to be submitted, who reviews them, the possible statuses and the consequences of each response. On a private project, this process must be tied into the contracts.

Approving the contractors’ construction design is the second stage of a construction supervision (MOEX, maîtrise d’œuvre d’exécution) appointment. This guide describes how to organise it; the service as a whole is covered in Construction supervision (MOEX): tasks and deliverables on a private contract.

What is drawing approval, and does it replace the contractor’s construction design?

Drawing approval (visa d’exécution) is the act by which the lead consultant states that it has reviewed one of the contractor’s construction documents and that the document complies with the design. It does not replace the construction design: the contractor, or the engineering consultant that produces it, remains responsible for producing, calculating and checking its drawings.

Construction design develops and sizes the solutions within the scope given to its author. Approval checks that the construction documents produced by the contractors comply with the design, in the wording used in French public procurement (Article R2431-1 of the Public Procurement Code). For new buildings, the same code states that the lead consultant makes sure that the documents produced by the contractors comply with the design, then issues its approval (Article R2431-15 of the Public Procurement Code). These texts apply to public clients; on a private contract, they serve as a reference vocabulary.

The scope of the review depends on the appointment and the expertise assigned. The structure, building services and envelope packages may call for different specialists. The contract must organise this split and how the comments are consolidated.

Approval does not relieve the contractor of its responsibilities as a whole. The general administrative conditions for French public works contracts (CCAG Travaux) say so expressly: issuing the approval does not release the contractor from its own liability (Article 29 of the CCAG Travaux, order of 30 March 2021). Approval may nonetheless make its author liable if a failure falls within its appointment (Article 1231-1 of the Civil Code). A blanket disclaimer stamped on every drawing therefore replaces neither a well-defined scope nor an actual review.

In short: drawing approval is a check of compliance with the design, not a piece of design work. The contractor remains responsible for its drawings and calculations; the approver answers for the review entrusted to it. The scope of that review, package by package, is written into the lead consultant’s contract.

Which approval statuses should you set: VSO, VAO, rejection?

Before the first submissions, set a short list of statuses, each with a meaning and an expected action: no comments, non-blocking comments, to be corrected and resubmitted, for information, outside the appointment. The codes VSO and VAO, common on French sites, have no legal definition: write your own into the contract.

There is no single private-sector classification that gives the codes the same meaning everywhere. VSO usually stands for visé sans observation (approved without comments) and VAO for visé avec observations (approved with comments), but neither the Public Procurement Code nor the CCAG Travaux defines them. One contractor may read “approved with comments” as permission to proceed, another as a request to reissue. The protocol must remove this ambiguity.

The table below suggests an arrangement to adapt and write into the contract. On its own, it creates no right to build: the contract’s other approvals and prerequisites still apply.

Scroll the table sideways →

Suggested statusMeaningExpected action
No comments (often marked VSO)No discrepancy found within the scope of the reviewIssued through the agreed channel; other prerequisites checked
Non-blocking comments (often marked VAO)Adjustments precisely identified, with nothing expressly flagged as blockingComments taken into account and a corrected revision submitted under the agreed rule
To be corrected and resubmittedDiscrepancy preventing use for the work concernedCorrection, then a new review before use
For informationDocument received, not subject to approval under this processRecipients informed, without this counting as an approval
Not applicable to this appointmentDocument outside the reviewer’s scopeReferred to the relevant party

The distinction between blocking and non-blocking comments must be explicit, document by document. Colours can make reading easier, but the status and the expected action must always be written out. A colour code on its own remains ambiguous and poorly accessible.

In short: an approval status is only worth something if the contract defines it. Keep to a few statuses, give each a meaning and an expected action, and state plainly whether or not a comment blocks the work. A code on its own, VSO or VAO, does not tell the contractor what it may do.

How do you know which version of a drawing was approved?

Each approval response identifies the document reviewed beyond doubt: project, trade package, originator, title, number and revision. It shows the date received, the date of response, the status, the comments and the name of the approver. An approval that does not state the revision does not prove which version was reviewed.

Each response states the project, trade package, originator, title, number and revision of the document. It gives the dates of receipt and response, the status, the comments, the references reviewed and the identity of the approver. The distribution list is kept on record.

Every change must be distinguishable from the previous version. Replacing a file under the same name without keeping its history makes it hard to prove which document was actually used. The register links successive revisions and flags the one that supersedes the others.

The “issued for construction” mark (bon pour exécution, BPE) also needs a definition. It can govern the issue or authorisation of documents within a given process; it is not a general transfer of responsibility. The client must know who applies it, and on the basis of which prerequisites.

How to write approval comments that can be acted on

A comment that can be acted on comes down to four things: the discrepancy found, the area concerned, the reference of the drawing or contract document, and what is expected. It does not redesign the contractor’s solution. If it changes the design or the contract, it follows the approval process set for changes.

A useful comment describes the discrepancy, locates the area and gives the reference concerned. It states what is expected without implicitly redesigning the contractor’s whole solution. Proposals that change the design or the contract follow a process suited to their scope.

In practice, writing “inconsistency to be checked” leaves several readings open. Identifying the builder’s work opening concerned, the two conflicting drawings and the coordination request makes it possible to prepare a response. If a new solution has to be calculated, the people who will produce and approve it are named.

Comments from the various parties must be consolidated. Conflicting responses from the architect and an engineering consultant are not resolved by asking the contractor to choose. The register keeps the question, the decision made and the documents it affects.

What review period should you allow, and does silence mean approval?

On a French private contract, the review period is the one set by the contract. On a public contract, the CCAG Travaux sets it at fifteen days and prohibits starting any part of the works without a favourable approval, unless the lead consultant expressly agrees. In both cases, a lack of response does not amount to approval, unless a clause expressly says so.

The submission timetable works back from the dates on which the documents will be needed to order, fabricate or start on site. It includes review time and any corrections. Sending a drawing the day before fabrication does not automatically make an immediate response acceptable.

Periods are set in the contract by document type and according to the agreed procedures. The fifteen-day benchmark comes from public contracts (Article 29 of the CCAG Travaux, order of 30 March 2021); it applies to a private project only if the contract adopts it. The protocol specifies how to deal with an incomplete submission, an emergency and a resubmission. Do not assume that a lack of response means approval: under French law, silence does not amount to acceptance, save for exceptions (Article 1120 of the Civil Code). Any rule of that kind needs an express, carefully considered framework.

The OPC consultant (scheduling and coordination, ordonnancement, pilotage et coordination) tracks the documents on which a critical task depends. An alert becomes actionable when it links a missing document to a deadline and an expected action. It allows decisions to be taken before a document delay turns into a production stoppage, then into an argument over construction delay penalties.

In short: the review period is set in the contract, by document type, working back from the date the drawing is needed. The fifteen days of the CCAG Travaux are a public-contract benchmark. Without an express clause, the lead consultant’s silence does not amount to approval.

How to keep the approval register and track what has been issued

The approval register is a single table, kept up to date by the lead consultant, which gives for each document its current revision, its status, the dates sent and returned, the approver and the distribution list. It makes it possible to prove which version was sent to site, and when.

  • Trade package, originator, title and number of the document.
  • Current revision and the revisions it supersedes.
  • Date received, date returned, contractual period.
  • Status, comments and approver.
  • Recipients and issue date of the usable version.

The register brings together versions, dates, statuses and recipients. The platform must make it possible to identify authors, protect the integrity of files and keep a usable history. Under French law, an electronic document has the same evidential value as a paper one only if its author can be identified and its integrity guaranteed (Article 1366 of the Civil Code). A shared folder without versioning rules does not automatically perform these functions.

Site teams must have access to the usable version, including when printed copies or offline files are needed. Withdrawing old versions is part of the process. Archiving nonetheless keeps earlier documents so that the sequence of events can be reconstructed.

An information management framework such as ISO 19650 can help organise exchanges. On its own, it does not define the legal effect of each approval under French law. The contract and the project’s protocol must complement this document organisation.

What should the contract say for the approval process to work?

Four rules are enough, written into the works contracts and the lead consultant’s contract before the first submissions: the list of documents subject to approval, the statuses and their effect, the return period by document type, and who consolidates the opinions. The approval register follows from them.

  1. List, package by package, the construction documents subject to approval and those sent for information.
  2. Define the statuses, their meaning and what each one permits.
  3. Set the return periods and how incomplete or urgent submissions are handled.
  4. Specify who reviews what, and who consolidates the opinions before the response goes back to the contractor.

The expected result is concrete: knowing which document was received, who reviewed it, with what response, and which version was sent to site. The approval register is one of the documents we hand over to the client in our construction supervision (MOEX) appointments. We work in Paris and Île-de-France: see our Delivery path: AMO, MOEX, OPC and stalled site recovery or write to us.

How many documents does a lead consultant approve? The volume at PRIMOE

PRIMOE approves an average of 450 construction documents a month: drawings, calculation notes, technical data sheets and samples submitted by the contractors. At that volume, an approval without a written status, a revision and a register does not hold up: each document must tell the contractor what it may build and what it must rework.

Starting work, silence, codes, platforms: common questions on drawing approval

Does an approval with comments allow work to start?

It depends on what the contract provides for that status. If the comments are declared non-blocking, the contractor can generally proceed while taking them into account, then submit a corrected revision. If a comment is blocking, the contractor must resubmit the drawing. The approval response must therefore state, comment by comment, what prevents the document from being used.

Does a lack of response from the lead consultant count as approval?

No, unless the contract expressly says so. Under French contract law, silence does not amount to acceptance, except where the law, custom or the parties’ business dealings provide otherwise (Article 1120 of the Civil Code). If you want an approval to be deemed given once a period has passed, write it into the contract, with the start of the period and the documents concerned.

Who consolidates the engineering consultants’ opinions?

The person named in the contract, most often the construction supervisor (MOEX). It gathers the opinions of the architect, the engineering consultants and, where relevant, the technical inspector (contrôleur technique), has any contradictions resolved, then sends the contractor a single response. The contractor should never have to choose between two incompatible opinions.

Is a document management platform enough to prove approval?

Not on its own. Its evidential value depends on identifying the authors, the integrity of the files, the version history and how long records are kept. How access rights are set up and how people habitually issue documents matter as much as the tool: a drawing sent through another channel, outside the platform, escapes the register.

What do VSO and VAO mean on a drawing?

VSO usually stands for visé sans observation (approved without comments) and VAO for visé avec observations (approved with comments). These are site conventions, not terms defined by any statute: their effect varies from one project to another. Check in your contract what each code permits, in particular whether a VAO drawing may be built before the corrected revision is submitted.

What is the difference between an approval and “issued for construction”?

Approval is the lead consultant’s opinion on whether a document complies with the design. “Issued for construction” (bon pour exécution) is an issue status: it flags the version to be used on site. Depending on the contract, it is applied by the contractor or by the lead consultant. Neither transfers responsibility for the design work.

Does the technical inspector approve construction drawings?

No, it gives opinions. Under French law, the technical inspector acts at the client’s request and advises it on technical matters, in particular the structural soundness of the building and the safety of people (Article L125-1 of the Construction and Housing Code). Its opinions come in addition to the lead consultant’s approval; they do not replace it.

Alain BonnetaudFounder of PRIMOE

Contact

Let’s talk about your project.

A building to study, a construction site to run or restart, an operator to find: tell us where you stand.

3 rue Alfred Roll, 75017 Paris, France · Projects across Paris and Île-de-France