Construction Claims Power BI Case Study | $1.2M Savings | Nexus Data Works
Case Study — Construction

From claims chaos to a single source of truth — $1.2M saved, 37% faster resolution

A $100M contractor had claims in Excel, schedules in Primavera P6, and costs in Sage 300 — no unified view, no executive visibility, and disputes compounding across projects. We built a four-tab Power BI Claims Dashboard that changed how their leadership team manages risk.

🏗 Construction Procore · Primavera P6 · Sage 300 · Power BI Decision-First BI Framework™
$1.2M
Annual savings delivered
37%
Faster claims resolution (120→75 days)
80%
Executive dashboard adoption
10×
ROI on pilot engagement

A $100M contractor flying blind on claims exposure

Every week, project managers at this mid-sized general contractor were exporting Excel files from Procore, reconciling schedule updates from Primavera P6, and cross-referencing cost entries in Sage 300 CRE. By the time those numbers reached the executive team, the data was already a week old.

With an average dispute value of $42M industry-wide and resolution timelines stretching past a year, the stakes were high. This firm had no single view of how many claims were open, which projects were at highest risk, or which subcontractors were responsible for the most unresolved disputes.

Strategic decisions were being made without a clear picture of total exposure. The executive team couldn't answer a basic question: “How much is at risk right now, and where?”

📈
No real-time claims visibilityClaim logs in Excel, updated manually, out of date by the time executives reviewed them
🔌
Fragmented data across three systemsProcore, Primavera P6, and Sage 300 CRE had no integration — reconciliation was a manual weekly task
😵
No accountability layerNo way to see which subcontractors or project types drove the most unresolved disputes
120-day average resolution timeWithout early visibility, claims aged into formal disputes before leadership could intervene
State Before Engagement
Avg resolution time120 days
Report preparation time~5 hrs/week per PM
Executive dashboard adoptionNear zero
Data sources unified0 of 3
Claims visibilityExcel only
Subcontractor accountabilityNot tracked
Avg claim age at escalation>90 days

Every metric mapped to an owner, a question, and a decision

Before building a single visual, we defined the KPI framework. Every metric has an owner, a data source, a refresh cadence, and a business question it must answer. Dashboards without this foundation become shelfware.

KPIBusiness QuestionOwnerData SourceRefresh
Total Claims (Pending vs Settled)How many open claims, and what’s the trend?Project ControlsProcore Claims LogWeekly
Total Claims Amount ($)What is our total financial exposure?Finance ManagerSage 300 CREWeekly
Average Resolution TimeAre we resolving faster or slower over time?Risk ManagerClaims Log + ScheduleMonthly
Claims by Responsible PartyWhich subs or GC actions are driving disputes?Claims AnalystProcore + P6Weekly
Pending >90 Days (Count + $)Which claims are about to become formal disputes?Risk ManagerClaims LogWeekly
Claims by Project / LocationWhich projects carry the most concentrated risk?Project ControlsProcore + P6Weekly

Four-tab Claims Dashboard — built for every level of the org

Each tab answers a specific set of questions for a specific audience. Executives see exposure and trends. Managers track project-level detail. Analysts drill into claim-level data. Owners’ reps see accountability views. No tab is for everyone — each is designed for one decision.

Claims Insights Overview — Executive View
All ProjectsBy Region
Total Open Claims
47
▲ 6 from last month
Total Claims Amount
$3.8M
$2.1M pending
Avg Resolution Time
94 days
Target: 75 days
Settled This Month
12
▼ 18% faster than avg
Claims by Type
Delay
Change
Differing
Weather
Other
Claims by Responsible Party
42%
Subcontractor — 42%
Owner — 31%
GC — 27%
Top Projects by Open Claims Exposure
Proj-04 Warehouse
$890K
● HIGH
Proj-07 Office Fit
$660K
● MED
Proj-11 Mixed Use
$518K
● MED
Proj-02 Retail
$356K
● LOW
Proj-09 Industrial
$228K
● LOW
Claims Aging Buckets
>120 days 4 claims $487K
90–120 days 7 claims $753K
30–90 days 22 claims $1.4M
<30 days 14 claims $260K
Claims Trends — Manager View
VolumeAmount
Claims Filed (6mo)
31
Across 8 projects
Highest Risk Project
Proj-04
9 open claims, $890K
Avg Age (Open Claims)
68 days
Target <75 days
Resolution Rate
72%
▲ 14pts YoY
Claims Volume & Amount by Month (6-Month Trend)
Jan
Feb
Mar
Apr
May
Jun
Volume (count)
Amount ($K)
Avg Resolution Time Trend — Days (6-Month)
Target 75d
Jan
120d
Feb
115d
Mar
108d
Apr
110d
May
100d
Jun
94d
Now
88d
Claims by Project — Open vs Settled
Project Open Settled Exposure
Proj-04 9 3 $890K
Proj-07 6 5 $660K
Proj-11 5 7 $518K
Proj-02 3 8 $356K
Others (4) 24 18 $476K
Claims Deep Dive — Analyst View
All ClaimsPending
Oldest Open Claim
147 days
Proj-04 — Sub dispute
Claims >90 Days
11 claims
$1.24M exposure
Top Responsible Party
Sub-07
9 open, $640K
Top Projects by Open Claims Exposure
Proj-04 Warehouse
$890K
Proj-07 Office Fit
$660K
Proj-11 Mixed Use
$518K
Proj-02 Retail
$356K
Proj-09 Industrial
$228K
Drill-through enabled — right-click any project bar to view claim-level detail: Claim ID, type, status, filed date, responsible party, and age.
Action Plan — Executive Intervention View
PriorityBy Party
Pending >120 Days
4 claims
$487K at risk
Pending >90 Days
11 claims
$1.24M exposure
Sub Accountability
42%
of all unresolved
Resolved This Qtr
19 claims
▲ vs 12 last qtr
Top 5 Aging Claims — Immediate Action Required
ProjectClaim TypeResponsibleAgeAmountStatus
Proj-04DelaySub-07147d$340KEscalate
Proj-07Change OrderOwner131d$290KEscalate
Proj-04Differing SiteSub-12118d$180KEscalate
Proj-11WeatherGC97d$148KMonitor
Proj-02DelaySub-0392d$112KMonitor

