The government fleet procurement guide

If you are buying fleet telematics or fleet management software for a government fleet, three things do most of the work: a requirements list written around your operation rather than vendor brochures, the security and privacy conditions government policy already expects, and the right buying channel for your organisation. This guide gives you all three, including a requirements checklist you can lift straight into a tender.

Why this exists

Telematics stopped being optional for parts of government some time ago: New South Wales has required telematics in general-purpose government fleet vehicles since 2021 under its fleet policy. Yet almost all published guidance is written for vendors, not for the officer who has to write the tender. This is the buyer's version.

Scope the problem before the product

The biggest cause of disappointing fleet systems is tendering for a tracker when the problem is an operation. Before writing requirements, answer four questions:

1. What decisions do we need the data for? Utilisation and right-sizing, maintenance, pool booking, compliance reporting, safety, or all five?
2. Which vehicles are in scope, including plant, trailers and employee-owned vehicles used for work?
3. Who will use it weekly: fleet, workshop, drivers, finance, WHS, executives?
4. What must it connect to: finance and asset systems, fuel cards, HR?

The answers decide whether you are buying GPS tracking or a fleet operating platform, and the two should be tendered differently.

Requirements worth copying

The checklist below is the condensed version; the fleet tender requirements checklist is the full, printable set. The items government IT and privacy teams most often wish they had included:

• Data ownership sits with you. Your fleet's data is yours, exportable in open formats, at no exit cost. NSW's telematics guidance makes agency data ownership explicit; every buyer should.
• Australian data residency, with hosting, processing and backups onshore, and the hosting provider's government certifications stated.
• Access control that maps to your directory: single sign-on, automatic deprovisioning, role-based access, and a full audit trail including vendor support access.
• Workplace surveillance compliance built in: 14-day written notice support and in-vehicle notices where required. See telling drivers about tracking.
• A working exit: data deletion on request, including remote deletion for lost devices, and a documented offboarding process.
• Details behind security claims: ask for certificates, the hosting region, the breach notification commitment in hours, and the incident contact.

The buying channels

• NSW agencies buy telematics through the ICT Services Scheme (SCM0020) or through the whole-of-government Fleet Management Panel providers, with the fleet policy setting the telematics requirements.
• Councils commonly buy through Local Government Procurement panels and VendorPanel marketplaces in NSW, and their state equivalents elsewhere, which pre-check insurances and compliance so you can run a lighter RFQ.
• Other states run their own panels and schemes; the requirements above travel unchanged even when the channel differs.

Running the evaluation

Give more weight to a live demonstration using your scenarios than to a feature matrix. Speak with named references from fleets like yours, and use a pilot or staged rollout with acceptance criteria before full commitment. Ask every shortlisted vendor the same operational questions: what happens when a pre-start fails, when a booking is not returned, when a device dies, and when you leave.

IntelliTrac supplies fleets to Australian councils, utilities and agencies, and can respond against every requirement above; ask us for the security pack when you get to that stage. But this guide is deliberately vendor-neutral: use the checklist against everyone, including us.

The tender requirements shortlist

The full printable version, with evaluation questions, is in the templates library.

• Agency ownership of all fleet data, with open-format export at no cost.
• Australian hosting, processing and backups, provider certifications stated.
• Single sign-on, directory-driven deprovisioning and role-based access.
• Complete audit trail, including vendor support access.
• Workplace surveillance notice and in-vehicle signage support.
• Named breach notification window in hours, with an incident contact.
• Remote data deletion for lost or decommissioned devices.
• Installation plan that keeps vehicles in service, with uptime commitments.
• Named references from comparable government fleets.
• Documented exit process tested before contract award.

Official sources

• buy.nsw: Buying and supplying telematics
• buy.nsw: Motor vehicle operational guidelines
• Local Government Procurement: approved contractors

Last updated 10 July 2026. General information, not tax or legal advice.