HomeGlossaryExplanation for Non-Division into Lots
Lot System & Structure

Explanation for Non-Division into Lots

An explanation for non-division into lots is the mandatory justification a contracting authority must publish when it decides not to divide an above-threshold contract into separate lots, as required by Article 46 of Directive 2014/24/EU, setting out the specific reasons why a single lot structure is appropriate for that procurement.

Quick answer

An explanation for non-division into lots is the mandatory justification a contracting authority must publish when it decides not to divide an above-threshold contract into separate lots, as required by Article 46 of Directive 2014/24/EU, setting out the specific reasons why a single lot structure is appropriate for that procurement.


The requirement to explain non-division into lots is one of the more significant structural obligations introduced by Directive 2014/24/EU. It shifts the burden of explanation: rather than buyers having to justify why they divided a contract, they must now justify why they did not. This "comply or explain" design reflects the EU legislature's policy commitment to SME access and market competition.

What is the explanation for non-division into lots?

Article 46(1) of Directive 2014/24/EU states that contracting authorities shall consider dividing contracts into lots. Where they decide not to do so, they must set out the main reasons for their decision in the procurement documents or the individual report required under Article 84.

The explanation is not a formality. It must identify the specific reasons that make lot division inappropriate for the particular procurement. A generic statement that division was considered and rejected is insufficient. The explanation must be grounded in the characteristics of the requirement, the market, or the operational circumstances.

The European Commission and national procurement oversight bodies across Europe have published guidance identifying the types of reasons that are generally accepted as sufficient:

Technical indivisibility is the strongest ground. Where the requirement forms a technically integrated whole and dividing it would create interface gaps, coordination risks, or contractual liability ambiguities, a single lot tender is justified. Complex systems integration, where a single supplier must hold end-to-end accountability, is a well-established example.

Disproportionate administrative cost applies where the contract value is relatively modest and the cost of managing multiple procurement procedures and contracts would consume a significant proportion of the contract value itself. This is most relevant for small-to-medium contracts just above the directive thresholds.

Delivery coordination risk covers situations where the outputs of different lots are so interdependent that awarding them to different suppliers would create unacceptable risks of delay, rework, or liability disputes. A construction project where design and build are deeply integrated is a typical example.

Why the explanation matters for bidders

For suppliers, the explanation for non-division is a signal about how the market looks from the buyer's perspective. A technically grounded explanation suggests the buyer has thought carefully about the requirement and has a genuine reason for the single lot structure. An explanation that reads as boilerplate or that does not connect to the specific contract may indicate a weaker justification that could be challenged.

If a supplier believes a contract should have been divided and the explanation is inadequate, this can form the basis of a procurement challenge before award, or a complaint to the relevant national oversight body. In practice, pre-award challenges on non-division grounds are relatively rare, but they do succeed where the justification is demonstrably weak.

For bidders assessing whether to pursue a single lot tender in a market where they only cover part of the scope, the explanation also informs whether subcontracting or consortium arrangements are likely to be necessary to comply with the specification.

Example

A Finnish university procures a fully integrated learning management system (LMS) with custom integrations to its student information system, library management platform, and HR system. The explanation for non-division states that the LMS and its integrations form a technically indivisible system: awarding the core LMS to one supplier and the integrations to another would require a shared API design authority that the university lacks the technical capacity to manage, and would create unresolvable liability gaps if integration failures occurred. This explanation is technically grounded, specific to the requirement, and would withstand scrutiny from a procurement review body.

Frequently Asked Questions

Is the explanation legally binding on the authority?

The explanation is part of the procurement record and binds the authority to the stated rationale. If the authority later awards the contract in a way that contradicts its own explanation (for example, by splitting the contract at the variation stage), this creates legal inconsistency that could form grounds for challenge.

What is the consequence of providing an inadequate explanation?

In EU member states, an inadequate explanation may be flagged by national procurement oversight bodies or challenged by dissatisfied suppliers. In the most serious cases, this can result in the procurement being suspended pending review, or in the award being set aside if division was required and the explanation does not justify the single lot approach. The UK Procurement Act 2023 includes equivalent transparency obligations.

Does the explanation requirement apply below the EU thresholds?

Below the EU directive thresholds, the explanation requirement under Article 46 does not apply directly. However, many EU member states have extended similar obligations to sub-threshold contracts in their national procurement laws. Buyers should check their applicable national rules. The underlying principle, that large undivided contracts require justification, is increasingly reflected in national procurement reform across Europe.

How Bidovate helps

Bidovate puts Explanation for Non-Division into Lots to work inside your capture and proposal workflow.

Tender discovery

See Bidovate in action

Book a demo and we will show you the platform using your actual contract data.

Related terms

Lot Division

Lot division is the process by which a contracting authority segments a public contract into separate, independently awardable parts, balancing access for smaller suppliers against the authority's need for coordinated delivery and administrative efficiency under EU Directive 2014/24/EU.

View

Lot

A lot is a self-contained subdivision of a public contract, defined by the contracting authority so that suppliers can bid for a portion of the overall requirement rather than the entire scope, enabling smaller firms to participate and increasing competition in European public procurement.

View

Single Lot Tender

A single lot tender is a public procurement procedure in which the contracting authority does not divide the contract into separate parts, issuing one undivided requirement to the market and awarding one contract to one successful supplier, with a mandatory explanation required under EU rules when this approach is chosen.

View

Lot Bundling

Lot bundling is the practice of combining multiple related lots or requirements into a single, larger contract package, which can reduce transaction costs and improve coordination but may limit access for smaller suppliers by raising the capability threshold for participation.

View

Lot Description

A lot description is the specification text published by a contracting authority for each individual lot within a divided procurement, setting out the scope, deliverables, technical requirements, and any lot-specific conditions that bidders must address in their tender response.

View