---
title: "Find relevant tenders behind vague notice titles"
description: "Decide whether a weak-title tender candidate deserves deeper review by tracing official scope evidence into a cited notice-to-scope relevance note."
canonical: "https://zephior.com/insights/find-opportunities-hidden-behind-vague-notice-titles"
last-updated: 2026-09-03
---

# Find relevant tenders behind vague notice titles

> Decide whether a weak-title tender candidate deserves deeper review by tracing official scope evidence into a cited notice-to-scope relevance note.

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

## Definition

A notice-to-scope relevance note is a dated record that connects one retrieved procurement candidate to an approved supplier capability using the current official notice and any safely accessible public attachments. It preserves the notice, procedure and lot identifiers; the exact title; title failure mode; fields inspected; positive and negative scope anchors; source language and version; missing evidence; and one controlled result: relevant, mixed, adjacent, irrelevant or unresolved. The note answers whether the candidate deserves the next level of review. It does not decide eligibility, capacity, commercial attractiveness or whether the supplier should bid.

## Problem

A notice titled “Professional services,” “Project Cedar,” “Package 6” or “Managed service framework” can conceal work that exactly matches a supplier. A precise-looking title can mislead too. “Network modernisation” may buy civil works, managed operations and hardware while mentioning analytics only as background. Search result cards often shorten text, flatten procedure and lot scope, or display a translated title without the surrounding description. Classification codes and buyer names add clues, but neither proves the deliverable. The reviewer therefore faces two costly errors: discard a relevant opportunity because its title says too little, or advance a false lead because the title sounds right.

## Point of view

Treat the title as a routing clue and preserve it unchanged. Resolve the latest official notice, then read scope in a deliberate order: procedure description, group or lot description, classifications, quantities and place, public attachments, and any change notice that alters those materials. Compare passages with a bounded capability brief, not with a product name or an embedding score. Record evidence both for and against relevance. A candidate is relevant only when an official field or document identifies a deliverable, object or outcome inside the supplier boundary. Missing or conflicting evidence produces an unresolved result. An agent may retrieve public material, extract anchors and draft the note, but it must stop before login, buyer contact, restricted-document access or a bid decision.

## Use the title to open the record, not to decide relevance

Begin with two fixed objects: one procurement candidate and one approved capability brief. The capability brief should state a deliverable, the object or process it affects, the buyer outcome, delivery conditions, available proof and explicit exclusions. “Data services” is no better as a capability than “professional services” is as a notice title. “Convert paper planning files into indexed digital records, validate metadata and return an exception log” gives the review something testable.

Copy the title exactly as published, including language, acronym and punctuation. Do not repair it in the evidence field. Add a separate title diagnostic that explains why it may be a poor summary. A title can be broad because the buyer is naming an entire programme, terse because it repeats an internal package code, or precise but misleading because the named technology is only one component of a wider obligation. The diagnostic directs inspection. It never supplies missing scope.

TED’s eForms model makes the distinction concrete. Title and description are separate business terms, and both may occur at procedure, group of lots, part and lot level. The TED search field list also exposes separate procedure and lot fields for titles, descriptions and classifications. A search interface that shows one title has compressed a record with several possible scope layers. Preserve that compression as a known limitation of the candidate view.

**Title diagnostics that trigger deeper inspection**

| Observed title pattern | What it may conceal | First field to inspect |
| --- | --- | --- |
| Generic umbrella, such as professional services | Several unrelated deliverables or lots | Procedure and lot descriptions |
| Project or programme name | An operating problem known only inside the buyer | Purpose description and public scope document |
| Package number or internal acronym | A coded workstream or planned part | Part, lot and internal identifier fields |
| Framework or transformation label | Multiple service families under one commercial vehicle | Lot structure and procurement documents |
| Familiar specialist term | Background technology rather than a purchased deliverable | Description, items and required outputs |
| Translated or clipped search-card title | Dropped qualifiers, location or lot wording | Official-language notice at the source |

## Read scope through a fixed evidence ladder

