Everything the work needs recorded
Grouped by the moment in the job rather than by module, because that is how a restoration business evaluates software. Nothing here is on a roadmap unless it says so.
First response
The visit where the claim is won or lost.
- Open a loss in under a minute
- Address, customer, cause and category. The property elevation resolves automatically from the address, because every psychrometric figure afterwards depends on it.
- Category and class on the record
- IICRC Category 1 to 3 and Class 1 to 4 captured at the outset, where they drive the drying plan and the equipment justification.
- Before-photos enforced
- A first visit cannot be closed without before-photos on every affected room. Overridable with a reason, which prints on the package, because a silent override is the same as no requirement.
- Authorisation signed on site
- Work authorization and certificate of completion captured as e-signatures against the job, with time and device recorded.
Measurement
The part most software leaves to the technician and a calculator.
- Psychrometrics computed
- Enter temperature and relative humidity. Specific humidity in grains per pound, dew point, vapor pressure and grain depression are derived from the published ASHRAE formulations.
- Altitude-correct, always
- Air pressure falls with elevation and takes specific humidity with it. The property elevation is resolved and stored, and a reading is refused rather than computed against a sea-level assumption.
- Fixed monitoring points
- The same designated spots measured every visit, so the series is comparable day to day rather than a collection of one-off numbers.
- Dry standard and drying goal
- An unaffected reference material is measured alongside the affected ones, so "dry" is a measured comparison within the S500 tolerance rather than a judgement call.
- Dehumidifier performance
- Grain depression across intake and exhaust, with a plain reading of whether the unit is working, marginal or doing nothing. A negative result is flagged as swapped probes rather than printed as fact.
- Corrections that leave a trail
- A wrong reading is superseded, never overwritten. Both rows survive with who changed it and why, because a record that can be silently altered is worth less in a dispute.
Evidence
Photographs and logs, captured where there is no signal.
- Offline-first capture
- Everything works in a crawlspace with no bars. The device holds the record until the server confirms it, and a retry never creates a duplicate.
- A sync queue you can read
- Every item is pending, uploading, synced or failed with a stated reason. No silent failure state, and the office is alerted when something has been waiting too long.
- Photos tied to rooms and visits
- Before, during, after, meter shots and documents, each attached to the room and the visit it belongs to rather than dropped in one pile.
- Bulk import
- Drag a folder in from a desktop. Moving photographs one file at a time is not a workflow.
- Location privacy by default
- Capture coordinates are a customer home address in disguise. They are never written into the EXIF of anything exported or shared.
Equipment and cost
The part that quietly decides whether the job made money.
- A deployment log, not an inventory
- Each unit placed and removed against a job and a room, with timestamps. Equipment-days become arithmetic instead of a memory exercise at invoicing time.
- Still-on-site at a glance
- What is running where, right now, across every open job. Equipment left behind after a job closes is equipment nobody billed for.
- Unbilled equipment surfaced
- Days recorded but not invoiced are raised as an exception for a person to settle, rather than silently written onto a customer invoice.
The deliverable
What leaves your office and goes to an adjuster.
- Claim package
- The full record assembled into one document: scope, moisture map, every reading, equipment log, photographs and signatures. Kept as a file with a checksum, so what was sent on a given day stays retrievable exactly as sent.
- Scope export
- The measured scope exported for estimating, so the estimate is built from the documented record rather than retyped from it.
- Share without an account
- A read-only link for an adjuster or a homeowner that shows the record without giving anyone a login.
Running the business
Optional. Off by default when a CRM is connected.
- Invoicing from the record
- Bill the job from the scope and equipment-days already captured, rather than rebuilding them in another system.
- Card and ACH payments
- Take a deductible on site or a balance at completion, with the payment recorded against the job.
- Deposits and progress billing
- Partial invoices across a long mitigation, with what has been collected visible on the job.
- Open API and webhooks
- Every record readable over a documented API, and signed webhooks for job, visit, reading and equipment events so another system can react.
See it against what you run now
The honest version, including what RescueWRX deliberately does not do.