Ongoing follow-up
A supplier-name match is not a confirmed award: a termination notice lesson
A council terminates a record after incorrect supplier details appear in an award notice. Names, legal entities and later notice changes all need verification.
A competitor table can start with a mistaken row
Imagine preparing a market report and adding a familiar supplier to recent wins. A correction or termination may require changing that row. Gateshead's historical notice illustrates the identity problem, but it does not justify concluding that all the supplier's business failed.
In Competitor Tracking, retain names, aliases, markets and dated source observations. Separate what the notice states from what you infer. A bare winner label cannot convey later changes or the evidence behind it.
After several searches show which markets and words produce relevant records, use 'Create monitor'. Set the supported category, keywords and region, and choose a name that explains its purpose. Start with a few conditions, assess relevance and then broaden the scope.
Broad conditions generate noise; narrow ones can miss differently worded notices. Observe a stable product term separately from a broader application term, record useful and irrelevant matches and adjust gradually. A monitor name does not imply automatic translation or attachment searching.
Refresh candidates manually and confirm the entity
Refresh potential matches from the authorized catalog, then verify legal name, registration identifier, buyer, lot and notice type. A summary mention may not be an award. Do not merge branches without supporting evidence.
Competitor matching is a manual refresh over stored records, not scheduled web-wide monitoring or a promise of outbound alerts. Award candidates depend on intelligence access. If this public example is not stored, add its official source as an observation. A failed refresh retains historical results with a stale warning; retry before treating them as newly checked.
Open monitors and the alert inbox to review new matches. Check the original notice, stage and date before classifying a record for assessment, research or exclusion. A match is a lead awaiting review, not proof that a project is eligible.
For projects already in progress, actively check official corrections, clarifications and document changes. Collection timestamps may lag the source. Increase verification frequency for approaching deadlines according to project risk. A weekly review is a suggested rhythm, not a replacement for timely checks before critical dates.
Organize the review into three short stages
Triage signals, review active projects and assign actions. Discuss new information, unresolved qualification questions, approaching dates and tasks needing coordination instead of rereading every notice. After updates, colleagues should be able to find both the evidence and the next step.
The following is a suggested team process, not an automated product schedule or a time-saving promise. Adapt the frequency to the team, while ensuring that each review produces a specific output.
| Stage | Focus | Output |
|---|---|---|
| Triage | New matches and noise | Candidates, exclusions and condition changes |
| Verify | Qualification gaps, files and deadlines | Updated evidence and open questions |
| Assign | Cross-team tasks and preparation margin | Owners, internal dates and next checks |
Give saved items, accounts and projects distinct purposes
Saved opportunities support later reading, target accounts support buyer research before a notice exists, and the bid pipeline manages projects the team intends to pursue. Features depend on current access. Without pipeline entitlement, organize your research conclusions and actions first, then assess whether an upgrade fits your needs.
Moving every unqualified lead into execution obscures priorities. Before handoff, explain relevance, verified conditions and who will resolve gaps. Your team performs partner discussions, pricing and formal submission through its process; the platform does not contact buyers or submit bids on your behalf.
Review relevance and decision quality
Track which matches warrant detailed review, which exclusions removed useful records, which qualification questions repeatedly block progress and whether tasks lack owners. A small relevant set may be more useful than a large unattended one; assess results against your own market and product.
After a project ends, retain reasons, submission evidence and outcome. For a decision not to bid, distinguish scope, qualification, partner and timing issues. For a lost bid, infer causes only when supported by official or buyer evidence. Use verified lessons to refine search conditions and preparation rather than presenting guesses as outcomes.
