Tender alerts with a clear review routine

First inspect the opportunities in your scope. If the geography or classifications are wrong, changing alert frequency will not fix the underlying relevance problem. Keep examples of relevant and irrelevant notices to guide adjustments.

Notifications depend on the matches and source data available to your scope. They do not establish that every opportunity in your market has been found.

In notification settings, check the overall email switch and the settings for each scope. Turning off all email notifications pauses email independently of an individual scope’s preferences.

The scope controls list Real-time, Daily digest, Weekly digest and None. Choose a cadence that someone on your team will act on. These are preference options; confirm actual delivery for your account before using email as your only monitoring route.

Scope alert settings include a minimum match score from 0 to 100, with 0 labelled as all matches. Raising the threshold can reduce the queue but may hide useful opportunities; review excluded examples before tightening it.

The settings also include an option for deadline extensions and corrigenda. Check that your change shows as saved. If saving fails, retry rather than assuming the new preference is active.

For an initial review, use a known match to compare the feed, scope settings and received message. If no email arrives, check the overall email setting, selected scope, cadence and score threshold, then ask support to inspect delivery.

Assign a reviewer to open the official notice, check the deadline and identify a bid, clarify or decline action. Continue watching the buyer’s official channel for changes during an active pursuit; a saved update preference is not proof that every amendment will generate a notification.