Read the record before you read a sales signal

PRACTICAL WORKFLOW · NORTH AMERICA AND EUROPE

A repeatable weekly procurement watch for cyber and IT vendors

Public notices are spread across systems, use different stages and codes, and change after publication. A useful watch is a small, repeatable research process: define what the supplier can deliver, collect a manageable set of candidate notices, verify the current source record, and preserve why each candidate did or did not merit attention. It is not a forecast of wins.

Start with the company, not a keyword. Write down two or three concrete service lines, the places where the company can perform work, the buyer types it can serve, and any known constraints such as language, certifications, clearance, registration, or contract size. Leave unknowns marked unknown; public notices do not establish the supplier's eligibility.

1. Build a focused search profile

Use a short list of precise phrases and relevant classification codes, plus a separate broader discovery search. For example, a managed detection provider might separate “managed detection and response” from broad searches for “cybersecurity” or “IT services.” Broad terms catch useful wording variants but also add noise. Keep separate profiles for materially different service lines or geographies so you can tell which one produced a useful result.

2. Set up alerts at the official portals

Use first-party alerts where available, then use Award Signal as a cross-source discovery and interpretation aid. SAM.gov allows signed-in users to save Contract Opportunities searches and enable notifications for new matches. TED supports saved searches and search alerts, including daily, weekly, fortnightly, or monthly frequencies. These free official tools should be part of the watch, because they can notify you directly and may surface changes before a weekly digest is checked. SAM.gov saved-search notifications · TED search alerts.

3. Triage without pretending a score is a prediction

For each candidate, record observable checks: service fit, geography, notice stage, listed deadline, buyer, and whether the notice changed. A simple “strong / uncertain / weak” label is enough if each label has a written reason. Do not turn keyword overlap, contract value, or an opaque numeric score into a probability of winning. Put missing facts in a separate “verify” field.

4. Open the latest official record before sharing it

Check the notice identifier, current version, amendments, closing date and time zone, lots, documents, buyer instructions, response portal, and any stated supplier requirements. A record in an open-tender feed or a recent search result can still be stale, changed, or incomplete. If a deadline is not visible in the summary, write “not confirmed” and inspect the notice; do not treat the blank as evidence that the bid is open.

5. Separate active notices from market context

Keep current solicitations in one list and planning notices, awards, modifications, and forecasts in another. Historical award activity can help explain a buyer's or supplier's context, but it does not itself invite a new bid or prove that the prime contractor is looking for partners. Link a historical award to an active opportunity only when the official records establish that relationship.

6. Keep a compact research log

For each item worth a second look, keep the official URL, source, notice or award identifier, date checked, stage, deadline, one-sentence fit rationale, unresolved questions, and next review date. Use “observed” for facts from the record and “inference” for your interpretation. This makes it possible to spot stale entries and explain why a lead was retained without reconstructing the search later.

7. Review the process after several weeks

Track how many candidates become verified current notices, how many fit the company's actual services and geography, and which searches repeatedly produce noise. Tighten or split the searches when they are unproductive. Keep a query that produces few results if those results are unusually well matched. The goal is a reliable review queue, not the largest possible record count.

UNITED STATES · HISTORICAL AWARD DATA

How to read U.S. award actions

USAspending's transaction view is a record of actions on federal prime awards. A transaction can be the initial award action or a later amendment or modification. That makes the date on a transaction row different from the date a new contract was first competed or awarded.

Start with the award identifier and recipient, then compare the transaction's action date, modification number, transaction amount, and the award's total and current obligated amounts. Read the description in the context of the parent award. A large dollar amount on one transaction can reflect added funding on an existing contract rather than a new opportunity for another supplier.

A practical sequence

1. Open the official award page and confirm that the recipient, agency, award type, and period of performance match the row.
2. Check whether the row represents the base action or a later modification. USAspending's federal spending guide describes prime-award transactions as initial awards or amendments/modifications.
3. Read the transaction description and parent-award history; do not use a keyword match alone to infer scope.
4. Look for a separate current solicitation, sources-sought notice, forecast, or teaming invitation before treating the record as a route to new work.
5. Record the source date and recheck the award page before publishing; public records can be updated or corrected.

In Award Signal's 90-day sample, 119 cyber/IT transaction rows included 18 rows classified as initial award actions and 101 later actions on existing awards. This is a sample-specific count, not a market-wide rate. It illustrates why a “recent award” label is too broad to support a sales recommendation.

Sources: USAspending.gov · Federal Spending Guide (PDF) · USAspending API documentation

EUROPE-WIDE · PUBLISHED NOTICES

