How to Manage Clarifications Across Linked Sub-Tenders
A clarification raised against one sub-tender may affect several packages. Answering the original bidder is only part of the job: the buyer must establish where the answer applies, who needs it, and whether the controlled requirement must change.
Consider an equipment supplier asking whether the stated power supply includes a particular operating condition. The answer may change the equipment design, the electrical package and the integrated test plan. If the response remains in a single email thread, neighbouring package owners may continue working from different assumptions.
Linked sub-tenders make it possible to coordinate smaller scopes under a main tender, but the link does not decide the engineering consequences of a question. A useful clarification process preserves the original clause context while making the cross-package effects explicit.
This guide addresses buyer-side clarification control during a linked competition. It follows package definition and tender issue, rather than replacing either activity. The examples are illustrative, not customer case studies. Apply the method within the procurement's stated rules, confidentiality requirements and authorised change procedure.
1. Keep the question attached to the requirement it challenges
Begin with the specific heading or clause that prompted the question. Record the main-tender or sub-tender reference, the relevant document and version, and the issue the bidder needs resolved. A general subject line such as 'technical query' is not enough to establish which requirement was being discussed.
The iSpec vendor manual describes selecting a document heading and using its mail icon to ask a question or add a comment, with attachments where needed. Messages relating to that item remain in its message history. That provides a defined place for the originating discussion rather than requiring the team to reconstruct the connection from a separate mailbox.
If the conversation affects another requirement, identify that requirement explicitly in the response and the team's impact record. Do not assume that a message against one clause automatically updates another clause or propagates to every linked sub-tender.
2. Decide whether the answer is common, package-specific or an interface issue
Classify the scope of the answer before deciding who should receive it. The main tender should contain information that applies across its sub-tenders; information unique to one scope belongs in the relevant sub-tender. The iSpec sub-tender manual makes this distinction important because adding a vendor to a sub-tender also adds that vendor to the main tender.
A question's location does not establish its full impact. A bidder may raise a common requirement from a package-specific document, or ask about a boundary that is described differently in two packages. Review the underlying obligation, not just the tender in which the message arrived.
Common requirement
The answer explains an obligation that applies to the relevant bidders across the linked competition, such as a shared reporting requirement.
Package-specific requirement
The answer concerns an obligation confined to one scope, such as that package's inspection evidence or equipment detail.
Interface requirement
The answer affects obligations on both sides of a package boundary. Identify each affected package and the owner who must review the consequence.
3. Review the consequences with the affected package owners
Give the technical authority and affected package owners the original question and clause reference, not an abbreviated retelling. Ask whether the proposed answer changes a deliverable, an exclusion, an incoming design assumption, a supplier-data obligation, a required date or an acceptance condition.
Use a small impact record alongside the controlled tender information. For each affected package, identify the requirement concerned, the proposed action, the responsible reviewer and whether an amendment is required. This is a recommended working method, not a claim that iSpec automatically discovers interfaces or creates an impact register.
Do not close the review merely because the originating package owner agrees. If an electrical requirement changes an equipment assumption, obtain the appropriate review on both sides before treating the response as complete.
4. Separate the shared answer from confidential bidder information
A response that clarifies a common tender requirement may need to reach several bidders. That does not mean every part of the originating question should be broadcast. A supplier's proprietary design, pricing approach or bidder-specific commercial information may require different treatment.
Prepare a neutral statement of the shared requirement where appropriate and keep restricted material within the authorised recipient group. Confirm the actual recipient list before sending. The iSpec correspondence manual describes checking who will receive a message; the procurement team still needs to decide the appropriate audience.
Keep a record of which common answer was issued to which relevant bidders and when. Evidence that information was distributed is not proof that every recipient understood it or incorporated it into a bid. Follow any acknowledgement requirements set for that procurement without substituting a delivery assumption for the required evidence.
5. Distinguish an explanation from a change to the tender
An answer may explain an existing obligation, or it may change what suppliers must deliver. If it changes scope, performance, responsibility or acceptance requirements, process the change through the authorised amendment procedure. Do not leave the revised obligation only in correspondence while the formal specification continues to say something else.
Identify the affected clauses and versions, obtain the required approvals, and issue the approved information to the appropriate bidders. Refer the correspondence to the resulting amendment so the reason for the change and the controlled requirement can be reviewed together.
Assess whether bidders have enough time to incorporate the change under the competition's rules. The documented iSpec linked structure follows the main tender's publication dates and specified settings. Do not assume one linked package can be given an independent tender calendar, or promise an automatic extension when a clarification is raised.
6. Reconcile the response with the bid that will be evaluated
Before evaluation, check that the relevant clarification or amendment is reflected in the submission being assessed. Record unresolved exceptions against the affected package rather than treating an unanswered assumption as compliance.
The iSpec vendor manual explains that suppliers select the sub-tenders included in their main-tender submission, and that changes require the bid to be resubmitted. A bidder editing a response is not the same as completing the required submission step. Keep reminders consistent with the closing arrangements and the documented vendor process.
After closing, handle questions and any permitted changes under the authorised post-submission procedure. The ability to change selections before closing is not unrestricted permission to revise a bid afterwards. Do not use a clarification to introduce an undisclosed evaluation advantage.
7. Apply the method to a connected project example
In an illustrative brewery upgrade, the equipment supplier asks whether a stated utility condition is available during cleaning as well as production. The answer affects the equipment scope, the utilities package and the test conditions. The clarification owner identifies the originating clause, involves the relevant package owners, and establishes whether the published requirements need an approved amendment.
The shared requirement can then be issued to the relevant bidders without disclosing a supplier's proprietary design proposal. The utilities obligation and equipment assumption should agree in the controlled documents. The evaluation team needs the approved position, not a forwarded fragment of the original conversation.
The same principle applies to terminal equipment power and control interfaces, EPC equipment and instrumentation boundaries, or infrastructure pumping and telemetry packages. These examples describe coordination needs; they do not imply that every project should use identical packages or that iSpec automatically resolves technical compatibility.
8. Close the issue with a record the next team can follow
A closed clarification should let an authorised colleague identify the question, its original requirement, the agreed answer, affected scopes, any approved amendment and the intended distribution. An issue is not complete merely because someone sent a reply.
At evaluation and handover, review the outstanding clarification list alongside package exclusions and interface obligations. Carry the final agreed requirements into the appropriate contract and delivery records. Do not rely on a supplier or new project team to recover an unrecorded agreement from personal email.
The practical test is simple: can someone who did not attend the discussion understand what was asked, which requirement was affected and what the team did about it? Clause-linked history supports that task; accountable review and controlled issue make the answer usable across the project.
Origin preserved
The question and response remain associated with the requirement that prompted them.
Impact reviewed
Affected package owners have addressed cross-scope consequences and unresolved obligations.
Audience checked
Shared information has reached the relevant bidders without unnecessarily disclosing restricted content.
Requirement controlled
Any authorised change is reflected in the appropriate tender documents and the basis used for evaluation.
References
- iSpec 10 User Manual — Using sub tenders
Read the live page: linked main/sub-tender organisation, vendor addition to the main tender, common versus scope-specific information, shared publication dates, and shared currency, evaluation-system, RFx and approval settings. It does not establish automatic interface-impact discovery, cross-package message propagation, independent linked-tender calendars or automatic amendment control.
- iSpec 10 User Manual — Clarifications and correspondence
Read the live vendor correspondence instructions: select the relevant document heading, use its mail icon, add questions/comments and attachments, check recipients, and retain item-level message history. The recommended audience classification and cross-package impact review are editorial process guidance, not claims of automatic broadcasting or automated confidentiality classification.
- iSpec 10 User Manual — Responding to a Sub tender
Read the live vendor instructions for selecting sub-tenders, including them in the main-tender submission, changing selections before closing, and resubmitting after changes. No unrestricted post-closing revision capability is inferred.
How iSpec keeps linked-tender discussions in context
- Organise smaller scopes as linked sub-tenders under a main tender, keeping common information separate from package-specific information.
- Start clarification correspondence from the relevant document heading and retain the item's message history for later reference.
- Check message recipients using the documented correspondence controls rather than assuming that every linked bidder should receive every message.
- Coordinate linked tenders within the main tender's documented shared dates and settings. Software structure does not replace technical impact review, confidentiality decisions or authorised amendments.
Keep package clarifications connected to the requirements and decisions they affect. Ask for an iSpec demonstration using a linked-tender scenario from your own procurement process.
See how iSpec connects procurement decisions, tender records, approvals, and delivery outcomes.
