TALOS
Field Notes · May 5, 2026 · Jason Keith

Moisture Readings From Yesterday Shouldn't Disappear

restorationmoisture-readingswater-damagedocumentation

Day one of a water damage job. Your lead tech sets up — dehumidifiers, air movers, moisture meter, thermal camera. He takes baseline readings. Kitchen subfloor: 42% MC. Living room wall cavity: 38% MC. Master bath: 55% MC. He deploys six dehumidifiers and twelve air movers.

He writes the readings on a form. Or texts them to the project manager. Or enters them into restoration software back at the shop.

Day two. Different tech shows up. Morning shift. He's supposed to take follow-up readings and decide if equipment stays or moves. But he doesn't have yesterday's numbers. They're on the other tech's clipboard. Or in a text thread he wasn't on. Or in software that's two logins deep and loading slowly on his phone.

So he takes his readings and guesses whether they're better or worse than yesterday. Or he calls the office. Or he calls the day-one tech and interrupts his current job.

The moisture readings from yesterday are the single most important piece of information for today's decisions. And they've disappeared into the space between two humans who work different shifts.

Why Restoration Is Different

Most trades show up, do the work, and leave. The job is done in a day. Maybe two.

Restoration jobs run days. Sometimes weeks. Multiple techs rotate through. Morning crew, evening crew, weekend crew. Each visit is a continuation of the last one — you're managing a drying process that happens over time.

That means every tech who shows up needs to know what the last tech found. Not just that they were there. What they measured. What they observed. What decisions they made.

Without that handoff, every visit is a fresh assessment instead of a continued process. Your tech isn't building on yesterday's work. He's re-evaluating from scratch. That wastes time, extends dry time, and costs you labor and equipment hours.

The Dehumidifier Doesn't Care Who Reads It

Here's the fix.

Your day-one tech takes his baseline readings. Before he leaves, he taps his phone to a chip on the dehumidifier. Records: Kitchen subfloor 42% MC. Living room wall 38% MC. Master bath 55% MC. Equipment deployed: 6 LGR dehus, 12 air movers. Access note: homeowner leaves key under mat.

Day two tech shows up. Taps the dehumidifier. Sees everything. Yesterday's readings. Equipment count. Access notes. He takes today's readings — kitchen 34%, living room 29%, master bath 44% — records them on the same dot. Done. Two taps total.

Day three tech — different guy again — taps and sees the full progression. Day one baselines. Day two follow-up. He can see the drying curve without anyone explaining it to him.

The dehumidifier doesn't care who reads it. It doesn't care if your day-one tech quit, called in sick, or got pulled to another job. The dot holds the data. The next tech gets the context.

The Adjuster Conversation

Here's where this gets expensive if you don't have it.

The insurance adjuster shows up on day five. He wants to know why you still have six dehumidifiers deployed. He wants to see the drying progress. He wants evidence that the equipment was necessary for the full five days — because if he can justify removing equipment on day three, that's two days of rental he doesn't have to approve.

Right now, you pull up your restoration software. You find the job file. You show him your daily logs — if your techs actually entered them. If the readings were recorded the day they were taken and not reconstructed three days later.

With on-equipment documentation, every reading is timestamped. GPS-stamped. Cryptographically signed by the tech who took it. The drying curve is built from verifiable daily records that were created on-site, in real-time.

The adjuster can see: Day one, 42%. Day two, 34%. Day three, 28%. Day four, 22%. Day five, 16% — just above the dry standard. Equipment stays. Documented. Undeniable.

That's not just good practice. That's how you protect your billing from adjusters who are incentivized to cut days.

Equipment Accountability

An average water damage job deploys $10,000-$20,000 in equipment. Dehumidifiers, air movers, air scrubbers. They go into a property and stay for days.

Where's the documentation that proves each piece of equipment was deployed, on-site, running, for the duration you billed?

Right now it's your word. Maybe a photo. Maybe a timestamp in your project management software.

With a dot on each dehumidifier, you have a documented deployment record. Tech tapped it when he set it up. Tech tapped it each day when he checked readings. Tech tapped it when he pulled it. Every interaction is a GPS-stamped record that the equipment was there, working, monitored.

When the adjuster asks "was this dehumidifier really on-site for five days?" you don't say yes. You show him five days of timestamped interactions. That's a different conversation.

Multi-Room Jobs

Big water loss. Three floors affected. Ten rooms being dried. Different areas at different stages. Some areas drying fast, some areas stalling.

Your tech walks into this job. He's supposed to monitor each area, decide where to redeploy equipment, identify areas that might have hidden moisture behind walls.

Without yesterday's readings per area, he's taking new readings and making decisions without baseline context. He might move equipment away from an area that's stalling because he doesn't know it was at 40% yesterday and 39% today. That's not drying. That's a problem.

With a dot in each monitoring zone — one per room, or one per affected area — the progression is visible. Tap the dot in the master bedroom, see three days of decline. Tap the dot in the kitchen, see a plateau. That plateau means something. Maybe there's trapped moisture. Maybe the equipment needs repositioning.

The dot doesn't interpret the data. It presents the history. Your tech makes the call. But he makes it with information instead of instinct.

What Your Techs Actually Want

Here's what restoration techs tell us they want: they want to show up to a job and know what they're walking into without making three phone calls.

They want to know what areas are being monitored. What yesterday's readings were. What equipment is deployed and where. Whether anything was flagged for attention.

That's not a management demand. That's a technician request. They want context. They want to walk in prepared instead of spending the first 30 minutes figuring out what's going on.

A two-second tap gives them everything the last tech knew. That's not surveillance. That's respect for their time.

Notes from the last tech for the next guy.


← All Field Notes

See How TALOS Works →