Resolve the current official record before interpreting it. Capture the portal, notice identifier, procedure identifier, version, publication time, source language and public URL. If a change notice exists, follow its reference to the changed notice and work from the current consolidated text. TED’s change-notice specification permits changes to notice sections and procurement documents, so an earlier description or attachment set cannot be assumed current.

Next, move from broad to specific. Read the procedure purpose and description, then enumerate groups, parts and lots. At each level, collect the title and description without moving a statement to another level. Continue with main and additional classifications, quantities, contract nature and place of performance. These structured fields can confirm the object or location of the purchase, but their meaning depends on the accompanying text. A CPV code that names software does not establish which software task the buyer will award.

Open public attachments only through links exposed by the official record or buyer. Record the document title, URL, date, version, language and the section or page inspected. Technical specifications, schedules and statements of work often settle whether an attractive phrase is a deliverable or context. If the file requires registration, agreement to terms, credentials or a private request, stop and record the access state. Do not describe unread material from its filename.

The Open Contracting Data Standard provides a useful cross-portal mental model. It distinguishes a tender headline from its description, item descriptions, classifications, lots and documents. The SAM.gov opportunities API similarly returns the opportunity title separately from a link to the description, classifications, place of performance and resource links. Field names vary by jurisdiction, but the research question remains stable: which current official field carries the scope claim?

**Evidence ladder for a weak-title candidate**

| Order | Evidence layer | Question | Recorded state |
| --- | --- | --- | --- |
| 1 | Current official notice | Which identifier and version are authoritative for this review? | Checked or unresolved |
| 2 | Procedure purpose and description | What is the buyer trying to procure at the broadest level? | Present, absent or conflicting |
| 3 | Group, part and lot text | Where is the work divided, and which level carries this statement? | Enumerated or not provided |
| 4 | Items, codes, quantity and place | Which structured facts support or limit the apparent scope? | Supporting, conflicting or silent |
| 5 | Public procurement documents | Which deliverables, objects and boundaries appear in readable source files? | Read, absent, inaccessible or not applicable |
| 6 | Change lineage | Did a correction alter the notice or documents used in the note? | Current, changed or unresolved |

## Turn passages into scope anchors, including evidence against the match

A scope anchor is a small, attributable unit of evidence. It contains the source level, field or document location, exact passage or structured value, source language, a restrained interpretation and the capability predicate it supports or contradicts. The interpretation must be reviewable. “The notice mentions records” is weak. “Lot 2 requires scanning paper case files, creating indexed PDF files and returning an exception report; these three outputs match the approved conversion capability” explains the link without claiming that every lot or condition fits.

Extract positive evidence and counterevidence in the same pass. A procedure description may mention document conversion while the only relevant lot bundles conversion with twenty years of physical archive storage, which the capability brief excludes. Another notice may use the right code but state that the contract is solely for scanner hardware. Those passages deserve the same prominence as the matching words. Relevance depends on what the buyer will purchase as a coherent obligation, not on the number of semantic similarities.

Separate quoted evidence from analyst interpretation. Preserve the official phrase in its source language, then add a plain explanation. If a translated rendering is needed for review, label it as a translation and keep the original beside it. Do not silently replace a buyer term with supplier vocabulary. Acronyms, internal programme names and technical abbreviations remain unresolved until the notice defines them or another official public source does.

Never infer scope from buyer identity. A transport authority can buy catering, insurance, construction or software. Never infer it from a filename either. “Digital strategy.pdf” might be background material. The source has to state a deliverable, object, outcome or binding boundary that bears on the capability test.

**Minimum record for one scope anchor**

| Field | Required content | Failure to avoid |
| --- | --- | --- |
| Source level | Procedure, group, part, lot, item or document | Applying broad text to a specific lot |
| Locator | Field name, section, page or stable fragment | An untraceable summary |
| Evidence | Exact short passage or structured value | A keyword without context |
| Language | Official source language and any labelled review translation | Treating a translation as controlling text |
| Interpretation | What the evidence supports and what it does not establish | Turning an observation into a bid claim |
| Capability predicate | Deliverable, object, outcome, boundary or exclusion | Comparing against a product name |
| Polarity | Supports, contradicts or limits relevance | Collecting only confirmatory evidence |

