Fleet Management Software for Australian Trades and Transport: Built Around Your Jobs.
What to buy and what to build, how a custom system uses your GPS and telematics data, and what the NHVR publishes about chain of responsibility, work diaries and records.
Running vehicles is mostly paperwork around a moving asset: where is the van, who is driving it, is the next service due, did the driver finish the job and can you prove what happened if something goes wrong. Ready-made fleet tools handle the first part well. The trouble starts when your jobs, customers and compliance duties do not look like the tool's idea of a fleet.
Devvista is a software development company that builds custom fleet, vehicle and job management systems for Australian trades, transport and service businesses. This page explains what is sensible to buy, what is worth building, how GPS and telematics data connects, and what the National Heavy Vehicle Regulator publishes about chain of responsibility, work diaries and records. To discuss your fleet, tell us what you run and what keeps going wrong.
What to Buy and What to Build in Fleet Software
Vehicle tracking is a solved problem, so we rarely recommend rebuilding it. What differs from business to business is everything wrapped around the tracker. A useful rule: buy the hardware and tracking, build the workflow that is specific to you.
| Need | Usually bought | Worth building |
|---|---|---|
| Live vehicle location and trip history | A telematics provider with its own devices and app | A view that places vehicles next to your jobs and customers |
| Driver work and rest records | An approved electronic work diary or a written diary | Rostering and scheduling that respect the limits before the job is booked |
| Job dispatch and proof of delivery | A generic dispatch app if your jobs are simple | Dispatch with your own job types, checklists, photos and signatures |
| Service, registration and inspection reminders | Built into many fleet tools | Reminders tied to your depots, suppliers and approval rules |
| Reporting and costs per vehicle or job | Standard dashboards | Cost and margin by job, joined with your accounting data |
If a ready tool covers what you need, use it. We build when the gap is your own process, or when you are paying for several tools that do not share data. For the broader approach to deciding, see our custom software development page.
What a Custom Fleet and Job System Includes
A custom fleet system is usually a set of connected parts rather than one big screen. These are the modules we most often scope for trades, transport and service businesses.
- Job and dispatch board. Jobs with customer, site, required skills and vehicle, assigned and re-assigned on a map or list, with status updates from the driver's phone.
- Driver app. A mobile app for job details, checklists, photos, signatures and pre-start checks, working in poor reception. See our mobile app development page for how we build and publish these.
- Vehicle and asset register. Registration, service history, inspections, defects and who is responsible, with reminders.
- Telematics layer. Location, trips and vehicle data pulled from your tracking provider into your own system so one screen shows the whole picture.
- Compliance records. Driver, vehicle and consignment records stored in a way you can retrieve for an audit.
- Reporting. Utilisation, idle time, job completion and cost per job, sent to the people who act on them.
These pieces connect to accounting and customer systems. If you also manage quotes, invoicing and staff in one place, our business management software page shows how that fits together.
GPS and Telematics Integrations: Geotab, Samsara and Routing
Most fleets already have a tracker. A custom system reads from it instead of replacing it, which keeps the proven hardware and avoids a new device on every vehicle. We open the vendor's developer documentation before we promise anything, because capabilities and access differ.
| Source | What the documentation states | What it means for a build |
|---|---|---|
| Geotab | The API returns devices (vehicles) with their properties, supports retrieving trips for a vehicle, and supports consuming a feed of data (Geotab SDK concepts) | Vehicles, trips and a data feed can be pulled into your own system, subject to your account |
| Samsara | The developer site lists guides for authentication, webhooks (notifications when actions occur), and telematics integrations (Samsara developer overview) | Event-driven updates are possible. We confirm which endpoints your plan includes at scoping |
| Google Maps Platform | The Routes API computes routes and route matrices and can include traffic. The separate Route Optimization API assigns tasks and routes to a fleet and supports time windows, load limits and a cost model (Routes; Route Optimization) | Route planning for many vehicles and jobs can sit inside your dispatch board |
Other tracking vendors and plain GPS devices are possible too. We have not named vendors whose documentation we have not opened. Where a provider limits API access to certain plans or approved integrators, we tell you before you sign for the hardware, not after.
Chain of Responsibility: Who Is Covered and What Software Can Do
If your fleet includes heavy vehicles, the Heavy Vehicle National Law (HVNL) places duties on more than the driver. The NHVR explains that you are a party in the chain of responsibility (CoR) because of a function you perform, not your job title (NHVR parties in the CoR). It lists ten functions:
| Function | NHVR description |
|---|---|
| Employer | Hires a heavy vehicle driver |
| Prime contractor | Engages a self-employed driver under a service contract |
| Operator | Directs the control and use of a heavy vehicle |
| Scheduler | Arranges transport jobs or a driver's work and rest times |
| Consignor and consignee | Sends goods for carriage, or accepts goods delivered |
| Packer, loader, unloader | Prepares, loads or unloads goods |
| Loading manager | Runs premises where five or more heavy vehicles are loaded or unloaded daily |
The Primary Duty is to ensure, so far as is reasonably practicable, the safety of your transport activities: identify risks, assess them, and eliminate or minimise them. The NHVR also says you must not take actions that could influence drivers to speed or breach the HVNL, giving contract terms, financial penalties or rewards and preferential treatment as examples (NHVR Primary Duty).
Software cannot discharge a duty for you, but it can create the evidence and the guard rails. Schedulers can see a driver's hours when they assign a job. Dispatch rules can flag a load or timing that conflicts with your own policy. Records show what was known and when. We design those into the job board, and your safety adviser decides what your policy says. Whether a given vehicle is covered by the HVNL is for you to confirm with the NHVR.
Work Diaries, Fatigue Rules and Record Keeping
Fatigue rules are where a fleet system can save real effort, and where a wrong assumption is expensive. The points below are what the NHVR pages say when we read them. The NHVR notes that changes to the HVNL took effect on 1 August 2026 with transitional arrangements, so always check its current information before you set a rule in software.
| Topic | What the NHVR page says | Why it matters for software |
|---|---|---|
| Who keeps a work diary | A diary is needed for standard hours work more than 100 km from base and for Basic Fatigue Management, Advanced Fatigue Management, Alternative Compliance Hours and exemption hours (NHVR work diary) | The system needs to know which hours option each driver and run is on |
| Standard hours (solo) | Limits include 12 hours of work in any 24 hours, 7 continuous hours of stationary rest and 72 hours of work in any 7 days (NHVR work and rest hours) | A roster view can warn a scheduler before a job pushes a driver over a limit |
| Electronic work diaries | An EWD is an NHVR-approved device or system. Only technology providers developing an EWD must apply for approval, and operators can use an approved one without applying (NHVR EWD) | We integrate with an approved EWD rather than claim to replace one |
| Record retention | Records must be kept for three years after they are created, readable and accessible to an authorised officer (NHVR record keeping) | Storage, backup and search must support retrieval for the full period |
| Local area records | Local area records are completed within 24 hours of the day's work and given to the record keeper within 21 days (NHVR record keeping) | Reminders and overdue flags help drivers and the record keeper |
The NHVR register lists the approved EWD providers, 13 of them when we opened it on 10 November 2026 (EWD register). If you need an electronic work diary, choose from that register and check each system's certificate of approval for its conditions of use. Our system then reads from or sits beside it, so you keep one source of truth for hours and one for jobs. We do not offer an EWD, and we do not give compliance advice.
How a Fleet System Project Runs
A fleet system changes daily habits for drivers and the office, so it is delivered in stages that people can absorb.
- Walk through a normal week. How a job arrives, who assigns it, how the driver learns about it and where the information goes afterwards.
- Scope and proposal. The first release covers the one problem that costs you most, often dispatch or job records.
- Data check. Which tracking provider, which devices, which accounting system, and what each one allows through its API.
- Clickable design. Dispatchers and drivers try the screens before they are built.
- Pilot with a few vehicles. We usually propose a staging environment and a pilot with a small group before the whole fleet changes over.
- Roll-out and training. Short sessions for drivers and dispatchers, and a plan for the first weeks of questions.
- Handover. Documentation and accounts in your name.
Drivers are not office workers, so the app has to be quick, readable in a cab and usable with gloves or poor reception. We test on the phones your team already carries. Weekly demos and an NDA are usual if you want them written in.
When Devvista Is a Good Fit, and When It Is Not
| We are a good fit if | A ready fleet tool is probably better if |
|---|---|
| Your jobs, checklists and approvals do not fit a standard dispatch product | You mainly need tracking and basic trip reports |
| You pay for several tools that do not share data | One provider already covers location, jobs and hours well |
| You want job cost and margin joined with accounting | You need compliance features that an approved provider already supplies |
| You want to own the system and its data | You want the lowest set-up effort and accept the provider's way of working |
Tell us what you run today and we will say whether to keep it, connect it or replace part of it. Our case studies show delivered work across the company, and our AI automation page covers tasks such as report summaries and job paperwork that can sit on top. For a project in a specific city, see our software development in Sydney page, and go back to the Australia home page any time.
Straight Answers.
Tell us how your fleet and jobs run today
Describe your fleet, the tools you use now and what keeps going wrong. Book a call and we will say what to keep, connect or build.
- 30-minute online call
- Honest feedback on fit
- No obligation
- Book a call30 minutes online. Tell us what you want to build.
- Get a straight answerHonest feedback on fit and scope.
- DecideYou choose the next step once the scope is clear.