---
title: "How to know whether your references meet tender rules"
description: "Test each project reference against the tender’s recency, scope, value, entity and proof conditions before relying on it for eligibility."
canonical: "https://zephior.com/insights/assess-tender-reference-eligibility"
last-updated: 2026-09-02
---

# How to know whether your references meet tender rules

> Test each project reference against the tender’s recency, scope, value, entity and proof conditions before relying on it for eligibility.

By [Tony Kim](https://zephior.com/authors/tony-kim). Published 2026-09-02; updated 2026-09-02. 11 minute read.

## Definition

Reference eligibility assessment is the rule-by-rule test of whether a prior contract, project or service record can be used to satisfy a stated tender condition for relevant experience or technical capacity. It checks the required number of references, look-back period, completion status, similarity, minimum value or scale, contracting entity, supplier entity, individual or consortium attribution, evidence form and verification rights. It determines admissibility. It does not write the case study, score the persuasive strength of the example or provide a legal conclusion beyond the procurement documents.

## Problem

Organizations have excellent client work that still fails a tender reference rule. The project ended one month outside the look-back window. The contract value belongs to a wider program while the relevant supplier work was smaller. A parent company delivered the service but the bidding subsidiary claims it. A joint venture lists the full contract even though its member performed one workstream. A live contract is described as completed. The client name and outcome sound convincing, so the team notices the defect only when a form demands dates, values, signatures or proof. Marketing quality cannot cure a mandatory eligibility failure.

## Point of view

Treat every reference condition as a set of predicates, not a general request for relevant experience. Preserve the exact tender words and define how each can be evidenced. Test the bidding entity and proposed consortium structure before testing the story. Normalize dates, value, currency, contract boundary and supplier share. Separate proven fact, reasonable interpretation and clarification need. A reference either clears every mandatory predicate, clears it only under a named interpretation, or does not clear it. Do not let a strong narrative turn a conditional match into an unconditional declaration.

## Turn one reference sentence into separate pass-fail tests

Copy the complete condition from the controlling document, including definitions, footnotes, form instructions, entity rules and clarification answers. Then break it into atomic predicates. A requirement for “three comparable contracts completed in the last five years, each worth at least EUR 1 million and including multi-site migration” contains number, similarity, completion, time, value, activity and evidence tests. None compensates for another. Four small projects do not necessarily replace three qualifying ones; exceptional similarity does not cure an expired date.

Classify each predicate as explicit, interpreted or unresolved. Explicit means the tender defines the test. Interpreted means the documents use a term such as “similar” without a complete boundary and the team has a reasoned reading. Unresolved means plausible readings change eligibility. Record exact question, source and consequence for clarification. Do not ask the buyer to approve your chosen project informally; ask for the rule needed to assess all bidders consistently through the prescribed channel.

Keep mandatory and scored experience apart. A project may clear the minimum and still be weak evidence against quality criteria. Another may be highly persuasive yet fall outside the mandatory look-back window. Build the eligibility set first. Only then choose which admissible examples best demonstrate understanding, complexity, outcomes and risk control. This prevents a favorite case study from dominating a gate it cannot pass.

**Example predicate register**

| Predicate | Question | Result evidence |
| --- | --- | --- |
| Count | How many distinct references? | Unique qualifying contract IDs |
| Period | Which event must fall in which dates? | Signed contract and completion record |
| Similarity | Which activities or outcomes are required? | Scope schedule and acceptance evidence |
| Scale | Which value, volume or users count? | Reconciled contract and delivery records |
| Attribution | Whose experience may be used? | Entity, role and reliance documentation |

## Define the work actually performed before testing similarity

Create a reference fact record from contracts, statements of work, purchase orders, invoices, acceptance records and controlled delivery data. Name customer legal entity, contracting supplier entity, contract and lot identifiers, base and option periods, status, geography, users or sites, supplier role, subcontractors and the service boundary. If several work orders sit under one framework, determine whether the tender permits them to be treated as one contract or requires distinct references.

Reconcile value carefully. Record total contract value, amount awarded to the bidding entity, amount performed to date and value attributable to the relevant services. State currency, tax treatment, price basis and conversion date if needed. A maximum framework value is not automatically spend. A consortium contract value is not automatically each member’s experience. A multi-service contract may exceed the threshold while the comparable work does not. Use the metric named by the tender rather than the largest defensible-looking number.

Map similarity at the level requested. It may concern the supplied outcome, technical activity, regulatory environment, delivery scale, contract model, geography, customer type or combination. Record direct match, comparable match and gap with evidence. Do not inflate a general platform deployment into a specific data migration unless the supplier actually performed and can prove that activity. Conversely, avoid rejecting a reference merely because buyer terminology differs when the underlying work clearly satisfies the defined predicate.

- Use controlled delivery records, not the marketing summary.
- Separate framework, contract, work order and relevant work value.
- Record supplier role and work actually performed.
- Normalize units, currency, tax and periods.
- Map similarity to the buyer’s required activity and scale.

## Test who owns the experience and when it counts

Begin with the bidding legal entity and planned consortium. Check whether the condition must be met by each member, one member, the group collectively, the lead, a named subcontractor or an entity whose capacity the bidder formally relies upon. The EU public-procurement directive provides for technical and professional ability and, under stated conditions, reliance on other entities’ capacities. The actual tender determines the permitted structure and evidence. Group branding alone does not transfer a contract from parent to subsidiary.

For acquired businesses, mergers, reorganizations and predecessor entities, establish the legal succession, assets, people and capacity that moved, then obtain the interpretation and documents required by the tender. Do not claim the seller’s entire history because several employees joined. For a joint venture reference, identify the member’s contractual role, share and activities. If named experts’ experience can count separately, keep personal and corporate experience distinct and prove availability where required.

Build a date line rather than a single “year” field. Include award, signature, service start, relevant activity, acceptance, completion, current status and any extension. Apply the precise look-back trigger. A contract signed six years ago but completed two years ago may qualify under a completion test and fail under an award test. A live contract may qualify when the rule says “performed during,” but not when it requires completion. Never change the label to fit the project.

**Attribution and period checks**

| Situation | Evidence needed | Unsafe shortcut |
| --- | --- | --- |
| Group company project | Contracting entity and permitted reliance | Same brand means same experience |
| Joint venture project | Member role, share and performed scope | Claim full contract for every member |
| Acquired business | Succession and transferred capacity | Claim all seller references |
| Ongoing contract | Rule trigger and performed milestones | Call implementation complete |
| Old award, recent completion | Full date line and rule wording | Use whichever date passes |

## Secure the prescribed evidence before relying on the reference

List the exact admissible proof: prescribed reference form, completion or performance certificate, contract extract, purchase order, invoice record, customer declaration, contact details, translation, signature or portal field. World Bank and EBRD standard procurement resources illustrate why form-specific experience records matter: dates, role, value and completion are often structured for comparison. Follow the current tender rather than assuming a general case-study document will be accepted.

Contact the customer through an authorized account owner. Explain the procurement, the facts to be disclosed, verification route, consent needed and deadline. Ask the contact to confirm only matters they can know and are permitted to state. A helpful executive who joined after delivery may not be able to certify historical scope. Respect confidentiality and data-protection duties. If disclosure is restricted, use the procedure’s permitted redaction or alternative-evidence route instead of inventing detail or sending confidential contracts.

Reconcile every form field to controlled records and the predicate result. Check dates, currencies, tax, names, entity numbers, values, role, completion wording and contact information. An independent reviewer should reproduce the pass result from the tender rule and evidence. Mark any conditional interpretation prominently in the qualification decision. If no project clears every mandatory test by the deadline, treat that as an eligibility failure or seek a permitted structural solution; do not submit a polished narrative as a substitute for proof.

- Follow the prescribed form and evidence hierarchy.
- Obtain customer consent and a verifiable contact.
- Protect confidential records through permitted handling.
- Reconcile every declared field to source records.
- Fail honestly when no reference clears all predicates.

## Useful outcomes

- Every mandatory reference predicate is visible and tied to a controlling source.
- Each proposed project has a pass, fail, conditional or unknown result by predicate.
- Contract value, supplier share and relevant work value are not conflated.
- Legal-entity, parent, predecessor, subcontractor and consortium attribution is explicit.
- Reference contacts, certificates and supporting documents are confirmed before submission.
- Qualification decisions do not depend on an attractive but inadmissible case study.

## Workflow

1. **Parse the condition.** Extract number, period, status, similarity, scale, entity, attribution, evidence and verification predicates exactly as issued.
2. **Define the project boundary.** Identify the actual contract, customer, supplier entity, dates, scope, value, role and portion of work being claimed.
3. **Test each predicate.** Issue pass, fail, conditional or unknown with exact supporting record and no compensating score between mandatory conditions.
4. **Resolve attribution.** Apply the tender’s rules for bidding entities, groups, joint ventures, acquisitions, named experts and subcontractors.
5. **Secure admissible proof.** Complete the required form, client consent, certificate and supporting record, then independently reconcile every declaration.

## Key decisions

- Which reference conditions are mandatory, scored or merely requested context?
- What event starts and ends the look-back period?
- Does “completed,” “performed” or “substantially completed” have a defined meaning?
- How much scope similarity is explicitly required?
- Which value counts: total contract, supplier revenue, lot value or relevant service portion?
- Must the bidder itself hold the experience, or can another entity’s capacity be relied upon?
- How is joint delivery attributed between members and subcontractors?
- Which documents and client verifications must be available by the deadline?

## Risks

- A publication, award, completion or reference date may be used for the wrong recency test.
- A framework ceiling may be presented as revenue actually delivered.
- Total program value may be attributed to one narrow supplier workstream.
- Group experience may be claimed by a bidder without a permitted reliance mechanism.
- A project may sound similar while missing the specific required activity or scale.
- A live service may be labelled complete because one implementation phase ended.
- A client contact may be unavailable, unauthorized or unable to verify the declaration.
- A translated or reformatted certificate may omit a field required by the prescribed form.

## Metrics

- mandatory predicates with controlling clause and interpretation
- candidate references tested before bid commitment
- conditional and unknown results closed before submission
- claimed values reconciled to contract and supplier share
- entity-reliance positions approved
- client verification permissions confirmed
- final forms independently checked against source records

## Frequently asked questions

### Can several smaller projects be combined to meet one value threshold?

Only if the tender permits aggregation. A requirement for each reference to exceed a value normally cannot be met by silently adding unrelated contracts.

### Can a subsidiary use its parent company’s reference?

Only under the entity and reliance rules of the procurement, with the required commitment and evidence. Common ownership alone is not enough.

### Does an ongoing contract count as completed experience?

Apply the exact status and date wording. It may count under a performed-services rule and fail when completion or acceptance is mandatory.

### What if the client will not sign the buyer’s form?

Check whether the procedure allows equivalent evidence, explain the permitted alternatives and seek clarification if needed. Do not forge, backfill or overstate client confirmation.


## Primary sources

- [Directive 2014/24/EU on public procurement](https://eur-lex.europa.eu/eli/dir/2014/24/oj/eng), EUR-Lex
- [World Bank Project Procurement Framework](https://www.worldbank.org/ext/en/what-we-do/project-procurement/framework), World Bank
- [EBRD library of procurement forms](https://www.ebrd.com/home/work-with-us/project-procurement/library-of-forms-and-alternative-options.html), European Bank for Reconstruction and Development


## Related articles

- [Does your company meet the tender's financial threshold?](https://zephior.com/insights/assess-financial-capacity-thresholds)
- [Can this consortium satisfy the tender rules?](https://zephior.com/insights/assess-consortium-eligibility-before-bidding)
- [Should you bid if a required certificate is not ready?](https://zephior.com/insights/decide-whether-to-bid-with-missing-certification)
- [How to verify a subcontractor meets tender conditions](https://zephior.com/insights/verify-subcontractor-tender-compliance)