## Five evidence states are more useful than a mysterious relevance score

Assign the result only after recording source coverage and counterevidence. Relevant means current official evidence identifies a deliverable inside the approved capability boundary and no reviewed scope fact contradicts that narrow conclusion. It does not mean the supplier is eligible, has capacity or should bid. Those questions need the documents and a separate qualification decision.

Mixed is appropriate when relevant work is present but bundled with material work outside the capability, split ambiguously across lots, or accompanied by a conflicting scope statement. Adjacent means the buyer problem is related but the purchased deliverable is different. A supplier that provides archive digitisation may find a records-management advisory contract adjacent: the domain overlaps, but the buyer is purchasing advice rather than conversion.

Irrelevant requires affirmative evidence. The reviewed description or document places the purchase outside the capability, and the reason is recorded. Unresolved is not a weak version of relevant. It means a named gap prevents the evidence test, such as a missing lot description, an inaccessible specification, conflicting versions or an undefined acronym. Keep that state until the missing fact is available or the candidate expires.

A numerical similarity score can help order a review queue, but it cannot replace these states. If a score is retained, publish its inputs and use it only as a retrieval aid. The decision must still identify the decisive evidence, counterevidence and missing facts in words.

**Controlled relevance states and next actions**

| State | Evidence test | Next safe action |
| --- | --- | --- |
| Relevant | Explicit bought deliverable fits the capability boundary; no reviewed scope contradiction | Inspect the named lot and begin full qualification |
| Mixed | Relevant work exists with material bundled duties, cross-level conflict or uncertain separability | Resolve lot structure or inspect the named scope document |
| Adjacent | The same domain or outcome appears, but the purchased work is outside the capability | Retain as market context or use it to refine discovery |
| Irrelevant | Official evidence positively places the deliverable outside the capability | Exclude with the cited reason and review date |
| Unresolved | A named source, version, definition or scope fact is missing or conflicting | Obtain that fact or schedule a recheck without guessing |

## A procedure can be relevant while a candidate lot is not

Write the object of the decision into the note. If the search result represents an entire procedure, the result can say that the procedure contains potentially relevant scope and name the lot or part that supports it. It cannot say every lot is relevant. If the candidate already represents one lot, procedure-level language is context until lot text or a linked document assigns the deliverable to that lot.

TED’s current information model places title and description at several levels and gives lots their own place, contract nature and requirements. OCDS uses related lot identifiers so items and documents can be attached to a particular lot; without a related lot, information may apply to the whole tender. These structures prevent a common analytical shortcut: copying one attractive sentence from the procedure into every child lot.

When a broad procedure contains a promising lot, stop the AN-019 task after naming that lot and citing the anchor. The next task is lot-level relevance inspection, which must bring down shared conditions and test the whole lot boundary. When the notice does not expose lots clearly, use mixed or unresolved. Do not invent a commercial division from headings, file folders or repeated codes.

Attachments need the same discipline. A scope schedule linked at procedure level may govern all lots, or only define common terms. A lot-specific pricing sheet may reveal purchased items but not the whole obligation. Record the document relationship stated by the portal or document itself. If that relationship is unclear, describe the evidence without promoting it to a lot fact.

**How to keep evidence at the right procurement level**

| Evidence found at | Permitted conclusion | Conclusion that needs more proof |
| --- | --- | --- |
| Procedure description | The procedure includes or discusses the capability | A named lot purchases that deliverable |
| Group of lots | The statement applies to the identified group | Every lot in the group has identical scope |
| Lot description | The lot expressly includes the stated work | The supplier can deliver every lot obligation |
| Classification code | The buyer classified the record in that category | The exact specialist deliverable is purchased |
| Public attachment | The document contains the cited scope statement | The statement governs a lot unless the relationship is shown |
| Search result snippet | The phrase is a lead to inspect | Any relevance conclusion |

