Define Your Requirements
Before you open a single vendor website, sit down with the people who will actually use the system and document what you need. This step is skipped more often than any other, and it is the most common reason tool tracking projects stall or fail.
Start with the basics: how many assets do you need to track? Include hand tools, power tools, test equipment, safety gear, vehicles and plant. Most teams undercount by 30 to 50 per cent on their first estimate because they forget about items in vehicles, personal tool kits and hire equipment. Walk your sites, sheds and vehicles with a clipboard before you start talking to vendors.
Next, document your sites and locations. A single-site workshop has different needs from a contractor running fifteen active job sites across Sydney and the Central Coast. Multi-site operations need location hierarchies (region, site, zone, container) and the ability to transfer assets between locations with a clear audit trail. If your team works fly-in fly-out in the Pilbara or rotates across remote sites, offline mobile capability becomes non-negotiable.
Identify your users. How many people need to scan and check tools in and out? How many need admin access to run reports and manage maintenance? The distinction matters because some vendors charge per user, which can blow out costs when you have forty tradies who only scan twice a day.
Finally, list your compliance obligations. In Australia, Work Health and Safety regulations require that plant and equipment is maintained, inspected and fit for purpose. If you need pre-start inspections, test-and-tag records, calibration tracking or scheduled maintenance evidence, those requirements should be in your brief from day one, not bolted on as an afterthought.
Must-Have vs Nice-to-Have Features
Once you have your requirements documented, split them into two columns: must-have and nice-to-have. Be ruthless. A feature is must-have only if your system will fail without it.
Must-haves for most teams: Asset register with unique identifiers (serial number, asset ID). QR code or barcode scanning via smartphone. Check-in/out with user and location stamp. Mobile app that works offline. Search and filter by location, category, status and assigned user. Basic reporting (asset list, location summary, overdue items). Data export (CSV at minimum).
Common must-haves for regulated industries: Maintenance scheduling (time-based and meter-based). Work order creation and tracking. Compliance forms and inspection records attached to assets. Audit and verification workflows. Photo and document attachments on asset records.
Nice-to-haves that add value: GPS tracking for high-value assets. Geofencing and movement alerts. Depreciation tracking and financial reporting. Integration with accounting, ERP or telematics. Custom forms and AI-assisted form creation. Reservation and scheduling boards. Automated alerts for expiring certifications.
The trap is treating everything as must-have. When you do that, you end up choosing the platform with the longest feature list rather than the one your team will actually use. A system with ten well-executed core features beats one with fifty half-baked ones every time.
Evaluate Mobile Experience
The mobile app is where your system will succeed or fail. Back-office dashboards and reports are important, but they are used by two or three people. The mobile app is used by everyone, multiple times a day, in dusty sheds and on wet construction sites.
Test the app on the devices your team actually uses. If most of your crew carries Android phones two generations behind the current model, test on those. A demo on the latest iPhone in a conference room tells you nothing about real-world performance.
Check these specific things. Scan speed: hold the phone up to a QR label and time how long it takes to recognise and open the asset. Under two seconds is acceptable; under one second is good. Offline mode: put the phone in aeroplane mode and try to scan, check in/out and complete a form. The data should queue and sync when connectivity returns. If the app shows an error or blocks you, that is a deal-breaker for remote and underground work.
Navigation: can a new user find an asset, check it out and log an issue within sixty seconds of opening the app for the first time? If the interface requires training to do basic tasks, field adoption will be low. Photo capture: can you take a photo of a damaged tool and attach it to the asset record in two taps? This is one of the most-used features in practice, and some apps make it unnecessarily difficult.
Finally, check notification support. Can the app send push notifications for overdue maintenance, geofence alerts or assignment changes? And does it support biometric login (fingerprint or face) so workers do not have to type passwords with dirty hands?
Check Integration Support
Integration support determines whether your tracking system fits into your existing tech stack or creates another data silo. Ask each vendor about four categories of integration.
Accounting. Most Australian businesses run Xero or MYOB. Can the platform sync asset values, depreciation and purchase costs? At minimum, can it export data in a format your bookkeeper can import? If you manage your own BAS and tax depreciation schedules, automated sync saves hours every quarter.
Project management. If your projects live in Procore, Buildertrend or Monday.com, check whether assets can be linked to projects and whether costs flow through. For construction teams, having tool costs allocated to a specific job rather than sitting in overheads makes a material difference to project profitability reporting.
Telematics. Fleet and heavy equipment teams need engine hours, odometer readings and fault codes flowing into the asset record. This data drives meter-based maintenance triggers. Ask whether the platform integrates with your telematics provider natively or requires custom API work.
API access. Even if you do not need custom integrations today, having API access means you can build them later. Check whether the API is RESTful, well-documented, and included in your pricing tier (some vendors gate API access behind enterprise plans).
Understand Total Cost of Ownership
Pricing pages show you the sticker price. Total cost of ownership (TCO) tells you what you will actually spend over two to three years. Build a TCO model with these line items.
Software subscription. Monthly or annual fee. Confirm whether the price is per asset, per user, or a flat tier. Model at your current asset/user count and at projected growth in twelve and twenty-four months.
Hardware. QR labels (one-off plus 10 to 15 per cent annual replacement for damaged or new assets). GPS tracker units and monthly data plans. Bluetooth beacons if applicable. Label printer if printing in-house.
Implementation. Some vendors charge for onboarding, data migration and initial configuration. Others include it. Clarify what is included and what costs extra. In-house time is a cost too: estimate the hours your team will spend on data cleanup, labelling and training.
Training. Is training included? Is it live or pre-recorded? Will the vendor train your field team on the mobile app, or only your admin users? Ongoing training for new starters is often overlooked.
Support. What level of support is included? Email only, or phone and chat? What are the support hours? For Australian teams, having support available in AEST/AEDT is a significant advantage over vendors operating on US Pacific time.
Add all of these up over a three-year period and compare. The cheapest subscription is not always the lowest TCO.
Run a Pilot
Never commit to an annual contract without running a pilot. A good pilot tests the system with real users, real assets and real workflows over two to four weeks. Here is how to structure one.
Choose one site or one team as your pilot group. Pick a group of 50 to 100 assets and five to ten users. Include a mix of tech-comfortable and tech-resistant people. If the resistant users adopt the system, everyone will.
Define success criteria before the pilot starts. Examples: 90 per cent of pilot assets have been scanned at least once. Average scan-to-checkout time under 10 seconds. At least one maintenance work order created and completed. At least one audit completed with reconciliation report generated. Net Promoter Score from pilot users above 7 out of 10.
Collect feedback formally. Send a short survey at the end of week one and at the end of the pilot. Ask: what worked well, what was frustrating, what is missing? Meet with the pilot team in person if possible. Their feedback will surface issues that demos never reveal.
Start a free trial with MapTrack to run a pilot on your own assets before committing.
Decision Checklist
Use this checklist as the final gate before you sign. Every item should be a confirmed yes.
Requirements coverage. Does the platform meet every must-have requirement in your brief? Have you verified this in a live demo using your own data, not the vendor’s sample data?
Mobile app quality. Have field workers tested the app on their actual devices? Did they find it fast and intuitive? Does it work reliably offline?
Pilot results. Did the pilot meet your success criteria? Did pilot users recommend the system?
Total cost. Have you built a three-year TCO model including software, hardware, implementation and support? Is it within budget?
Integration confirmed. Have you verified that required integrations (accounting, ERP, telematics) work or are on the vendor’s roadmap with a committed delivery date?
Data ownership. Can you export all data (asset register, maintenance history, compliance records, photos) at any time? Is the export format open (CSV, JSON)?
Contract terms. Is the contract monthly or annual? What is the cancellation policy? Are price increases capped?
Support and training. Is onboarding included? Are support hours compatible with your timezone? Is there a dedicated account manager for the first 90 days?
If every answer is yes, you have done the work. Make the decision confidently, assign a project lead, and move into implementation. The guide on 14-day QR rollout planning covers what comes next.
