For a multi-location operator, the hard part isn't any single metric — it's seeing all of them, for every branch, on one screen. This scorecard puts one headline KPI from every pillar against each branch, so fleet-buy, redeployment, and staffing decisions start from a single comparable picture instead of five separate exports.
What this report answers
The scorecard answers the regional owner's weekly question: how is every branch doing across the things that matter? Company KPI cards run across the top — Total Rental Revenue, Fleet Dollar Utilization, Fleet Time Utilization, Idle Capital, Collection Rate, Revenue per Available Unit — and below them sits the executive matrix with one row per branch carrying a headline metric from every pillar: revenue, both utilization rates, idle capital, collection rate, RevPAU, repeat-customer revenue, and maintenance cost % of revenue. One screen, the whole company.
The metrics that matter
Fleet Dollar Utilization is the headline profit driver — revenue per dollar of fleet — and seeing it per branch reveals which locations deploy capital best. The time-vs-dollar gap per branch is the diagnostic the scatter and clustered bar expose: a branch high on time but low on dollars is busy with the wrong (cheap or underpriced) fleet. Idle Capital by branch flags overstock, and Revenue per Available Unit ranks raw productivity. Every rate is a SUM-over-SUM ratio so branches stay comparable regardless of size.
Why the data is trapped
This is the report that's hardest to build by hand because it spans every system at once — utilization and contracts from the rental ERP (Point of Rental, Wynne, InTempo, Texada), acquisition cost and collections from QuickBooks — across multiple branches and months. Assembling one comparable row per branch from all of that is a multi-export, multi-tab spreadsheet exercise that goes stale immediately, which is why most multi-site owners never have a current single-screen view.
How to read it
Read the company cards for the headline, then scan the matrix down each column to rank branches: who's leading on dollar utilization, who's carrying the most idle capital, who's slow on collections. The branch-comparison scatter of RevPAU versus dollar utilization is the location leaderboard — top-right branches are your model; bottom-left are the turnaround or right-size candidates. Use the time-vs-dollar clustered bar to tell a demand problem from a fleet-mix problem before you move capital.
The sample uses fully synthetic, anonymized data — no real branches, fleet, or financials.
Metrics it tracks
| Metric | What it means |
|---|---|
| Total Rental Revenue ($) | SUM(rental_revenue) across all branches — top-line for the company. |
| Fleet Dollar Utilization % | DIVIDE(SUM(rental_revenue), SUM(fleet_acquisition_cost)) — company-wide revenue per dollar of fleet (the headline profit-driver metric). |
| Fleet Time Utilization % | DIVIDE(SUM(rented_days), SUM(available_days)) — company-wide share of time the fleet was on rent. |
| Idle Capital ($) | SUM(idle_capital) across branches — total fleet dollars not currently earning. |
| Collection Rate % | DIVIDE(SUM(amount_collected), SUM(invoice_amount)) — company-wide cash conversion. |
| Revenue per Available Unit ($) | DIVIDE(SUM(rental_revenue), SUM(available_units)) — fleet productivity yardstick across the company. |
Used by: Owner / regional ops manager wanting every branch's headline metrics on one screen for fleet-buy and staffing decisions
Frequently asked questions
What should a multi-site rental owner scorecard include?
One headline metric from each pillar, per branch, on one screen: total rental revenue, fleet time and dollar utilization, idle capital, collection rate, revenue per available unit, repeat-customer revenue %, and maintenance cost % of revenue. The point is comparability — every branch on the same metrics so capital and staffing decisions start from one picture.
Why compare time and dollar utilization per branch?
The gap between them diagnoses the problem. A branch high on time utilization but low on dollar utilization is busy with cheap or underpriced fleet; a branch low on both has a demand or overstock problem. Seeing the two side by side per branch tells you whether to re-price, redeploy, or right-size before you act.
Why is a multi-branch scorecard so hard to build manually?
It spans every system at once — utilization and contracts from the rental ERP, acquisition cost and collections from QuickBooks — across several branches and months. Assembling one comparable row per branch means multiple exports stitched in a spreadsheet that's stale the day it's done. A modeled report keeps it live.
Build this report on your own data
Clone this Rental yards template — describe it and we’ll generate sample data so you can try it free, or upload your own export. You get a fully modeled, branded Power BI project that opens in Power BI Desktop.
Use this as a template →