## Publish a note that another reviewer can reproduce

The final note should be compact enough to review quickly and complete enough to rerun. Begin with identity and provenance: portal, official URL, notice ID, procedure ID, candidate lot or part, version, publication time, retrieval time and source language. Preserve the exact title and the separate title diagnostic. Link the approved capability brief by identifier and version so later edits to the brief do not silently change the old decision.

Add a coverage ledger. Each expected layer receives one explicit value: checked with a source, absent in the official record, inaccessible with the access condition, not applicable, or unresolved. Blank does not mean absent. Then list positive anchors, counterevidence and missing facts. Each row contains its level, locator, evidence, interpretation and capability predicate. Finish with the controlled state, decision reason, narrow next action, owner and refresh trigger.

Consider an illustrative candidate titled “Programme Northstar, package four.” The current procedure description says the programme replaces an estate-wide records platform. Lot 4 says the supplier will scan legacy property files, create indexed records and return an exception register. A public schedule adds permanent off-site storage, which the capability brief excludes, and the notice does not show whether bidders can price scanning separately. The defensible result is mixed, not relevant. The note cites the matching outputs, the bundled storage duty and the missing separability fact, then routes the candidate to whole-lot review.

That example is useful because it can be disproved. A reviewer can open the same sources, inspect the cited locations and challenge the interpretation. “Eighty-seven per cent match” offers no comparable route unless every input and rule is exposed. Prefer a short reason that names the evidence and limit: “Lot 4 buys the three conversion outputs, but storage appears inseparable in schedule B; separability is unresolved.”

**Notice-to-scope relevance note**

| Block | Fields to publish | Why an agent needs them |
| --- | --- | --- |
| Identity | Portal, official URL, notice and procedure IDs, lot or part | Refinds the same candidate without title matching |
| Version | Notice version, publication time, retrieval time, change lineage | Detects stale evidence and schedules refresh |
| Title | Exact source title, language, diagnostic | Separates observed text from interpretation |
| Comparison | Capability brief ID, version, predicates and exclusions | Makes the relevance boundary stable |
| Coverage | State of every notice, hierarchy, field and document layer | Distinguishes absence from failed access |
| Anchors | Positive evidence, counterevidence, locators and interpretation | Supports citation and independent review |
| Result | One controlled state, reason and missing facts | Prevents a ranking score from becoming a conclusion |
| Action | Next task, owner, authority boundary and refresh trigger | Keeps discovery separate from external or bid action |

## Let agents inspect public evidence, then make them stop at the boundary

This task suits an agent because the inputs, source order and outputs can be made explicit. Give the agent one candidate, one approved capability brief and a permitted public-source list. It may resolve identifiers, follow official public links, enumerate lots, extract exact fields, compare scope predicates and draft the relevance note. Require citations for every non-trivial scope statement and an explicit null state for each missing field.

The agent must not sign in, accept portal terms, request documents, contact the buyer, bypass access controls or infer the contents of an unread file. It also cannot convert relevance into eligibility or a bid recommendation. Stop conditions should be machine-visible: no official notice found, competing current versions, an undefined acronym that controls the scope, a required attachment behind access, conflicting procedure and lot text, or evidence that contains personal or restricted information.

Give the output a stable schema rather than a free-form confidence paragraph. Controlled states, source locators, timestamps and missing-fact fields make the note usable by another agent. Natural-language reasoning still matters, but it sits beside the evidence rather than hiding it. A downstream agent can search only relevant and mixed notes, reopen unresolved ones when a document appears, and exclude irrelevant records using the stored reason.

Refresh on evidence change, not an arbitrary rewrite cycle. Reopen the note when the official notice version changes, the portal marks procurement documents as changed, a missing attachment becomes public, the lot structure changes or the approved capability brief receives a new version. Preserve the old result and time. That history shows why a candidate moved from unresolved to mixed or relevant.

**Agent authority for weak-title review**

