AU Tender Intelligence

Methodology

Every figure on this site is computed from published open data. Here is exactly how.

The renewal score (0–100)

Three additive components, capped at 100:

Bands: High ≥70, Medium ≥45, otherwise Watch.

Clustering: notices vs opportunities

Agencies frequently publish one contract notice per line item. Six separate notices for "Vehicle Spare Parts" to the same supplier, in the same category, all ending on the same day, are one re-procurement — not six.

The radar therefore groups notices sharing buyer + supplier + category + end date into a single opportunity, sums their disclosed value, and recomputes the score from that combined value using the formula above. The raw notice count is shown on the row, and the underlying records remain individually linked. Total value is unaffected by grouping.

~ATM (approach-to-market estimate)

Set at 120 days before the contract end date, reflecting the typical Commonwealth lead time for re-procurement. This is a rule of thumb, not a published date, and it will be wrong for panels, extensions and options. Treat it as "start paying attention", not as a deadline.

Entity resolution

Suppliers are merged on ABN, which is authoritative. Where a record carries no ABN, its normalised name (case-folded, legal suffixes and "trading as" clauses stripped) is matched against known ABNs; it is merged only when that name maps unambiguously to exactly one ABN. Otherwise it stays separate.

Currently 622 resolved suppliers, with zero ABNs split across multiple display names.

Categories

Commonwealth records carry a UNSPSC code, rolled up to its official 2-digit Segment label so that free-text descriptions aggregate into real categories. Records without a UNSPSC code fall back to the source's own category field, or to the raw description.

What the radar shows, and what it leaves out

The AusTender contractEnd feed returns tens of thousands of releases over a 12-month horizon and is not ordered by end date — a partial pull is a broad sample across the whole window, not the soonest-expiring contracts. Ranking such a subset would quietly bury the largest and most imminent opportunities.

So every contract in the pull is scored before anything is discarded. Aggregate figures (contract count, total value up for re-procurement) are computed over that full pool. Only the top-scoring slice is then published as radar rows.

The API uses cursor pagination and exposes no total-count endpoint, so an exact population figure cannot be obtained without walking every page. Totals are therefore published as a lower bound (≥) whenever the feed still had pages remaining — never as a complete count. The practical consequence: the radar is the highest-scoring slice of a large sample, and a contract's absence from it is not evidence that it does not exist.

Limitations — read these

These numbers are a research and business-development aid built from public records. They are indicative. Before you commit bid resources, open the linked source record.