A lot applicability and consistency map connects one authoritative buyer clarification to the complete lot structure of a procurement. It records the buyer’s question and answer identifiers, source, version, publication time and stated scope; lists every lot using the buyer’s own identifiers; and gives each lot a separate applicability state, reason, affected requirement, response action and verification result. It distinguishes a lot that the answer expressly governs from a related lot that must only be checked for contradiction. The map does not enlarge the buyer’s words, decide the legal status of an answer, or replace the procurement documents and applicable rules.
A passenger rail operator is buying station cleaning services in six geographic lots. The common service specification requires attendance at a hazardous spill within 60 minutes. Published answer Q-54 says, “For Lots 2, 3 and 5, the attendance period is 30 minutes.” The bidder plans to tender for Lots 2, 3, 4 and 5. Its central method statement, staffing model and pricing workbook currently use 60 minutes everywhere. One manager changes all four bids to 30 minutes because the work looks identical. Another changes only the three named pricing tabs but leaves the shared method statement at 60. Neither response is controlled. Lot 4 has been given an unsupported obligation, while the documents for Lots 2, 3 and 5 contradict one another.
Follow the buyer’s scope before following similarity. Freeze the answer exactly as published, build the whole lot universe, and decide applicability separately for every lot. An explicit lot reference supports direct application. Identical wording, a shared template, the same service team or commercial convenience supports a consistency review, not an automatic extension. Update each directly affected lot through its requirements, solution, evidence, price and submission artifacts. Keep unmentioned lots on their current supported basis unless another authoritative source changes it. Escalate conflicts instead of manufacturing one tidy rule for the whole procurement.
Answer identity
Anchor the buyer’s answer before deciding where it applies
A clarification starts as a specific buyer event, not as a sentence copied into a bid workspace. Preserve the procedure identifier, stage, buyer’s question number, answer number, issuing document or portal record, publication time, time observed, intended audience and any attachment or amendment named in the reply. Store the answer text without silently correcting punctuation, terminology or lot numbers. A team summary can sit beside that record, but it cannot replace it.
Check whether the response is the latest authoritative material. Some portals publish a cumulative Q&A file, others issue individual messages, and some answers point to a revised schedule that carries the actual change. A notification email may only announce the publication. If the current pack contains Q&A version 4 and the team retained the wording from version 3, the applicability exercise begins from the wrong object no matter how careful the later mapping is.
Keep legal effect separate from operational impact. UK Procurement Act section 31 and current Cabinet Office guidance address modifications to an ongoing covered procurement. Under FAR 15.206, changed United States federal requirements or conditions are issued through a solicitation amendment. The World Bank rules and UNCITRAL Model Law address clarifications separately from modifications or addenda. None of these sources creates a worldwide rule for supplier Q&A. The actual procedure and competent reviewer determine what controls.
Do not infer a new deadline from the importance of an answer. EU Directive Article 47, UK section 54, German VgV section 20 and French Code Article R2151-4 contain regime-specific time rules. The supplier records a changed time only when the buyer publishes it through the authorized route. Until then, the existing verified deadline remains the planning constraint.
Lot universe
Map every current lot, not only the lots you intend to bid
Build the lot universe from the current notice, procurement documents and amendments before interpreting the answer. Use the buyer’s stable identifier and exact title for each lot. Record lot groups separately. If a notice, schedule and portal label disagree, preserve all three observations and resolve the identity conflict before assigning Q&A. A spreadsheet row called “North” is not enough when the notice says LOT-0004 and the pricing workbook says Area C.
Include lots outside the bidder’s current bid decision. An answer can expressly exclude them, name a group that reveals the intended scope, or change a shared dependency that crosses the bidder’s selected lots. Mapping only Lots 2, 3, 4 and 5 in the rail example would hide whether Q-54 was deliberately limited or whether the published lot set changed. The full universe provides the denominator for a defensible scope decision.
This discipline follows the shape of public procurement information. EU Directive Article 46 treats the size and subject matter of lots, the lots that may be tendered and award limits as distinct information. UK guidance similarly explains that lots can be separately competed and awarded. TED eForms assigns dedicated lot identifiers and attaches communications, documents, criteria and results to a lot context. Those structures are useful evidence. They do not override the buyer’s consultation documents.
Keep the lot universe versioned. If an amendment combines, cancels or renumbers lots, do not rewrite history. Close the former version, link the buyer’s change and create the new set. Clarification decisions made under the earlier structure then become candidates for reassessment instead of being carried forward by matching a title that happens to look familiar.
| Field | Record | Why it matters |
|---|---|---|
| Procedure | Official identifier and current stage | Stops reuse across a rebid or later call-off |
| Lot key | Buyer identifier plus exact title | Provides a stable target for the clarification |
| Grouping | Named lot group and membership, if any | Prevents bidder-created groups from acquiring authority |
| Source set | Notice, schedule, portal and amendment locations | Shows which documents establish the current identity |
| Bid state | Bid, no bid, undecided or ineligible | Separates scope truth from commercial selection |
| Version | Effective source version and observation time | Makes later remapping and audit possible |
Applicability
Give every lot its own applicability decision
Extract the scope language before interpreting it. Capture explicit references such as “Lots 2, 3 and 5,” “all lots,” “Lot Group A,” “the lots using Schedule 7,” or “lots for which overnight access is required.” Preserve exclusions and conditions. Do not replace the buyer’s defined expression with a convenient internal label unless the equivalence is proved.
Assign one evidence-bearing state per lot. `direct` means the answer expressly names the lot or an authoritative rule unambiguously includes it. `excluded` means the text expressly places it outside scope. `conditional` means a stated fact must be tested for that lot. `review_only` means similarity or a dependency warrants checking, but direct application is not established. `conflict` records irreconcilable current sources. `unresolved` means the evidence does not support a safe conclusion. `superseded` preserves a prior result displaced by later buyer information.
In the rail case, Lots 2, 3 and 5 are direct because Q-54 names them. Lot 4 is not direct merely because its service schedule repeats the same 60-minute clause. It is `review_only`: the team must inspect whether the answer creates a document conflict, whether another Q&A covers Lot 4, and whether the common specification was amended. Unless the buyer extends the rule, Lot 4 remains on its currently supported basis.
A state without a reason is only a colour on a dashboard. Link the decisive wording, source locator, answer version and reviewer. If a conditional answer applies to “stations open after 01:00,” record the station-hours source and the result for each lot. If those hours change, the lot’s applicability decision reopens automatically because its supporting fact has expired.
| State | Meaning | Permitted response |
|---|---|---|
| Direct | Buyer text or a controlling cross-reference includes the lot | Open the full impact and update path |
| Excluded | Buyer text expressly removes the lot | Preserve the exclusion and test shared files |
| Conditional | Application depends on a stated lot fact | Verify the fact before changing the bid |
| Review only | A shared clause or dependency creates a consistency question | Inspect for conflict without applying the answer |
| Conflict | Current authoritative sources point to different scope | Hold the affected decision and escalate |
| Unresolved | Available evidence cannot establish scope | Use the authorized clarification or review route |
| Superseded | Later buyer information displaced this decision | Retain for traceability but do not use |
Two reviews
Direct change and cross-lot consistency are different jobs
A directly affected lot needs an impact review. The team identifies the requirement changed or confirmed by the answer, traces it through the lot’s solution, capacity, timetable, calculations, price, risks, claims, evidence, attachments and approvals, then proves that the next response baseline uses the accepted proposition. That is change control within the lot.
A related unnamed lot needs a consistency review. The team asks whether a shared document now states two rules, whether a central artifact accidentally asserts the named-lot rule for every lot, and whether the bidder’s own use of common resources creates an internal contradiction. The output may be a documented no-change decision, a revised shared paragraph with lot-specific branches, or an unresolved source conflict. It is not permission to import the clarification.
The distinction prevents opposite errors. Updating only lot-specific files produces a fragmented offer when the common method statement still says 60 minutes. Updating every file globally produces an unsupported 30-minute promise for Lot 4. A controlled response can instead say, in the correct buyer-facing locations, that the 30-minute design applies to Lots 2, 3 and 5 while the substantiated requirement for Lot 4 remains separate.
Route the queues to the right owners. Direct effect usually needs the requirement owner, solution lead, estimator, commercial reviewer and release authority for the named lots. Consistency review needs the owner of the shared artifact plus the owners of every represented lot. One person may fill several roles, but each conclusion still needs an explicit scope.
| Question | Directly affected lot | Related unnamed lot |
|---|---|---|
| Buyer rule | What proposition changed or was confirmed? | Does the answer actually govern this lot? |
| Response action | Update every dependent object | Check for contradiction or accidental generalization |
| Commercial action | Recalculate affected lot drivers | Change nothing unless a supported dependency changes |
| Closure evidence | Reconciled lot response on the new basis | Reasoned no-change, separated wording or escalation |
| Failure mode | Answer stays local and the lot remains inconsistent | Similarity is mistaken for buyer authority |
Shared documents
A common document does not make every sentence procedure-wide
Multi-lot packs often mix a general invitation, shared contract conditions, a common service specification, lot schedules, pricing tabs and separate response templates. Position in a common file is evidence to inspect, not conclusive proof that every clause applies identically. Definitions, headings, applicability statements, cross-references, exceptions and the subject matter of each lot still control how the document reads.
Create a document-to-lot matrix. For every shared artifact, record whether it applies to all lots, named lots, a lot group, a particular service type or an unresolved set. Then locate the clarification within that structure. If Q-54 amends paragraph 8.2 only for Lots 2, 3 and 5, retain both the shared paragraph and the narrower answer. Do not edit the source text into an imaginary clean master document.
Shared bidder artifacts require the same care. A single method statement may cover several lots, but its claims need an explicit lot scope. A staffing diagram can show a central management team and different local response cells. A common evidence annex can identify which certifications support every lot and which depot records support only one. Reuse is efficient only when the reader can tell exactly where each statement applies.
Lot groups deserve their own row. A buyer-defined group can carry shared award rules or submission conditions, but it is not interchangeable with every informal cluster the supplier uses for management. TED eForms represents a group and its member lots separately. Follow the buyer’s declared membership, and reopen the map if a later notice changes it.
Lot change
Update each named lot from requirement to final artifact
For each direct lot, preserve the previous bid basis and write the smallest proposition the buyer supplied. In Lots 2, 3 and 5, Q-54 changes the hazardous-spill attendance period from the earlier 60-minute working basis to 30 minutes. It does not define when the clock starts, alter the response for non-hazardous incidents or say that one team may cover simultaneous events. Keep those axes unchanged or unresolved according to their sources.
Trace the proposition separately through each lot. Lot 2 may need an additional mobile team because of travel distances. Lot 3 may meet the period with an existing station-based team. Lot 5 may depend on a subcontractor whose letter covers weekday hours only. The same buyer answer can produce different solution and price effects because the lots have different geography, volumes, access and existing commitments.
Recalculate from controlled drivers. Change travel zones, roster coverage, incident concurrency, equipment placement and subcontractor availability before updating cost and price. Do not copy the percentage increase from one lot into another. A shared commercial model should retain separate input sets and show which cells the answer changed. Savings deserve the same trace if the clarification narrows an obligation.
Finish at the submitted objects. Check technical narratives, compliance matrices, implementation plans, resource tables, risk schedules, price workbooks, evidence annexes, portal fields and partner declarations for that lot. A correct internal decision is not enough if the uploaded schedule still contains 60 minutes or a reused method statement promises 30 minutes for the wrong set of lots.
Conflict
Do not repair the buyer’s scope by inference
A narrow answer can conflict with a broad clause. It can also be partial, use an obsolete lot number, refer to “these lots” after several questions, or name a schedule that no longer exists. Preserve the exact conflict. A tidy internal sentence such as “30 minutes applies to all operational lots” destroys the evidence needed to obtain a reliable resolution.
Search the complete current pack and published Q&A before escalating. Another answer may define the expression, an amendment may replace the common clause, or the notice may show that Lot 4 is a different service category. Record both supporting and contrary sources. If the scope remains open, use the official question channel and deadline, or route the point to the authorized legal and bid decision owners. Silence is not agreement.
Apply a bounded interim treatment only when the organization has authority to do so. The treatment might permit reversible drafting on two branches while blocking price approval and external commitments. It might retain the existing supported rule for Lot 4 while holding a common narrative that cannot yet express both cases safely. It must not transform an internal planning premise into a buyer-facing qualification unless the procedure permits that form and the right authority approves it.
Keep the unresolved state visible at release. If the tender must proceed before an answer arrives, the decision owner chooses among the procedure’s permitted options with legal, commercial and delivery input. The lot map records that decision and its boundary. It does not invent authority, waive a mandatory requirement or conceal a contradiction to make the package appear complete.
What good looks like
Useful outcomes from manage tender clarifications across lots
- The clarification can be traced to the buyer’s exact question number, answer number, source, version and publication time.
- Every lot in the current procurement has one stable buyer identifier and a separate applicability decision.
- Expressly named lots are distinguished from unnamed lots that merely share wording, systems, people or documents.
- Procedure-wide, lot-group, single-lot and condition-specific statements are represented without flattening them into one scope.
- Each directly affected lot carries the clarification through compliance, solution, capacity, evidence, price and response files.
- Related but unnamed lots receive a bounded consistency review without acquiring an unsupported requirement.
- Conflicts between the answer, a common specification and lot schedules remain visible until an authorized resolution exists.
- No-change conclusions identify the lot, object, reviewer, evidence and version they cover.
- The final multi-lot submission uses one reconciled answer basis while preserving documented differences between lots.
Operating model
How to run the work
- 01
Fix the clarification identity
Record the procedure, buyer question and answer numbers, source, publication time, document version, audience and any linked amendment before interpreting scope.
- 02
Rebuild the current lot universe
List every lot and lot group from the current notice and documents using the buyer’s identifiers, even when the bidder will not tender for all of them.
- 03
Extract the scope words
Preserve every named lot, exception, condition, shared document reference and phrase such as all lots, these lots or this lot without adding a synonym.
- 04
Decide applicability per lot
Assign direct, excluded, conditional, review-only, conflict, superseded or unresolved to each lot and cite the evidence for that decision.
- 05
Separate change from consistency review
Open change work for directly affected lots and a narrower contradiction check for related unnamed lots. Do not merge the two queues.
- 06
Update affected response chains
Trace the answer through each named lot’s requirements, method, resources, calculations, price, evidence, attachments and approvals.
- 07
Resolve cross-lot conflicts
Compare common documents and lot schedules, preserve contrary text, and use only an authorized clarification, amendment or review decision to settle the conflict.
- 08
Reconcile the multi-lot release
Test shared and lot-specific files against the map, close every applicable row, and preserve the approved basis for every unmentioned lot.
Evaluation
Questions that change the decision
- Is the buyer response authentic, current and addressed to this procurement stage and supplier audience?
- Which buyer identifiers define the complete current lot universe?
- Does the answer name individual lots, a lot group, all lots, a common document or a condition that selects lots?
- Does a later amendment restate, narrow, expand or supersede the answer?
- For each lot, what source proves direct application or non-application?
- Which unnamed lots share wording or dependencies and therefore require only a consistency review?
- Does a common specification conflict with the answer’s narrower lot wording?
- Which response objects and calculations are distinct per lot, and which are reused across several lots?
- What test supports each no-change decision for a shared artifact?
- Which unresolved scope point requires a further buyer question or qualified legal review?
- What evidence proves that the release preserves both cross-lot consistency and legitimate lot differences?
Failure modes
Where teams lose control
The team treats similar work as proof that an answer applies to every lot.
Only the lots being bid are mapped, hiding an explicit exclusion or cross-reference elsewhere in the procurement.
A lot title is used instead of the buyer’s stable identifier, causing a later renumbering or translation to misroute the answer.
A common method statement keeps the old rule after lot-specific pricing and staffing have changed.
A global edit imposes an unsupported condition on a lot the buyer did not name.
The team gives a Q&A response amendment status before verifying the governing procedure or any associated notice.
An answer naming a lot group is applied to a different grouping inferred by the bidder.
A conditional answer is copied without the condition that controls where it applies.
An unresolved conflict is hidden behind a single preferred interpretation.
The team assumes an answer changed the submission deadline although the buyer published no such change.
A shared artifact is marked reviewed even though no one tested every lot-specific statement it contains.
Measurement
Measure the finished job
Measure the completed workflow, including review effort and exceptions. Output volume on its own is not evidence of a better process.
- Clarifications with verified question, answer, source, version and publication metadata
- Percentage of the current lot universe with an evidence-backed applicability state
- Number of directly affected lots without a completed response-chain review
- Number of related unnamed lots awaiting a consistency decision
- Cross-lot conflicts open by source, owner and decision deadline
- Shared artifacts tested against every lot for which they will be submitted
- No-change decisions with a named reviewer, test and version
- Superseded clarification bases still found in draft or pricing files
- Elapsed time from answer publication to a reconciled multi-lot baseline
- Release defects caused by applying an answer too broadly or too narrowly
Questions
Common questions
If several lots contain the same clause, does one clarification apply to all of them?
Not by similarity alone. Identical wording is a reason to inspect every lot for consistency. Apply the answer directly only where its text, a controlling cross-reference or later authoritative publication establishes that scope.
Should we map lots we are not bidding for?
Yes. The complete lot universe can reveal express exclusions, buyer-defined groups, renamed lots and dependencies that explain the answer’s scope. Your commercial bid decision remains separate.
What if the answer says “all lots” but one lot schedule says something different?
Record a source conflict and check the procedure’s document hierarchy, later amendments and complete Q&A set. Do not choose the convenient rule silently. Escalate through the authorized buyer or review route if the current sources do not resolve it.
Can one shared method statement cover lots with different clarification outcomes?
Yes, if every affected proposition has a clear scope and the lot-specific branches are consistent with their schedules, prices and evidence. A generic statement that implies one rule for all lots is unsafe.
Does a clarification automatically amend the tender documents?
No universal answer exists. Check the procedure, the buyer’s publication and the applicable regime. Some responses point to a formal amendment or addendum; others confirm existing wording. Keep operational impact and legal effect separate.
Does an important multi-lot clarification extend the deadline?
Do not infer an extension. Use only a deadline changed through the authoritative channel. Applicable law may require the buyer to consider or grant more time in certain cases, but the bid plan cannot manufacture the new date.
What is the difference between review-only and no change?
Review-only is an open instruction to test an unnamed but related lot. No change is the completed result of that test, supported by the lot, object, source, reviewer and version it covers.
When is a multi-lot clarification fully closed?
Closure requires an applicability result for every current lot, completed impact work for each direct lot, evidenced consistency decisions for related lots, resolved or authorized conflicts, and reconciliation of the actual shared and lot-specific submission artifacts.
Sources
Primary references
- Guidance: Lots, updated 13 July 2026 UK Cabinet Office
- Procurement Act 2023, section 18, duty to consider lots The National Archives
- Procurement Act 2023, section 20, competitive tendering procedures The National Archives
- Procurement Act 2023, section 21, tender notices and documents The National Archives
- Procurement Act 2023, section 31, modifying a section 19 procurement The National Archives
- Procurement Act 2023, section 54, time limits The National Archives
- Guidance: Modifying a Competitive Procurement, updated 17 August 2026 UK Cabinet Office
- Guidance: Time Periods under the Procurement Act 2023 UK Cabinet Office
- Directive 2014/24/EU, Articles 18, 46, 47, 53 and 56, consolidated 1 January 2026 EUR-Lex
- TED eForms schema usage, procedure, lot and part information Publications Office of the European Union
- TED eForms latest business terms, including lot references Publications Office of the European Union
- TED eForms FAQ on lot identity and lot groups Publications Office of the European Union
- German Act against Restraints of Competition, section 97 German Federal Ministry of Justice and Federal Office of Justice
- German Act against Restraints of Competition, section 97a, lot principle German Federal Ministry of Justice and Federal Office of Justice
- German Act against Restraints of Competition, section 121, performance description German Federal Ministry of Justice and Federal Office of Justice
- German Public Procurement Ordinance, section 9, communications German Federal Ministry of Justice and Federal Office of Justice
- German Public Procurement Ordinance, section 20, information and extensions German Federal Ministry of Justice and Federal Office of Justice
- German Public Procurement Ordinance, section 29, procurement documents German Federal Ministry of Justice and Federal Office of Justice
- German Public Procurement Ordinance, section 30, division into lots German Federal Ministry of Justice and Federal Office of Justice
- French Public Procurement Code, Article L2113-10, division into lots Légifrance
- French Public Procurement Code, Article R2132-1, consultation documents Légifrance
- French Public Procurement Code, Article R2132-6, additional information Légifrance
- French Public Procurement Code, Article R2151-4, extension after important changes Légifrance
- DAJ technical note on division into lots, December 2025 French Directorate for Legal Affairs
- FAR 15.206, amending the solicitation, FAC 2026-01 Acquisition.gov
- Procurement Regulations for IPF Borrowers, seventh edition, September 2025 World Bank
- UNCITRAL Model Law on Public Procurement, Article 15 United Nations Commission on International Trade Law
- WTO Agreement on Government Procurement, Articles X and XI World Trade Organization
About the author
Tony Kim
Tony writes about applied AI, dependable product engineering and the systems that turn complex response work into controlled delivery.
Ziva
Proposal software for source-grounded RFP, RFI, DDQ and questionnaire response work.
Bid, proposal, presales, security and compliance teams. Start with the workflow, constraints and evidence you already have.
