iSpec Logo
Work Package and Sub-Tender Procurement
...
Published October 2026

How to Set Bid and Award Rules for Sub-Tenders

A project can have well-defined work packages and still receive bids that cannot be compared fairly. Before inviting suppliers, decide what they may bid for, which conditions they may attach, and how the permitted award combinations will be evaluated.

One supplier offers a complete equipment package. Another quotes only the components it manufactures. A third offers a discount if it wins two sub-tenders together. Each proposal may have merit, but the procurement team needs a declared basis for comparing them rather than inventing one after prices arrive.

This guide addresses the bid and award rules that follow package definition. It is not another method for drawing package boundaries. The objective is to turn an agreed scope structure into clear instructions for bidders and a defensible evaluation process. The examples are illustrative, not customer case studies; the approach must be adapted to the project's contracts and applicable procurement requirements.

1. Separate the work package, the bid unit, and the award unit

A work package describes a defined scope of equipment, information, or services. A bid unit is the scope a supplier is permitted to price. An award unit is the scope the buyer may place under a contract. These can coincide, but they should not be assumed to mean the same thing.

For each sub-tender, decide whether the whole scope must be offered and awarded together, whether defined item groups may be separated, and whether the buyer may award several units to one supplier. Identify the common obligations that remain necessary under every permitted arrangement, including documentation, integration inputs, testing, and warranties.

Complete-package bids

Require every stated deliverable within the package. Explain how an omitted item or qualification will be treated.

Defined partial bids

Name the items or groups suppliers may bid for separately. Permission to bid for one sub-tender does not automatically permit an incomplete offer within that sub-tender.

Split or combined awards

State which allocations are allowed and any disclosed restrictions. Do not imply that a software feature creates a contractual or legal right to divide an award.

2. Publish participation and completion rules before issue

Tell suppliers whether they may bid for one, several, or all eligible sub-tenders. Explain any minimum scope they must include and what constitutes a complete submission. Specialist competition is useful only if specialists know where their responsibility begins and ends.

Separate eligibility to participate from technical compliance and award selection. A supplier permitted to quote two scopes may still need to demonstrate that it can deliver both concurrently. State the evidence required and how capacity constraints will be considered under the published evaluation approach.

Required responses

Identify common declarations, commercial terms, technical responses, schedules, and package-specific documents.

Alternatives and exclusions

Explain whether alternatives are permitted, whether a compliant base offer is required, and where exclusions must be recorded.

Submission conditions

Set out the closing arrangements, validity requirements, clarification process, and treatment of incomplete or conditional offers.

3. Put common information in the main tender and specific obligations in the sub-tender

The iSpec manual describes linked sub-tenders managed under a main tender. Adding a vendor to a sub-tender also adds that vendor to the main tender. The manual therefore directs buyers to keep information applicable to all sub-tenders in the main tender and information unique to a scope in its relevant sub-tender.

Use that distinction to control the bid instructions. Common participation rules can be stated once, while each sub-tender defines its own deliverables, permitted bid units, technical requirements, and package-specific response obligations. Check that the documents do not give conflicting instructions.

The documented linked structure also shares publication dates and the main tender's currency, additional-currency, evaluation-system, RFx, and approval settings. Do not design the competition on the assumption that linked sub-tenders have independent tender calendars or independently configured evaluation systems. If those differences are essential, confirm an appropriate procurement structure before creating the tenders.

4. Make combined offers explicit and comparable

If combined offers are allowed, distinguish an unconditional price for each award unit from a price that depends on winning another unit. Specify how suppliers should state the condition and how the procurement team will evaluate it. Do not quietly assume that every quoted price remains available under every award combination.

For example, suppose a supplier offers package A for 120 units and package B for 80 units, or both together for 190 units. Two specialist offers total 195 units. The combined offer is cheaper on those illustrative prices alone, but it is not automatically the preferred award. Scope completeness, disclosed evaluation criteria, delivery capability, and any properly included integration costs still matter.

Avoid counting a discount twice or treating a conditional price as an independent offer. If a supplier withdraws or changes the condition through an authorised clarification or negotiation, retain the revised basis and assess its effect on the feasible award combinations.

Independent availability

Record whether each package price can be accepted on its own.

Combination condition

Identify the exact scopes, quantities, or award assumptions required for a discount or bundled price.

Common costs

State how shared mobilisation, documentation, tests, or other common charges should be quoted so they are neither omitted nor duplicated.

Evaluation basis

Disclose the method for considering combined offers, including relevant restrictions and adjustments. Check it against applicable procurement rules before tender issue.

5. Compare feasible award configurations, not disconnected low prices

First establish which offers satisfy the published requirements and which qualifications remain unresolved. Then compare the permitted configurations using a consistent scope and the disclosed evaluation method. The lowest number in each package column may not form a valid overall offer.