10 weeks from fragmented spreadsheets to live executive dashboard

We use a staged approach — prove value early, scale once ROI is confirmed. The first deliverable lands in week 5. By week 10, executives have verified results and a sponsor-ready ROI summary.

Weeks 1–2
Align & Define
Align on decision questions and delay type definitions
Confirm systems of record (Procore, P6, Sage 300)
Nominate data owners and draft governance note
Define coding standards and refresh cadence
Deliverable
Decision matrix · Data ownership matrix · Governance note
Weeks 3–5
Build Semantic Model
Build star schema in Power BI
Land schedule extracts, cost ledgers, field logs
Create Claims Fact with key dates (filed, submitted, resolved)
Implement Row-Level Security by role
Deliverable
Clean star schema · Claims Fact table · RLS security model
Weeks 6–8
Design & Deploy
Design executive overview (exposure, aging, hotspots)
Build prioritized action lane with owners and due dates
Add drill-through for claim-level detail
Instrument adoption tracking (who views what, when)
Deliverable
Executive dashboard · Drill-through views · Adoption reports
Weeks 9–10
Verify & Scale
Close-out sprint on 5 oldest, highest-value claims
Document cycle time reduction with before/after data
Gather stakeholder feedback and refine
Prepare sponsor-ready ROI summary
Deliverable
Before/after impact summary · ROI snapshot · Sponsor presentation

What changed for the executive team

$1.2M
Annual Savings
Combined from reduced dispute resolution costs, faster close cycles, and avoided margin erosion across active projects
37%
Faster Resolution
Average claims resolution dropped from 120 days to 75 days — early visibility enabled intervention before claims became formal disputes
80%
Executive Adoption
From near-zero engagement with existing reports to weekly dashboard use by the full executive team — because the data finally answered their questions
80%
Faster Reporting
Report preparation time dropped 80% across project managers — 10 PMs reclaimed ~40 hours per week previously spent on manual reconciliation
Before
Claims tracked in Excel, manually updated weekly
No unified view across Procore, P6, and Sage 300
120-day average resolution — disputes compounding
Near-zero executive dashboard adoption
No visibility into which subcontractors drove disputes
~5 hrs/week per PM on manual report preparation
After
Real-time claims dashboard with weekly automated refresh
Single source of truth across all three source systems
75-day average resolution — early alerts prevent escalation
80% executive adoption — used in every weekly review
Subcontractors account for 42% of unresolved claims — now tracked
Reporting time down 80% — 40 hrs/week returned to project work

Why this engagement delivered — and why most don’t

Most BI projects fail because they start with the tool. We start with the business outcome, map every KPI to a decision, and only then open Power BI. The Decision-First BI Framework™ is the difference between a dashboard that gets adopted and one that collects dust.

1
🎯
Define the Business Outcome
We started with the executive question: “How much is at risk, and where?” — not the data model.
2
👥
Map Personas to Decisions
Separate views for executives, managers, analysts, and owners’ reps — because their decisions are completely different.
3
📊
ETL Before Visuals
Built the star schema in Power BI first — star model over flat tables, aggregations for performance, RLS for secure access.
4
📈
Prove ROI Early
Pilot in weeks 1–5 with existing data. Measured hours saved before committing to full production build.
Start Your Engagement

See what a Decision-First approach changes for your projects

Start with a free Power BI Precision Audit™ — we’ll map your current reporting environment, identify your highest-ROI opportunities, and show you exactly what a claims dashboard would change for your executive team.