📞 24/7 Emergency Call Line: (385) 247-9359

Real restoration jobs from True Day Water Damage Restoration: water damage, sewage and fire projects across South Jordan and the Salt Lake Valley, done by our own W-2 IICRC-certified technicians and backed by a 2-year transferable workmanship warranty. 5.0 stars from 41 Google reviews.

Call (385) 247-9359

Case Studies

These case studies document actual water damage restoration, sewage cleanup, and fire damage projects completed by True Day Water Damage Restoration in South Jordan and the surrounding Salt Lake Valley communities. Each case study includes the event timeline, the FLIR thermal imaging findings on arrival, the calibrated penetrating moisture meter baseline readings, the equipment deployment, the drying timeline, the insurance outcome, and the specific construction or material conditions that shaped the project. The specifics matter because vague statements like “quick response” and “complete drying” fail to convey the actual procedures and outcomes in homes resembling theirs.

True Day Water Damage Restoration is based at 11268 S 2865 W, South Jordan, UT 84095. Licensed Utah Contractor #960332-3505, IICRC Firm ID #927354-5258. Call (385) 247-9359.


Project Case Studies


True Day Water Damage Restoration | 11268 S 2865 W, South Jordan, UT 84095 | (385) 247-9359 | Utah Contractor License: #960332-3505 | IICRC Firm ID: #927354-5258

Were we your crew on a water-damage job?

If True Day did right by you, a 60-second Google review helps the next South Jordan homeowner trust us the way you did. Mention your technician by first name if you remember — it means a lot to the crew.

If something fell short, call Michael at (385) 247-9359 first — we would rather fix it than see it in a review and not know.

Leave a Google review →

About our case study library

A field library of real True Day jobs — so you can see what your situation actually looks like after we handle it.

23
Real jobs documented
6
Scope types covered
5
Cities represented
7
Year file retention

Browse by scope

  • Supply-line and plumbing failures — burst pipe, supply line, toilet overflow, refrigerator ice-maker, dishwasher
  • Appliance overflows — washing machine, refrigerator line
  • Weather-driven — ice dam, storm flood, sprinkler freeze
  • Hidden & mechanical — crawl space moisture, HVAC condensate, sump pump failure
  • Category 3 (sewage) — sewage backup basement
  • Fire + water combined — fire smoke water damage

Browse by city

  • South Jordan — our home market, 24/7 with 45-minute arrival guarantee
  • Riverton, Herriman, West Jordan — adjacent coverage, 45–75 minute arrival
  • Salt Lake City, Sandy — secondary coverage, call to confirm availability

What’s documented in each case

Every case study follows the same methodology rules — real jobs, first names only, no addresses, no faces without consent, scope language matches the actual IICRC Category drawn, day counts are the real days from arrival to equipment pull. The moisture-log file is retained for 7 years and can be shared with your insurance carrier.

If one of these cases looks like your situation and you want to talk through what we did, call Michael directly at (385) 247-9359. Where a customer agreed to be a reference, we can connect you.

About these case studies — honest framing

Every page in this section describes a type of water-damage loss we handle in the Salt Lake Valley — the pattern, the scope, the typical outcome — not a specific identifiable customer. We don’t fabricate specific customer stories, and we don’t attach homeowner names, addresses, or photos to scenarios they didn’t explicitly authorize.

Why we write them this way

Two reasons. First, privacy: homeowners experiencing a loss are rarely in a position to also co-author a public case study with their name on it. Second, honesty: the scope you’ll see on a job is driven by water category, affected area, and response time — not by a dramatic narrative. The scenario-type format shows you the pattern you’re actually likely to encounter.

Browse by scenario

Appliance / supply-line lossesWashing machine · Refrigerator line · Dishwasher · Water heater · Supply line
Winter / cold-weather lossesBurst pipe ceiling · Ice dam
Fixture / plumbing lossesToilet overflow · Sprinkler line
Basement lossesSewage backup · Sump pump failure · Basement storm flood · Crawl space
HVAC lossesHVAC condensate
Compound lossesFire + smoke + water combined
Have a loss that matches one of these?Call (385) 247-9359 — the scenarios tell you the pattern, we tell you the specifics on-site. 24/7/365 live-answered.

How we choose which jobs become published case studies

Not every job becomes a case study on this page. We publish a case only when it teaches a homeowner something useful about the pattern of loss, the mitigation choice, or the insurance interaction. If a case is just “pipe broke, we fixed it,” it doesn’t help anyone decide what to do, so it doesn’t make the cut.

The four questions a case has to answer before we publish it:
  1. What was the actual cause of loss (so a reader with similar signs can recognize it)?
  2. What was the decision point that mattered (dry in place vs. remove, repair vs. replace, who covered what)?
  3. What did the homeowner have to decide, and what information did they need to decide it well?
  4. What was the measurable outcome — days, scope, documented moisture reduction?

What we don’t publish

  • Cases that would identify the homeowner against their wishes — we ask permission for every case, and we honor “no” without question
  • Cases where the outcome depended on a factor the reader can’t reproduce (one-off supplier delays, unusual policy exclusions)
  • “Hero” stories where the lesson is really just “call fast” — those don’t help the decision; they’re marketing
  • Cases still in warranty window with pending questions — we wait until the full outcome is settled

Patterns we see across the published cases

  • Supply-line failures (toilet, washing machine, dishwasher) are the most common water loss we respond to — and they’re the fastest to mitigate when caught within hours
  • Basement intrusions during spring runoff or heavy summer storms are the most expensive to miss — the pattern is “we smelled something but it looked fine” and that’s when the hidden mold starts
  • Upstairs bathroom overflows are the most multi-level jobs — water finds its way down through two floors fast, and the drying scope grows accordingly
  • Sewer backups are the only ones where the insurance interaction is harder than the physical work — because most policies need the backup rider

Reading the cases helps you spot the pattern of your own situation before you call — and makes the first phone call more useful on both ends.

How we decide which jobs become case studies

Published case studies are a slice, not a highlight reel. The jobs we write up are chosen for teaching value, not for how impressive they look. Here is the editorial standard:

Common enough to be useful. If a scenario is a once-in-ten-years loss, documenting it doesn’t help the next homeowner. We prefer cases that reflect the losses we see most often — supply-line failures, drain backups, roof leaks, basement intrusion.
Decision-rich. A case study earns its place when it shows a trade-off: save vs replace, dry in place vs demolish, repair vs supplement. Jobs that run on rails without a judgment call don’t teach anything new.
Documented end-to-end. Arrival photos, moisture mapping, equipment placement, daily logs, completion photos — the full set. Jobs with gaps in documentation don’t get published, even if the outcome was good.
Homeowner consent. No case gets published without written consent from the property owner. Addresses are generalized to the city or neighborhood, and identifying photos are reviewed with the owner before posting.
Honest outcome. If a case had an avoidable mistake on our side — a miss on day-two moisture readings, a missed secondary leak — the case study says so. Published cases are not sales material.

The ratio: for every ten jobs we complete, roughly one becomes a published case study. Not because the other nine were disappointing — because the one chosen taught us or the reader something worth writing down.