Production guide. The specific notice and tender documents prevail over any checklist.

From the tender documents to a compliance matrix

A production system to know what each clause requires, who is responsible, where the evidence is, and what must be checked before signing.

Direct answer

A compliance matrix is a table that turns each requirement in the procurement file into a controllable unit: exact reference, obligation, document or envelope type, owner, evidence, status, review, and risk. It reduces omissions, but it does not interpret an ambiguous clause on its own.

1. Freeze an inventory of documents

Record the notice, administrative specification, technical specification, annexes, templates, questions and answers, rectifications, and links. Add the download date and a fingerprint or internal version. If a correction appears, don’t overwrite without leaving a trace of what changed.

2. One row per verifiable obligation

FieldExample
ReferencePCAP 12.3, page 24
ObligationProvide a list of similar services
ConditionPeriod, amount and nature required
EvidenceTable + available certificates
LocationFile/envelope indicated by the procurement file
OwnerName, delivery date, and reviewer
StatusLocked / in progress / reviewed

3. Don’t mix eligibility and the proposal

Administrative documentation shows who is participating and under what conditions. The technical proposal responds to the scope and the evaluable criteria. The economic offer follows the template and the rules of the procurement file. Mixing information between files or envelopes can have consequences; use exactly the structure requested and validate each platform.

For solvency, apply first the method from the economic and technical solvency guide. The ESPD (DEUC) may serve as a preliminary statement in the applicable scenarios, but the supporting documentation and the time of submission depend on the procurement file.

4. Design from the evaluation

Create a second view with criterion, scoring, evidence, response section, and limit control. Every promise must be translated into method, owner, deliverable, or indicator. Avoid corporate text that doesn’t answer a scoring scale or the needs of the procurement file.

Recommended traceability: “Criterion 2.1 / maximum 15 points → section 3.2 → transition diagram → deliverable D4 → technical owner → indicator: reopened incidents”.

5. Control the economic offer as a critical data point

  • Confirm whether amounts are requested with or without taxes.
  • Check units, annual amounts, lots, extensions, and options.
  • Make the official template, the report, and the cost sheet match.
  • Subject discounts, rounding, and formulas to a double review.
  • Don’t reuse an economic template from another procurement file.

6. Submit with margin and keep evidence

Verify certificate, signing power, application, file size and format, encryption if applicable, lots, envelopes, and the alternate team. The closing time is a condition, not a recommendation. After submitting, keep the receipt, date, fingerprint, and exact version of each file.

Final check for rectifications: reopen the official source right before closing the version and before submitting. A perfect matrix built on outdated documents is still an offer at risk.

Checklist for the last 24 hours

  • Official source reviewed and with no pending changes.
  • All requirements have a row, evidence, and reviewer.
  • Names, tax IDs (NIF), amounts, and references match across all documents.
  • Each file is in the required location and format.
  • Signature and certificate tested on the same team.
  • There is room for a second submission if the platform allows it.
  • The receipt will be archived with the submitted version.

Official sources

NL
NexoLicit editorial team

Document control method; does not replace legal advice or the submission platform instructions.

Always check amounts, deadlines, requirements, and rectifications in the official source.