Cycle time & inventory
Days from first notice of loss to first contact, to first payment and to closure, plus open claims aged in buckets. See where files stall by line, desk and adjuster before backlogs become complaints.
Claims operations reporting for risk-bearing and administering teams
Power BI Insurance Claims Dashboard for Carriers, MGAs and TPAs
A senior-built Power BI insurance claims dashboard that puts cycle time, severity, open inventory, reserve movement and loss ratio in one model your claims, finance and partner teams all read from — delivered from prepaid Flex hours, no in-house BI team required.
Representative dashboard — sample data
One claims picture, not five reports
Your claims system answers one file at a time
A Power BI insurance claims dashboard joins your claims system, policy and premium data, and partner loss runs into one refreshable model, so carriers, MGAs and TPAs see cycle time, severity, open inventory, reserve movement and loss ratio together — cut by line, program, adjuster, client and accident period without rebuilding spreadsheets every month-end.
Claims platforms are built to work a file: take the first notice of loss, assign it, set a reserve, pay, close. They are much weaker at telling a claims VP which desks are falling behind, which programs are deteriorating, or why incurred jumped this quarter. That operational, carrier-side view is what this build is for. If you run an agency or brokerage and your question is producer commission and book profitability rather than claims handling, our insurance broker commission and renewal dashboards are the better fit.
Metrics we wire up
- Cycle time
- Average severity
- Open inventory aging
- Paid & incurred development
- Reserve movement
- Loss ratio
- Adjuster caseload
- Reopen rate
Try us risk-free for 4 hours
If you’re unhappy within the first 4 hours of your block, we’ll refund you in full — no questions asked. Hours are deducted only for work you’ve reviewed and approved.
Common views
Reports we build most often for claims teams
Each is a starting point — we tailor the measures to how your organization defines a claim, a closure, a reopen and an accident period.
Severity & frequency
Average paid and incurred per claim, large-loss flags above a threshold you set, and claim counts against exposure or policies in force — trended so a shift in mix is visible early.
Reserve & development
Case reserve movement by period, paid and incurred development by accident year or quarter, and the largest reserve changes listed for review — the view finance and claims both argue from.
Loss ratio by program
Incurred losses against earned premium by line, program, state and underwriting year, so an MGA or carrier can see which business is performing before the next capacity or rate conversation.
Adjuster workload
Open files per adjuster, new assignments per week, diary compliance where your system records it, and closure rate — so supervisors rebalance desks on evidence rather than on who complains loudest.
Client & partner reporting
Secured, per-client views for a TPA’s accounts and standard loss-run and bordereaux-style summaries for an MGA’s capacity providers, generated from the same model instead of hand-built workbooks.
What does a claims dashboard track for a carrier, MGA or TPA?
It tracks how fast claims move, what they cost, and how that cost is developing. The core set is cycle time, open inventory aging, average severity, frequency, case reserve movement, paid and incurred development, and loss ratio — each sliceable by line of business, program, state, adjuster, client and accident period.
The emphasis shifts with your role. A carrier’s claims leadership watches inventory, cycle time and reserve adequacy across desks. An MGA with delegated authority needs program-level loss ratio and the reporting its capacity providers expect. A TPA lives on service commitments to each client — contact and closure timeliness, caseload, and clean client reporting — while the financial result belongs to the client. We build the same reliable foundation for all three and shape the pages around the decisions you actually make. Every measure is defined with you in writing before it is built, because “closed” and “reopened” rarely mean the same thing in two organizations.
Which claims KPIs belong on the first build?
Start with the measures that drive weekly management decisions: cycle time, open inventory aging, severity, reserve movement and loss ratio. The table below shows how each is typically calculated and who reads it. The exact definitions are agreed with you, and we do not publish benchmark targets we cannot source.
| KPI | Typical calculation | Primary reader | Common slices |
|---|---|---|---|
| Claim cycle time | Days from first notice of loss to closure (plus interim stages: first contact, first payment) | Claims managers, TPA client leads | Line, desk, adjuster, complexity tier |
| Open inventory aging | Count of open claims grouped by days open as of a snapshot date | Claims supervisors | Adjuster, office, client, claim type |
| Average severity | Paid or incurred loss divided by the number of claims in the period | Claims VP, underwriting | Line, coverage, state, accident period |
| Case reserve movement | Change in outstanding case reserves between two dates, split into new, increased, decreased and closed | Claims leadership, finance | Program, adjuster, large-loss flag |
| Incurred loss | Paid loss plus outstanding case reserves (IBNR added only where your actuaries supply it) | Finance, MGA principals | Accident year, underwriting year, program |
| Loss ratio | Incurred loss (with or without loss adjustment expense, as you define it) divided by earned premium | Executives, capacity providers | Line, program, state, underwriting year |
| Reopen rate | Claims reopened in the period divided by claims closed in a defined prior window | Claims quality, TPA client leads | Adjuster, claim type, client |
How do you model claims data so the numbers reconcile?
We build a star schema: claim, policy, adjuster, client and calendar dimensions around transaction-level payment and reserve facts. Modeling at the transaction grain, not the current-state snapshot, is what lets the dashboard show reserves and incurred as of any past date and reconcile back to your claims system and general ledger.
Most claims reporting breaks because it is built on a current-status extract: once a reserve changes, last quarter’s picture is gone. Keeping every payment and reserve transaction with its effective date lets development and reserve movement be recalculated for any period. We follow Microsoft’s star schema guidance for Power BI (opens in new tab) and write the DAX measures for paid, incurred, reserve change and loss ratio once, so every page uses the same definitions. Claims histories grow quickly, so larger books use incremental refresh (opens in new tab) to reload only recent periods. The modeling side of this work is covered in more depth on our data modeling and DAX service page.
How do MGAs and TPAs share reporting safely?
With row-level security on a single model. Each client, program or capacity provider is mapped to the rows it may see, so a TPA’s accounts or an MGA’s carriers open the same report and see only their own claims, while your internal team sees the whole book.
This replaces the common pattern of maintaining one spreadsheet per client and emailing it monthly, which is slow and easy to get wrong. Security roles are tested user by user before launch, and claimant-level detail can be limited to the people whose role requires it, with partners seeing aggregated counts and dollars. Our row-level security setup guide explains how the roles work. If your finance team also needs premium, expense and ledger reporting alongside claims, our finance and accounting dashboards connect to the same calendar and program dimensions.
How is this different from an agency commission dashboard?
An agency dashboard measures distribution: commission per producer, premium written, renewals and overrides. A claims dashboard measures what happens after a loss: handling speed, cost, reserve development and program loss ratio. The entities are claims, payments, reserves and adjusters, not producers and commission statements.
Agencies do see a claims ratio, but only as context for a producer’s book — they do not hold reserves or manage adjusters. Carriers, MGAs and TPAs do, which is why the model here starts at the transaction level of a claims system rather than at a carrier commission statement. The two can coexist in one organization, but they are different builds with different source data.
How does Flex Support keep the dashboard current?
Flex Support is prepaid blocks of senior-led Power BI hours that never expire. You email a request — a new program, a changed closure definition, a client report — and we return a scope and hours estimate before any work starts. Hours are drawn down only for work you approve.
Claims reporting changes constantly: a new program goes live, a capacity provider wants a different summary, a TPA signs a client with its own reporting requirements. A full-time BI hire is often more than a claims operation needs, so you bank hours and use them as those needs appear. Most tasks ship 3 to 5 business days after you approve the estimate. If you would rather have a named engineer working your backlog by the hour, see our page to hire a senior Power BI developer.
| Block | Hours | Rate | Total | Good fit for |
|---|---|---|---|---|
| Starter | 20h | $125/hr | $2,500 | A first cycle time and open inventory dashboard from one claims source |
| Growth | 40h | $115/hr | $4,600 | Adds reserve movement, development and loss ratio against premium |
| Power (best value) | 80h | $100/hr | $8,000 | Multi-source model, secured client or partner views, ongoing changes |
Pricing is our Flex Support labor rate, not Microsoft licensing. You hold your own Power BI licenses; we work inside your tenant, so you own the workspace, semantic model and credentials.
Built for claims teams like yours
- Regional and specialty carriers
- MGAs reporting to capacity providers
- TPAs serving multiple client accounts
- Self-insured programs and risk pools
- Claims teams without a dedicated BI analyst
3–5
business days, typical
Prepaid
hours, never expire
You
own everything
A first cycle time and inventory view fits a Starter block. See Flex pricing →
How it works
From claims extracts to a live operations view
- 1
Scope & define
Tell us the views you need and where claims, payments, reserves and premium live. We agree definitions for closure, reopen, severity and loss ratio, then send a scope-and-hours estimate before any work begins.
- 2
Model & reconcile
We build the transaction-level model and DAX measures, then reconcile paid, reserves and claim counts against your claims system and ledger totals so nobody disputes the numbers at launch.
- 3
Secure & launch
We publish to your workspace, schedule refresh, set row-level security by client, program or office, and hand it over. Banked hours stay ready for the next program or reporting request.
Representative perspective
Every month-end we rebuilt the same reserve and inventory spreadsheets by hand. What we wanted was one place where the claims team and finance looked at the same incurred number and could see what moved it.Claims operations lead, specialty carrier
Representative perspective
Our clients each wanted their own loss runs in their own format. A single secured model meant we stopped maintaining a separate workbook per account and started answering questions the same day.Account director, third-party administrator
See cycle time, reserves and loss ratio in one place
Tell us your claims system, where premium lives, and who needs to see what. We’ll scope the work and tell you the hours needed before anything begins — drawn from prepaid Flex hours that never expire, with no project minimums and no obligation.
FAQ
Claims reporting questions, answered
Any claims platform that exposes a reportable database, a replica, an API or a dependable scheduled extract. Core suites, homegrown claims databases and spreadsheet loss runs from partners can all feed the same model. We confirm the extraction route and the fields available in the scope estimate, before any of your hours are used.
No. Reserving is an actuarial and claims judgment, and we do not replace it. The dashboard reports the case reserves your adjusters set, how they move over time, and paid and incurred development by accident period. Where your actuaries supply IBNR figures, we load them so ultimate loss ratio views use their numbers.
Yes. Row-level security filters the same report by client, program or carrier, so each account sees only its own claims while your operations team sees the full book. That lets one model serve internal management and client reporting instead of maintaining a separate workbook for every client.
Most requests are delivered within three to five business days of your approval of the scope. Flex hours never expire: Starter is 20 hours for $2,500, Growth is 40 hours for $4,600, and Power is 80 hours for $8,000, with senior hourly work from $100. A first cycle time and inventory build usually fits one block.
Book a free demo
Get senior Power BI help, on demand
Tell us the task. We scope it, you approve, and a senior consultant delivers — typically in 3–5 business days. Prepaid hours that never expire.
- Prepaid hours from $100/hour — and they never expire
- Senior-led delivery — 20+ years on the Microsoft platform
- Typical 3–5 business day turnaround
- Full refund if you’re unhappy in your first 4 hours
The fastest way to reach us is the form — tell us the task and we'll reply within one business day.