Fleet Mileage (Quick Chart)
Overview
- Column chart, the first of the two chart types the Quick Chart web part offers, rendering miles driven by vehicle
- Pie chart, the web part’s second chart type, added as a separate Quick Chart web part on the same page so one dataset answers two questions at once
- Automatic value labels above every column, with the category names angled and the longest of them truncated when the web part runs out of horizontal room
- A value axis the web part scales and labels on its own, running here from zero to 75,000 in even steps
- Chart title plus custom X and Y axis titles, all typed straight into the web part property pane
- Pie slices labeled automatically with the category, its percentage, and the underlying value – built-in behavior rather than a setting to switch on
- Both charts read their source live and cap at fifty data points, the web part’s display ceiling; forty-six vehicles sit just inside it
Benefits
- Ranks the whole fleet by utilization in one visual, so the under-used vehicles are visible immediately
- Puts miles against fuel cost, which is where the case for replacing a vehicle gets made
- Makes the hybrid and EV saving concrete – similar mileage, a fraction of the fuel spend
- Turns a list operations already maintains into reporting, with no new system to buy or roll out
- Serves both the operations director and the fleet supervisor, because both charts come off the same list
- Reads the list live, so the chart moves as monthly mileage is entered
- Takes about five minutes to set up, with no code and nothing to license beyond Microsoft 365
Details
- Chart Types: Column chart, Pie chart
Common Questions About the Fleet Mileage Chart
What is this fleet mileage chart built with?
The Quick Chart web part, out of the box in SharePoint, pointed at a standard SharePoint list. There is no telematics reporting add-on, no Copilot license, and nothing to license beyond Microsoft 365. Both charts sit directly on a SharePoint page next to the list they read from – the kind of clean, maintainable reporting Greg Zelfond builds for operations teams.
What is included in this fleet mileage example?
A forty-six-row SharePoint list of vehicles, a column chart of miles driven by vehicle, and a pie chart of fuel cost. The column chart ranges from a trailer tractor at 71,230 miles down to a service cart at 4,380. The pie splits roughly 245,000 in fuel spend across the same forty-six vehicles.
Why are some vehicle names cut short on the chart?
Because forty-six long labels do not fit across one axis. Quick Chart angles them and truncates the longest rather than overlapping them. It is worth knowing before naming a column, since short, distinct labels read far better in a chart than a full asset description does.
What are the limits of the Quick Chart web part?
Four worth knowing. It draws column and pie charts only. It shows at most fifty items. The list needs one text column for the X axis and one number or currency column for the Y axis, or it will not appear as a data source. And it does no grouping or summing – one row becomes one data point, so the list must be pre-aggregated. At forty-six rows, this example sits close to that ceiling.
Should we use Copilot, the Quick Chart web part, or Power BI?
It depends on how much you need. The Quick Chart web part is the lightest option – one chart, pointed at a list, no setup. A Copilot-generated dashboard suits a full page with filters and several linked charts that move together. Power BI earns its place when data volumes are large, sources need joining, or row-level security and scheduled refresh matter.
Can Greg build this for our organization?
Yes – this is exactly the kind of work Greg Zelfond does. As an independent SharePoint consultant and Microsoft MVP, he sets up the underlying list, shapes the columns so the chart is worth drawing, and builds the reporting around the questions your leadership actually asks rather than the ones the data happens to answer. Reach out through the contact page.
