A restoration profitability dashboard earns its place on your wall when it shows job-level gross margin after labor, equipment, and subs—not when it paints a company-wide chart in green. For water, fire, mold, and storm operators in 2026, the useful view is one row per job at close (or at a defined milestone), built from the same hours, equipment logs, and Xactimate export your billing team already fights over. If the number cannot survive a concurrent water loss and a rebuild on the same crew, it is a report, not an operating system.
Fields that must exist at job close
Close is a decision point, not an accounting fiction. Before a PM marks a job complete in your CRM or job tracker, the dashboard row should carry enough structure that finance, supplements, and field leads argue about interpretation—not about missing data.
Minimum close-out row (operator checklist)
- Gross margin after direct costs: Revenue recognized (or expected) on the claim file minus labor burden, equipment cost (owned depreciation or rental invoices), subcontractor and supplier invoices posted to the job—not rolled into overhead.
- Estimate vs supplement in line items: Original Xactimate total versus approved supplement total, ideally at line-item granularity so a cut on drying equipment days shows up as margin erosion on that job, not as a vague “write-off.” Use your installed price list when reconciling; a category map like the one in our Xactimate line-item cheat sheet for restoration estimators helps estimators and ops speak the same language when the dashboard flags a mismatch.
- Labor hours vs estimate: Crew hours booked to the job compared to hours implied by production rates on the estimate (mitigation labor pools, demo, contents manipulation). A ratio above 1.0 is not automatically failure—Category 3 containment or after-hours emergency work can justify it—but unexplained overrun is where margin dies quietly.
- Equipment hours and asset identity: Dehumidifier, air mover, scrubber, and generator days or hours with serial or asset tags where your process tracks them. Fuel type or power source matters when you later tie runtime to carbon records.
- Sub and supplier cost timing: Dumpster hauls, emergency board-up subs, asbestos or environmental vendors—invoiced and allocated to the job before the customer invoice or carrier billing packet leaves the building. Costs that land in QuickBooks after month-end close make the dashboard lie at job close.
- Supplement-cycle status: Open, submitted, partially approved, closed, or denied—with dates. Margin at close should be labeled provisional when material supplements are still in flight.
- Documentation-to-approval lag: Days from first structured photo set (or first visit) to carrier approval on the scope you are dashboarding. That lag is cash and carrying cost, not a vanity KPI.
- Concurrent load: Active jobs assigned to the same PM or lead tech during this job’s peak week. Multi-location shops often lose margin through dispatch stacking, not through the estimating platform brand.
Platform names—DASH, Albiware, PSA, Xcelerate, and others— differ in whether these fields are native or require Xactimate / XactAnalysis export plus manual job costing. The evaluation question is simple: is the margin number computed from exports and field time, or from a budget someone typed once at kickoff?
How to read margin by job type
Job type is not a color label on a map pin. Water, fire, mold, and storm losses carry different cost curves, supplement behavior, and failure modes. A dashboard that averages them teaches you nothing except which division subsidizes the others.
Water (mitigation-heavy)
Water jobs often compress margin in the first 48–72 hours: extraction labor, equipment density, and repeat visits before the adjuster assigns. Margin looks acceptable on paper when equipment days on the estimate match logs; it collapses when Day-1 documentation was thin and supplements arrive late with denied lines. Pair dashboard review with field discipline from the first 24 hours water loss operator’s checklist—jobs that skip pre-demo moisture maps and equipment placement photos frequently show labor-over-estimate with revenue still stuck in “supplement pending.”
Fire and smoke
Fire losses spread margin risk across phases: emergency board-up, structural clean, seal, and often contents. Labor hours can look efficient while subs (pack-out vendors, duct cleaning, odor contractors) blow the job row if their invoices post late. Trap: approving margin at mitigation complete when rebuild or contents scope still sits on a separate estimate with no costs attached yet.
Mold
Mold work ties margin to containment duration, clearance expectations, and carrier scrutiny on overlap between demo, clean, and treatment lines. Jobs that mix mold scope into a water file without splitting job costing blur margin—water looks profitable while mold labor rides untagged. Dashboards should either split phases or tag cost codes so mold hours do not hide inside a generic “mitigation” bucket.
Storm / CAT-style volume
Storm work introduces throughput and pricing pressure: standardized scopes, compressed documentation windows, and temporary labor. Margin by job type here often diverges from single-loss water because equipment churn and lodging or per-diem costs may not flow back to the job row if your system defaults them to a CAT overhead pool. If your dashboard cannot allocate those costs to individual files, storm margin will read artificially high until finance true-ups the month.
The supplement-cycle lag trap
The dashboard row you snapshot at job close is a photograph of belief: belief that approved revenue matches filed scope, that denied lines are final, and that no new supplement will reopen the file. Carriers routinely approve supplements weeks after the crew demobilized. When that happens, margin at close was wrong—not because anyone lied, but because revenue and cost sat in different time windows.
How the trap shows up: Labor and equipment are fully booked at close; gross margin reads at or above target. Three weeks later, a supplement adds drying days and demo; alternatively, an auditor cuts equipment lines on the original estimate. Your close-out dashboard still shows the old margin unless someone reopens the job economically. Cash arrives late; costs were real-time.
Operating rules that reduce distortion:
- Tag every close-out row with provisional vs final margin based on supplement status. Provisional is the default when any supplement is open or when carrier approval on the primary estimate is less than a defined internal threshold (your policy, not an industry standard).
- Maintain a reopened job workflow: when a supplement posts or an estimate version changes after close, the job row updates margin and stamps a “reopened” reason (supplement approved, audit reduction, change order). Without reopen semantics, year-to-date margin reports double-count wins or hide losses.
- Separate earned margin (costs incurred vs revenue approved on the file today) from collected margin (payments received). Restoration businesses live in the gap; the dashboard should show both when supplement lag is material.
- Align estimate versions to dashboard snapshots: store which Xactimate export or claim version the margin row used. When version 3 replaces version 2, margin should recompute from version 3, not patch manually in a spreadsheet cell.
Shops that treat supplement approval as “free upside” often discover at quarter-end that labor overruns on closed jobs were never offset because supplements landed on different job numbers. Fixing the lag trap is a data model choice, not a pep talk for estimators.
Job costing and Restoration Carbon Protocol (RCP) records
Equipment runtime hours, fuel or energy type, material quantities, and trip counts already live in serious job-costing workflows—because margin depends on them. The Restoration Carbon Protocol asks for operational quantities drawn from the same work: dehumidifier and generator hours, miles or trips where applicable, material volumes where your methodology requires them. A profitability dashboard that captures those fields at job close is most of the way to a defensible carbon record without a parallel shadow spreadsheet.
Practical linkage for operators:
- Single source for runtime: If air mover and dehu days on the invoice match asset tags in the job file, that same table can export to RCP-style reporting. Forcing crews to re-key hours into a “sustainability form” guarantees gaps.
- Material quantities from scope: Line-item quantities on approved scope (bagged debris, disposed drywall square footage where documented, cleaning product usage if your protocol tracks it) tie revenue defense to carbon-relevant mass or volume without inventing new measurements—provided field documentation supports what was billed.
- Margin-first, carbon-second: When margin review catches missing equipment days, you fix billing and carbon at once. When margin review ignores runtime because “we don’t bill those days,” carbon records will be weak for the same reason.
None of this replaces a formal RCP methodology document or third-party verification where your program requires it. Carbon-ready data is job-cost data with discipline—not a second data entry pass for PMs.
Building the dashboard without fantasy numbers
Start from exports and timecards. Pull carrier-approved totals into the job row, map labor to the same job number techs use in the field, and block close until subs are allocated or marked “pending” with a provisional flag. If the software only shows company-wide gross profit, extend the job object before you buy another charting tool.
Frequently asked questions
What fields belong on a restoration profitability dashboard at job close?
At minimum: job-level gross margin after labor, equipment, and subcontractor costs; original estimate versus approved supplement totals with line-item detail where possible; labor hours booked versus estimate-implied hours; equipment runtime with asset identification; supplement-cycle status and key dates; sub and supplier costs posted to the job; and documentation-to-carrier-approval lag. Optional but valuable: concurrent jobs per PM during peak load.
Why does gross margin look wrong weeks after I closed a water job?
Supplements and audit reductions often post after demobilization while labor and equipment costs were recorded in real time. If the dashboard snapshot at close treated revenue as final, later-approved or denied lines change true margin unless the job row reopens and recomputes from the current claim file. Label “provisional” margin when supplements are open.
Should water, fire, mold, and storm jobs share one margin target?
They can share a company goal, but not one blind average. Water is equipment- and documentation-sensitive; fire spreads cost across subs and contents; mold ties to containment duration and scrutiny; storm work may bury costs in CAT pools. Read margin by job type and cost-code tagging, not only company totals.
How do I connect job costing to Restoration Carbon Protocol reporting?
Use the same equipment runtime, trip, and material quantity records you require for margin. Dehumidifier and generator hours logged for billing or internal costing can feed carbon quantities when your RCP methodology maps those inputs. Avoid duplicate entry; fix missing runtime in job costing first.
What is the supplement-cycle lag trap?
It’s the mismatch between costs booked at job close and revenue recognized when supplements approve or when auditors cut lines later. The dashboard showed healthy margin at close because future revenue and retroactive denials were not in the row. Handle it with provisional/final flags, “reopened” jobs, and estimate version stamps.
Can platform dashboards replace Xactimate line-item reconciliation?
Only if the platform ingests claim exports and field hours into the same job key. A manually typed budget at kickoff will not survive supplements. Reconcile estimate lines to documented scope—category familiarity from estimator cheat sheets and field checklists reduces denials that show up later as margin noise.
Leave a Reply