Features / monitoring

Tender monitoring that starts with your market

For business development and bid teams: define the work you can deliver, review the opportunities in your scope and decide which deserve attention. Start with countries, relevant classifications and delivery constraints, then test the resulting feed against examples you already know.

Review owner: Duke editorial team · Updated

1. Define a scope your team understands

A scope groups your procurement interests. In scope setup, select the countries and regions you serve and the relevant classifications. Add a description explaining what belongs in this market so colleagues can interpret it consistently.

The setup includes optional value, procedure and contract-type filters. Start broad enough to inspect the market before narrowing it. A value filter is only useful when the source provides a usable value; classification systems should not be treated as interchangeable.

2. Review the feed in context

Select the scopes you are authorised to access. The feed offers search and filters for country, source, minimum value, deadline, procedure and document availability. Use lifecycle filters to distinguish opportunities at different stages rather than mixing historical awards into an active bid queue.

Check the source, notice stage and deadline on a result, then open its details and documents. A matching score or category is a reason to review an opportunity, not evidence that you meet its participation requirements.

3. Turn discovery into a team decision

Use feed triage and priority controls to organise the queue. For each opportunity worth investigating, record the unresolved eligibility, delivery and commercial questions before committing bid resources.

For example, a campus IT supplier can start with its service regions and relevant IT categories, review mixed hardware-and-services lots, then prioritise the notices its team can deliver. This is an illustrative workflow, not a measured customer outcome.

4. Check availability before concluding there is no work

The feed can show that scopes are still being prepared or that results and statuses are incomplete. Resolve an availability warning before interpreting an empty queue or a count as the whole market.

Duke coverage depends on the source, country and notice stage. Compare known notices with the feed and verify attachments and amendments in the official tender channel. This page does not promise every portal, instant ingestion or complete source coverage.

Evaluate Duke on your own market

Bring five known notices and the countries and services you care about. Ask to see how the scope, feed filters, source records and triage workflow behave for those examples.

Request a walkthrough