How to verify a subcontractor meets tender conditions

First decision

The subcontractor label is not enough

The first question is not whether the partner is good. It is what legal and tender role the proposed arrangement creates. A company delivering planned maintenance under the prime can be an ordinary subcontractor. If the prime also uses that company's maintenance references to pass a minimum experience test, the same company becomes a capacity provider for that criterion. The evidence burden changes even though the work package does not.

A mandatory specialist named by the buyer can face its own qualification test. A consortium member submits the bid jointly and should not be pushed through a subcontractor checklist. A distributor providing standard goods may be a supplier rather than a subcontractor under the applicable rules. Preserve the tender's definitions and obtain legal review where classification affects eligibility.

Create a separate record for each legal entity. Do not let a group logo, brand or commercial nickname stand in for registration details. Capture parent and affiliate relationships only when a rule or claim makes them relevant. The assessment must follow the entity whose capacity, declaration or performance is actually offered.

Control record

Build an entity-specific compliance and evidence matrix

One supplier questionnaire cannot prove compliance with an unknown tender. Build rows from the current notice, selection questionnaire, procurement document, schedules, draft contract, amendments, clarification answers and visible portal prompts. Each row needs the source and locator, the condition in neutral terms, the role and scope that trigger it, the required proof, its owner, reviewer and current state.

Keep the buyer rule separate from the team's conclusion. For example, store the source text requiring all intended subcontractors to be listed, then record whether the proposed fire systems company is within that definition. This separation allows a reviewer to correct interpretation without losing the source or the underlying entity facts.

Use states that reveal what is wrong. `evidence_pending` means the condition may be satisfied but proof is incomplete. `condition_failed` means available evidence does not satisfy it. `buyer_approval_pending` means internal checks have passed but external acceptance remains open. These states demand different next actions and should never collapse into amber.

Tender rules

Confirm permission, reserved work and disclosure timing

Find the general permission first, then read every exception. Some tenders permit subcontractors but reserve critical tasks for the bidder. Others cap subcontracted scope, require named specialists, restrict multiple appearances by the same subcontractor, or demand advance buyer acceptance. Swiss federal law, for example, permits subcontractors unless the procurement limits them and generally expects the characteristic supply from the tenderer. The procurement documents still determine how that rule operates in the case.

Disclosure is its own test. Record whether the buyer asks for the entity at request stage, tender stage, before award or after a change. Capture the required fields, such as legal identity, work share, value, payment conditions, tier and relied capacity. The UK Procurement Act regime requires authorities to request information about intended subcontracting and check the debarment list. French rules specify information for a subcontractor declared with the offer. Neither example should be transplanted into another jurisdiction without checking its law and documents.

Tender permission does not necessarily equal final acceptance. Keep `condition_satisfied` for the bidder-side rule separate from `buyer_approval_pending` where the authority must still accept, consent to or approve the arrangement. Detailed consent procedure and contract-stage replacement belong in their own review; this matrix records the dependency and prevents a premature green status.

• Record any percentage, tier, location or work-package restriction.
• Identify tasks the prime or a named member must perform directly.
• Preserve the exact disclosure event and required buyer form.
• Distinguish an unnamed future subcontractor from an omitted known entity.
• Do not equate internal partner approval with buyer acceptance.

Selection capacity

If the bid relies on the entity, prove capacity and availability

Map each participation condition to the entity or combination that satisfies it. Turnover, insurance, equipment, professional qualifications, experience and staff are not interchangeable. Under EU-derived rules, reliance can be possible regardless of the legal form of the relationship, but the bidder must prove access to the necessary resources. For educational or professional qualifications and relevant experience, the supporting entity must perform the work for which those capacities are required.

Inspect the tender's required means of proof. A letter of intent may be insufficient if the buyer asks for a binding undertaking, completed ESPD, guarantee, named staff commitment or subcontract. Match the commitment to the relevant resource, period and work package. A broad statement that a partner will “support the bid” does not prove that its certified engineers, workshop or financial capacity will be available for contract performance.

Check whether joint liability, direct performance or replacement provisions follow from the type of reliance. If a supporting entity fails the corresponding criterion or a mandatory exclusion test, some regimes require the authority to demand replacement. That possibility is not a reason to submit an unverified entity. Treat replacement as a controlled change that reopens solution, price, evidence, declaration and approval rows.

