Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Industries

IT public procurement, read in the French public procurement code and the CCAG-TIC

In brief

IT public procurement contracts are governed by the French public procurement code for their preparation and award, and by the CCAG-TIC for their performance when the contract refers to it. Management Square reads both texts here: definition of needs, division into lots, procedures, contract documents, verifications, ownership of results and reversibility, with what each leaves to the contract.

Page contents

Under Article L. 1111-1 of the French public procurement code, “a contract is an agreement concluded by one or more buyers subject to this code with one or more economic operators, to meet their needs in terms of works, supplies or services, in return for a price or any equivalent”. IT public procurement contracts are one application of it: hardware, software, development, maintenance, hosting or managed services.

Two texts set the framework. The code governs preparation and award: needs defined before the consultation, separate lots unless there is a reason not to, a procedure chosen according to value, subject or circumstances. The general administrative clauses document for public contracts for information and communication technologies (CCAG-TIC), approved by an order of 30 March 2021, proposes performance clauses: contract documents, verifications, ownership of results, reversibility. It applies only to contracts that refer to it, and these may derogate from it. The rest is written into each contract.

These texts were read on 13 November 2026 in the LEGI database of the DILA open data (archive of 8 November 2026), in the version in force.

Needs defined before the consultation

Article L. 2111-1, in its wording in force since 16 October 2025, requires that “the nature and extent of the needs to be met” be “determined precisely before the consultation is launched”, taking sustainable development objectives into account. From the European thresholds upwards, it adds “energy efficiency and sobriety”.

The services are defined by technical specifications (Article L. 2111-2, version in force since 22 August 2026). Article R. 2111-7 prohibits mentioning a brand or a type likely to favour or eliminate operators, unless justified by the subject of the contract or, exceptionally, where it is impossible to describe it otherwise, the mention in that case being accompanied by the words “or equivalent”.

On our reading, naming a commercial software product in the specifications therefore requires a justification that the buyer can produce. Needs expressed through their functions, volumes and constraints lend themselves better to this; our article on application requirements specification describes its content, outside public procurement rules.

Divide into lots, or justify the opposite choice

Article L. 2113-10 lays down the rule: “Contracts are awarded in separate lots, unless their subject does not allow distinct services to be identified.” The buyer sets the number, size and subject of the lots.

Article L. 2113-11 (version in force since 25 October 2023) allows it not to divide into lots if it is not able to ensure organisation, management and coordination itself, or if award in lots would restrict competition or make performance technically difficult or financially more costly; a third case concerns contracting entities. This choice is justified in law and in fact.

An information system lends itself to several divisions: hardware, licences, development, maintenance, hosting. The text designates none of them. Its first ground suggests, on our reading, that one more lot is also one more interface to coordinate. The division and its justification are for the buyer and its lawyers.

A procedure set by value, subject or circumstances

Under Article L. 2120-1, a contract is awarded without prior advertising or competitive tendering, under an adapted procedure, whose terms the buyer “defines freely” (Article L. 2123-1), or under a formal procedure, to which Article L. 2124-1 refers when the estimated value of the need reaches the European thresholds set out in a notice annexed to the code: call for tenders, without negotiation; procedure with negotiation; competitive dialogue, in which the buyer holds a dialogue with candidates “with a view to defining or developing the solutions” (Articles L. 2124-2 to L. 2124-4). This notice may be amended: we quote none of the thresholds.

Among purchasing techniques, Article L. 2125-1 includes the framework agreement, which preselects operators for the orders of a given period, not exceeding four years for contracting authorities, except in duly justified exceptional cases. Our reading proposes no particular arrangement: the choice of procedure and the assessment of its lawfulness belong to the buyer.

The CCAG-TIC, a document to which IT public procurement contracts may or may not refer

Article R. 2112-2 allows the clauses of a contract to be set by reference to a general administrative clauses document, and Article R. 2112-3 requires the articles from which it derogates to be indicated. The order of 30 March 2021, in force on 1 April 2021, approves the CCAG-TIC, which “applies only to contracts that refer to it”, and repeals as of 1 October 2021 the order of 16 September 2009 approving the previous document. Its preamble declares it unsuited to contracts concluded by private buyers.

