UK Tender Pipeline Monitor avatar

UK Tender Pipeline Monitor

Pricing

from $3.00 / 1,000 procurement observations

Go to Apify Store
UK Tender Pipeline Monitor

UK Tender Pipeline Monitor

Track official Find a Tender procedures, deadlines, values and award changes. Export one compiled record per OCID with source links and optional saved comparisons.

Pricing

from $3.00 / 1,000 procurement observations

Rating

0.0

(0)

Developer

Brandt May

Brandt May

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Categories

Features

Limited permissions

Share

UK Tender Pipeline Monitor - procurement change intelligence

UK Tender Pipeline Monitor

Track official Find a Tender procedures, deadlines, values and award changes. Export one compiled record per OCID with source links and optional saved comparisons.

Open in Apify Console · First run · Output · Pairings · Price

First run and source setup

  1. Review the source targets and filters before starting. Apify account authorization is required to run the Actor.
  2. Open the JSON input editor and start with the bounded configuration below. Review dates and targets for your intended use.
  3. Review the current Pricing tab and set a maximum run charge and timeout in Run options. A result limit does not set a spending limit or promise that many rows.
  4. After completion, inspect the dataset and the run's diagnostics/Storage records described in the full guide. A successful process alone does not establish complete source coverage.
{
"maxResults": 3,
"maxSourcePages": 1
}

Checked against the captured input schema. This bounded configuration has not been run as part of the presentation refresh.

Output worth checking

The published default dataset view includes these fields. Missing values and source-specific coverage are explained in the full guide.

  • Ocid · ocid
  • Title · title
  • Buyer Name · buyerName
  • Tender Status · tenderStatus
  • Tender Deadline · tenderDeadline
  • Value · value

Keep original source links and observation dates when interpreting records. JSON preserves nested values; CSV is useful for flat columns.

Use this with other Mayd It Actors

These are separate tools for a reviewed workflow. Each run uses its own input, authorization and pricing; this guide does not configure automatic execution.

FedRAMP Marketplace Monitor

Monitor official FedRAMP offering metadata and dated status paths. Compare saved observations with clear source timestamps, legacy labels and deterministic package variants. Keep this FedRAMP Marketplace Monitor evidence alongside the original source in a reviewed procurement pipeline workflow.

Parallel research context: Choose the corresponding source target in this second Actor’s own input form; no automatic field transfer is configured. Keep both original source URLs and observation dates in your review sheet; reconcile identities manually.

Keep the distinction: A solicitation, grant listing and contract award are not interchangeable. Match official identifiers and dates and retain original eligibility and jurisdiction limits.

SAM.gov Opportunities Scraper - Federal Solicitations

Search SAM.gov contract opportunities via the official API. Title and posted-date filters. Requires a free Public API Key from SAM.gov Account Details. Source errors stay in the run summary. Keep this SAM.gov Opportunities Scraper evidence alongside the original source in a reviewed procurement pipeline workflow.

Parallel research context: Choose the corresponding source target in this second Actor’s own input form; no automatic field transfer is configured. Keep both original source URLs and observation dates in your review sheet; reconcile identities manually.

Keep the distinction: A solicitation, grant listing and contract award are not interchangeable. Match official identifiers and dates and retain original eligibility and jurisdiction limits.

Price and run limits

At the captured FREE-tier rate (2026-11-16 UTC), $0.005 per procurement observation. Actor Start is $0.00005 per event; the number of startup events depends on memory. Plan rates and future changes may differ; check the current Pricing tab before starting.

A capped or interrupted run can save useful rows without covering its intended scope. Review the source-specific completeness and comparison rules below before treating missing rows as removals.

Documentation and support

Product guide, source limits and saved output · API and MCP setup · Input schema

Open this Actor's Issues tab with a run URL, the relevant input field and the result you expected. Remove API keys and private information before sharing.

Complete source guide

Keep a UK bid pipeline current

Turn official Find a Tender notices into one current procurement observation per OCID. Watch deadlines, published values, buyer details, lots, awards and document links, then compare the fields with your last saved observation.

Built for bid teams, procurement analysts and suppliers maintaining a shortlist. The Actor discovers a bounded window of recent notices and resolves each procedure through the official compiled OCDS record, so repeated notices do not become duplicate pipeline entries.

Run in Apify Console · Output · Watchlist · Coverage

Start with three procedures

{
"maxResults": 3,
"maxSourcePages": 1
}

Run the Actor, open Dataset for observations, and open Run report for checked procedures, failures and limits. The default inspects up to 20 recent official releases and saves at most three matching procedures. It requires no account or API key for the source.

What you receive

