Burke

How Australian government buys technology

The short version, for vendors who are new to it or tired of learning it the hard way.

Australia's government bodies span the Commonwealth, six states and two territories: departments, agencies, councils, universities and health districts. Most of their technology spend goes to vendors who are already on a panel with a local contracting party. That sentence is the whole opportunity and the whole problem.

How Burke works with vendors

One country, nine sets of rules

The Commonwealth buys under the Commonwealth Procurement Rules and the PGPA Act; each state and territory has its own procurement framework, its own portal, its own panels and its own thresholds. A supplier who is set up for New South Wales is not set up for Western Australia. The rules are public and reasonable; the work is knowing all nine at once.

  • CommonwealthAusTender
  • New South Walesbuy.nsw
  • VictoriaBuying for Victoria
  • QueenslandQTenders
  • Western AustraliaTenders WA
  • South AustraliaSA Tenders and Contracts
  • TasmaniaTasmanian Government Tenders
  • Australian Capital TerritoryTenders ACT
  • Northern TerritoryQuotations and Tenders Online

Where the money is

Figures as published by each source; follow the link for the period and method.

Panels and head agreements

Much of government ICT spend runs through pre-qualified panels and head agreements: a supplier joins once, then agencies buy from the panel without an open tender. Joining takes months, needs insurance, financials and compliance evidence, and is maintained by category. A vendor who is not on the relevant panel usually cannot be bought from directly, however good the product. A local prime contractor whose panel standing covers the category changes that.

Where deals die

Government contract terms are largely non-negotiable: liability, indemnity, governing law, data location, privacy, accessibility and audit rights. Global vendor terms are often US-law, limited-liability and cloud-standard. The two meet at the legal stage, late in the process, and many deals stop there. Knowing the standard departures each jurisdiction will and will not accept, before the negotiation starts, is most of the job.

Where the data lives matters

Expect questions about data location, hosting certification, the Information Security Manual, the Essential Eight, IRAP assessment and the supply chain behind your product. The answers do not have to be perfect; they have to be accurate, specific and the same every time they are asked.

The response is a document set, not a proposal

A government tender response is a set of returnable schedules: compliance matrices, capability statements, pricing schedules, referee forms and declarations, each in the buyer's format. Evaluators score what is in the schedules. A beautiful proposal with a missing schedule is non-compliant and is not read. Procurement teams see the difference between a response written for them and one assembled from a sales deck, and they say so in debriefs.

Days, not quarters

Clarification questions close a week or two after release. Responses close at a fixed hour, often early afternoon in the buyer's time zone, with no extension for a late upload. Debriefs are offered and worth taking. Forward procurement plans and expiring contracts are published months ahead, for anyone who reads them.

Why a local partner, and what kind

A vendor can learn all of this. Most choose not to, because the Australian market is small next to their home market and the learning curve is paid for in lost bids. The alternative is a local partner who already lives inside it: one who is on the panels, holds the contract, prepares the response in the buyer's format, and works the agencies before the tender is written rather than after. That is the work Burke does.

How Burke works with vendors