UK FTS Contract Extension Review
Pricing
from $10.00 / 1,000 useful unique contract revieweds
UK FTS Contract Extension Review
Review current contract periods and stated renewal options from a bounded official FTS feed.
Pricing
from $10.00 / 1,000 useful unique contract revieweds
Rating
0.0
(0)
Developer
Kagerou AP
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Review contract periods and stated renewal options from recent official UK Find a Tender (FTS) releases. This Actor helps UK bid and capture agencies maintain a source-linked contract review pipeline.
The output separates the contract's stated current end date, maximum extension date and renewal declaration. An extension option is not evidence that an extension was exercised, and it does not confirm a future tender. Every result requires human review.
Try the default input
{"maxPages":1,"maxContracts":10,"cpvPrefixes":[],"previousRows":[]}
This uses the live recent feed. No API key, login, proxy or date maintenance is required. The default scans one page (normally up to 100 releases) and returns at most 10 useful unique contracts. It may legitimately return a coverage summary with no useful contracts; it never substitutes demo contracts for an empty or failed source.
For a recent window, optionally supply updatedFrom as an ISO datetime with timezone, no more than seven days before the run. The end of that window is the run's start time. Blank or omitted updatedFrom uses the recent feed. maxPages is 1–3; maxContracts is 1–50. A run fetches at most 300 releases. Requests are serial, spaced by at least 10.5 seconds. HTTP 429 or a Retry-After header stops retrieval without retries.
Optional cpvPrefixes accepts up to ten numeric prefixes, each 2–8 digits. It filters observed contract, explicitly matched award and release-level tender CPV classifications. It does not enrich codes or establish a contract-specific classification where the source only supplies a tender classification.
Optional previousRows accepts at most 50 prior rows keyed by exact ocid and contractId, with currentEndDate, maximumExtensionDate, and/or renewalDeclared. Supply only observed fields. For example:
{"ocid":"ocds-h6vhtk-07854b","contractId":"1","currentEndDate":"2027-10-10T07:59:59+09:00"}
Differences are computed only for records and fields observed in both inputs. Missing dates remain unknown. A previous contract absent from this bounded scan is unobserved; it is never marked expired, removed or unchanged. Same-time conflicting releases and duplicated prior identities are held for review. Latest retrieved releases supersede older ones without copying missing historical fields forward.
Results
The default Dataset contains source-linked contract rows, or a coverage summary when no useful contracts are observed. KVS record OUTPUT contains the same contract facts, coverage and authoritative settled custom-event counts. Dataset rows are saved before charging and refer to OUTPUT or the native charge ledger for final billing; their pre-charge snapshot does not claim a settled fee.
Rows include ocid, contractId, releaseId, buyer, supplier IDs when explicitly linked by awardID, observed CPV codes, currentEndDate, maximumExtensionDate, renewalDeclared, renewalText, sourcePaths, periodBasis, unknown fields and source attribution. Periods come only from contracts.period; tender or lot planned periods are not presented as contract periods. Original ISO strings and offsets are preserved. No UK calendar-date conversion is implied.
Coverage reports pages and release counts, requested window, next cursor, filtered/unknown/duplicate counts, output truncation and source failures. This is a review of retrieved releases, not a complete UK market, historical contract record or verified current portfolio. The API may omit releases in larger time windows; use narrower windows when appropriate and retain coverage with your report.
On source failure, useful facts already observed can remain accessible with partial/unknown coverage, but the run fails and no custom fee is requested. All-unknown records incur no custom fee. Result writes happen before charge requests. Interrupted or ambiguous writes/charges are not automatically replayed on resurrection; the saved checkpoint and native ledger must be reviewed. An incomplete checkpoint or uncertain charge response fails the run rather than claiming success.
Pricing
- $0.01 per unique
ocid+contractIdwith at least one meaningful contract date or stated renewal field (contract_reviewed). - Automatic platform start event: $0.00005 per run.
- Default Dataset item event: $0. No extra Dataset fee.
- Source failure, all-unknown rows, summaries and duplicate occurrences: $0 custom fee.
Ten charged contracts cost $0.10005 including the start event; 50 cost $0.50005. On successful paid runs, useful contract output is limited to the funded event capacity before saving to OUTPUT or the Dataset, with exact budget checks before serial custom-event requests. A budget below one contract event returns only a budget and coverage summary. Source-failure facts retain the no-custom-fee exception described above. Pricing is an untested commercial hypothesis.
Source and licence
Source: FTS official OCDS release packages. Contains public sector information licensed under the Open Government Licence v3.0. Source links and this notice accompany the output. No government endorsement is implied. Only selected public factual contract fields are exported; contact points, attachments, logos and company enrichment are excluded.
Local verification
Node 24.22.1 and official Apify SDK 3.7.2 are pinned with the dependency lockfile. npm ci --ignore-scripts, npm test, npm run validate and npm run sample run the local checks. The sample output is generated from an actual stored official source fixture and is explicitly labelled as a fixture execution. npm run live performs a bounded public-source read without an Apify cloud run or charge. Cloud build, pricing configuration and public listing are separate release checks.