The EU tender timeline — plan backwards from submission day, not forwards from publication

It is 09:00 on a Monday. You are on day 26 of a 35-day window.

Your ESPD for the Article 63 capacity-reliance partner — the entity whose financial standing fills the gap your own turnover cannot — is still unsigned. The partner’s authorised signatory is in Warsaw. You are in Lyon. The submission platform is in Bucharest. The deadline is in nine days.

Nine days and three moving parts, each with its own dependencies. The ESPD is not a form you fill in at this point. It is a project.

This is what running a tender forwards looks like. You track the clock from publication day, you organise by what needs doing, and somewhere in the final week you discover that what needs doing has more prerequisites than you planned for.

This article is about running it backwards.

The clock is read wrong on almost every tender

Article 27 of Directive 2014/24/EU sets the minimum time limit for receipt of tenders in an open procedure at 35 calendar days from the date on which the contract notice was sent. That is the legal floor for above-threshold works contracts. Contracting authorities may allow longer for complex procurements, but 35 is the minimum.

Thirty-five days sounds like a lot. It is not — not because 35 days is short, but because most of those days disappear before the work most people associate with “writing a bid” has even begun.

The 35-day period is not for writing the bid. It is the hard deadline by which the bid must already be assembled, checked, signed, and loaded into a platform that has never seen your file before.

There is a further complication. The clock starts from transmission, not from publication. The contracting authority sends the notice to TED; TED publishes within five calendar days. By the time the notice appears in your monitoring feed, one to five days are already gone. The 35 days you see on TED is already shorter.

Backwards from D-0

The only reliable way to manage a tender is to fix the submission deadline as D-0 and work back. Every internal milestone is a distance from that point.

D-0: Submission closes. Nothing is added, changed, or amended. The file is either in the platform or it is not. The portal timestamp is the legal record.

D-1 to D-2: Platform dry run. Load the full package. Confirm file sizes. Confirm PDF/A compliance on every document that requires it. Confirm that electronic signatures validate — not that they look correct, but that the platform’s validation step accepts them. Confirm the package structure matches the notice requirements. If there is a problem on D-2, you have two days to fix it. If you find it on D-0 at 16:00, you have whatever the platform allows.

D-7: Full draft locked. Every document — technical methodology, reference list, pricing schedule, team CVs, quality plan, whatever the notice requires — is in final draft. Internal review is complete. No open sections, no placeholders.

D-14: ESPD track closed. Every ESPD for every entity in your submission is signed, validated, and in hand. Your own. Every Article 63 capacity-reliance entity’s. Every named subcontractor whose capacity is relied upon. Each one is a separate document, separately signed, and it needs to be compatible with the national ESPD service or platform format the contracting authority’s system accepts. If your consortium has four entities, you have four ESPDs to coordinate. D-14 is not the day you start chasing ESPDs. It is the day they are done.

D-21: Decision confirmed, tracks staffed. Firm bid/no-bid decision made. Every track has a named owner. Platform accounts are activated and tested. Clarification answers have been received and absorbed.

D-28: Notice studied, clarifications filed. In the first week after publication, read the full notice and tender documents. Every ambiguity, every specification clause that conflicts with another — filed as a clarification question by D-28. Contracting authorities are not obliged to answer questions received close to the deadline. File early and you get answers in time to act on them.

D-35: Notice published. The work starts now. Not next week.

The four tracks

Every construction tender runs four parallel tracks with different cadences.

ESPD track. Coordination-heavy, not writing-heavy. The bottleneck is signatures. Start immediately. Chase early. Do not assume partners will read a request on the day you send it.

Technical track. Writing-heavy and expertise-dependent. Methodology, reference list, team CVs, quality management plan. This is the track that takes most of the days between D-35 and D-14, and it is the track that gets compressed when the ESPD track runs late.

Financial track. Pricing requires the technical track to be substantially settled. Opens properly around D-21; closes by D-7.

Platform track. Underestimated almost universally. Account registration, document format testing, understanding which file types the platform accepts and in what structure. Start at D-28. Test at D-7. Confirm at D-2.

These tracks do not queue. They run in parallel. The bid manager’s job is to keep them moving simultaneously.

What the reform delay means for your planning

The European Commission’s proposed Public Procurement Act — the revision of Directives 2014/23, 2014/24, and 2014/25 — has been pushed back to 9 September 2026 on the College of Commissioners’ agenda, as announced on 23 June 2026. The aims include simplifying procedures, building a digital EU procurement marketplace, and mainstreaming sustainability and European-preference criteria.

None of it is in force.

Plan against the rules that exist. The 35-day minimum, the Article 27 clock, the Article 63 ESPD requirements — these govern every tender you submit in 2026.

What D-1 calm looks like

There is a version of this where D-1 is quiet.

Every document is in the platform. Every signature was collected before D-14. The technical methodology was locked at D-7 and reviewed by two people who did not write it. The financial schedule was cross-checked three days ago. The platform has already accepted a test upload of the full package. The only task on D-1 is to confirm nothing has changed since yesterday.

That version requires the tracks to have been running in parallel from D-35, with internal deadlines that gave you a real buffer. Steinlog is built around that discipline: a version-controlled, timestamped workspace where each track has a completion indicator, where the ESPD log shows when each partner document was received and validated, and where D-1 is a confirmation, not a scramble.

The practical point

Back to 09:00 on day 26. The ESPD for the Warsaw partner is unsigned. Nine days. That is not nine days to get a signature. That is nine days that also contain your technical methodology review, your pricing closure, your platform upload test, and your internal compliance check.

The ESPD needed to be in hand on day 21. It needed to be started on day 28. It was not, because on day 28 the partner list was still being discussed and nobody had mapped the four tracks against the remaining window.

Backwards planning does not prevent complexity. It surfaces it early enough to absorb it.

The 35-day window is your delivery window. The writing needs to finish well inside it, in every track, before the platform deadline arrives and the only remaining question is whether the upload goes through.