The European Single Procurement Document (ESPD/DUME) makes it easier to submit an application, but its reuse does not exempt you from rereading the consultation. A company can save time by maintaining a structured base, provided that it distinguishes stable information from dated declarations and criteria specific to the buyer. Copying an old file unchecked may leave capacity exceeded, a consortium member missing, or a response that is inconsistent with the procurement. The best practice is to reuse the structure and evidence, then regenerate a controlled statement for each filing.
French framework for international readers
DUME is the French acronym for the European Single Procurement Document, commonly abbreviated ESPD in English. The underlying European concept travels across borders, but the submission portal, buyer instructions and supporting evidence remain procurement-specific. Keep the official French acronym when working on a French notice and add ESPD for international colleagues rather than replacing one with the other. This guide focuses on evidence freshness and controlled reuse. It does not assume that a statement accepted by one contracting authority will satisfy a different procedure or national implementation.
“Master DUME and consultation DUME” control grid
- buyer-provided DUME used if provided
- exact identity of each operator
- declarations reread on the date of filing
- capacities attached to a proof
- coherent group roles
- final and receipt file archived without overwriting
Scenario: DUME and application
A company regularly responds to IT consultations. It maintains a library of verified data, but creates an immutable record per response. When a buyer provides a pre-filled DUME, the team starts from this file and compares the criteria to its matrix. A partner's capabilities are only added if their role and commitment are documented. Before filing, a second person checks the final file and the submission receipt. After sending, reusable data is updated separately; the deposited version is never overwritten.
Read the visual “Master DUME and consultation DUME”
Master data and dated evidence appear before the buyer-provided DUME and its criteria. A cross-check then leads to the submitted version. The visual separates reusable preparation from the procurement-specific review that must happen before filing.
Instructions for using the “DUME freshness matrix” tool
It links each response in the form to a proof, a date and the corresponding requirement. The entries are: DUME section, response, proof, proof date, entity, buyer criterion. The expected output is a complete table, incomplete or to be updated before submission. The guardrails are explicit: no answer inferred; immutable deposited version; priority buyer criterion. When an input is unknown, the tool flags the missing evidence instead of choosing the most favourable outcome.
Official reference for DUME
The Legal Affairs Department presents the DUME as a harmonized sworn declaration used by buyers and economic operators. Its dematerialized service aims to simplify proof of selection criteria and prohibitions on bidding. The official page specifies the role of the structured format and the possibilities of reuse, while the sheet on the presentation of applications places the document in the entire file. The DUME does not replace the reading of the consultation regulations or any supporting documents requested at the appropriate stage.
Alerts specific to evidence and eDUME
- copy the DUME of the last market
- confuse reusable proof and always true declaration
- forget an entity whose ability is invoked
- modify the file after submission without keeping the version sent
Working method: DUME freshness matrix
1. Read the consultation regulations and note the application requirements in a matrix: entity concerned, capacity, expected document, format and deadline. To validate this step, note “BUYER DUME used if provided”. The risk to avoid is: copying the DUME of the last market.
2. Create a master file per economic operator with SIREN, identity, authorized representatives and proof, each associated with a date and an internal owner. To validate this step, note “exact identity of each operator”. The risk to be avoided is: confusing reusable proof and always true declaration.
3. Import or take back the buyer’s DUME when it is provided. Do not substitute an old template if the consultation document contains pre-populated criteria. To validate this step, note “declarations reread on the date of filing”. The risk to avoid is: forgetting an entity whose capacity is invoked.
4. Reexamine each sworn declaration on the day of filing. A response valid in a previous market is not automatically current. To validate this step, note “abilities linked to a proof”. The risk to avoid is: modifying the file after submission without keeping the version sent.
5. Check the links between candidate, co-contractors, subcontractors and entities whose capacities are invoked. Each role must correspond to the parts and commitments. To validate this step, note “consistent group roles”. The risk to avoid is: copying the DUME of the last market.
6. Keep the transmitted file, its fingerprint, the acknowledgment of submission and the control matrix, then separate this version from the working model. To validate this step, note “final file and receipt archived without overwriting”. The risk to be avoided is: confusing reusable proof and always true declaration.
Limits of interpretation for DUME
A technically accepted DUME is not proof that the application is complete or admissible. Reusing XML does not guarantee the freshness of the declarations. Information obtained automatically should not be validated without verifying the entity concerned. Finally, the selection criteria are not identical from one market to another: previously sufficient capacity may be outside the scope for a new consultation.
Decision and operational handoff
Authorize submission when the matrix covers all requirements, each declaration has been reviewed and the final file corresponds to the consultation. If proof is missing, use the provided clarification procedure or stop internal validation; do not invent a value to complete the form. After deposit, process any buyer requests from the archived version in order to respond consistently.
Official sources checked for DUME
Sources and method
- Official source 1 — checked on 2026-08-17.
- Official source 2 — checked on 2026-08-17.
Continue in Propecto
Source éditoriale : Propecto. Date de publication : 2026-08-17. Lorsqu'une donnée vient d'une source externe, sa référence est citée dans le corps de l'article.