Build a tender deadline queue with an explicit comparison date

I maintain this Actor. This is an AI-assisted technical walkthrough, fact-checked against its accepted source contract and saved acceptance evidence.

A procurement queue needs to distinguish “deadline missing” from “deadline passed.” It also needs a reproducible answer to a basic question: passed relative to which date? Using the current machine clock makes an old snapshot produce a different assessment tomorrow without any source update.

The Tender Notice Deadline Review Queue reconciles supplied notice observations and can compare deadlines with an explicit asOf date. It accepts relevant Gov Tender Radar and Tender Alert records. It does not fetch new notices, submit bids, establish eligibility, or silently assume that an omitted deadline is overdue.

Make the comparison reproducible

asOf is optional and uses a strict YYYY-MM-DD value. When it is absent, deadline comparison remains unmeasured. The saved acceptance example demonstrates this: its status is deadline_present_not_compared, its action is review_unscheduled, and its confidence is high. High confidence in that output does not mean that the notice is currently open; it means the output preserves the stated evidence basis.

For an operational queue, choose an explicit comparison date and retain it with the exported result. For a historical investigation, use the date relevant to that investigation. A processing timestamp belongs in a separate column. Reusing a saved input with a different asOf is a changed assessment request, even when the source observations are unchanged.

Reconcile identity before prioritizing

Known TED adapters place publication numbers in the TED namespace. An arbitrary source needs its own namespace and exact identifier. This prevents unrelated sources with the same short number from being merged accidentally. A similar title is not enough to join notices. Identity handling should happen before evidence is capped for display.

Useful result fields include publicationNumber, buyer, buyerCountry, deadline, deadlineStatus, daysUntilDeadline, and conflictingFields. Preserve the namespace and source evidence in your downstream table. CPV codes are observed classifications; their presence does not establish that your business qualifies to bid.

Keep ambiguous dates visible

A date-only deadline and a timestamp with a timezone do not carry the same precision. The Actor preserves that granularity rather than inventing a midnight ordering for ambiguous timestamps. Invalid observed deadlines are also explicit. A queue that replaces every unknown value with the same spreadsheet date would undo that useful distinction.

Test a notice with an exact deadline, one with no deadline, one with an invalid calendar date, and two observations that disagree. Use an explicit asOf in a second run to inspect comparison behavior. Verify that missing remains unknown, contradictions remain inspectable, and displayed evidence omissions are not mistaken for absent source observations. A useful next step is a review queue with reasons and links, rather than an automated bid/no-bid decision inferred from incomplete notice data.

Run a small saved snapshot

Start with an existing Dataset you are authorized to read. Replace the Dataset placeholder below with its actual ID. Supported input can also use a source run ID or inline records; choose one explicit source. This Actor does not launch the upstream collection for you.

curl --request POST \
  'https://api.apify.com/v2/acts/zinin~tender-notice-deadline-review-queue/runs?maxTotalChargeUsd=0.10' \
  --header "Authorization: Bearer $APIFY_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{"datasetId":"REPLACE_WITH_YOUR_DATASET_ID","maxInputRows":100,"maxResults":10}'

The response identifies an asynchronous run. Save that run ID and check its status before reading its default Dataset. A client timeout does not cancel a server run; inspect the existing ID before starting another one. maxInputRows bounds ingestion and maxResults caps useful output. Neither option establishes complete coverage of a larger source. The API charge limit is a ceiling, not a promise that ten results will fit.

Price and evidence limits

On 15 October 2026 the observed FREE-plan price is $0.025 per notice assessment, with no paid start event for this Actor. Other subscription tiers can have different prices; verify the current Actor page before use. Source collection is a separate activity and may carry its own charges. Free diagnostic rows do not count as paid useful assessments.

The examples discussed here come from saved owner acceptance runs. They show specific observed behavior, rather than customer acceptance, profitability, or an exhaustive guarantee for every input. A new run of identical input can be charged again without adding new source evidence. Retain input provenance, the actual build ID, and the source observation window when comparing results over time.