For each configuration, check that all required deliverables are included, common costs are treated consistently, interfaces have accountable owners, and supplier capacity supports the proposed allocation. Where the tender permits a project-level cost adjustment, use an evidenced basis rather than an improvised allowance introduced to favour a preferred result.

Keep technical and commercial judgements traceable. A reviewer should be able to see why a configuration was admissible, which assumptions were accepted, and why an apparently cheaper combination was rejected. Tender structure does not remove the need for engineering, commercial, and approval decisions.

6. Explain sub-tender selection and resubmission to bidders

The iSpec vendor manual describes suppliers selecting the sub-tenders they wish to bid for, completing the main and selected sub-tender information, and including the selected sub-tenders when submitting the bid through the main tender. It also explains that selections can be changed before the closing date and that changes require the bid to be resubmitted.

Include a clear completion reminder in the bidder instructions. Preparing a response or changing a selection is not the same as completing the required submission step. Direct bidders to the documented process and the actual closing arrangements rather than promising that an edited response is automatically submitted.

Treat later clarifications and negotiations under the authorised procedure for that procurement. The pre-closing ability to change a selection should not be described as unrestricted permission to change bids after closing.

7. Record the award decision and carry the conditions into the contracts

The award recommendation should identify the selected configuration, the alternatives considered, the applicable evaluation basis, and the remaining conditions. Include a package-to-vendor allocation and show that no required obligation disappears between the proposed contracts.

Before issuing the awards, confirm that any combined-price condition is satisfied by the actual allocation. Check whether changing one award alters another supplier's price, warranty position, delivery commitment, or integration responsibility. Resolve those consequences before treating the comparison as final.

Carry the agreed scope, qualifications, prices, shared obligations, and acceptance requirements into the contract documents. A procurement comparison sheet is useful evidence, but it does not replace clear supplier obligations in the final agreements.

8. Apply the rules to the sector without assuming identical packages

The same questions apply across the sectors in this cluster, but the appropriate bid and award units depend on the actual equipment, market, and integration responsibilities.

Ports and terminals

For equipment required at several locations, clarify whether suppliers may offer one location or several and how location-specific testing, delivery, and common charges will be evaluated.

Breweries

If process equipment and cleaning systems can be offered separately or together, retain clear responsibility for compatibility, utility assumptions, and performance demonstrations under each permitted award configuration.

EPC projects

For specialist equipment and associated controls, check that a combined offer and split supplier offers include equivalent engineering inputs, documentation, and agreed interface obligations.

Infrastructure

For pumping, electrical controls, and telemetry scopes, define which combinations may be bid and awarded and who remains responsible for proving the connected equipment works as required.

A final check before publishing the tender

A colleague who did not design the competition should be able to read the instructions and determine what a supplier may offer and how that offer will be assessed. Test the documents with an independent package bid, a combined offer, and a supplier exclusion before issuing them.

Participation is clear

Suppliers can identify eligible sub-tenders, mandatory response requirements, and permitted partial or alternative offers.

Prices can be compared

Independent prices, combination conditions, shared charges, and the evaluation method are explicit.

The award is deliverable

Every permitted configuration preserves required scope, accountable interfaces, capacity, and acceptance obligations.

The process fits the system

The linked tender dates and shared settings match the intended competition, and bidders understand the selection and submission steps.

References

  • iSpec 10 User Manual — Using sub tenders

    Reviewed the live manual page for linked main/sub-tender structure, common versus scope-specific information, shared publication dates and tender settings, vendor invitations, item allocation, consolidated costing, and negotiation cost visibility. It does not document automatic award-combination optimisation. The article's proposed bid and award rules are practical editorial guidance, not claims that iSpec automatically enforces them.

  • iSpec 10 User Manual — Responding to a Sub tender

    Reviewed the live vendor instructions for selecting one or more sub-tenders, completing main and selected responses, including selected sub-tenders in the main submission, changing selections before closing, and resubmitting after changes. The page's crane-location example supports the multi-location illustration; no customer deployment or unrestricted post-closing bid changes are inferred.

iSpec Advantage

How iSpec supports a coordinated sub-tender competition

  • Organise smaller project scopes as linked sub-tenders under a main tender, with documented shared dates and settings.
  • Invite different vendors to individual sub-tenders, allowing eligible suppliers to quote across more than one where permitted.
  • Let vendors select sub-tenders and include those selections in their main-tender submission using the documented response process.
  • Allocate individual sub-tender items to different vendors, or exclude items from final contracts, where the procurement and contractual rules allow.
  • See consolidated project costing and the effect of sub-tender negotiations on the total project cost. These documented capabilities do not establish automatic award-combination optimisation or automatic validation of procurement rules.

Make package-level offers easier to compare and award with clear scope, shared tender information, and a documented procurement process.

See how iSpec connects procurement decisions, tender records, approvals, and delivery outcomes.