In the event of contradiction, Article 4.1 gives precedence to the deed of commitment, then the special administrative clauses document (CCAP), the special technical clauses document, the CCAG, the general technical clauses document if referred to, before the contractor’s technical offer. Verifications and the acceptance decision (Articles 30 to 34) are presented in our article on user acceptance testing. For the rest, the document sets a default regime and refers to the special documents:

Subject What the CCAG-TIC provides What the contract writes
Warranty At least one year from notification of acceptance (Article 36.1) The repair time, set by the buyer by default (Article 36.3)
Managed services Definitions, transition period (Article 38) Service levels, their measurement and penalties (Article 38.2.1)
Reversibility Definition and minimum content (Article 38.4) The reversibility plan annexed to the CCAP: duration and conditions
Results Non-exclusive assignment of economic copyright, with exceptions (Article 46.2.1) The purposes of use, confidentiality, any royalty (Articles 46.1 and 46.3.1)

Results, prior knowledge and reversibility

Chapter 7 distinguishes results, produced under the contract, from prior knowledge, produced independently of it, including standard software (Article 43). The contract does not transfer rights in prior knowledge (Article 44.1); if not identified as such in the offer or before its integration, a delivered element “is deemed to be a result” (Article 44.2).

The contractor assigns the economic copyright in the results, for the purposes of the contract, and delivers progressively the executable code, the documentation and the source code (Articles 46.2.1 and 46.4.1.1). Data integrated or generated under the contract “belongs exclusively to the buyer” (Article 46.2.3). Custom software development is directly concerned: the specific software falls under results, pre-existing components under prior knowledge.

Reversibility refers to the operations by which the buyer, or a third party it designates, takes back the services entrusted to the contractor (Article 38.4). It includes at least the executable software, where applicable the source code, the documentation, the configuration and operating scripts, and access to data in documented formats. Our entry on third-party application maintenance describes the takeover of maintenance; for cloud hosting, the plan joins that of a cloud migration.

Hosting and security fall under other texts: the “cloud au centre” doctrine, the SecNumCloud qualification, security accreditation. Our public sector page places public procurement among the frameworks of a public digital project.

For a contract in preparation, you can go through the CCAG-TIC article by article, noting what the future CCAP takes over, supplements or sets aside. The articles set aside form the list of derogations required by Article 1.2 of the document; the references to special documents, what the contract will have to write itself.

FAQ

Frequently asked questions

Another question? Ask us

Is the CCAG-TIC mandatory for an IT contract?

No. The order of 30 March 2021 approving it specifies that this document applies only to contracts that refer to it, and Article R. 2112-2 of the public procurement code presents reference to a general administrative clauses document as an option. A contract that refers to it may derogate from some of its provisions, provided these derogations are listed in the last article of its special administrative clauses document.

Must a public IT contract be awarded in separate lots?

Article L. 2113-10 of the public procurement code lays down the principle of separate lots, unless the subject of the contract does not allow distinct services to be identified. Article L. 2113-11 lists the cases in which the buyer may choose not to divide into lots, for example when it cannot itself ensure management and coordination, and then requires it to justify this choice in law and in fact. Assessing a specific case is for the buyer and its lawyers.

Can a software brand be named in a public contract?

Article R. 2111-7 of the public procurement code prohibits mentioning a brand, a patent or a type in the technical specifications when this mention may favour or eliminate certain operators or products. It allows it if the subject of the contract justifies it, or exceptionally when the subject cannot be described otherwise, the mention then being accompanied by the words "or equivalent".

Who owns the software developed under a contract subject to the CCAG-TIC?

Unless derogated from, the contractor assigns to the buyer, on a non-exclusive basis, the economic copyright in the results (the document provides for an exclusive assignment for some, including results classified as confidential), for the contract's purposes of use (Article 46.2.1 of the CCAG-TIC), and delivers the source code with the documentation (Article 46.4.1.1). It retains its know-how and may commercially exploit results not assigned on an exclusive basis, in return for a royalty whose calculation is set by the special documents (Article 46.3.1). Prior knowledge remains with its owner.

How is the procedure for an IT contract chosen?

Under Article L. 2120-1 of the public procurement code, a contract is awarded without advertising or competitive tendering, under an adapted procedure or under a formal procedure, depending on its value, its subject or the circumstances of its conclusion. The European thresholds that trigger formal procedures appear in a notice annexed to the code, which may be amended. The choice and its lawfulness are matters for the buyer.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.