| Agent may | Required output | Agent must stop when |
| --- | --- | --- |
| Retrieve an official public notice | URL, IDs, version, language and retrieval time | No authoritative public record can be resolved |
| Read public fields and attachments | Coverage state and stable locators | Access needs credentials, consent or a private request |
| Enumerate procedure, group, part and lot levels | Evidence kept at its source level | Published hierarchy is contradictory or incomplete |
| Compare evidence with the approved brief | Positive anchors, counterevidence and missing facts | Acronym, translation or boundary needs expert interpretation |
| Draft a controlled relevance state | Rule-based result and narrow next action | The requested conclusion concerns eligibility, capacity or bid strategy |
| Monitor public change signals | New version event and preserved prior state | The next act would contact the buyer or alter external state |

## Useful outcomes

- The original title remains visible as an observation rather than becoming a relevance verdict.
- Procedure, group, part and lot scope are kept at their published levels.
- Every relevance claim points to an official field, passage or public attachment.
- Positive scope anchors are weighed alongside exclusions and counterevidence.
- Relevant, mixed, adjacent, irrelevant and unresolved candidates follow different next actions.
- Missing descriptions, inaccessible files and version conflicts remain explicit.
- Another person or agent can reproduce the decision from the recorded source and check time.
- The note hands a promising candidate to lot inspection or qualification without claiming bid readiness.

## Workflow

1. **Fix the comparison boundary.** Attach one approved capability brief to one candidate notice. Record the deliverable, object, outcome, operating boundary and exclusions before reading the title as evidence.
2. **Resolve the current notice.** Capture the official URL, notice and procedure identifiers, version, publication time, language and any change lineage. Do not rely on a search card or aggregator copy.
3. **Diagnose the title.** Keep the exact title and label why it may hide scope, such as an umbrella term, project name, internal code, framework label, stale wording or truncation.
4. **Traverse the scope fields.** Read the procedure purpose, lots or parts, classifications, quantities, place and public attachments in order. Mark every field as checked, absent, inaccessible or not applicable.
5. **Extract both sides of the case.** Capture exact scope anchors, explain their relation to the capability and record counterevidence, bundled duties and explicit exclusions with the same source discipline.
6. **Assign a controlled result.** Choose relevant, mixed, adjacent, irrelevant or unresolved from stated evidence rules. State the missing fact that prevents a firmer result rather than inventing a score.
7. **Publish the next safe action.** Return the cited note with a check time and route it to lot review, qualification, query refinement, exclusion or source resolution. External action still requires human authority.

## Key decisions

- Which approved capability brief is the candidate being compared with?
- Is this the current official notice and, if changed, which version contains the consolidated text?
- Why is the title weak: generic, coded, bundled, stale, translated, truncated or apparently precise but misleading?
- At which level does each statement apply: procedure, group, part, lot, item or attachment?
- Which exact official words identify the bought deliverable, affected object or required outcome?
- Which passage excludes the capability or makes it inseparable from work outside the supplier boundary?
- Are public attachments necessary to settle relevance, and were they safely accessible?
- Does the evidence justify relevant, mixed, adjacent, irrelevant or unresolved?
- What is the narrowest permitted next action, and what new fact would change it?

## Risks

- A generic title may cause a relevant candidate to be discarded before its description is read.
- A familiar service word in the title may refer only to background context or an incidental task.
- Procedure-wide text may be attributed to a lot that does not buy the capability.
- A classification code may describe the main procurement category but omit a specialist work package.
- A filename may look relevant while the attachment contains a different scope or version.
- A translated or truncated search result may change the apparent emphasis of the official wording.
- A change notice may supersede the description or signal that procurement documents changed.
- Restricted or failed document access may be silently treated as absence of relevant scope.
- An opaque similarity score may conceal missing evidence, exclusions or contradictory passages.
- A relevance result may be mistaken for proof of eligibility, capacity or a recommendation to bid.

## Metrics