FieldsUse in your workflow
ocid, title, buyerId, buyerNameStable procedure identity and CRM label
tenderStatus, tenderDeadline, enquiryDeadlineReview published status and submission dates. tenderStatus is null when the official record publishes none, as some award and contract update notices do
value, cpvCodes, deliveryRegionsPublished amount/currency and sector/geographic screening
lots, awards, documentsStructured lot/award summaries and links to procurement documents
noticeIds, latestReleaseDate, sourceUrlTrace the compiled record back to the official source
contentHash, comparisonStatus, changedFieldsRoute new or changed observations
previous, previousObservedAt, observedAtExplain a change using the previous saved snapshot

For example, retained official source evidence from 15 October 2026 contains procedure ocds-h6vhtk-0784ad, Sevenoaks District Council's sports-hall roof replacement, with GBP 120,000 excluding tax and a published tender deadline of 6 November 2026. This dated example is not a promise that the opportunity is still open.

Watch a named procedure

{
"ocids": ["ocds-h6vhtk-0784ad"],
"maxResults": 3,
"comparePrevious": true,
"snapshotName": "roof-procurement-demo"
}
  1. Save your exact OCIDs in a private Apify task.
  2. Use a dedicated snapshotName; the first comparison emits new and establishes history after each row is saved.
  3. On later runs, route changed rows to review. changedFields identifies top-level fields; previous lets your integration inspect the old deadline or amount.
  4. Set onlyChanges: true when you want unchanged observations counted in SUMMARY without additional dataset rows. Empty output can therefore be a successful no-change check.
  5. Upsert into your own spreadsheet or CRM by ocid. Check the run's own summary before treating missing output as meaningful.

Use one writer per snapshot namespace and filter scope. A concurrent history change prevents overwrite and makes the run partial; it is not a distributed lock. Only confirmed saved rows advance history. No missing procedure becomes a deletion signal.

Inspect recent award procedures

{
"stages": ["award"],
"maxResults": 3,
"maxSourcePages": 1
}

stages selects notices during discovery. The compiled record represents the current procedure and can include later changes. Optional keywords match title, description or buyer; cpvPrefixes match published item codes. OR applies within each filter list, AND between keyword and CPV lists. Filtering a small window can correctly return no matches.

Pricing and controls

The base result price is $0.005 per saved procurement observation, plus the Actor's published start event. Your Apify plan may apply its displayed discount. A no-change row skipped by onlyChanges, a failed source request, or a filtered record is not a paid result.

  • maxResults: 1-100 confirmed rows, default 3.
  • maxSourcePages: 1-5 discovery pages of up to 20 releases each, default 1.
  • ocids: up to 50 exact procedures; bypasses discovery.
  • maxRunSeconds: default 240, also constrained by the platform timeout with a 25-second reserve.
  • The official service limits request rates. On 2026-11-13 it asked for a 120-second pause after about 20 requests. The Actor waits when the official Retry-After pause fits the remaining run time, so allow a larger maxRunSeconds for larger samples. A pause that does not fit ends the run early and keeps the saved rows.
  • Set a platform spending limit appropriate for your task. A spending stop is explicit in SUMMARY; check saved counts before downstream actions.

Coverage and boundaries

Source: Find a Tender only. This does not aggregate Contracts Finder, devolved portals or all UK purchasing. The source exports OCDS records under the Open Government Licence.

The Actor reads current compiled records, not an as-of reconstruction. updatedFrom and updatedTo filter the source's release last-update window in its documented timezone-less YYYY-MM-DDTHH:MM:SS format. They do not filter deadlines or freeze the compiled record at that date. Date and stage discovery filters cannot be combined with an explicit watchlist.

Published dates, amounts and labels are preserved. Missing optional fields remain null or empty arrays; they are not estimated. This is a selected metadata projection, not every OCDS field: it does not download attachments, collect contact details, submit bids or assess eligibility. Supplier organization names in awards remain public procurement evidence.

status: "ok" means the configured bounded work succeeded. Read coverageComplete, discoveryComplete, stoppedOnSourcePageLimit, sourcesNotReached and stoppedOnMaxResults to understand its extent. Reaching a configured sample cap is distinct from a failed source. Partial source failures and time/spending stops are explicit; an all-failed run fails instead of emitting error rows.

The official service sometimes answers a published procedure with no content (HTTP 200 and an empty body). The Actor asks once more for the first two such records in a run. In a recent-release sample, a record that stays empty is skipped and listed in sourceRecordsUnavailable, with coverageComplete: false and a coverageNotes line; it is not a paid row, the run report shows partial coverage, and the run does not fail while readable records are at least as many. A procedure you named in ocids that stays empty is reported in failedSources.

When the official service asks for a pause (HTTP 429, or 503 with Retry-After), the Actor waits as instructed if the pause fits the run. sourceWaits and sourceWaitSeconds count every wait before a retry, including the half-second retry after a gateway error. Otherwise it sends no further requests, records stoppedEarlyOnRateLimitAt and lists the unread procedures in sourcesNotReached.

Source references and support

For source changes, support or data correction requests, use this Actor's Issues tab or bmay@mayd-it.com. Include a run URL and OCID; do not send credentials or private bid documents.