Skip to main content

One system for fleet, plant and tools

Vehicles, machines, small tools and test gear in a single register, with inspections, servicing, custody and documents attached to each one. The asset spreadsheet is the thing this replaces.

Lachlan McRitchie

Lachlan McRitchie

GM of Operations

Published 3 September 2026

Trusted by construction, mining and field service teams

Saunders InternationalMineral ResourcesSupagasHacer GroupMetro TunnelUltrabuilt
Rated 4.9 out of 5 on G2Rated 5.0 out of 5 on Capterra15 reviews on G2 · 17 reviews on CapterraCapterra Best Value 2026 badgeCapterra Best Ease of Use 2026 badge

What does consolidating the asset layer actually mean?

It means one register for everything you own that has to be found, checked, serviced or proven, instead of a separate list per asset class and per department. In practice that is vehicles, plant, small tools, test and measurement gear and safety equipment in the same system, each with its own inspections, maintenance, custody and documents. It does not mean replacing your jobs system, your payroll or your accounting. The asset records are the part that is scattered, and they are the part worth bringing together.

  • In scope: Register, custody, inspections, maintenance, documents, audits.
  • Out of scope: Jobs, payroll, accounting. Those stay where they are and integrate.
  • What disappears: The asset spreadsheet, and the second copy of it somebody else keeps.

Why does the same asset end up in four places?

Because each system was bought to solve one department's problem. The jobs system needed a plant list so it could schedule. The forms app needed an asset list so inspections could be filed against something. The GPS platform came with its own. Finance keeps the depreciation schedule. None of them was wrong on its own, and together they mean one excavator exists four times, with four different names and four different ideas of whether it is on site.

The problem

Most teams did not choose to run five systems. They bought a jobs system, then a forms app, then GPS on the trucks, and each one arrived with its own asset list. The register that everyone actually trusts is a spreadsheet on somebody's desktop, and it is the one thing that is not in any of them. So the same machine is entered several times, the inspection lives apart from the service history, the certificate lives in a shared drive, and nobody can answer a simple question about one asset without opening three tabs.

How MapTrack addresses it

MapTrack is the asset layer underneath the systems you keep. One register holds vehicles, plant, small tools and test gear, with categories and custom fields carrying what makes each class different. Inspections, maintenance, custody, meter readings, photos and documents attach to the asset itself. QR or barcode labels mean the crew opens the right record by scanning rather than searching. The systems you keep stay connected through integrations and the public API, so the same asset stops being typed in twice.

How it works

  • 1

    Decide the shape before you import

    Categories, asset numbering and the handful of custom fields you actually report on. This decision shapes every report afterwards, so it is worth the afternoon.

  • 2

    Import the spreadsheets you already have

    Bring the registers in from wherever they live now, including the one on somebody's desktop that everybody actually trusts.

  • 3

    Label what moves

    Durable QR or barcode labels on the gear that changes hands, so the crew opens the right record by scanning instead of guessing at a name.

  • 4

    Move the recurring work onto the record

    Pre-starts, inspections, servicing and calibration due dates attach to the asset, so the history and the schedule are the same thing.

  • 5

    Connect what you are keeping

    Accounting and telematics integrations and the public API let the asset layer feed the systems around it, rather than duplicating them.

The consolidation that works, and the one that does not

Teams are right to be sceptical of all-in-one platforms. The version worth doing is narrow and specific.

One asset layer, not one platform for everything

The scope is the register and everything that hangs off it. Your jobs system, payroll and accounting keep running, and integrate.

Every asset class in the same register

A ute, an excavator and a laser level answer the same five questions. Categories and custom fields carry the differences without needing separate systems.

The crew opens records by scanning

Adoption is the thing that kills consolidation projects. Scanning a label beats searching a list, which is the difference between a system people use and one they route around.

It stops the double entry, not the other systems

The measure of success is how many places the same asset gets typed into, not how many logins you cancelled.

Retire the asset spreadsheet

Bring vehicles, plant and tools into one register, and keep the systems that are already working.

  • No credit card required
  • 30 days free trial
  • Cancel anytime

Frequently asked questions

No, and you should not want to. MapTrack consolidates the asset layer: the register, what condition things are in, who has them, what is due and the documents that prove it. Your jobs system, your payroll and your accounting keep doing what they do. The asset spreadsheet is the thing that disappears.

Yes, and they should, because the questions you ask about them are the same. What is it, where is it, who has it, what is due on it, what proves it was done. A ute, a 20 tonne excavator and a laser level differ in what you track against them, not in whether they belong on the register. Categories and custom fields carry the differences.

Not always, and it is worth being honest about that. A system that tries to do eight unrelated jobs usually does most of them badly, and teams that have just rolled out a new platform rarely want another one. The consolidation that works is narrower: one place for asset records, instead of a register in one spreadsheet, inspections in a forms app, servicing in a workshop diary and certificates in a shared drive.

Most often the spreadsheet running out of road, or an audit with a date on it. Growth does it too: the method that worked at forty assets and one yard stops working at four hundred across three. The other common one is a person leaving, because that is when everyone discovers how much of the register lived in their head.

Importing from a spreadsheet is usually the fastest part. The work that takes time is deciding your categories, your asset numbering and which custom fields you actually need, because that shapes every report you will run afterwards. Doing that thinking first is worth more than importing quickly.

They keep running. MapTrack has a public API and integrations for accounting and telematics, so the asset layer can feed the systems around it. The aim is fewer places where the same asset is typed in twice, not a single platform that owns everything.

See the asset layer in one place

Join construction, mining and field service teams across Australia.

G2 4.9 out of 5 stars4.9 on G2 · 5.0 on CapterraCapterra 5.0 out of 5 stars
  • No credit card required
  • 30 days free trial
  • Cancel anytime