- weak-title candidates with a current official notice and retrieval time
- notes that identify the level of every cited scope statement
- positive anchors paired with source field, language and reviewed interpretation
- candidates with counterevidence and exclusions actively checked
- fields recorded as absent, inaccessible or not applicable instead of left blank
- unresolved results preserved until the named missing evidence is obtained
- relevant candidates recovered after their titles initially looked irrelevant
- false leads excluded from a reproducible official-source reason
- notes refreshed after a notice or public document change

## Frequently asked questions

### Should we reject a tender when its title is too vague?

No. Treat the title as a reason to inspect the current official description, hierarchy and public documents. Reject only when official scope evidence places the purchase outside the approved capability. If the necessary evidence is unavailable, use unresolved.

### Is a matching procurement classification code enough to call the tender relevant?

No. A code supports retrieval and may identify the main or an additional category. Relevance still needs text or item evidence that identifies the purchased deliverable and its boundary.

### Must every attachment be read before assigning a result?

Read the public documents needed to settle the scope test. If the notice already gives explicit, uncontradicted scope, other documents can remain outside this narrow review and be named for qualification. If a missing or inaccessible attachment could reverse the result, the state is unresolved or mixed.

### Can semantic search or an embedding score decide relevance?

It can prioritize candidates for inspection. It cannot show whether a phrase applies to the procedure or lot, whether work is bundled, or which source version controls. The final state needs cited official evidence and counterevidence.

### What if the procedure is relevant but the retrieved lot is not?

State the decision object explicitly. Mark the retrieved lot irrelevant if its own scope is outside the capability, while recording that another named lot may be relevant. Do not transfer procedure-level language to the wrong lot.

### What if the translated title and official-language description suggest different scope?

Preserve both, identify the official source language and base the anchor on the controlling source text. Label any working translation. If the difference affects the deliverable or boundary and qualified review is unavailable, mark the result unresolved.

### Does relevant mean we should bid?

No. It means the current reviewed evidence contains scope inside the approved capability boundary. Eligibility, capacity, economics, deadlines, risk and strategic fit belong to later qualification.

### What can an AI agent safely do with the relevance note?

It can retrieve public evidence, populate locators, compare approved predicates, draft the controlled state, monitor changes and route the note. It should stop before restricted access, buyer contact, external submission or any conclusion that commits the supplier.


## Primary sources

- [eForms BT-21: Title](https://docs.ted.europa.eu/eforms/latest/reference/business-terms/BT-21.html), Publications Office of the European Union
- [eForms BT-24: Description](https://docs.ted.europa.eu/eforms/latest/reference/business-terms/BT-24.html), Publications Office of the European Union
- [eForms business terms](https://docs.ted.europa.eu/eforms/latest/reference/business-terms/index.html), Publications Office of the European Union
- [Procedure, group of lots, lot and part information](https://docs.ted.europa.eu/eforms/latest/schema/procedure-lot-part-information.html), Publications Office of the European Union
- [TED website search fields](https://docs.ted.europa.eu/ODS/latest/reuse/field-list.html), Publications Office of the European Union
- [TED Search API](https://docs.ted.europa.eu/api/latest/search.html), Publications Office of the European Union
- [eForms change notices](https://docs.ted.europa.eu/eforms/latest/schema/change-notice.html), Publications Office of the European Union
- [Open Contracting Data Standard 1.1.5 release reference](https://standard.open-contracting.org/latest/en/schema/reference/), Open Contracting Partnership
- [SAM.gov Get Opportunities Public API](https://open.gsa.gov/api/get-opportunities-public-api/), US General Services Administration


## Related articles

- [How to find tenders when buyers describe outcomes](https://zephior.com/insights/find-tenders-by-business-capability)
- [How to find requirements hidden in RFP annexes](https://zephior.com/insights/find-requirements-hidden-in-rfp-annexes)
- [How to find public tenders your company can actually bid](https://zephior.com/insights/how-to-find-public-tenders)
- [How to find the one tender lot that fits a narrow capability](https://zephior.com/insights/find-a-tender-lot-that-matches-a-narrow-capability)