Intelligent alerts

Intelligent alerts turn FedGrade into a daily-active tool. A workspace defines rules that bind a trigger (a class of domain event) to a watched scope (the agency, vendor, program, or opportunity you care about). When a matching event appears, the rule fires — and every fired alert carries a why: the triggering event plus a citation, so it lands in your inbox as an actionable item, not noise. Alert rules are a Team-and-above capability: Team includes 25 rules, Enterprise 200, and Government is uncapped.

Trigger types

Six trigger classes, each answering a distinct capture question:

• recompete_posted — a watched agency posted a new solicitation in a NAICS lane it has awarded before (an established award lane — the notice itself is not confirmed as a recompete of a specific expiring contract).
• pwin_threshold_crossed — a watched pursuit's pWin crossed a configured threshold, up or down.
• forecast_materialized — a forecast you watch became a real solicitation.
• vendor_award_change — a watched vendor won or lost a relevant award (a competitive-position shift).
• oversight_on_watched_program — new GAO/IG oversight dropped on a watched program.
• agency_strategic_update — a watched agency published a strategic-plan or budget signal that reshapes its pipeline.

How firing works

An evaluator runs on a schedule. For each new domain event since the last tick, it asks every enabled rule "does this event fire you?" The pipeline is fail-closed and runs these gates in order:

1. Match — trigger type, watched scope, rule config, and tenancy all have to line up.
2. Entitlement — alerting is Team+; a downgraded workspace stops firing.
3. Dedup — an append-only ledger with a unique (rule, event) key stops a re-evaluation from re-firing on an event you've already been told about.
4. Deliver — the alert is created as a notification, respecting your in-app, digest, and email preferences.

Managing rules

Create and toggle rules at /settings/alert-rules. Fired alerts are delivered to your in-app notifications and, per your preferences, by email or in a digest — set those at /settings/notifications.

Honest limits

An alert can only fire on an event FedGrade observed in the research library or computed in its pipeline. Coverage and timeliness track the underlying connectors — an alert is as current as the source ingest behind it. Every alert is cited, so when one fires you can verify the trigger before acting on it.