A group principal can usually tell you last month’s gross for every store from memory. Ask the same person how many claims are open across the group right now, how much subrogation is sitting uncollected, or which rooftop has a deadline lapsing this week, and the room goes quiet. Not because nobody is working claims - because the numbers live in fifteen different places and never add up in one view. That gap is exactly what a multi-rooftop claims dashboard is supposed to close.
What is a multi-rooftop claims dashboard?
A multi-rooftop claims dashboard is a single view that rolls every open claim across all of a dealer group’s locations into one place - with status, owner, deadline, and recovery on each - so leadership can see the whole group’s claims exposure without asking fifteen stores for a report.
The key word is single. Most groups do not lack claims data - they have too much of it, scattered. Each store keeps its own spreadsheet, its own DMS notes, and its own idea of what “done” means. A multi-rooftop claims dashboard takes those separate piles and normalizes them into one live picture: every claim, tagged to the rooftop it belongs to, with the same fields on each. It is the difference between a group principal driving to every store to check the lot and standing in one place watching all of them at once.
This is a commercial problem, not a cosmetic one. The claims you cannot see are the ones that quietly cost you - and at a group, invisibility scales with the number of rooftops.
Why do store-level reports hide group problems?
Because a problem that is small at one store is invisible until you sum it across all of them. Each rooftop’s report looks fine on its own; the group-level total that would trigger alarm never gets assembled.
Say each of your ten rooftops writes off two loaner-damage claims a month and lets one subrogation file go cold. At the store level, that is a rounding error nobody escalates. Rolled up, it is thirty recoverable losses a month walking out the door - and no single store manager is ever confronted with that number, because no single store owns it. This is the same death-by-a-thousand-cuts dynamic we break down in how multi-rooftop groups lose money on claims.
A loss too small to escalate at one store, multiplied by ten stores, is a number that would get someone fired - if anyone could see it.
Store-level reporting also hides variance. When each rooftop reports its own way, you cannot tell the store that is genuinely clean from the store that is simply not logging its claims. A group dashboard makes both the totals and the outliers visible, which is the entire point of cross-rooftop visibility.
What are the five views a multi-rooftop claims dashboard should show?
Five: open claims by rooftop, deadlines coming due, open subrogation and recovery, body shop and cycle-time status, and claims aging. Together they answer where the exposure is, what is about to cost you, and which rooftop needs attention this week.
Open claims by rooftop
The base layer: every open claim, grouped by store, with a status and an owner on each. A group principal should be able to open one screen and see total open claims, how they split across rooftops, and which store is carrying more than its share. This is the view that turns “how are claims going?” into a number.
Deadlines coming due
Every claim with a clock - demand response dates, mediation windows, impound meters, filing deadlines - surfaced by how soon it lapses, not by which store it sits at. A deadline three days out at your smallest rooftop is more urgent than a routine claim at your biggest one, and the dashboard should rank it that way.
Open subrogation and recovery
Total recoverable dollars in flight across the group, by stage: identified, demand sent, negotiating, recovered. This is the view that exposes money you have already earned and not yet collected - and it only works when every rooftop’s recoveries feed one pipeline instead of ten notebooks.
Body shop and cycle-time status
Every vehicle in repair across the group, keyed by VIN, with days at the shop and any supplement pending. Cycle time is the group’s most-quoted stat and its least-tracked one; a live view of what is stuck where is how you actually move it.
Claims aging
The oldest open claims at every rooftop, sorted by how long they have sat untouched. Aging is the earliest warning sign of a leak - a claim nobody has moved in 45 days is usually a claim nobody owns, and it is almost always where a recovery or a deadline is quietly dying.
Why does cross-rooftop visibility change what you manage?
Because you can only manage what you can compare. Cross-rooftop visibility lets leadership rank stores against each other, spot the outlier, and move attention to where the exposure actually is - instead of trusting fifteen self-reports.
The moment claims from every rooftop sit in one view, three questions that used to be unanswerable become routine. Which store has the most claims aging past 30 days? Which rooftop recovers the smallest share of its subrogation? Where is cycle time drifting? None of these can be asked of a stack of separate spreadsheets, because there is no shared definition and no shared total. All of them are one filter away in a dealer group dashboard built on one data model.
Visibility also changes behavior at the store. When a rooftop manager knows their open-claim count and recovery rate sit next to nine peers on a screen leadership actually looks at, the aging claim gets worked. The dashboard is not just a reporting tool - it is the accountability the group was missing. That same leverage is why recovery rate climbs once it is measured honestly, which we cover in how to improve your subrogation recovery rate.
How does a claims roll-up actually work?
A claims roll-up works by tagging every claim to its rooftop at intake and running all rooftops on one shared set of statuses, so totals and breakdowns compute automatically instead of being reconciled by hand each month.
A roll-up is only as good as the data feeding it. Two things have to be true. First, every claim has to be tagged to the rooftop it belongs to the moment it is opened - not sorted out later. Second, every rooftop has to use the same statuses and the same fields, so “open” means the same thing at store one and store ten. Get those two right and the group total is just a sum; get them wrong and you are back to reconciling spreadsheets at month-end, which is where most roll-up attempts die.
This is why a claims roll-up cannot be bolted onto a pile of store spreadsheets after the fact. It has to be built in from intake, on one platform, with the rooftop as a required field on every claim. When that is true, the deadline view, the recovery pipeline, and the aging report all draw from the same source - and the same deadline discipline extends to mediation and impound, which we lay out in claims SLA management.
How do you build a dashboard your rooftops actually use?
Build it on one shared intake so the data is clean by default, show leadership the five roll-up views, and give each rooftop a filtered view of only its own claims - so the same system serves the group and the store at once.
The dashboard that gets used is the one nobody has to maintain by hand. If a store manager has to export a spreadsheet and email it up every Friday, the roll-up is stale by Monday and abandoned by spring. The working model is the opposite: every rooftop runs its daily claims work in one system, tagged to its store, and the group dashboard is simply the unfiltered view of that same data. Nobody assembles anything. The roll-up is a byproduct of the work, not a separate task.
The practical build order looks like this:
- Put every rooftop on one intake with the store as a required field, so every claim is tagged from the first notice.
- Standardize statuses and deadlines across stores, so “open,” “demand sent,” and “overdue” mean one thing group-wide.
- Give leadership the five roll-up views; give each store a filtered view of only its own claims.
- Make the aging and deadline views the ones you check first, because they surface the leaks earliest.
A multi-rooftop claims dashboard is not a nice-to-have report. It is the difference between running a group’s claims and hoping fifteen stores are running them for you. It is also, at VIP Auto Group, part of how a ten-rooftop group cut claim cycle time in half - by making every open claim, deadline, and recovery visible in one place instead of fifteen. To see the roll-up on your own claims, look at ClaimsPointe claim tracking or request a demo and bring a few open claims from two or three rooftops - we will show you the group view.
Frequently asked questions
Dana Whitfield
Head of Claims Operations, ClaimsPointe
Dana spent over a decade running claims and fixed-operations desks across multi-rooftop dealer groups before joining ClaimsPointe. She writes about the operational side of dealership claims - the deadlines, recoveries, and hand-offs that decide whether a claim costs you money or earns it back.