Monitor pursued opportunities and follow-ons
Use saved searches, direct government-record changes, pursuit context, similar records, Opportunity Stack, and GovTribe AI automations to watch for related opportunities and follow-on work.
Use a combination of saved searches, direct government-record changes, pursuit context, similar-record discovery, Opportunity Stack, and GovTribe AI automations when you need to monitor an opportunity, recompete, follow-on, market segment, or agency buying pattern over time.
Choose what you are monitoring
Start by naming the monitoring job clearly. Common examples include:
- a single active opportunity and its amendments
- a recompete or likely follow-on to an award
- an agency office, program, or buying command
- a set of incumbent vendors or likely competitors
- an expiring contract vehicle or ordering path
- a pursuit list that needs regular capture review
That choice determines whether you should start with a saved search, a pursuit, a similar-record search, or GovTribe AI.
Save searches around the market
Saved searches are the most reliable way to return to the same monitoring view. Build the search from the record type that best fits the question, then save the query, filters, and sort.
Use saved searches for repeatable questions such as:
- new opportunities from an agency office
- notices mentioning a recompete phrase, program name, contract number, or incumbent
- awards or IDVs nearing an end date
- vendors active in a target market
- state and local opportunities in a jurisdiction or category
If email alerts are available for the saved search, choose the saved-search email frequency that matches your review cadence. This setting controls saved-search email only. If alerts are not available for the workflow, reopen the saved search during your regular capture review.
Use pursued records as context
Pursuits help your team track internal capture work. Start a pursuit from a useful record when the record belongs in your pipeline, then keep notes, owners, stages, files, tasks, and custom fields in the pursuit workflow.
Marking or creating a pursuit does not automatically guarantee that GovTribe will notify you about every future related notice. Use saved searches and follow-on discovery alongside pursuits when you need monitoring coverage around the pursued record.
Review Opportunity Stack and Similar Opportunities
When a record looks relevant, use the related context around it before deciding how to monitor it.
| Option | Use it for |
|---|---|
| Opportunity Stack | Review the broader opportunity context, related records, and lifecycle signals that GovTribe can show around the opportunity. |
| Similar Opportunities | Find records that resemble the current opportunity by concept, requirements, source context, or other available similarity signals. |
| Similar on related records | Start from a file, vendor, award, IDV, or category when the related context is a better clue than the opportunity text. |
After you find a useful related record, save the search that found it or create a pursuit when the record needs pipeline tracking.
Add AI automation when available
GovTribe AI automations can run a saved prompt from one or more schedules, government-record changes, or workspace events when your account has access. Each start trigger is independent, so any one of them can run the same monitoring prompt.
If your AI client is connected to GovTribe MCP, it can manage these monitors directly. Use Create_Automation to create a new monitor, Search_Automations to find its current version and start triggers, and Update_Automation to change its prompt, triggers, cadence, or linked project.
For one known opportunity, award, IDV, grant, forecast, or state/local opportunity, add A government record changes and select the exact record. This is useful for amendment-driven deadline or description changes and for award or IDV modifications that affect recompete timing.
That trigger watches only the selected record. It does not discover a separate follow-on or recompete record by itself. Combine it with other start triggers when the monitoring job is broader:
| Monitoring goal | Start triggers |
|---|---|
| Watch a solicitation and keep a regular review cadence | The opportunity changes OR a weekly schedule. |
| Watch an award for lifecycle changes and find a new follow-on notice | The award changes OR a saved search gets new related results OR a recurring research schedule. |
| Watch several known records | Add one government-record trigger for each record. |
For Saved search gets new results, choose the automation's own Instant, Daily, or Weekly polling frequency. When creating an automation, the builder copies an existing supported saved-search frequency; otherwise, it starts with Daily. That value is copied once: later saved-search email changes do not alter the automation, and disabling saved-search email never stops it.
A new or retargeted record-change or saved-search trigger begins listening when you save that change. Resuming the automation restarts listening from the resume time, so earlier record activity or saved-search results are not replayed.
Useful automation prompts include:
Use Market Intelligence > Recurring Capture Monitor and Pipeline Report.
Every Monday, review my saved searches for new opportunities related to our active cybersecurity pursuits and summarize what changed. If the automation provides saved-search result IDs instead of full records, retrieve those records before summarizing them.
Group the report into urgent actions, high-priority new items, watch items, stale pipeline items, timing risks, missing evidence, and recommended owner actions.Review opportunities similar to my pursued records and flag likely recompetes, incumbent clues, agency fit, and next actions.For an automation that combines a selected opportunity's record-change trigger with a weekly schedule, use a prompt such as:
Review changes to this opportunity and explain any amendment, deadline, requirement, attachment, or buyer update that changes our capture plan. On scheduled runs, also check for related follow-on signals and summarize only material changes, evidence gaps, and recommended next actions.Summarize new records from this saved search and separate urgent due-date changes from lower-priority market signals.Automations can support monitoring, but they still depend on the prompt, selected skill, available data, account access, and credit-powered usage settings.
Current limits
GovTribe monitoring works best when you combine saved searches, pursuits, Similar, Opportunity Stack, and automations deliberately. These limits matter:
| Limit | What it means |
|---|---|
| Pursuits are not universal alerts. | Creating or marking a pursuit tracks capture work, but it is not a guarantee of automatic follow-on notifications. |
| Similar results depend on available context. | Similar can be unavailable or less useful when GovTribe does not have enough similarity context for the selected record. |
| Saved-search scope determines matching results. | If the search is too broad, too narrow, or missing a filter, its emails and automation runs can be noisy or miss the records you expected. |
| Saved-search email and automation cadence are separate. | Change saved-search email settings and each automation trigger's polling frequency independently. |
| Government-record triggers watch one exact record. | Use a saved search or recurring research trigger when you also need to discover separate follow-on or recompete records. |
| AI summaries should be verified. | Review the underlying GovTribe records before acting on deadlines, eligibility, pricing, or compliance claims. |
Related articles
- Use saved searches: Create saved searches, reopen current results, and manage alert frequency.
- Create pursuits from records: Start or extend a pursuit from a GovTribe record.
- Create custom pursuit fields: Track workspace-specific pursuit details.
- Find similar records: Start from one useful record and discover comparable records.
- Automations: Combine schedules, government-record changes, and workspace events in recurring GovTribe AI work.
- Create automation MCP tool: Create a monitor through GovTribe MCP.
- Update automation MCP tool: Change an existing monitor through GovTribe MCP.