Why teams move to RescueWRX
Restoration documentation is a mature category, and most of it is good at photographs. The gaps show up later: in what the drying log can prove, in what the equipment cost, and in what happens when a claim is questioned.
The four that come up again and again
The numbers are right, but only at sea level
Specific humidity depends on air pressure, and air pressure depends on elevation. Software that assumes sea level understates every reading taken above it, on a document a carrier reads. RescueWRX resolves the elevation from the property and will not compute a reading without one.
Equipment is an inventory, not a log
Knowing you own forty air movers does not tell you that four of them ran for six days on one job. Without placement and removal timestamps tied to the job, equipment-days are reconstructed from memory at invoicing time, if at all.
Sync fails quietly
The single most common complaint in this category is photographs that sit unsynced for hours and are discovered missing at the worst moment. The fix is not a faster uploader, it is a queue the technician and the office can both read.
Documentation and billing never meet
The scope is documented in one system and invoiced in another, joined by a PDF. Nobody can answer what a job actually made. RescueWRX can bill from the record it captured, or stand aside and let your CRM do it.
Side by side
No product names. If you already use something, you know which column it sits in better than we do.
Specific humidity computed for you
Typically
PartialOften typed in by hand, or left as relative humidity
RescueWRX
YesASHRAE formulations, from temperature and humidity
Corrected for the altitude of the property
Typically
NoSea level assumed, which is wrong everywhere above it
RescueWRX
YesResolved from the service address, and refused if unknown
Equipment placement and removal timestamped
Typically
PartialAn asset list, with no link to the job or the dates
RescueWRX
YesPer job, per room, so equipment-days are arithmetic
Sync state you can actually read
Typically
NoItems can sit unsynced with no visible state
RescueWRX
YesPending, uploading, synced, or failed with a reason
Bulk photo import from a desktop
Typically
NoCommonly one file at a time
RescueWRX
YesDrag a folder in
Before-photo completeness enforced
Typically
NoA reminder at best
RescueWRX
YesA gate, with a recorded override when genuinely needed
Invoicing and payments without another system
Typically
NoDocumentation only; billing lives elsewhere
RescueWRX
YesBuilt in, and switched off when a CRM is connected
Priced by jobs per year
Typically
YesA busy season costs more, or forces a tier upgrade
RescueWRX
NoFlat. Volume is not a billing event
Open API and outbound webhooks
Typically
PartialLimited surface, often without the field data
RescueWRX
YesDocumented, with signed webhooks for every event
“Typically” describes what is common across the category, not any one product. Several tools do some of these well. The point of the table is which ones tend to be missing together.
What we are not
Being specific about the edges is more useful than claiming everything, and it saves you a trial that was never going to fit.
Not a dispatch and scheduling platform. If you run a large mixed-trade operation, keep the system that schedules it and connect this to it. Standalone mode is built for restoration-first businesses, not to replace a full field service suite.
Not an estimating package. We produce the scope and the measured record an estimate is built from, and export it. We do not price line items against a carrier’s list.
Not 3D capture. Photographs, moisture mapping and room geometry, done properly. If you need a navigable 3D tour, that is a camera and a different product.