Q&A summary of the TED eSender workshop (27 March 2026)  

These consolidated questions and answers have been reviewed and may have been regrouped or modified to provide a more cohesive and complete response. Some answers might no longer be accurate, as the Publications Office (OP) has updated its approach based on feedback.    

The presentation slides as well as the recording of the live session are available in the agenda section.   

Questions from the participants:  

• Is there a limitation on TED regarding the number of lots displayed in a notice? Do you plan to check the number of lots with your APIs? 

Answer: Yes, there is a limitation in the embedded browser display on the TED website for notices with very large numbers of lots. Notices with more than around 1250 lots may not display fully in the embedded online view. However, this does not prevent submission or publication. Users can still download the HTML or PDF and view the full notice that way. 

• What are unpublished fields and dynamic rules in SDK 2.0? 

Answer: This was covered in the presentation. In SDK 2.0, the concept of “unpublished fields” is revised and renamed to “undisclosed fields”. Dynamic rules will also be further developed, including checks between related notices to ensure that submitted information remains consistent. 

• Do you plan to implement stricter validation rules for Clean Vehicles Directive fields? In which SDK version? 

Answer: At present, the CVD fields and rules are considered stable. No stricter validation rules are currently planned for SDK 1.15 or SDK 2.0. If stakeholders believe additional stricter rules are needed, they are encouraged to raise this as soon as possible so it can be assessed for a future release. 

• Is it possible to add another Notice Official Language through a Change notice? 

Answer: In principle, the choice of notice official language is intended to remain fixed once selected. Technically, this is not currently blocked by a rule, but in SDK 2.0 dynamic rules are expected to prevent changes to the set of official languages in later notices. In practice, users should assume that the official language choice must be correct from the start. 

• Is the extension of SDK 1.12 until 31 October 2026 confirmed? 

Answer: Yes. The extension of SDK 1.12 until 31 October 2026 was confirmed during the workshop. The active SDK versions/ CVS range have been updated in the meantime, as well as the SDK roadmap. 

• Are dynamic rules a move away from “loosely connected” notices towards a more connected approach, for example through a common backend across notices? 

Answer: From a business perspective, notices are not considered loosely connected, as they follow a sequence that should be respected and maintain consistent information. Dynamic rules aim to check that this business logic is respected by comparing notices with one another. 

Technically, this means introducing cross-checks between related notices to verify that the information submitted in a new notice is consistent with previous ones. However, notices are not being merged into a single backend and remain separate entities. 

This approach helps address the current limitation where notices behave as largely independent “islands”, making it difficult to ensure consistency across related notices. Dynamic rules are therefore a first step in improving this, starting with basic checks and evolving progressively over time. 

• Could the Version Range API return a clearer table of SDK versions and their allowed use until dates? 

Answer: The Version Range API currently provides information only on the next foreseen change, indicating when an SDK version will be added or removed. It is not intended to serve as a complete planning table. 

eSenders are invited to propose improvements to the structure of the JSON output via GitHub discussions. Information on longer-term version lifecycles is already available in the official documentation. The API could be adapted in the future if there is a clear and agreed proposal. 

• Is it possible to provide the planned AI-assisted validation to eSenders so it can be implemented in their systems? 

Answer: This is part of the longer-term vision, but not in the near future. The Publications Office would first need to validate the tool internally and ensure it performs reliably at scale. 

At this stage, the solution is still in a prototype phase and no commitments can be made. The current approach foresees using it internally (e.g. after submission, as part of backend checks), rather than as a real-time validation service like TED CVS. 

If the system proves stable in production, the Publications Office may consider sharing it with eSenders (e.g. as a service or in another form), but this will depend on performance and implementation considerations. 

• Regarding the planned TED Data Quality AI Assistant: will it rely on internal AI models or external ones (e.g. Claude, ChatGPT)? 

Answer:  This is still under evaluation as part of the prototype phase. The Publications Office has asked its contractor to explore different options and determine what works best. 

