Government Fleet Telematics Procurement Basics

Note: Procurement rules vary by agency and jurisdiction and change over time. This is a general overview, not legal or procurement advice. Work with your contracting officer or purchasing office on any specific purchase.

Telematics helps public fleets answer questions they get asked all the time: How many vehicles do we really need? Where was that vehicle at 2 p.m.? Why is fuel spending up? But buying telematics in government is different from buying it in a private company. You will deal with approved contract vehicles, security and privacy reviews, public records rules, and often a separate process for installation.

Federal fleets

GSA-leased vehicles

If your agency leases vehicles from GSA Fleet, telematics is already part of the program. GSA says its leased vehicles include telematics at no additional cost, delivered through a FedRAMP Authorized platform. On eligible Ford and GM vehicles, GSA can use factory-installed (OEM) telematics instead of an aftermarket device. Contact your headquarters fleet manager or GSA Fleet for details on plans and add-ons.

Agency-owned vehicles

For agency-owned vehicles, the U.S. Department of Energy’s Federal Energy Management Program (FEMP) notes that agencies can use the GSA contract to install telematics or choose another provider. Either way, the FEMP guide recommends:

Coordinating fleet, IT, and cybersecurity teams before selecting a provider
Confirming the provider is FedRAMP Authorized
Verifying encryption of data at rest and in transit
Using role-based access and audit logs
Clarifying data retention and deletion terms and confirming the agency owns its data
Integrating with your fleet management information system to reduce manual reporting

Policy changes to watch

Federal fleet policy has shifted recently. Executive Order 14057, which set federal fleet sustainability goals, was revoked in January 2025, and in April 2025 GSA rescinded FMR Bulletin B-2023-55 on fleet management information systems. The operational case for telematics (utilization, safety, maintenance, and accountability) does not depend on those orders, but check current GSA and agency policy before you write requirements.

State and local fleets

Statewide contracts and policies

Many states set telematics rules for their own fleets. California, for example, requires state agencies to buy telematics through the state’s mandatory telematics service contract and keep it working for the life of the asset, unless an exemption is granted. Minnesota’s Department of Administration policy sets a 13-month retention period for raw telematics data. Colorado’s state fleet program has its own telematics policy. If you are a state agency, start with your state fleet office.

Cooperative purchasing contracts

Cities, counties, school districts, and other public entities often buy through cooperative purchasing contracts. These are contracts that another public body competitively solicited, which eligible members can use instead of running their own full bid. Sourcewell, for example, lists cooperative contracts with several fleet telematics providers. Check whether your jurisdiction allows cooperative purchasing and confirm each contract’s current status and scope directly with the contract holder.

One thing to check carefully: what the contract actually covers. A telematics contract may cover devices, software, and subscriptions without clearly covering installation labor, swaps, or de-installs. Know who is responsible for each before you sign.

Running your own RFP

If you issue your own solicitation, be specific about what you need. Recent public RFPs for fleet systems have included requirements such as integration with existing telematics and fuel systems, data migration, training, and data protection standards. Public safety fleets may also need to consider CJIS requirements for certain data.

Records, privacy, and driver concerns

Telematics data in a public fleet may be a public record. Colorado’s and North Dakota’s state fleet policies both note that telematics information may be reviewed for claims, litigation, or open records requests, subject to applicable law. Minnesota’s policy addresses when telematics data tied to an identifiable driver may be private personnel data.

Plan for these questions early:

Who can see location and driver data, and for what purposes?
How long is data kept, and how is it deleted?
How will you respond to records requests?
Do labor agreements require notice or bargaining over cameras or monitoring?
How will you explain the program to employees?

Don’t forget installation in the budget

Public budgets need clear line items, and installation is the one most often left out. When you scope the project, plan for:

Installation labor for each vehicle type, including multi-camera systems that take longer
Site access at each yard, including any security escort or badging requirements
Scheduling around shifts, emergency response, and seasonal operations
Upfitted vehicles such as police, fire, plows, and utility trucks, which need careful wiring around existing equipment
Quality control to confirm every unit reports before final acceptance
Documentation with serial numbers, photos, and install dates for each asset, which helps with audits and asset records
Ongoing work such as swaps when vehicles are replaced and de-installs when they are retired

Write acceptance criteria into the contract: for example, that each unit is installed to the maker’s standards, verified reporting on the platform, and documented with photos before it counts as complete.

A simple path for public buyers

Define goals and requirements with fleet, IT, security, legal, and HR
Check what contract vehicles you are allowed or required to use
Confirm security, privacy, and records requirements
Pilot on a sample of real vehicles
Scope installation, QC, and documentation as their own line items
Roll out on a schedule built around operations
Verify every unit, train users, and close out with full records

How TCI supports public fleets

TCI Installations has worked on government projects as well as for large trucking companies and local businesses. We fit in alongside whatever platform or contract vehicle your agency uses. We can scope and manage the installation, install to each maker’s standards, run quality control, document every asset, and train your drivers and managers.

Sources

GSA, GSA Fleet Telematics
U.S. DOE, FEMP, Telematics for Federal Fleets
GSA, Federal Register, FMR; Rescinding FMR Bulletin B-2023-55 (April 17, 2025)
California DGS, State Administrative Manual 4122, Telematics
Minnesota Department of Administration, Telematics Policy (Oct. 2025)
Colorado State Fleet Management, Telematics Universal Policy
North Dakota DOT, State Fleet Telematics Policy
Sourcewell, example telematics cooperative contract listing

Government Fleet Telematics Procurement: The Basics for Federal, State, and Local Buyers