How to search TED notices

Tenders Electronic Daily (TED) publishes procurement notices that can be searched by business opportunity, sector, location, and notice type. Its Common Procurement Vocabulary (CPV) is hierarchical: the code prefix describes a broader group, while later digits identify a more specific category. A very broad CPV filter can retrieve many records that are only loosely related to a supplier's work.

Notice stage matters. A prior-information notice, a call for competition, a tender notice, a contract award notice, and a contract modification do not all mean the same thing. A notice title that contains “security” is not enough to conclude that it is open for bids or that a specific supplier can participate. Open the latest official notice and inspect its procedure, lots, deadline, documents, and any related or changed notices.

A practical sequence

1. Search by a precise CPV code and compare it with a broader parent code; check whether the result set changes materially.
2. Filter by place of performance when the country or region matters. TED's NUTS geography is about location; the buyer's registered country is not necessarily the contract's performance location.
3. Check the notice type and version history; look for amendments or a later notice linked to the same procedure.
4. Read the full notice, including lot-level dates and language-specific material. A missing deadline in a compact data response is not evidence that the procedure remains open.
5. Keep a source link and note what could not be checked.

A TED title/CPV match is a discovery cue only. The current Award Signal sample checks English title phrases and exact CPV codes against an illustrative profile; it does not translate every language, read full specifications, or establish supplier eligibility.

Sources: TED search and browse help · TED CPV reference · TED NUTS reference · TED Search API documentation

CANADA · FEDERAL TENDER NOTICES

Check CanadaBuys tenders against the live notice

CanadaBuys is the federal tender portal. Public datasets provide downloadable notice records that can help with discovery, including separate open-notice and new-notice files. A row in an open-tender dataset is a lead to verify, not a guarantee that the opportunity is still open or that a supplier qualifies.

Use this source-first sequence

1. Search the notice title or reference on CanadaBuys and open the current notice page.
2. Check the current closing date, amendments, solicitation documents, buyer and procurement category.
3. Confirm whether the opportunity is federal and which supplier registration or security requirements apply.
4. Check the English and French versions where available; not every notice has both languages.

The Award Signal sample screens the open-tender CSV for cyber and IT text and future closing dates. It does not read every solicitation document, establish current status, or determine bid eligibility. Use the official portal before acting.

Sources: CanadaBuys tender opportunities · CanadaBuys tender notices dataset

UNITED KINGDOM · FIND A TENDER OCDS DATA

Read UK Find a Tender notices by stage

Find a Tender publishes procurement records in the Open Contracting Data Standard (OCDS). A release can describe a planning, tender, or award-stage change. The Award Signal sample requests recent releases tagged for the tender stage, then screens the notice text for cyber and IT terms.

Before treating a match as an open bid

1. Open the notice and confirm the current procedure, closing date, amendments, and procurement documents.
2. Check which UK procurement portal handles the notice and response; Scotland, Wales, Northern Ireland, and UK-wide processes can differ.
3. Confirm the contracting authority's supplier requirements and whether the company can meet them.
4. Use the OCDS match as a discovery aid only; it is not a qualification or recommendation.

The feed is updated data, so a recent record can be an amendment to an existing notice. This prototype uses a seven-day update window and ignores records whose listed tender closing date has passed.

Sources: Find a Tender data and API documentation · Find a Tender · Contracts Finder

NORTH AMERICA AND EUROPE · DATA LIMITS

What public records cannot tell you about cross-border fit

A searchable notice is not the same as a supplier qualification. Public records can show a buyer, a described need, codes, dates, and documents. They do not necessarily show a company's right to bid, required local registration, country-specific exclusions, security clearances, language capacity, tax status, insurance, subcontracting posture, or whether the notice has changed since the last data pull.

The data systems also describe different things. USAspending records U.S. federal award transactions after public reporting; TED is a publication and search service for notices. Their code systems, stages, timing, geography, and legal processes are not interchangeable. Canada's CanadaBuys and the UK's separate procurement services are not included in this prototype.

Use a source-first checklist

• Use the official notice or award record as the authority, not an aggregator's summary.
• Check current version, deadline, documents, lots, buyer country, place of performance, and notice stage.
• Ask the company's authorized procurement or legal contact to confirm eligibility and registration requirements.
• Separate observed facts from inference. Write “may merit review” when evidence is incomplete.

These limits are why a useful research site should explain how a signal was produced, preserve the official link, and make uncertainty visible. It should not imply that a public-data match is a bid recommendation or a promise of work.

Sources: TED features and scope · SAM.gov Contract Opportunities · CanadaBuys · UK Find a Tender