A mixed approach is expected, potentially combining different AI technologies. This may include a generative AI component to summarise findings (e.g. explaining why a notice is flagged), alongside other models used during the validation process. 

At this stage, it is not expected that general-purpose public models (such as ChatGPT-like services) will be used directly. The solution will also need to comply with internal governance requirements, including data protection and alignment with Commission AI rules. 

The final approach will be defined once the prototype is more advanced. 

• Why was the redesign of unpublished fields moved to SDK 2.0 instead of SDK 1.15? 

Answer: The redesign of unpublished fields is considered a breaking change and therefore requires a new major version (SDK 2.0). It could not be implemented properly within the SDK 1.x framework. 

Although this was initially expected for SDK 1.15, the timing of SDK 2.0 is planned to be very close. A release candidate is expected around mid-2026, allowing development to start early, even before SDK 2.0 reaches production. 

For most implementations, the transition from SDK 1.15 to SDK 2.0 should be manageable, as the metadata is expected to remain largely similar. More impact is expected for implementations relying on EFX. 

Overall, while the version change is significant from a technical perspective, the intention is to keep the transition as smooth as possible and to simplify the model in the longer term. 

• Are you planning to consolidate the two visualisation applications into one? Currently, the TED API visualisation and the TED website visualisation do not produce identical PDF/HTML outputs, and the HTML is not fully printable. 

Answer: For now, the TED API visualisation and the TED website visualisation remain separate applications and are maintained in parallel. While there are some differences, the outputs are generally similar. 

Some divergence is due to technical and contractual constraints, and this is expected to persist in the short term. However, with SDK 2.0, certain improvements should help bring the two visualisations closer together. 

In the longer term, the intention is to move towards a single, consolidated system, but this will depend on how the SDK 2.0 visualisation evolves. No concrete timeline can be confirmed at this stage. 

Regarding printing, PDF is recommended, as HTML is not optimised for printing. 

• Regarding the EFX pattern visitor, we'd love to read an answer : https://github.com/OP-TED/eForms-SDK/discussions/1073 

Answer: OP acknowledged the concern. The problem relates to live validation, where certain mandatory/forbidden rules depend on a context (node) that may not exist, making them difficult to evaluate. 

No immediate solution was provided. It was suggested to follow up bilaterally to discuss the issue in more detail. Improvements are expected with SDK 2.0, but further clarification is needed. 

• Is there more clarity on when the third amendment will be published? 

Answer: The current expectation is around Q1-Q2 2027. Work is expected to resume after summer 2026, following progress on the proposal of the new Public Procurement Act . 

If timelines hold, there should be a clearer view of the amendment to the eForms implementing regulation by this time next year, with implementation in the SDK to follow afterwards. 

• How long are eSenders expected to be able to send notices directly to OJEU instead of national gateways? Is there a plan or timeline per country? 

Answer: There is no single EU-wide timeline. The situation depends on each Member State. 

In some countries, national gateways already exist, while in others eSenders still submit directly. The general direction is towards national gateways or central hubs, but planning and timelines remain at national level. eSenders are advised to coordinate with their respective national authorities.  

For example, one participant indicated during the workshop that in their country (Denmark), below-threshold notices are submitted to a national gateway, while EU notices are still submitted to TED via eSenders and then reused nationally. 

• Is there any chance to further develop TED Expert search to allow contract-level results instead of only notice-level? 

Answer: This is recognised as a valid point, but it is primarily a TED-side topic rather than an eSender issue. The feedback will be discussed internally within the TED team for possible future improvements. 

• Are there any challenges with migration from SDK 1.x to 2.x? How difficult will it be, especially for undisclosed fields? 

Answer: This has not yet been fully assessed as it still needs further analysis. 

The main impact is expected around undisclosed fields, where the structure will change (moving away from many field-level elements to a different approach). 

Potential challenges may arise when modifying or continuing existing notices, particularly result notices. Contract modification notices are not expected to be affected in the same way. 

Overall, this is an area that will need to be addressed as implementation progresses. 

-

Last update: 24 April 2026