Queensland Forward Procurement Pipeline Monitor

Find planned Queensland Government purchases before tenders are released and monitor changes automatically.

This Actor turns the official Forward procurement pipeline into structured, filterable opportunity records for suppliers, business-development teams, procurement advisers, market researchers, and automation workflows.

Built by UpsideRadar from authoritative public data.

Most important limitation: a pipeline entry is an indicative purchasing plan, not a live tender, confirmed budget, award, or guarantee that procurement will proceed. Verify material details at the official source.

Best for

• suppliers looking for earlier visibility into planned Queensland Government purchasing;
• business-development and bid teams prioritising agencies, categories, regions, timing, and spend ranges;
• procurement advisers and market researchers comparing pipeline activity;
• recurring Apify Tasks that should report additions, changes, and removals.

Why use this instead of downloading the source?

The Actor reads the official machine-readable API and adds:

• normalized agency, category, region, timing, spend, method, and funding fields;
• parsed planned-release dates and numeric AUD spend-range bounds;
• deterministic filtering, ordering, deduplication, and change detection;
• customer-scoped monitoring baselines that advance only after complete output and charging;
• source attribution, stable-looking IDs, fingerprints, warnings, and run summaries;
• dataset views and schemas ready for Apify API, Make, Zapier, n8n, and AI agents.

The source contact-email column is deliberately excluded.

Typical price

Current pay-per-event prices before any Apify Store discount:

Result	Approximate price
25 opportunity records	about US$0.10 (US$0.101)
100 opportunity records	about US$0.40 (US$0.401)
500 opportunity records	about US$2.00 (US$2.001)
Successful no-change monitor comparison	about US$0.006

These examples use the live event configuration: US$0.001 start, US$0.005 successful monitor check, and US$0.004 per valid opportunity record written.

Three-step quick start

1. Choose Find planned opportunities, Monitor changes, or Market summary.
2. Add optional filters. Start broad if you do not know the source’s exact vocabulary.
3. Set Maximum records and run. Review the opportunities dataset view and the run summary before automating.

Safe 25-record preview:

{
  "customerGoal": "search",
  "includePast": false,
  "maxItems": 25
}

Practical use cases

Find high-value planned procurement

Use minSpendAud to find records whose published spend range may reach a threshold. A parsed bound is not an exact or confirmed budget.

{
  "customerGoal": "search",
  "minSpendAud": 10000000,
  "includePast": false,
  "maxItems": 25
}

Monitor ICT or construction plans

Save the filters as an Apify Task, run it once to create a baseline, then schedule the same Task for later comparisons.

{
  "customerGoal": "monitor",
  "categoryGroups": ["Information and communication technology"],
  "monitoringStateKey": "ict-plans",
  "includeUnchanged": false,
  "maxItems": 25
}

Preview a selected Queensland region

{
  "customerGoal": "search",
  "regions": ["Cairns"],
  "includePast": true,
  "maxItems": 25
}

Customer goals

Find planned opportunities

Return records matching keywords, agencies, category groups, categories, regions, procurement methods, funding status, spend bounds, release dates, or the source’s Brisbane 2032 classification.

Monitor changes

The first automatic monitor run:

• creates the private baseline successfully;
• emits no opportunity records because no changes are expected yet;
• writes a non-opportunity MONITORING_CHECK receipt with a clear message and next steps;
• confirms that the same Task, filters, and monitoring state name should be scheduled again.

Subsequent successful runs return new, changed, and removed records. Leave Include unchanged records off for low-cost scheduled monitoring.

A removal means only that a record is absent from the current comparable filtered snapshot. It does not mean the procurement was cancelled, awarded, or completed.

Market summary

Return matching opportunity records and write deterministic aggregates to the run’s SUMMARY record. Aggregates cover agencies, category groups, regions, procurement methods, funding, timing status, spend-range medians, and change counts. No LLM is used.

Filters

Filters are optional and combine across fields. List filters use case-insensitive matching, but source wording still matters.

Useful starting examples:

• agency: Queensland Health;
• category group: Information and communication technology;
• region: Cairns;
• procurement method: Open tender;
• funding status: Funded;
• keywords: software, digital, construction, or medical.

If an exact field is unfamiliar, start with a keyword and inspect returned source values before tightening the filter.

Brisbane 2032-related purchasing plans

The official pipeline contains a field named Brisbane 2032 related. Set brisbane2032Only to true to return records carrying that source-published classification.

This Actor does not independently classify records as Games-related. It is not affiliated with, sponsored by, or endorsed by Brisbane 2032, the Australian Olympic Committee, the International Olympic Committee, Paralympics Australia, or the International Paralympic Committee. No protected emblems are used.

Output

