Key takeaways
- A transportation and corporate services company replaced disconnected fleet spreadsheets with a Power Apps fleet management system built in 7 business days.
- Drivers and maintenance staff log fuel, mileage and maintenance events from a phone or tablet. SharePoint stores the records, and Power BI turns them into one shared dashboard.
- Maintenance reporting became 60% faster, and operational visibility across the fleet rose by 50%.
- Operations, Logistics and Finance now work from the same figures instead of three separate sets of spreadsheets.

Power Apps fleet management replaces disconnected fleet spreadsheets with a mobile app for logging fuel, mileage and maintenance in the field, a SharePoint data layer and a Power BI dashboard shared by Operations, Logistics and Finance.
Fleet managers rarely lose sleep over big strategic decisions. They lose it over small things. A driver fills in a maintenance form wrongly, a fuel log never reaches the spreadsheet, or a vehicle misses its service window. Good Power Apps fleet management is about closing exactly those gaps.
This case study shows how we closed them for a transportation and corporate services company. If your vehicles, fuel and maintenance still live in separate spreadsheets, the same approach applies to you. The company needed one place for vehicle tracking, maintenance schedules, fuel logs and cost analytics. Instead, it had a patchwork of files that each team updated in its own way.
In this article
- Project snapshot
- The problem: a fleet tracked in disconnected spreadsheets
- How we built the Power Apps fleet management system
- The result: 60% faster maintenance reporting
- How to set up Power Apps fleet management: step by step
- The lesson: close the gap between the event and the record
- Need Power Apps fleet management without building it yourself?
Seven business days later, it had a mobile app for data capture and a Power BI dashboard. Together, they work as a command centre for the whole fleet.
Project snapshot
| Item | Detail |
|---|---|
| Industry | Transportation and corporate services |
| Solution | Power Apps fleet management system: mobile app, SharePoint data layer and Power BI dashboard |
| Tools | Power Apps, SharePoint, Power BI |
| Timeline | 7 business days |
| Departments | Operations, Logistics, Finance |
| Impact | 60% faster maintenance reporting; +50% operational visibility |
The problem: a fleet tracked in disconnected spreadsheets
Before the project, fleet data sat in separate Excel files across Operations, Logistics and Finance. Each department tracked what mattered most to it. However, nobody had a single, trustworthy view of the whole fleet.
Staff entered maintenance records by hand, often after the fact. As a result, the team tracked service intervals reactively instead of planning them. Someone also compiled fuel figures manually at the end of each month, so cost overruns usually surfaced weeks after they happened.
The root of the problem was a mismatch. A fleet is a moving, physical asset, yet the files tracking it were static and tied to a desk. Drivers and field staff needed a fast way to log information wherever they were. Meanwhile, managers needed a view that combined everything without someone merging several files first.
Without that visibility, maintenance can slip until a breakdown forces the issue. Fuel costs can drift upwards unnoticed, and Finance struggles to allocate vehicle costs across departments. Solving this meant rethinking the whole data flow, not just tidying up the reports at the end of it.

