Event-Driven Collection

Scheduled collection ensures baseline coverage. Event-driven collection captures intelligence that arrives between scheduled runs. An event-driven collector monitors trigger sources — news feeds, social media keywords, regulatory filing databases — and initiates targeted collection when a trigger fires. A competitor mentioned in three news articles within an hour triggers a competitive profile refresh. A customer's competitor filing a patent triggers a landscape update. The trigger does not wait for the schedule — it activates collection immediately.

1. Define Trigger Conditions Each trigger has a condition (what event must occur), a threshold (how significant the event must be to warrant unscheduled collection), and a collection scope (what additional data to collect when triggered). A single news mention is not a trigger. Three mentions in 24 hours is a trigger. Define thresholds to prevent trigger fatigue.
2. Build Trigger Sources RSS feeds with keyword filtering, API webhooks from monitoring services, change-detection scripts on web pages, and social media keyword tracking. Each trigger source feeds an event bus that the orchestrator monitors. When a trigger fires, the orchestrator initiates the configured collection scope.
3. Deduplicate Against Scheduled Event-driven collection may duplicate data that scheduled collection would have captured within hours. The normalizer deduplicates: if the event-driven data is already present from a scheduled run, it is merged rather than duplicated. The event-driven collection adds urgency, not redundancy.