Entity evidence

Test exclusions and work-specific conditions separately

An exclusion review asks whether the applicable mandatory or discretionary grounds, debarment lists and declarations cover the proposed entity. The answer depends on the regime, role and tier. Current UK guidance distinguishes subcontractors used to satisfy participation conditions from the broader set of intended subcontractors whose details may be requested. US federal rules place primary responsibility for prospective subcontractor responsibility on the prime and contain specific controls for excluded firms. Record the exact rule instead of using one global sanctions checkbox.

Next test conditions tied to the work. These may concern licensing, security clearance, quality or environmental certification, data location, labor rules, health and safety, site access, conflicts, insurance, export controls or named personnel. Verify the holder, issuing body, covered activity, geography, site, expiry and any surveillance or renewal status. A valid certificate can still be irrelevant to the proposed entity or scope.

Do not ask a bid coordinator to make an unsupported legal conclusion. The matrix should display the source facts, search result, declaration and ambiguity, then route the decision to the authorized legal, compliance or procurement reviewer. Record the check time and source because lists, company status and certificates can change before submission.

• Use the legal entity identifier, not only the partner name.
• Record whether the check reaches direct subcontractors or lower tiers.
• Keep self-declarations separate from independent registry evidence.
• Scope every certificate to activity, site, service and validity period.
• Recheck material time-sensitive evidence before release.

Cross-bid control

Make the subcontractor story agree everywhere

Compare the approved entity record with the organization chart, method statement, responsibility matrix, staffing plan, references, certificates, pricing schedule, subcontracting form and portal fields. The same company cannot be a minor installer in the price narrative and the provider of decisive technical capacity in the selection response without that relationship being made explicit and supported.

Record tender-stage obligations that must reach the subcontractor before the bid can safely rely on it. Examples include confidentiality, information security, data handling, employment standards, audit access, named-person commitments and acceptance of the proposed scope. This is a narrow readiness test: identify the applicable obligation, obtain evidence of acceptance where required, and flag unresolved contradictions.

Do not turn this check into full contract flow-down drafting or post-award supplier management. Those activities need clause-level legal analysis, negotiated contract language, onboarding, monitoring and change control. The tender matrix hands off open obligations with their source and owner while retaining only the facts needed to approve this bid configuration.

Worked example

An airport maintenance bidder relies on a fire systems specialist

Consider a fictional airport facilities tender. Northfield Services will be prime and proposes Redfield Fire Systems for fire alarm inspection and emergency repairs. The selection schedule requires three comparable airside fire-system contracts and qualified technicians. Northfield has general facilities references but uses Redfield's specialist experience and people to pass those tests. The tender also reserves command-center operations to the prime and requires all intended subcontractors to be declared.

The matrix classifies Redfield as both a subcontractor and a relied-upon capacity provider. It checks the registered company, exact inspection scope, references, technician qualifications, airside access assumptions, exclusion declarations and binding resource commitment. It confirms that command-center work stays with Northfield. The pricing schedule, method statement, organization chart and subcontractor declaration all need the same split.

Review finds that one reference belongs to Redfield Holdings, not Redfield Fire Systems, and the commitment letter promises “access to group expertise” without naming technicians or contract duration. Those are not missing formatting details. The experience claim and resource availability are unproved for the named entity. Rows move to `evidence_pending`; release remains blocked until valid entity-level proof is obtained or the bid is reconfigured and retested.

Release boundary

Approve the configuration, not the partner in the abstract

The reviewer approves a defined configuration: legal entity, role, tier, lot, work package, relied criteria, evidence set and tender version. Approval does not certify the partner for every future bid. Record any conditions, the authority that accepted them and the event that would invalidate the conclusion.

Reopen affected rows after a tender amendment, buyer clarification, entity substitution, scope transfer, new tier, changed price share, expired certificate, altered key personnel or revised commitment. A replacement may solve one exclusion issue while breaking an experience criterion or delivery assumption. Repeat both the entity tests and the reconciliation across the bid.

This process stops at tender readiness. It does not select the commercial partner, negotiate the subcontract, approve every contract flow-down, secure buyer consent, operate delivery or monitor post-award performance. Hand those activities the current matrix and unresolved obligations. The final bid decision remains with the authorized team, supported by procurement and legal advice appropriate to the jurisdiction.