Still piecing fleet data together from separate spreadsheets at the end of each month? Tell us how your vehicles, fuel and maintenance are tracked today and we will map the options with you.
How we built the Power Apps fleet management system
We designed the solution as three connected layers inside the Microsoft Power Platform. Because every layer reads from the same data, nobody has to re-enter information between stages.
Mobile data capture with Power Apps
The first layer is a custom Power Apps app that runs on a phone or tablet in the field. Drivers, maintenance staff and logistics coordinators log vehicle status, fuel fill-ups, mileage and maintenance events as they happen. Previously, they pieced that data together from memory at the end of the week. Recording at the moment of the event closes the gap where fleet data quality usually breaks down.
SharePoint as the shared data layer
Behind the app, SharePoint stores vehicle records, maintenance history and fuel logs in a structured format. Both the app and the Power BI reports read from it.
This is a real shift from spreadsheet tracking, where one file acts as both the input form and the database. That set-up tends to break when several people edit at once. By separating data capture from data storage, we let multiple users log information at the same time without overwriting each other’s work.
One Power BI dashboard for three departments
The final layer is a Power BI dashboard connected to the SharePoint data. Operations, Logistics and Finance now share one view of fleet performance, and it refreshes automatically instead of someone rebuilding it each month. As new records arrive through the app, leadership can review maintenance schedules, fuel trends and costs without asking anyone to prepare a report first.
We also built for growth from the start. Fleets change: new vehicles arrive, new routes open and reporting needs evolve. On this set-up, adding a new vehicle category or a new maintenance field is a configuration change, not a rebuild.
The result: 60% faster maintenance reporting
The impact was measurable. Maintenance reporting became 60% faster, because data now flows from the field into the dashboard without anyone copying it across by hand. Operational visibility across the fleet also rose by 50%. Managers see vehicle status, costs and maintenance needs as the records arrive, not in a monthly snapshot that is already out of date.
Each department gained something specific. Operations has a current view of vehicle availability and condition. Logistics can plan routes and assignments with confidence in the data behind them. Finance, for its part, gets combined fuel and maintenance costs, which supports budgeting and supplier negotiation.
Because the whole fleet is visible in one dashboard, the team is far more likely to catch small maintenance issues before they become costly breakdowns. Similarly, it can look into fuel cost spikes within days rather than a month later.
The most valuable outcome is harder to measure. With Power Apps fleet management in place, the company now has a system of record for its fleet. It no longer relies on spreadsheets that only made sense to the person who built them. New staff learn one consistent tool instead of inheriting someone else’s spreadsheet quirks.
Sapphire Business Technology replaced a transport company’s disconnected fleet spreadsheets with a mobile Power Apps app, a SharePoint data layer and a Power BI dashboard in 7 business days, making maintenance reporting 60% faster.
How to set up Power Apps fleet management: step by step
You can apply the same structure to your own fleet, even without technical experience. These steps follow the same logic we used on this project.
- List what you need to know about each vehicle: status, mileage, fuel fill-ups and maintenance events. Next to each item, write down who sees it happen first, because that person should record it.
- Create three SharePoint lists: one for vehicles, one for maintenance events and one for fuel logs. Give every vehicle a unique ID and use that same ID in the other two lists.
- Decide where data entry happens. If one or two office staff update the records, a shared Excel table may do for now; if drivers or mechanics log data on the road, build a mobile app.
- Generate a starting app from your maintenance list in Power Apps. Then trim the form to the few fields a driver can fill in quickly.
- Connect Power BI Desktop to the three lists with the SharePoint list connector, and link the tables through the vehicle ID.
- Build one dashboard page per audience: availability and condition for Operations, assignments for Logistics, and fuel and maintenance costs for Finance.
- Publish the report and set a scheduled refresh. If managers review the fleet once a day, one morning refresh is enough; if they need updates during the shift, schedule several.
- When the business changes, add a column or a category to the relevant list rather than starting a new spreadsheet.
Test the whole chain with one vehicle before rolling it out. A single, complete record trail tells you more than a hundred half-filled rows.
The lesson: close the gap between the event and the record
Fleet tracking shows a pattern we see across logistics and asset-heavy businesses. Manual spreadsheets work for a while. However, they scale poorly once several people need to update the same data from different places.
The bottleneck is rarely a lack of data. Instead, it is the delay between something happening on the ground and that fact reaching a decision-maker. The same rule applies to equipment inventories and facilities maintenance, not only to vehicles.
Microsoft’s guide to creating a canvas app from a SharePoint list shows that Power Apps can generate a working app straight from a list. The layout adapts to phones and tablets, so a first version is quick to produce.
In our experience, though, the generated app is only the starting point. What makes Power Apps fleet management last is the data design behind it. Separate lists for vehicles, events and fuel, linked by one vehicle ID, let the dashboard trust every row.
Refresh timing matters too. According to Microsoft’s documentation on scheduled refresh in Power BI, a Power BI Pro licence allows up to 8 scheduled refreshes per day. For most fleet reviews that is plenty.
The bigger gain comes from recording events on time. After all, a dashboard that refreshes every hour still shows an old problem if the fuel log arrives a week late. Timely entry beats frequent refresh.
Need Power Apps fleet management without building it yourself?
The steps above give a small fleet a solid foundation. Larger operations, however, bring more users, more vehicle types and more reporting needs, so the design choices get harder. That is where an experienced team saves weeks of trial and error.
Our Power Apps and Power BI specialists build Power Apps fleet management systems like this one, from the data model to the final dashboard. If you want the same result without building it yourself, see our Power Apps development services and tell us how your fleet runs today.
Planning a fleet app for more users, vehicle types or reports? Send us a short description of how your fleet runs today and which teams need the data.
Frequently asked questions
What is Power Apps fleet management?
How long did the fleet management project take?
What results did the company see?
Why use SharePoint instead of a shared spreadsheet?
How often should the Power BI fleet dashboard refresh?
This case study was written by Sapphire Business Technology, drawing on its experience with 500+ clients and 2,000+ projects in Excel, Power Apps and Power BI.




