What is a fleet management organisation (FMO)?

An FMO is a specialist third party that handles the acquisition, funding, maintenance, administration and disposal of corporate, government and commercial vehicle fleets. In Australia, FMOs typically provide operating leases and novated leases, delivering vehicles to end customers and managing them through the lease lifecycle.

Who owns the telematics data in a managed fleet?

It depends on what the contract says, which is exactly why a data agreement matters. In practice, the client generally holds rights to operational data about its own fleet, while the FMO holds rights necessary to deliver its services. The platform provider typically acts as a data processor. The agreement should state each party’s rights explicitly rather than leaving them implied.

Is fleet telematics data personal information under Australian law?

Data linked to an identifiable driver is personal information under the Privacy Act 1988. Handling it must comply with the Australian Privacy Principles, and state workplace surveillance laws may also apply depending on the jurisdiction.

What should drivers be told about telematics data collection?

Drivers should know what data is collected, why, who can see it and how personal trips are protected.

What happens to fleet data if a client changes FMOs?

That depends entirely on the exit terms agreed at the outset. A well-drafted agreement specifies what data the client receives, in what format, within what timeframe and at what cost.

Can an FMO’s clients access their own fleet data directly?

Ultimately, fleet data belongs to the customer. When partnering with a quality FMO and a leading telematics provider, a transparent agreement ensures the client retains primary control over their data environment. This setup allows customers to set strict user permissions and security clearances. FMO access is usually granted on a consent basis for ongoing service, leaving the client free to connect their data to third-party tools via open APIs whenever they choose.

Fleet management

Do FMOs need clear data agreements with clients?

When a Fleet Management Organisation and its client rely on the same telematics data, a written agreement defines who can access what, for what purpose and on what terms.

By Keiran McMinn

Sep 21, 2026

two people in front of screen looking at computer

Key Insights

FMOs and their clients have different needs, but rely on the same data.
A clear data agreement between an FMO and a customer settles the rules while the relationship is good, providing both with security if something goes wrong.
Driver data is personal information under Australian privacy law, and should be addressed upfront in the agreement.
Data portability at contract end is the question clients increasingly ask first, and FMOs that define it turn a risk into a competitive advantage.

When a Fleet Management Organisation (FMO) and its client both rely on the same telematics data, they need a written agreement that defines who can access what, for what purpose and on what terms. The data serves the FMO's need to protect asset value and the client's need to manage costs and compliance. But without clear rules, friction could surface at the worst possible moment. A good data agreement prevents that.

The battery in a company vehicle is starting to fail. The car’s telematics have picked up the warning signs and have been recording them for days.

Unfortunately, the alert is sitting in the customer’s dashboard, and hasn’t reached anyone at the FMO, who are in the best position to act on it. When a driver is unable to start the car, it means roadside assistance, a replacement vehicle and an urgent workshop booking instead of simple maintenance.

All of it was preventable. The data existed, but it never reached the right people because the FMO and their client never agreed on what data they would share with each other.

That’s why it’s crucial for FMOs to have clear data agreements with their customers. Without it, they leave themselves exposed to situations like this, and the reputational risk that goes with it.

Who should see what?

The Australian Fleet Manager Association / Fifth Quadrant 2026 Australian Corporate Fleet Insights Report Open in new window found that 87% of large corporate fleets and 49% of small fleets track key metrics.

There’s no shortage of data, but FMOs and their clients aren’t always looking at the same numbers. And FMOs are sometimes in a slightly awkward position because they often lack access to the data that could help them manage the condition, servicing, compliance, operating cost and residual value of their vehicles.

The corporate customer has legitimate claim to most of the data their fleet generates. Their employees are driving the vehicles, and information about where those vehicles go, how drivers behave and how the fleet is used can be commercially sensitive or personally identifiable. In many cases they are also the ones paying for the telematics subscription.

The FMO's needs are narrower. It does not need to know where a driver stopped for lunch. It needs to know whether the vehicle is going to make it to the next service.

What does an FMO actually need?

There is an important distinction between monitoring a driver and monitoring the health of an asset. In many cases, an FMO only really needs to do the latter, and a relatively small set of signals can create significant operational value. These include:

