An evidence scope check is a claim-to-source comparison performed before a fact, example, report or record is used in a proposal. It writes the proposed statement as a bounded proposition, records what the evidence directly covers, and compares legal entity, organizational unit, delivery role, service or product, version or configuration, geography, customer or asset population, scale, period and operating state one dimension at a time. Each dimension is marked exact, evidence narrower, evidence broader, different, unknown or not applicable, with a source passage and reviewer. A difference may be resolved only by an explicit, evidenced relationship such as legal succession, committed reliance on another entity, controlled product lineage or a valid disaggregation. The result permits the original wording, narrower wording, a disclosed relevance statement, further review or removal. It does not decide whether the source is generally prestigious, whether a statistic is correctly calculated, whether a certificate is valid, or whether old evidence remains current.
A county council asks for evidence that the bidder has delivered an offline building-inspection workflow on a comparable education estate. The fictional bidder, Harbour Civic Systems Ltd, plans to say that it has already delivered the offered service across UK schools. Its evidence folder contains a polished Harbour case study, an acceptance letter and product screenshots. The acceptance letter names Harbour Field Services Inc in Canada, the estate consisted of 41 commercial warehouses in Ontario, a local surveying company performed the site work, and the screenshots show FieldTrack 5 rather than the CivicInspect 8 configuration offered for 68 schools. Every document is authentic. Together they still do not cover the sentence the proposal team wants to write.
Treat the claim and the evidence as two independently bounded objects. Extract coverage from each before deciding whether they match. A shared brand, parent company, product family, customer sector or large total is not a bridge. A broader dataset may conceal the subgroup named in the claim; a narrower example cannot silently represent a larger service. Record exact differences instead of averaging them into a relevance score. Use an explicit relationship only when the tender permits it, the relationship is evidenced and the resulting wording says no more than that relationship proves. If one material dimension remains different or unknown, narrow the statement, describe the evidence as adjacent rather than direct, seek the missing source or remove the claim.
Direct answer
Compare the claim and the source as two bounded objects
A source supports a proposal statement only inside the part of reality it actually describes. Start by writing the statement as actor, predicate, object, conditions, place and time. Then describe the evidence without borrowing words from the statement. If the claim says the bidding company operated an offline inspection service for UK schools, a document about an affiliate supplying software to Canadian warehouse surveyors has several independent differences. An authentic document can still be irrelevant to a particular sentence.
The comparison needs named dimensions rather than one overall feeling of similarity. Entity asks whose experience or result is recorded. Delivery role asks who designed, supplied, operated or accepted the work. Service and product ask what was delivered, in which version and configuration. Geography, population and scale capture operating conditions. Period and state separate historic, current, pilot, production and planned capability. Add another dimension only when it can alter the conclusion.
Record the result at the dimension level. Exact means the evidence directly covers the claim value. Evidence narrower and evidence broader are differences, not weaker versions of exact. Different means both values are known and conflict. Unknown means the evidence does not let the reviewer decide. Not applicable is reserved for a dimension the claim does not contain. A blank cell is not a match.
| Record part | Required content | Control |
|---|---|---|
| Claim | Exact proposed wording, buyer source, response location and purpose | Freeze before inspecting fit |
| Evidence | Native object, version, producer, locator and direct statements | Do not rely on filename or summary alone |
| Dimensions | Claim value, evidence value, state, source passage and reviewer | Decide each material axis separately |
| Bridge | Named relationship, proof, authority, permitted use and limit | Never infer from branding or convenience |
| Disposition | Approved wording, replacement, removal, owner and reopen event | Keep release text inside proven coverage |
Claim boundary
Freeze what the proposal sentence actually says
Scope cannot be checked against a topic such as “relevant experience.” Capture the exact proposed sentence and its function. A condition of participation, scored example, method explanation, contractual commitment and contextual illustration place different weight on the same source. Record whether the actor is the legal bidder, an associated supplier, a named delivery party, a person, a product or the combined solution. Words such as all, across, current, proven, our and already expand scope and deserve explicit fields.
Read the buyer’s requirement before setting the dimensions. Section 22 of the UK Procurement Act separates supplier capacity and technical ability from the tender assessment under section 23. Current Cabinet Office guidance likewise says conditions of participation assess the supplier separately from award criteria. EU, German and French rules define their own evidence and reliance arrangements. The bidder should not change the buyer’s requested subject simply because a nearby source is easier to find.
Turn the sentence into a claim-side record. For “Harbour Civic Systems Ltd has delivered the offered offline inspection service across comparable UK school estates,” record the company number, bidder role, service boundary, offered edition, offline configuration, field-work responsibility, education-estate population, UK geography, historic production state and relevant period. The review can later shorten the sentence, but it must not silently move those fields after seeing the evidence.
Source boundary
Read the evidence object without borrowing from its label
Identify the native object before extracting scope. A case-study page, acceptance letter, operating report and slide may describe different slices of the same project. Preserve the issuer, producer, addressee, version, date, source system and any referenced contract. If a slide derives its number from a report, keep the derivation visible. The W3C provenance model distinguishes an entity, the activity that generated or used it and the responsible party; that distinction prevents a copied statement from acquiring a new owner.
Use what the object says directly. A logo is not a legal-entity statement. A product screenshot does not establish who operated the service. A customer quotation may describe satisfaction without defining the delivered components. An acceptance letter may prove acceptance for a named contract but not every claim later added to its case study. Record absent fields as unknown instead of filling them from internal memory or another document.
If several sources are needed, preserve their individual scopes and the relationship among them. A registry record can connect a legal name to a company number; it does not attribute an affiliate’s contract performance to the bidder. A controlled release record can connect two product versions; it does not establish the customer’s configuration. A service report can identify an operating population; it does not create permission to name that customer. Each object should do only the work its content supports.
Entity and role
Prove the entity and delivery-role connection
Begin with durable identifiers. Companies House can confirm a UK registered name, number, type and status, while equivalent official registers serve other jurisdictions. That establishes identity, not ownership of every branded case study. Capture the contract party, performing entity, relevant division and any predecessor separately. A merger, transfer or name change needs its effective record. Common ownership on its own does not move experience between companies.
Procurement rules sometimes allow reliance on another entity, but the conditions matter. UK section 22 addresses associated suppliers. Directive 2014/24/EU Article 63, German VgV section 47 and French Article R2143-12 provide routes for relying on other operators and require proof that the necessary resources will be available; professional experience can depend on the other entity performing the relevant work. These provisions do not make all group evidence automatically the bidder’s own. Apply only the live tender’s permitted arrangement and wording.
Separate role from entity. The reference may show that one party licensed software, another configured it, a third performed inspections and the customer operated the help desk. The proposed contract may allocate those acts differently. Attribute each evidenced act to its performer, then compare that role with the delivery model in the offer. If the affiliate is committed to deliver the same component and the arrangement is accepted, describe that contribution precisely. Do not convert supporting-product experience into prime-service experience.
| Proposed bridge | Evidence needed | What it cannot prove alone |
|---|---|---|
| Name change or succession | Official identity record plus effective transfer or continuity record | Untransferred contracts or capabilities |
| Parent or affiliate | Exact corporate relationship and tender-permitted reliance arrangement | That the bidder performed the earlier work |
| Consortium or subcontractor | Named role, commitment and resources for this offer | Experience outside the component that party will deliver |
| Predecessor or acquired team | Relevant people, assets, records and continuity evidence | Whole-company performance after acquisition |
| Shared brand | No bridge by itself | Legal identity, delivery role or resource availability |
Offer match
Test service, product, version and operating model
Write the offered capability at component level. Product family names hide modules, hosting patterns, integrations, data boundaries, human operations and customer responsibilities. A reference for a reporting module may be relevant to reporting while saying nothing about mobile capture. A software licence is not evidence that the supplier ran field operations. A pilot proves a bounded test, not a production service, unless the claim says pilot.
Version lineage needs controlled facts: the earlier edition, the offered edition, relevant feature or process, material changes, test or release evidence and accountable owner. “Same platform” is too loose when the architecture, workflow, measurement or delivery responsibility changed. A bridge may show that a specific capability continued from FieldTrack 5 into CivicInspect 8. It cannot make the entire earlier service identical to the offer.
Configuration matters even within one version. Record hosting region, enabled modules, integration pattern, device class, accessibility mode, service hours and division of operational responsibilities when they affect the statement. The source may directly support one component and leave others unknown. Split the proposal sentence rather than forcing an all-or-nothing verdict across the combined solution.
Operating context
Treat geography, population, scale and period as separate axes
Geography is more than a country label. Regulation, language, climate, network coverage, labour model, public-estate access and customer governance can change whether an example is comparable. Record only the conditions that matter to the claim. A Canadian warehouse project can still inform offline synchronization, but it does not establish UK school safeguarding, estate access or the complete local operating model.
A larger number is not automatically stronger. Evidence for 10,000 mixed commercial sites may be broader than a claim about 68 schools, yet the aggregate may contain no school at all. Evidence from twelve specialist sites may be narrower in scale while closer in operating complexity. Preserve population definition, inclusions, exclusions, distribution and unit of analysis. Ask for a valid subgroup before using an aggregate to describe that subgroup.
Period scope asks whether the record covers the time expressed by the sentence. It is distinct from deciding whether the evidence is too old. A report covering January through June does not support “throughout the last calendar year.” A source about a planned configuration does not support “currently operating.” Mark historic, current, pilot, test, production, planned and retired states explicitly. Send age and continuing validity to their own review after the period match is known.
| State | Meaning | Default treatment |
|---|---|---|
| Exact | Source directly covers the claim value | Continue to the other evidence checks |
| Evidence narrower | Source covers only part of the claimed range or population | Narrow the wording or obtain extension evidence |
| Evidence broader | Source combines the claim population with other cases | Obtain a valid subgroup or avoid the subgroup claim |
| Different | Known source value conflicts with the claim value | Remove, replace or rewrite the proposition |
| Unknown | The object does not reveal the needed value | Request the missing source or leave unsupported |
| Not applicable | The dimension does not form part of this proposition | Record the reason and do not score it |
Worked case
Rebuild the school-inspection statement from the actual source
The team freezes the sentence and opens the three original objects. Companies House confirms Harbour Civic Systems Ltd as the bidder. The Canadian acceptance letter names Harbour Field Services Inc and a contract for warehouse inspection analytics. The delivery schedule attributes on-site surveys to Maple Survey Co. Product records show that offline capture exists in both editions, but CivicInspect 8 replaced the synchronization service and uses a different mobile security model. No source places the bidder in a UK school deployment.
The dimension record now has evidence-different for legal entity, geography, estate type, product edition and delivery role. Population is evidence-narrower in site count and different in asset context. Historic production state is exact only for the Canadian service. A controlled release note can bridge one narrow product lineage fact. Corporate records show the group relationship, but the tender file contains no approved reliance arrangement and the Canadian affiliate has no delivery role in the offer.
The original statement is removed. If useful to the scored answer and approved, the team may say that the offered workflow’s offline-capture design descends from a feature used in a Canadian commercial-estate deployment, then state separately how the current edition and UK school delivery will be validated. It may not say the bidder has already delivered the offered service to UK schools. The case study remains adjacent product evidence, not direct supplier-experience evidence.
| Dimension | Claim value | Evidence value | Decision |
|---|---|---|---|
| Entity | Harbour Civic Systems Ltd | Harbour Field Services Inc | Different; group link does not transfer performance |
| Service role | Complete software and field-inspection service | Affiliate analytics; local surveyor performed field work | Different; do not claim complete delivery |
| Product | CivicInspect 8 offered configuration | FieldTrack 5 with earlier synchronization service | Narrow lineage fact only after change review |
| Context | 68 UK schools | 41 Ontario commercial warehouses | Geography, population and operating conditions differ |
| Disposition | Prior delivery of offered UK school service | No direct support | Remove; optionally use disclosed adjacent product evidence |
Disposition
Record the disposition and reopen when either side changes
Use a small set of final states. `direct_support` means every material dimension is exact. `support_for_narrower_wording` links the source to an approved reduced sentence. `adjacent_relevance` preserves a disclosed difference that the buyer’s question allows the team to explain. `scope_mismatch` means a known difference defeats the proposition. `scope_unknown` means missing source fields prevent a decision. `specialist_review_required` routes a defined issue without pretending it passed.
Do not add dimension scores. Five exact fields cannot cancel the wrong legal entity or delivery role when the sentence attributes performance to the bidder. A valid bridge records the relationship, source, effective date, tender permission, participating party, reviewer and exact wording limit. It supplements the dimension decision; it does not rewrite the original evidence. Statistical accuracy, source hierarchy, certificate validity, age and source conflicts remain separate reviews.
Close by storing the final sentence identifier, evidence version, dimension table, accepted bridge, reviewer, approver and allowed use in text, table, visual or attachment. Reopen after a source replacement, expanded sentence, different bidder configuration, partner change, product release, new geography, revised buyer requirement or evidence correction. The proposal must continue to point to the decision that covers the words it actually uses.
What good looks like
Useful outcomes from verify scope of proposal evidence
- Every review pairs one frozen buyer-facing proposition with one identified evidence object and version.
- Claim scope and evidence scope are recorded separately before comparison.
- Legal entity, organizational unit and delivery role are not inferred from a shared trading name.
- Product, service, version, environment and operating model differences remain visible.
- Geography, population, scale, period and operating state receive separate decisions.
- Broader and narrower evidence are not treated as exact without the needed subgroup or extension proof.
- Every accepted bridge names the relationship, supporting object, tender permission and wording limit.
- The final proposal wording stays within the dimensions the reviewed source actually covers.
- Changes to the claim, source, bidder structure or offered service reopen the scope check.
Operating model
How to run the work
- 01
Freeze the proposition
Record the exact sentence under consideration, its buyer source, answer location, purpose and current approval state.
- 02
Identify the evidence object
Preserve the native object, version, issuer or producer, source locator and any derivation from an earlier record.
- 03
Extract both scopes
Write claim coverage and direct evidence coverage independently across every dimension that can change the conclusion.
- 04
Compare each dimension
Mark exact, narrower, broader, different, unknown or not applicable and cite the decisive source passage.
- 05
Test proposed bridges
Require evidence and authority for succession, affiliate reliance, product lineage, role attribution or disaggregation.
- 06
Choose the treatment
Keep, narrow, describe as adjacent, replace, remove or route the claim without hiding the mismatch.
- 07
Approve exact wording
Link the reviewed source and scope decision to the final sentence, table, graphic or reference form.
- 08
Set the reopen rule
Repeat the check after any material change to the claim, evidence, offer, entity arrangement or buyer requirement.
Evaluation
Questions that change the decision
- What exact actor, capability, result or experience does the proposal ask the evaluator to believe?
- Is the claim about the bidder, a named affiliate, a consortium, a subcontractor, a product or the combined offer?
- Which organization and operating unit does the evidence directly describe?
- Who performed the work evidenced, and what role will that party perform in this contract?
- Do service, product, version, configuration and delivery model match the proposed offer?
- Do geography, legal context, environment, population and scale preserve the relevant conditions?
- Does the evidence cover the exact period or state expressed by the claim?
- Can a named difference be bridged by a current source and tender-permitted arrangement?
- What is the strongest sentence that remains true after every dimension is compared?
- Which change would invalidate the decision and require a new review?
Failure modes
Where teams lose control
A group logo makes an affiliate’s work appear to belong to the legal bidder.
A case study names a product family but omits the edition, configuration and delivery model.
The bidder supplied software on the reference while the proposed claim says it operated the complete service.
A global total is used to support a regional or customer-segment statement without disaggregated records.
A larger population is called more relevant even though it contains different users, assets or operating conditions.
A current offer is mapped to an old product through a roadmap slide rather than controlled change evidence.
Corporate ownership is mistaken for legal succession, committed resources or performance attribution.
Several partial sources are combined without proving that their populations and definitions align.
A numerical relevance score allows one hard mismatch to disappear inside several loose similarities.
The source is swapped or the sentence expands after approval without reopening the scope check.
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.
- open scope checks by response section, owner and review cutoff
- claim-to-evidence pairs with independently recorded coverage on every material dimension
- entity and delivery-role mismatches found before proposal approval
- product, version or configuration differences resolved with controlled evidence
- broader or narrower populations converted into bounded wording rather than assumed matches
- proposed bridges accepted, rejected or awaiting evidence by relationship type
- claims narrowed, relabelled as adjacent evidence, replaced or removed after scope review
- final statements linked to the reviewed evidence object and decision version
- scope decisions reopened after an entity, offer, source or requirement change
Questions
Common questions
What does evidence scope mean in an RFP response?
It is the entity, role, service, product, configuration, geography, population, scale, period and operating state that a source directly describes. Those values must be compared with the exact proposal statement.
Can a parent company case study support a subsidiary’s proposal?
Not automatically. Identify the performing entity, the bidder’s relationship to it, the live tender’s reliance rules, the resources or role committed to this contract and wording that attributes the experience accurately.
Does evidence from a larger project prove a smaller claim?
Only when the larger source contains the relevant subgroup or the conditions demonstrably transfer. An aggregate across unlike sites or users may reveal nothing about the narrower population.
Can several partial documents be combined to cover one claim?
Yes, if their identities, populations, definitions and relationships are explicit. Preserve each scope and the derivation. Do not splice unrelated fragments into an apparent whole.
Is an older product version relevant evidence?
It may support a specific continuing capability when controlled change records establish the lineage. It does not make the complete old and new services equivalent. Evidence age requires a separate review.
What if the evidence does not name the legal entity?
Mark entity scope unknown. Locate the contract, acceptance, registry, invoice or other authorized record that identifies the performing party before attributing the work.
Should I give every scope dimension a relevance score?
No. Record categorical states and consequences. One material mismatch can defeat a sentence even when several other dimensions are similar.
When is the evidence scope check complete?
When every material dimension has a source-backed state, any bridge is approved, and the decision is linked to exact final wording or a recorded removal. Define what changes will reopen it.
Sources
Primary references
- Procurement Act 2023, section 22 on conditions of participation and associated suppliers UK Legislation
- Cabinet Office guidance on conditions of participation, updated August 2026 Cabinet Office
- Cabinet Office guidance on assessing competitive tenders, updated August 2026 Cabinet Office
- Directive 2014/24/EU, including Articles 58, 60, 63 and 67 and Annex XII EUR-Lex
- German GWB section 122 on supplier suitability and evidence German Federal Ministry of Justice and Consumer Protection
- German VgV section 46 on technical and professional ability German Federal Ministry of Justice and Consumer Protection
- German VgV section 47 on relying on the capacities of other companies German Federal Ministry of Justice and Consumer Protection
- German VgV section 48 on requested suitability documents German Federal Ministry of Justice and Consumer Protection
- French Public Procurement Code Article R2143-11 on participation evidence Légifrance
- French Public Procurement Code Article R2143-12 on relying on other operators Légifrance
- French Public Procurement Code Article L2152-7 on objective award criteria Légifrance
- FAR 15.305 on relevance, context and source of past-performance information Acquisition.gov
- FAR 42.1502 on the entity, division or unit whose performance is evaluated Acquisition.gov
- World Bank guidance on evidence required for rated criteria World Bank
- W3C PROV-O recommendation on entities, activities, agents and derivation World Wide Web Consortium
- UK Government Data Quality Framework on fitness for intended use Government Data Quality Hub
- Companies House guidance on searching registered company information Companies House
- Joint Register Portal of the German federal states on official entity records German state justice administrations
- French public-service guidance on SIREN and SIRET entity identifiers Direction de l’information légale et administrative
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.