In-depth practical guides

Read a procurement notice without confusing its stages

Connect procedures, lots, participants, amounts and versions: use public notices for documented monitoring without treating an intention, estimate or award as evidence of payment.

Updated :

Legal research space with reference books and files.

AI-generated illustration

Which stage and scope does this notice document?

A search may mix planning, competition, results and modifications. Several notices can describe one procedure, while one notice can cover several lots. Start with the full document and its references to avoid counting every publication as an additional contract. This method concerns reading public records; it does not determine whether a procedure is legally compliant.

  1. Identify the document

    Record the portal, reference and notice type before extracting a result. TED distinguishes planning, competition, result, modification and change notices, among others. Express the conclusion using the observed stage: an announced opportunity is not an award result.

  2. Connect the versions

    Look for references to earlier notices and changes. Keep publication date separate from decision date and submission deadline. Record search filters: showing only the latest version can hide earlier publications needed to reconstruct the timeline.

  3. Separate procedure, lot and contract

    Create a working record for the level being studied. Record the lot reference and its corresponding outcome before attaching a winner. Do not apply one lot’s result to the entire procedure. Explicitly leave relationships unknown when the consulted records do not establish them.

  4. Identify the participants

    Distinguish buyer, economic operator, representative and consortium members when specified. Copy identifiers with their identifier system, then check the legal entity in the relevant register. A trading brand or abbreviated name alone does not establish the contractor’s identity.

  5. Read amounts with their labels

    Retain currency, unit, field, lot and amount type: estimate, ceiling, awarded value or another stated value. Do not add a total and its components. A ceiling or published value does not automatically measure expenditure actually paid.

  6. Write a checkable conclusion

    Cite reference, version, passage and access date. Separate published information, your entity matching and missing evidence. When monitoring, compare new records against the existing procedure instead of creating another participant or contract for every notice.

Reading workshop

A changed notice is not an award

This fictional case follows a deadline changed for one lot without inventing an outcome.

Fictional data and records for learning: none of these results comes from a live service query.

DEMO-M12: lot L2 changes date

Notice N1 lists two lots. N2 references N1 and postpones only L2’s closing date; no award evidence is supplied.

  1. N1 published 2 June

    Evidence or value
    L1: 20 June; L2: 20 June
    Reading
    Two initial deadlines.
    Decision
    Retain N1 and lot references.
  2. N2 published 10 June

    Evidence or value
    References N1; L2: 27 June
    Reading
    Change targets L2.
    Decision
    Link N2 to N1, not a new procedure.
  3. L1 in N2

    Evidence or value
    Deadline remains 20 June
    Reading
    No postponement established for L1.
    Decision
    Keep separate tracking rows.
  4. Outcome search

    Evidence or value
    No award notice in the file
    Reading
    Outcome is not established here.
    Decision
    Name neither contractor nor paid amount.

What should monitoring report?

Open each proposition to compare its diagnosis. More checks may still be needed.

The whole procedure closes on 27 June.

No: only L2 is postponed here.

A second contract was awarded on 10 June.

No: that is publication of a change, not an outcome.

L2 postponed to 27 June; award undocumented.

Appropriate. Cite N2 with N1 and retain the file consultation date.

Deadline tracking by lot

Procedure: DEMO-M12
N1: published 2 June; L1/L2 due 20 June
N2: published 10 June; references N1
L1: 20 June; L2: 27 June
Award: evidence not supplied
Outcome: L2 change, not a new contract

Attach version and lot references whenever repeating the date. Change publication and deadline are different events.

Documentation of the rules, separate from fictional examples

Compare other situations and exercises

A new notice repeats an existing procedure

Examine references and amended sections. Update the existing timeline when the link is established; retain uncertainty when identifiers differ. Publication count alone cannot establish contract count.

A winner appears for only one lot

Find each lot’s result. Connect the business to the documented lot and distinguish lots with no retrieved outcome. Do not describe a partial award as winning the entire procurement.

A maximum amount becomes supposed revenue

