The seven-stage restoration workflow, and where it leaks office time.

Restoration company workflows in 2026 sit on a wide spectrum. At one end, a small operator is still running on pen and paper, a yellow legal pad on the dispatcher's desk and a folder cabinet for completed jobs. At the other end, a regional company has stitched together a six-platform stack with API integrations and middleware. Most mid-market companies sit somewhere in the middle, running four to six tools that work but do not fully talk to each other.

This piece walks one representative version of the modern stack stage by stage, and names the places where time is still being lost to manual data movement. The exact platforms vary by company. The shape of the leaks is consistent across all of them.

The example workflow below uses Albi as the CRM, Company Cam for photos, Matterport for scans, Xactimate for estimating and Slack for internal communication. Other companies use DASH, Restoration Manager, PSA, Encircle, ServiceTitan or some combination. The platform names matter less than the structure of the handoffs between them.

The seven stages of the restoration workflow

Whether the company runs on a yellow pad or a six-platform stack, every restoration job moves through the same seven stages from inbound call to carrier payment.

Stage one is intake. The homeowner calls or fills out a lead-gen form. Someone captures the loss details. At a small operator this lands as handwritten notes in a notebook or a Google form. At a mid-market company it lands in the CRM directly (Albi, DASH, Restoration Manager, PSA, ServiceTitan, or one of several others) or in an answering service log that gets transcribed later.

Stage two is the CRM record. The contact and the job get created. Loss type, address, carrier, claim number, source water source. Pen-and-paper operators do this by hand on a job folder. Mid-market and larger operators do it in their CRM of choice. The job exists somewhere a dispatcher can find it.

Stage three is photo documentation setup. At one end, the field rep takes photos on a personal phone and uploads them to a folder later. In the middle, a dedicated photo platform (Company Cam is the dominant one) auto-creates a geolocated project. At the top, the photo platform integrates back into the CRM so the job and the photo set share a single record.

Stage four is dispatch. The dispatcher sees the job and assigns a crew. The signal that the job is ready varies wildly: a phone call to the on-call tech, a chat message in Slack or Teams (often manually pasted), a CRM notification, or an automated webhook that fires when intake hits a certain threshold.

Stage five is the site visit. The representative arrives, runs the inspection, takes photos and (at companies that use it) runs a 3D scan with Matterport or a similar tool. The lower end of the spectrum still captures dimensions with a tape measure and a sketch.

Stage six is estimating. Xactimate is the dominant tool for estimates in restoration. The estimator either traces dimensions from a 3D scan, copies them from the field rep's notes, or measures from photos. Line items get added based on affected materials. The estimate goes through whatever internal review the company runs.

Stage seven is the carrier handoff. PDFs from the photo platform, the scan tool, the CRM and the estimating tool get pulled into one package. The office team assembles the final submission and sends it to the carrier through the appropriate portal or by email.

Where the workflow leaks office time

The leaks show up in the same three stages regardless of the operator's maturity level: intake, dispatch handoff and carrier package assembly. The platforms change. The leaks do not.

Stage one (intake) sets the data quality for everything downstream. If the intake captures only the address and the homeowner's name, the rest of the workflow inherits the gap. The carrier name gets filled in later by office staff. The category designation gets assigned by the estimator. The room dimensions get measured by the field rep. Every missing data point at intake is office time spent later. Companies that route after-hours intake to voicemail, an answering service or an unstructured form lose 30 minutes to 2 hours of office time per loss, downstream of the original call. This is true at the pen-and-paper company and at the company running a $200K stack.

Stage four (dispatch handoff) reads as a small thing but is one of the more revealing manual steps. Someone has to notice the new job and route it to the right crew. At small operators this is the owner answering a personal call at 2am. At mid-market companies it is a manually pasted Slack message that the dispatcher has to remember to check. The handoff is reliable when the team is small. It degrades quickly as the company scales past 10 people in the office.

Stage seven (carrier package assembly) is the largest single time sink in restoration. The office team pulls PDFs from three to five different systems, renames them, organizes them in a folder structure and attaches them to the carrier submission. A clean package takes 20 to 40 minutes per loss. A complicated one with multiple revisions can run to 2 hours. At a mid-market company doing 80 carrier submissions a month, that is 40 to 100 hours of office time monthly, almost all of it spent moving files between platforms or assembling them from a filing cabinet.

The four leverage points worth investing in

Four handoffs in this workflow are worth investing in, whether that investment looks like an integration, a tool upgrade or a process redesign.

The first is intake-to-record. Whatever captures the intake call should write structured data into the place where dispatch will look for the job. The right tool depends on call volume, complexity and current maturity. An operator on pen and paper can lift their intake quality through a structured paper template that captures the same fourteen data points every time. A mid-market operator can route after-hours intake to an AI voice agent that writes directly into the CRM. The point is the data shape, not the technology. Source water, preliminary category, room count, materials affected, carrier and claim number should land in the dispatch record without re-keying.

The second is dispatch notification. The signal that a new job is ready should reach the dispatcher without anyone remembering to send it. At a small operator this might be a shared phone the on-call dispatcher actually answers. At a mid-market company it is a webhook or a Zap that fires the chat notification automatically when the CRM record is created. The discipline is the same. The dispatcher should not have to check three places to know what is in their queue.

The third is photo and document organization. Photos exist on every job. The question is whether they are tagged and grouped in a way that the office team can find them later. Companies that build out a tagging discipline (or use the AI tagging features that most photo platforms now offer) cut document-assembly time by 50 to 70 percent. Pen-and-paper operators get the same benefit by organizing the job folder consistently from day one.

The fourth is carrier package assembly. This is the largest time sink and the hardest to fix. The right approach is a defined package template per carrier (the documents required, in the order required) with the assembly process running off that template. At a smaller company this is a printed checklist taped to the office wall. At a mid-market company it is a workflow in the CRM or middleware like Make.com or Zapier pulling files from the right systems. The cleanest implementations save 30 to 60 minutes per submission. The mechanism varies. The discipline is constant.

What connected restoration looks like in production

The companies running the most efficient workflows have one trait in common, regardless of where they sit on the platform-maturity spectrum: the office team's job is to handle exceptions, not to move data between systems or rooms or filing cabinets. The intake is structured at capture. The dispatch notification is automated or reliably manual. The photo tagging is disciplined. The carrier package assembly is template-driven.

Concretely, a connected restoration company at $10 to $25M in revenue handles 80 carrier submissions a month with an office team of three to four people, including dispatch. A company at the same revenue running the manual workflow needs six to eight office people to clear the same volume.

The difference is rarely the platforms themselves. A pen-and-paper operator who runs a tight intake template and disciplined package assembly can outperform a six-platform stack that nobody has connected. The platforms accelerate the work. The handoff discipline is what creates the gain.

The audit worth running this quarter

For a restoration operator wanting to find the leaks in their own stack, the work is straightforward.

List every platform in use. For each one, name the input (where the data comes from), the output (where it goes), and the handoff (who or what moves the data between them). The handoffs that involve a human moving files, pasting text or sending a notification are the candidates for automation.

Then rank by frequency. The handoffs that happen on every job are higher leverage than the ones that happen occasionally. Office time saved on a per-job basis compounds quickly across hundreds of monthly losses.

The tools restoration companies already use, whether they cost $200,000 a year or nothing at all, can do 80% of the workflow. The 20% that is still manual is where the office time goes. Closing that gap is what the next phase of operational maturity looks like for the industry, from the pen-and-paper operator to the regional company with a full platform stack.