A connected operation, from first call to final report
Orva is in active development, shaped directly by restoration professionals — we don't have a customer result to report yet. What follows is a realistic walkthrough of what a connected operation looks like once water mitigation, equipment, documentation, and reporting share one system, not a specific company's measured outcome.
The starting point: familiar friction
Picture a multi-branch water mitigation company running the way most do today: jobs dispatched over text and a whiteboard, moisture readings written on paper in the field and typed up that evening, equipment tracked by whoever remembers which truck it went out on, and a report assembled by hand once the job closes — days after anyone can clearly recall which room needed what.
None of that is negligence. It's just what happens when connected work runs through disconnected tools. The office staff aren't careless and the technicians aren't cutting corners — everyone is doing their job reasonably well within a set of tools that were never designed to share information with each other.
Day one: the loss comes in
A call comes in for a supply-line break at a commercial property. Instead of a dispatcher relaying details verbally, the job gets created with the loss source, address, and authorization captured immediately, and the assigned crew has everything they need before they're even in the truck: prior job history at that address if there is any, the customer contact on file, and the loss details as reported by the caller.
The job, connected room by room
On site, the crew's photos, moisture readings, and equipment placements attach directly to the rooms they belong to. A dehumidifier scanned into the primary loss area shows up immediately in that room's record — not as a line on a separate equipment spreadsheet someone reconciles at the end of the week. The lead technician documents the category and class of the loss, and that classification carries forward into what the workflow expects for containment, PPE, and monitoring cadence for the rest of the job.
A complication, and how it gets caught
Two days in, a moisture reading in a secondary bedroom plateaus instead of continuing to trend downward. In a disconnected process, that's a data point on page four of a daily log nobody reviews until the job wraps. Here, the reading is compared against the room's drying target the moment it's logged, and the plateau gets flagged for the technician's next visit — equipment gets repositioned two days earlier than it otherwise would have, instead of being discovered as a surprise at the final inspection.
The first monitoring visit, and the ones after it
Each subsequent visit adds to the same room-level history instead of starting a new page. A technician who wasn't on the original visit — because schedules shift, people take days off, crews rotate — can see exactly what was measured last time, what equipment is already in place, and what the plan calls for next, without a handoff call to whoever was there before.
Customer and carrier communication along the way
The customer gets a progress update that reflects the same verified data the technician is seeing, not a generic status message. If an adjuster calls asking about drying progress in week two, the answer is a specific, current number pulled from the job record — not "let me check with the crew and call you back."
What leadership sees while the job is still open
A project manager overseeing several branches can see which crews are on site, which jobs need attention, and where drying progress is behind target — without a phone call, because the field data is already visible the moment it's captured. If this job's secondary bedroom is still behind target three days after the equipment reposition, that shows up as a flag on the operations view, not as something the PM finds out about when the job runs long.
Closeout and the report that's already built
By the time the job reaches dry standard, the moisture history, equipment log, and photos are already organized by room. The report isn't written from scratch the night before it's due — it's assembled from a record that was accurate the entire time the job was open. The two consecutive on-target readings required for drying certification are already documented, not something someone has to go verify happened.
Fewer disputes, because the record was built as the work happened instead of reconstructed afterward. Less time spent assembling reports, because they're already assembled. Faster payment, because nothing is missing when a carrier asks a question. These are the outcomes the model is designed to produce — not a specific measured result, since Orva doesn't have one to report yet.
What this would have looked like the old way
In the disconnected version of this same job, the secondary bedroom's plateau likely wouldn't surface until the daily logs got reviewed at closeout — if they got reviewed closely at all. The report would get assembled the night before it's due, from paper logs and whoever's memory of which photos went with which room. If a carrier later questioned the drying timeline, answering would mean reconstructing a sequence of events from scattered notes instead of pulling up a record that was already organized.
Where this stands today
Orva is in active development, built and refined alongside real restoration professionals. Their field experience helps shape the connected workflows shown throughout this scenario.
Help shape what a connected operation looks like
See how connected workflows create clearer operations and better outcomes.