--- site: bid-writing-software.ai slug: /comment-analyser-un-dce langue: en title: How to analyze a set of tender documents (DCE): the reading method to miss nothing before drafting the technical proposal. description: Analyzing a set of tender documents means reading each part of the tender file in order, extracting the requirements and scoring criteria, and logging them in a matrix before drafting. rubrique: Understanding intention: Info requete_type: factual derniere_revue: 2026-09-05 statut: publiable --- # How to analyze a set of tender documents (DCE) Analyzing a set of tender documents means reading each part of the file in order, extracting the requirements and scoring criteria, then logging them before drafting. ## What is the DCE and what does it contain? In France, the DCE (dossier de consultation des entreprises), or tender documents, brings together every paper a public buyer issues to bidders for a given contract. It is the single source of what is being asked for and of how the bid will be judged. It typically contains the tender rules, or instructions to tenderers (the RC in France, which sets the rules of the game: response format, criteria, dates), the technical specification (the CCTP in France, which describes the requirement to be met), the contract conditions (the CCAP in France, which sets the terms of performance), the signed bid form, the financial response template, and annexes specific to the contract. Reading a set of tender documents is not skimming one document, it is taking several apart. Each part speaks to a different piece of the response, and a requirement missed in one of them is paid for when bids are opened. ## In what order should you read the parts of a tender file? The reading order for a tender file starts with the rules before moving to the requirement. You read the tender rules first, because they say how to respond, what the bid will be scored on, and by what deadline to submit. You then read the technical specification, which describes what the buyer wants to obtain, requirement by requirement. You read the contract conditions and the financial framework last, since they govern performance and price. This order avoids the costliest mistake: writing a brilliant technical proposal that misses the criteria, because the tender rules were only opened at the end. ## What does each part of the tender file govern? Each part of the tender file governs a piece of the response. The table below links the document, what it dictates, and where in the response that will be used. Spotting this correspondence is the reading work; extracting each requirement from it, one by one, is the detailed work covered on the [dedicated requirement-extraction page](/en/extraire-les-exigences-d-un-appel-offres). | Tender-file document | What you look for in it | Where the information is used | |---|---|---| | **Tender rules (RC)** | scoring criteria, weighting, format, and deadline | the proposal outline, the matrix, the schedule | | **Technical specification (CCTP)** | every technical requirement of the need | the compliance matrix, every response | | **Contract conditions (CCAP)** | performance conditions, penalties, deadlines | the commitment, the delivery method | | **Financial framework** | expected structure and detail of the price | the financial bid | | **Annexes** | documents to attach, mandated formats | the completeness check | A reading that places every document like this turns the file into a map; skimming it, by contrast, leaves requirements with no anchor point. ## How do you connect analysis of the tender file to scoring? Connecting the analysis to scoring means finding, in the tender rules, the award criteria and their weight, then allocating drafting effort accordingly. Award criteria and their weighting are announced in advance in the tender documents (in the United States, under the Federal Acquisition Regulation; in the United Kingdom, under the Procurement Act 2023). Analyzing the tender file therefore also means reading this grid before writing, to concentrate the evidence where it earns points. A technical proposal that ignores the weighting treats every part equally; a proposal that reads the weighting during the file analysis puts the most argument where the criterion weighs the most. ## When is a quick read enough, and when do you need a full analysis? To decide whether the opportunity is worth pursuing, a quick read of the tender rules and the technical specification is enough, because nothing is submitted or signed yet. Generic AI can even summarize these documents for a first pass. For the bid actually submitted, a full analysis becomes essential: every requirement in the specification must be extracted, linked to evidence, and checked, or you risk missing a disqualifying clause. The line is submission itself: once the bid commits the bidder, an unseen requirement becomes a risk. ## The steps of a tender-file analysis, in order 1. **Inventory the documents**: check the file is complete and spot mandatory annexes. 2. **Read the tender rules**: note the required format, the deadline, the criteria, and their weighting. 3. **Identify requirements document by document**: the detailed, requirement-by-requirement extraction is covered on the requirement-extraction page. 4. **Read the contract conditions**: spot the performance conditions, penalties, and deadlines that create commitments. 5. **Build the compliance matrix**: log every requirement and assign it a piece of evidence. 6. **Check completeness**: cross-check the matrix against the tender rules before drafting, then again before submission. On the Optivalue.ai platform, which publishes this site, 85 specialized agents (72 subject-matter agents, 12 sector-specific agents, 1 librarian agent) analyze the tender documents, classify every requirement, and match it to the company's own documents, so that every response cites its source. ## Frequently asked questions **Which part of the tender file should you read first?** The tender rules, because they set the response format, the scoring criteria, and the deadline. Reading them first shapes the analysis of the rest of the file. **What is the difference between the technical specification and the contract conditions?** The technical specification (CCTP) describes the technical requirement to be met; the contract conditions (CCAP) set the administrative terms of performance. The technical proposal responds to the specification, the signed bid form to the contract conditions. **Is analyzing the tender file the same as reading the specification?** The specification is one part of the tender file, often the technical specification. Analyzing the full tender file covers every document, including the tender rules and the contract conditions, not just the technical requirement. **Do these terms apply outside France?** DCE, CCTP, and CCAP are French terms. Other markets use their own local equivalent of the tender documents. Check the law and terminology that apply in your own market. ## Analyze a real set of tender documents on your own files Bring a real set of tender documents. You will see requirement-extraction coverage, sources cited on every page, and a gap analysis of your response, not a prepared demo. [Discover the Optivalue.ai platform](https://www.optivalue.ai/?utm_source=bid-writing-software.ai&utm_medium=satellite&utm_campaign=comment-analyser-un-dce) ยท [Book a demo](https://www.optivalue.ai/demo?utm_source=bid-writing-software.ai&utm_medium=satellite&utm_campaign=comment-analyser-un-dce) Written by the compliance and presales team at Optivalue.ai. Last reviewed: 5 September 2026. This page does not constitute legal advice. [Markdown version](/en/comment-analyser-un-dce.md) ### Sources cited - Public procurement rules on the publication and weighting of award criteria (in the United States, the Federal Acquisition Regulation; in the United Kingdom, the Procurement Act 2023); the applicable rule in each market should be verified. ## Further reading - [How to write a technical proposal that wins a public contract, with the help of AI software](/en/) - [How to extract every requirement of a tender, one by one](/en/extraire-les-exigences-d-un-appel-offres) - [How to find out why a public-contract bid was rejected](/en/comment-connaitre-les-motifs-de-rejet) - [How does the buyer evaluate bids in a public contract](/en/comment-l-acheteur-evalue-les-offres) - [How to respond to a technical specification point by point](/en/comment-repondre-a-un-cctp-point-par-point)