Saving & Tracking Opportunities
Save tenders into your pipeline, track status and stage, and collaborate with your team
Saving & Tracking Opportunities
Your pipeline is built by saving tenders and creating opportunities, then moving each one through a status lifecycle from first sighting to final outcome.
Saving Opportunities
Saving a tender from the Tenders browser creates an opportunity and triggers AI enrichment: Cothon processes the tender's description and documents so requirements can be extracted and assessed against your capability profile, and generates the semantic embedding used for similarity matching.
Opportunities you create manually (see Creating Custom Opportunities) enter the same pipeline with the same tracking.
Status Lifecycle
Each opportunity has one status:
| Status | Meaning |
|---|---|
| Identified | Discovered, not yet evaluated |
| Evaluating | Under bid/no-bid review |
| Bidding | Committed to bid — appears in Active Bids |
| Submitted | Proposal delivered |
| Awarded | Won |
| Lost | Awarded to another vendor |
| Declined | You chose not to bid |
Tip
Setting status to bidding is the trigger that surfaces the opportunity in Active Bids, the war-room view with deliverables and submission gates.
Status changes are recorded in the opportunity's activity log, so the pursuit history stays auditable.
Stages
Independently of status, each opportunity has a stage describing where the work is: discovery, qualification, proposal, negotiation, or closed. Use stages to describe process progress and statuses to describe the pursuit decision and outcome.
Archiving
Archive opportunities you no longer need in the working pipeline. Archived opportunities are hidden by default and can be shown again with the archived toggle in the list filters.
Team Collaboration
Team Members
Add team members to an opportunity from its workspace. Members are visible on the opportunity so everyone knows who is involved in the pursuit.
Comments
Opportunities support threaded comments — use them for evaluation notes, open questions, and decisions. Comments appear in the workspace and are captured in the history.
Activity Log
The History tab shows the opportunity's full activity log — status changes, document events, team changes, and comments — filterable by type.
What Tracking Does Not Include
To set expectations, the Opportunities module does not currently have: automatic status-change notifications or email alerts, tags, lists/folders or watchlists, a kanban board, pipeline analytics dashboards, CSV/CRM exports, or bulk actions. Tracking is done through statuses, stages, filters, and the per-opportunity workspace.
Next Steps
- Filtering & Search — slice the pipeline by status, stage, and source
- Linking Analyses — attach the analysis work
- Active Bids — the workspace for committed pursuits
Related Articles
Was this page helpful?