Create alert

Overview

The create alert wizard builds a ruleset that monitors the notice catalog and notifies you on a schedule you choose. Three guided steps — general information, rules, preview — mirror the power of Notices browse / Lead Finder search in an automated watch you do not have to rerun daily.

Creating an alert is the main way to turn a one-time successful filter into ongoing market coverage. The same filter dialogs appear in browse and in step 2 here — skills transfer directly.

Tip: Before you click Save on step 3, confirm:

  • Name is recognizable to you and teammates (not "My new alert ruleset")

  • Scope (personal vs team) is correct — you cannot change it later

  • At least one filter is configured in step 2

  • Notification frequency matches how often you review email

  • Enabled is on if you want matches immediately

  • You are under plan ruleset limits (check Alerts list usage meter)

Important: Filter rules are fixed after creation in the current UI. Invest time in step 2 — you can only change name, enabled, and frequency later via Edit alert.

How create alert fits in Opportunities

Flow diagram

How to open the create wizard

Path

Steps

Alerts list

Click New ruleset

Notice overview

Receive alerts in command bar (pre-fills step 2)

Team overview

Configure alerts checklist step

Sign-in required.

Wizard layout

Element

Description

Back arrow

Returns to alerts list (unsaved progress may be lost)

Title

New alert ruleset

Stepper

General information → Rules → Preview

Footer

Previous · Advance / Save

Desktop: horizontal stepper with step icons.

Mobile: compact step name + progress bar.

Save on step 3 creates the alert and returns to the list with success toast:

Alert ruleset created — We will be sending you alerts when we detect matching tenders as configured.

Step 1 — General information

Name

Property

Detail

Control

Text input

Placeholder

My new alert ruleset

Help

A name by which you and your team will be able to recognize this ruleset at a glance.

Validation

Required — empty blocks advance

Use names that encode intent: RO supplies medical CPV 33100000 weekly beats generic defaults.

Scope (owner)

Property

Detail

Control

Owner selector

Options

Personal identity or one of your teams

Help

Choose whether you wish this resource to be scoped only to yourself or to one of the teams you belong to.

Scope

Effect

Personal

Ruleset tied to you; team colleagues do not manage it as team resource

Team

Shared visibility; changes visible to team per Edit alert toast

Not changeable after creation — pick carefully.

Enabled

Property

Detail

Control

Toggle

Default

On

Help

Choose whether to immediately begin receiving alerts.

Turn off to create a paused ruleset you enable later from Edit alert Overview tab.

Notification frequency

Property

Detail

Control

Select dropdown

Options

Digest intervals (immediate, daily, weekly — exact labels in UI)

Help

Controls email batching — reduces noise on active markets

Frequency

When to use

Immediate / shortest interval

Fast-moving deadlines, small result sets

Daily

Default balance for most teams

Weekly

Broad CPV watches with high match volume

Step 2 — Rules

Uses the same filter dialogs as Notices browse and Lead Finder.

Adding filters

  1. Click Add filter.

  2. Choose category from the picker (keywords, country, CPV, etc.).

  3. Configure values in the dialog.

  4. Filter appears as a chip in the rule list.

  5. Repeat — additional filters append with AND semantics.

Available filter types (non-exhaustive)

Filter

Purpose

Keywords

Text in title, description, documents

Country

Publication country

CPV

Industry classification codes

Notice type

CN, award notice, etc.

Contract type

Supplies, services, works

Status

Ongoing, awarded, …

Estimated value

Min/max range

Publication date

Date range

Deadline

Submission window range

Contracting authority

Specific buyer

Procedure type

Open, restricted, …

Awarded companies

Post-award competitor filter

Rule structure

  • First filter starts the rule set.

  • Each added filter narrows results — all must match.

  • Remove filters via chip dismiss control.

Empty state

Step 2 shows guidance when no filters exist. You must add at least one filter before Advance to step 3.

Caution: Stacking many AND filters quickly yields zero matches. Mirror a browse session that already returns rows before saving as alert.

Step 3 — Preview

Read-only summary before commit:

  • Ruleset name and scope

  • Enabled state

  • Notification frequency

  • Visual list of applied filter chips

  1. Review each filter chip for typos and range mistakes.

  2. Click Previous to fix step 1 or 2.

  3. Click Save to create.

Validation errors block Save — return to earlier steps via Previous.

Button

Visible

Action

Previous

Steps 2–3

Go back one step

Advance

Steps 1–2

Next step without saving

Save

Step 3 only

Creates alert; returns to list

Validation on step 1 (name required) and step 2 (≥1 filter) blocks Advance.

Receive alerts from a notice (shortcut)

On Notice overview, Receive alerts opens a dialog that seeds step 2 filters from the current notice:

  • CPV codes

  • Country

  • Estimated value band

  • Contracting authority

  • Contract type

  • Related fields when published

Workflow:

  1. Open a notice that exemplifies what you want to watch.

  2. Click Receive alerts.

  3. Complete step 1 (name, scope, frequency) in the wizard.

  4. Review pre-filled filters in step 2 — tighten or add keywords.

  5. Preview and Save.

Faster than rebuilding filters from scratch in Lead Finder.

After creation

  1. Redirect to Alerts list.

  2. New card appears in the grid.

  3. Click card → spotlight panel.

  4. Monitor Activity tab for first matches.

  5. Edit name, frequency, enabled via Edit alert — not filter rules.

Limits and billing

Subscription may cap total rulesets. Check header usage meter on alerts list before creating near-duplicate rulesets. At cap, New ruleset locks until upgrade or deletion.

From tuned browse

  1. Find a good result set in Notices browse.

  2. Note active filters.

  3. New ruleset → recreate same filters in step 2.

  4. Set digest frequency based on match volume.

From exemplar notice

  1. Open strong-fit notice.

  2. Receive alerts → wizard with seeded filters.

  3. Add keyword for product specificity.

  4. Save as team scope if whole org should see matches.

Paused draft

  1. Complete wizard with Enabled off.

  2. Share name with manager for review.

  3. Enable from Edit alert when approved.

What you cannot do in the wizard

  • Change scope after Save

  • Edit filters after Save without new ruleset

  • Set OR logic across unrelated filter groups (AND only within one ruleset)

  • Exceed plan ruleset count

Troubleshooting

Issue

Likely cause

What to do

Save fails

Validation / network

Check step 1 name; retry

Advance disabled step 2

No filters

Add at least one filter

Duplicate notifications

Overlapping rulesets

Disable old ruleset first

Zero matches after weeks

Too strict

New ruleset with looser CPV/value

Too many matches

Too broad

New ruleset with country + keyword

FAQ

Can I create multiple rulesets with the same filters?

Yes — different digest schedules, personal vs team scope, or experimental tweaks.

Do keywords need quotes?

Follow keyword filter guidance in the dialog — same as Lead Finder browse.

Can the Home assistant create alerts?

The dashboard assistant may create an alert — open Configuration tab afterward and verify filters.

Will this ruleset match notices already in browse today?

Alerts focus on forward detection when notices enter or update in the monitoring pipeline — not replacing a full historical browse query.

Can I copy filters from an existing ruleset?

Configuration tab is read-only — note chips manually when creating a replacement ruleset.

What happens if I hit the plan limit mid-wizard?

Save may fail or New ruleset may be locked — delete unused rulesets or upgrade.

  • Alert rulesets (list)

  • Edit alert

  • Notices browse

  • Notice overview

  • Notice (Tender)