> ## Documentation Index
> Fetch the complete documentation index at: https://docs.driven.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Set Up Watchlist Monitoring

> How to set up watchlist monitoring in Driven with threshold-based alerts, so you only get notified when a name moves, breaks news, or crosses a level you care about.

This guide covers monitoring a watchlist with a scheduled task, so you get told when something happens instead of checking constantly. The key to a useful monitor is thresholds: it should stay quiet until a name does something worth your attention.

The concept behind this is [Scheduled Tasks](/concepts/scheduled-tasks).

## When to use this

* You track a set of names and want to be alerted to changes
* You want signal, not a daily report of nothing happening
* You want to catch big moves, news, or level breaks without watching the screen

## Step 1: Define what counts as notable

A monitor is only as good as its trigger. Decide what is worth an alert:

```text theme={null}
Monitor my watchlist throughout the trading day. Alert me only when a name moves more than 5%, has significant news, or breaks a key technical level.
```

Notice the word "only." That is what keeps the monitor from becoming noise.

## Step 2: Set the cadence and channel

```text theme={null}
Check every hour during market hours and send any alerts to Telegram. If nothing crosses the thresholds, don't send anything.
```

A monitor that says "nothing happened" every hour trains you to ignore it. Let silence mean "all clear."

## Step 3: Make alerts actionable

An alert should tell you enough to decide whether to act:

```text theme={null}
When you alert me, include what happened, why it likely moved, and whether it changes anything for that name.
```

## Step 4: Layer monitors if needed

You can run more than one monitor at different sensitivities:

* A fast, high-threshold monitor for big intraday moves (Telegram)
* A slower, end-of-day monitor summarizing everything notable (web app)

## Example variations

A move-and-news monitor:

```text theme={null}
During market hours, watch [tickers]. Alert me to any move over 4%, any material news, or any unusual volume. Quiet otherwise. Deliver to Telegram.
```

A level-break monitor:

```text theme={null}
Watch [ticker]. Alert me if it breaks above [level] or below [level], with the context for the move.
```

## Common mistakes

* **No threshold.** A monitor with no trigger is just a recurring report. Define what is worth an alert.
* **Threshold too low.** A 1% trigger fires constantly. Set it where a move actually matters to you.
* **Alerts with no context.** "NVDA -6%" is incomplete. Ask for the why and the so-what.

## Related

* [Scheduled Tasks concept](/concepts/scheduled-tasks) — how scheduled tasks work
* [Unusual volume monitor](/guides/scheduled/unusual-volume-monitor) — a volume-specific monitor
* [Create a market briefing](/guides/scheduled/create-a-market-briefing) — the daily-summary counterpart
* [Scheduled task prompts](/prompts/scheduled-task-prompts) — more templates