The tender pack arrives as an archive, with its documents and its vocabulary. The platform recognises them, extracts each requirement with its originating clause, writes the technical proposal in the structure imposed by the tender rules, and fills in the response templates without distorting them.
The DCE (dossier de consultation des entreprises), or tender documents, is the full set of documents a public buyer provides to the candidates in a procurement procedure. It includes, in particular, the tender rules, the CCTP, the CCAP, the price schedules and the response templates to be completed.
Definition as used on this page. See the glossary.
Each document has its own role and its own handling. A requirement read in the CCTP does not carry the same weight as a clause in the CCAP: the first must be demonstrated, the second is accepted or negotiated.
The RC sets the rules of the game: documents to submit, deadline, award criteria and their weighting, negotiation arrangements.
Handling: the outline of the technical proposal mirrors the criteria and their order of weighting; the list of documents becomes a completeness checklist.
The CCTP describes the technical need and the requirements for the expected service.
Handling: each requirement is extracted with its clause and page, classified as an obligation, an option or a scored criterion, then linked to the reference in your document base that proves it.
The CCAP sets the performance conditions: timescales, penalties, payment terms, termination.
Handling: the commitments the clause places on you are flagged for a decision; this is risk detection, not drafting.
The schedule of unit prices (BPU), the breakdown of the lump-sum price (DPGF) and the technical response template (CRT) are the forms imposed by the buyer.
Handling: the technical response template is filled in with its original formatting. Prices remain your decision: the platform does not price the bid for you.
The DC1 and DC2 forms, and the European Single Procurement Document (DUME), are the declarations by which a candidate attests that it meets the conditions for participation.
Handling: the information is taken from your indexed administrative documents, and expired certificates are flagged before submission.
In a MAPA, the buyer freely sets the terms of the procedure, while respecting the principles of public procurement.
Handling: since the pack is lighter and the deadline shorter, the value of the knowledge base is at its highest: answering a MAPA in two days becomes realistic.
The archive is uploaded exactly as downloaded from the buyer profile, without any prior sorting. Each file is identified by its type, even when its name does not say so.
A list of traceable requirements replaces three days of combing through the file: each one carries its document, clause, page and type. It is also the guarantee that you will not miss the isolated requirement on page 214, the one that makes a bid non-compliant.
Each section answers a scored criterion, backed by your indexed references, in the vocabulary of public procurement. See the technical proposal page.
Is every requirement covered? Is every requested document present and valid? The list of what is missing is explicit, and each answer goes out with the name of its approver.
The practice is emerging among French public buyers, following the United Kingdom. A bid in which inaccurate content is discovered at clarification is liable to be rejected: the defensible answer is therefore to declare a controlled use and to be able to show the traceability — sources cited, scores, named approval.
Frequently asked
Yes, without any prior sorting: the documents are recognised one by one, even when their file names are not very explicit. The requirements are then extracted with their document, clause and page.
Yes, exactly: structure, section order, formatting, drop-down lists. Altering an imposed template exposes the bid to being non-compliant, so the platform never restructures it.
No. Prices are a matter for your commercial strategy and your risk analysis. The platform structures the schedule, checks that it is complete and flags inconsistent lines, but it does not set your prices.
They are flagged before submission, with their validity date. This is a frequent reason for a bid being excluded on purely administrative grounds.
Yes, and it is often on MAPAs that the gain is clearest: the deadline is short, the pack lighter, and an indexed knowledge base makes it possible to answer tenders you used to let pass for lack of time.
Yes: processing in your private instance, never shared, in the jurisdiction you choose, with on-premise deployment compatible with air-gap for defence or sensitive infrastructure contracts. See the sovereignty page.
We analyse them in front of you: the requirements extracted, the documents recognised, and what is missing from your references. One hour, on your documents.