Return to the amount’s label and scope. Remove the calculation equating a maximum with realised income. State the value actually published and the evidence needed to establish execution or payment.

Worked exercise

Two awarded lots do not describe the whole procedure

Fictional example: the values and documents teach the method and do not describe a real organisation.

One procedure has three lots. A correction changes B’s name without awarding another lot.

If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.

Starting information
LotNamed recipientAwarded amount in EUR
1A80 000
2B50 000
3Not awardedNot established by the notice

Your checks

  1. Associate publications with procedure and lot.
  2. Separate awarded amounts from unawarded lots.
  3. Apply the correction without counting a new contract.
Read the answer

Answer and decision

Two awarded lots document EUR 130,000 in this notice. The correction updates B, not a third awardee. No awarded amount is established here for lot 3. This sum proves neither payment nor the total of subsequent stages.

If the case changes

If lot 3 is later awarded, add its date and version rather than rewriting the old state retrospectively.

Record to retain

Keep procedure, lots, notice type, correction, qualified amounts and gaps.

Record to retain

  • Portal, notice reference, type, version, URL and access date.
  • Procedure, lot and contract identifiers and established links between notices.
  • Participant identities and roles, identifier systems and uncertain matches.
  • Amount, currency, qualification, scope and passage supporting the conclusion.

Official references

Related source profiles

Related protocols

Checks before reaching a conclusion

  • Do notice type, procedure and lot support the precise stage stated in your conclusion?
  • Does each retained amount have a type, currency and scope without mixing estimates and payments?
  • Have successive notices been linked before counting contracts or winners, with uncertain relationships retained?

Frequently asked questions

Does a competition notice prove an award?

No. Find the record reporting the result, then identify the relevant lot and participant. Preserve the announced stage in your wording.

Can amounts in successive notices be added?

Only after establishing their relationships and scope. A correction, a total and a lot may repeat the same value; avoid counting it twice.

What if the buyer uses several names?

Compare identifiers and records, then retain name variants as labels. Document the match; do not merge legal entities because their names resemble each other.

Does a notice reveal payments?

A notice and its amount do not establish actual payments. Seek suitable execution records or data and explain what remains unknown.

Is it possible to add the amounts of several opinions?

Only after checking their nature, scope and relationships. Opinions related to the same procedure or different types of values can make a misleading addition.

DOCUMENTED REFERENCE

CPV: choose the procurement search level

The Common Procurement Vocabulary describes what is being bought. Its main vocabulary is hierarchical; the supplementary vocabulary adds qualitative detail. X marks a position below, not an assigned code.

XXXXXXXX−Y81
CPV: choose the procurement search level
ReferenceValue or formWhat it identifies
XX000000-Y2The first two digits identify a division.
XXX00000-Y3The first three identify a group.
XXXX0000-Y4The first four identify a class.
XXXXX000-Y5The first five identify a category; later digits refine it.
XXXXXXXX-Y8 + 1The main code has eight digits and a ninth check digit, not an extra subject level.

Implication for the record

Keep the full code, label and monitoring level. A narrow search may miss notices classified in a broader branch; compare the target code with parent levels. A CPV is neither a procedure identifier nor proof of a supplier’s competence.

Do notices with the same CPV describe the same contract?

No. They may only share a purchasing subject. Deduplicate using procedure identifiers, lots and notice links. Broaden searches through the hierarchy and record the filter rather than merging contracts on CPV alone.

Primary documentation

Documentation consulted on .

DEEPER READING / PRACTICE

Place a procurement notice in its procedure

A review indicates a buyer, an object and amounts. The reading must determine the type of document and avoid confusing consultation, outcome and execution of the contract.

Updated on .

Priority checks

Release identifier, buyer, object, lots, dates and type of opinion. Compare the related documents and preserve the units and reserves that accompany the amounts.

Interpretation pitfalls

An announced amount may correspond to an estimate or a threshold. The aforementioned authority does not demonstrate itself the realization of the benefits.

Working record to retain

The file connects opinion, procedure, lots, qualified amounts and associated documents. It indicates the necessary elements to follow the following steps.