VIN — Without a reliable VIN, a fault code or odometer reading cannot be connected confidently to the correct vehicle, lease agreement, maintenance schedule or service history.
Live odometer — Accurate mileage drives service scheduling, lease kilometre management, warranty compliance and end-of-lease reconciliation.
Battery voltage — A weakening battery often provides warning before it fails. If voltage is trending down over days or weeks, there may be an opportunity to intervene before the driver is stranded.
Diagnostic trouble codes (DTCs) — Access to relevant DTCs allows an FMO to move from reactive maintenance towards preventative intervention.
Fuel level — Combined with transaction data, fuel information can help identify anomalies and improve visibility of vehicle utilisation. At fleet scale, automated comparisons can surface discrepancies that manual processes are unlikely to find.
Crash detection — Rapid visibility allows the appropriate response processes to begin immediately rather than waiting for information to work its way through multiple parties.
These signals are fundamentally different from a detailed record of where an employee drove or stopped. They enable an FMO to look after the vehicles it has been contracted to manage.

What data do FMOs and their clients both rely on?

The table below shows where the same data stream serves both parties, and what a data agreement should settle for each.

Data type	What the FMO uses it for	What the client uses it for	What to agree
Live odometer	Service scheduling, end-of-lease kilometre calculations, residual value protection	FBT logbooks, utilisation reviews	A single verified source of truth; who can view and export records
Fuel transactions	Fuel card matching, fraud detection, cost reporting	Budget control, anomaly investigation	Who flags discrepancies and how they are communicated
EV home charging	Accurate employer reimbursement calculation	Employee reimbursement, cost management	How charging events at a driver's home address are handled and who can view them
Fault codes	Asset health monitoring, maintenance cost management	Uptime planning, safety assurance	Client visibility into fault status and how urgent faults are escalated
Trip classifications	Personal use allocation, lease billing	FBT compliance	How drivers classify trips and who can view personal trip records
Dashcam footage	Incident management, claims support	Driver exoneration, liability defence	Access rights, retention periods and release protocols

How does driver privacy affect fleet data sharing?

More than many FMOs expect, and Australian law is specific about it.

Telematics data tied to an identifiable driver is personal information under the Privacy Act 1988. Collection, use and disclosure must comply with the Australian Privacy Principles Open in new window administered by the Australian Information Commissioner (OAIC). Several states also apply workplace surveillance laws with their own notification requirements.

Privacy, more broadly, is a legitimate and growing concern for Australian businesses. The most recent published statistics Open in new window from the OAIC reveal that 2025 saw the highest number of data breach notifications (1,205) since mandatory reporting began in 2018.

There are a range of telematics functions that might require a cautious approach to privacy concerns. For example, FBT logbook automation records personal trips. EV home charging data captures reimbursable events at a driver's own address. Location tracking can reveal where a driver is outside working hours if vehicles are used for personal use.

A solid data agreement addresses each of these directly. It defines what drivers are told at onboarding, who can view identified driver data and how personal trip records are masked from client reporting.

What should a good data agreement cover?

Data access, privacy and consent obligations will vary depending on the fleet, the technology involved and how the data is being used. FMOs should seek appropriate legal and privacy advice for their specific circumstances. But as a practical starting point, there are some fundamental questions every data agreement should address:

Access — Who can see the data? Which fields can they access? Is that access real-time, event-based or delayed?
Purpose and use — What can each party use the data for? Can fleet information be used for benchmarking, analytics or product development? If so, under what conditions and at what level of aggregation?
Driver privacy — What are drivers told? Which information can be associated with an individual, who can view it and how are potentially sensitive trip records separated from routine vehicle-management data?
Third-party sharing — Under what circumstances can information be provided to maintenance providers, insurers, regulators, remarketing partners or other third parties?
Security — What controls protect the information, who is responsible for them and what happens if there is a breach?
End of contract — When the relationship finishes, what happens to the data? What does the customer receive, in what format, how quickly, and what information is retained or deleted?

An FMO does not need to take an aggressive position on every question. It does need to have an answer. Ambiguity is what creates disputes.

Would a data agreement help my FMO?

With the right data, FMOs can get ahead of problems instead of reacting to them. That might mean replacing a battery before it dies, booking a service on time, dealing with a fault before the vehicle breaks down, or spotting a mileage problem while there’s still time to do something about it.

That means less downtime, fewer unexpected costs and fewer headaches for drivers and customers. And when everyone is clear about what data is being used and why, it builds trust too.

Find out how Australian fleets are maximising productivity and reducing costs with Geotab