The default table puts decision-friendly fields first:

1. change type and program description;
2. agency, category group, and category;
3. planned-release window and spend range;
4. procurement method and funding status;
5. region, Brisbane 2032 indicator, and related public URL.

Full JSON retains source identifiers, normalized date and spend bounds, deterministic identity and scope fingerprints, timestamps, completeness, warnings, and official-source attribution.

Example:

{
  "schemaVersion": "1.0.0",
  "recordType": "queensland_forward_procurement_opportunity",
  "agency": "CS Energy Ltd",
  "categoryGroup": "General goods and services",
  "programDescription": "Services and management of oil fluid power",
  "estimatedReleaseWindow": "Jul - Sep 26",
  "estimatedReleaseStart": "2026-07-01",
  "estimatedReleaseEnd": "2026-09-30",
  "procurementMethod": "Open tender",
  "spendRange": "$5M - $10M",
  "spendMinAud": 5000000,
  "spendMaxAud": 10000000,
  "fundingStatus": "Funded",
  "region": "Multiple",
  "changeType": "current",
  "sourceAttribution": {
    "publisher": "Queensland Government — Housing and Public Works",
    "license": "Creative Commons Attribution 4.0"
  }
}

API and automation

New integrations should use customerGoal. Existing API clients and saved Tasks may continue sending supported legacy mode values. Hidden reliability, debug, and previous-dataset fields remain API-compatible.

JavaScript

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor(
  'fixmyerrorcode/queensland-forward-procurement-monitor'
).call({
  customerGoal: 'search',
  categoryGroups: ['Information and communication technology'],
  includePast: false,
  maxItems: 100,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

from apify_client import ApifyClient

client = ApifyClient("YOUR_API_TOKEN")
run = client.actor(
    "fixmyerrorcode/queensland-forward-procurement-monitor"
).call(run_input={
    "customerGoal": "search",
    "brisbane2032Only": True,
    "includePast": True,
    "maxItems": 100,
})

for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

CLI

apify call fixmyerrorcode/queensland-forward-procurement-monitor \
  --input '{"customerGoal":"search","regions":["Cairns"],"includePast":true,"maxItems":25}'

HTTP

curl -X POST \
  "https://api.apify.com/v2/acts/fixmyerrorcode~queensland-forward-procurement-monitor/run-sync-get-dataset-items?token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"customerGoal":"search","minSpendAud":10000000,"includePast":true,"maxItems":25}'

Use environment variables or a secret manager for tokens.

Pricing details

• synthetic apify-actor-start: US$0.001 per run;
• monitor-check: US$0.005 per successful automatic baseline creation or comparison;
• opportunity-record: US$0.004 per valid, deduplicated dataset item;
• platform usage included.

The first automatic monitor run costs approximately US$0.006 and emits no paid opportunity records. Duplicates, discarded rows, failed requests, and records withheld by the maximum charge are not charged as opportunity records.

For a scheduled monitor, set the run maximum to at least US$0.006 + US$0.004 for each change you want returned. Monitoring state advances only after complete output and charging, so a charge-limited run can safely retry unsaved changes.

What this does not tell you

• whether a live tender has been released;
• whether a published spend range is an exact or confirmed budget;
• whether funding, timing, scope, or procurement method will remain unchanged;
• whether a pipeline item will proceed, be awarded, or produce a contract;
• who to contact, how to bid, or whether your organization is eligible;
• whether a removed monitoring record was cancelled or awarded.

Results do not include tender documents, bids, awards, personal contacts, or procurement advice.

Source and independence

Source: Queensland Government, Housing and Public Works, Forward procurement pipeline, licensed under Creative Commons Attribution 4.0.

The Actor uses the official machine-readable Queensland open-data API and fails closed if the expected licence, resource, or datastore contract changes.

This is an independent product. It is not affiliated with, endorsed by, or operated by the Queensland Government, QTenders, or the Australian Government. Verify material information at the authoritative source before acting.

Support and troubleshooting

• Empty search: remove optional filters, set includePast to true, and inspect broad results for current source vocabulary.
• First monitor run returned no opportunities: this is expected. Open the MONITORING_CHECK result to confirm baseline creation, then schedule the same Task and filters.
• Later monitor run returned no changes: check the receipt; a successful no-change comparison is a valid result.
• Maximum charge reached: increase the run limit only if you want more records. The Actor does not advance monitoring state after incomplete output.
• SourceContractError: the official licence, resource shape, or datastore contract may have changed. This deliberate fail-closed behavior protects provenance.
• Other failure: report the run ID and a non-sensitive log excerpt through the Actor’s Issues tab.

Do not include API tokens, private dataset contents, personal information, or source contact-email values in a public issue.