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

# Expand Drafts from Monitors

> Turn a monitor event into a ready-to-run Expand search with one click

When a [monitor](/monitors/overview) surfaces a signal worth acting on, you usually want to broaden it: the event tells you "Acme Corp just raised a Series B," but the action is "find every other company that just raised a Series B with similar attributes." **Expand Drafts** automate that handoff. One click on the event card and Emanate generates a search prompt, deep-links into the Expand editor, and lets the existing Expand pipeline produce the matching pills.

## How It Works

<Steps>
  <Step title="Click Generate Expand draft">
    On any event card in the [Events Timeline](/monitors/overview#events-timeline), click **Generate Expand draft**. The button enters a loading state.
  </Step>

  <Step title="Emanate writes a search prompt">
    Behind the scenes, an LLM reads the event content and writes a **broader Expand-style objective**. For example, an event about Acme Corp raising a Series B becomes a prompt like *"Find all B2B SaaS companies in California that raised Series A or B funding in the last 90 days."*

    Critically, the LLM only writes the **prompt sentence**. It does **not** generate the structured pills (filters). That's handled by Expand's existing pipeline once you hit Run, so there's a single source of truth for pill logic.
  </Step>

  <Step title="Land in the Expand editor">
    You're redirected to `/expand?searchId=N` with the prompt pre-filled in the bottom search bar. The pill area is empty. That's expected.
  </Step>

  <Step title="Hit Run in Expand">
    Expand's Claude-based schema-generation pipeline takes the prompt, generates the pills, and runs the search. From here you're in the standard Expand flow: review, refine pills, drill into matches, and export.
  </Step>
</Steps>

## Drafts Are Idempotent Per User

Each user gets their own draft per event:

* **First click** on an event creates a new draft
* **Subsequent clicks** by the same user open the same draft (preserving its `searchId`, so deep-links don't break)
* **Two users in the same org** clicking the same event each get their own independent draft. Editing one doesn't affect the other

After the first generation, the button on the event card flips to:

* **View Expand draft:** opens the existing draft
* **Refresh icon (Regenerate):** overwrites the draft with a fresh LLM call, preserving the same `searchId` so any deep-links you've shared stay valid

## Regenerate

If the first prompt isn't quite right (too narrow, too broad, or focused on the wrong attribute), click the **refresh icon** next to **View Expand draft**:

* A new LLM call generates a different prompt sentence
* The existing draft is overwritten in place
* The `searchId` is preserved
* Pill area resets to empty so the next Run regenerates pills from the new prompt

<Tip>
  Regenerate is a no-cost UX-level reset. It's just one LLM call for the prompt sentence. It doesn't burn an Expand search until you hit Run.
</Tip>

## Calendar Date Picker on the Timeline

The same release added a **calendar date picker** at the top of the Events Timeline, useful when you want to jump back to a specific day's events to generate drafts in batch.

* Click the date-range header → a month-grid calendar popover opens
* Each day cell shows an **event count badge**
* Today and your selected date are highlighted in the same pill style as the inline date strip
* Pick a date → the strip auto-pages to that week and selects that day

Combined with **View Expand draft**, this makes it easy to revisit a day's worth of events, see which already have drafts, and generate or regenerate drafts for the rest.

## Deep-Linking and Sharing

The `?searchId=N` URL is a stable pointer to the draft, so it's safe to:

* Bookmark a specific draft for later
* Share with a teammate (subject to Expand's normal access rules)
* Link from Slack, email, or notes back into the draft

If a draft falls off the first 50 in your Expand sidebar (paginated), the deep-link still works. The page falls back to fetching by ID directly.

## What Carries Over to Expand

| From the monitor event | Into the Expand draft                                       |
| ---------------------- | ----------------------------------------------------------- |
| Event content          | Used as LLM context to write the prompt                     |
| Source URLs            | Not copied. They stay on the event card                     |
| Detected date          | Stored in draft metadata; not used in the search            |
| `searchId`             | Newly minted on first Generate; preserved across Regenerate |
| Pills (filters)        | **Not** generated yet. Produced by Expand when you hit Run  |

## Permissions

* Drafts are scoped to the user who generated them. Your draft is **not** visible in another teammate's Expand sidebar
* The webhook flow for events themselves is unchanged: events still arrive automatically; draft generation is always **user-initiated**

## Next Steps

<CardGroup cols={2}>
  <Card title="Monitors Overview" icon="radar" href="/monitors/overview">
    Create monitors and review the events timeline
  </Card>

  <Card title="Sequences" icon="send" href="/sequences/overview">
    Turn an Expand result set into a multi-channel outreach
  </Card>

  <Card title="Accounts" icon="building-2" href="/accounts/overview">
    Land matched companies as accounts
  </Card>
</CardGroup>