Tag: Project Management

This is the fifth and final article in the Mitigation-to-Reconstruction Intelligence cluster under The Restoration Operator’s Playbook. It builds on the handoff piece, the prep standard piece, the photo discipline piece, and the feedback loop piece.

Two functions cannot share a job if they do not share a number

The hardest problem in the mitigation-to-reconstruction handoff is not technical. It is not procedural. It is not even cultural in the broad sense. It is a measurement problem.

In most restoration companies, the mitigation function and the reconstruction function are measured on different numbers. Mitigation is measured on dryout time, equipment utilization, response speed, maybe a per-job revenue or margin number specific to the mitigation portion of the work. Reconstruction is measured on cycle time, gross margin per job, scope accuracy, customer satisfaction at the close-out. Each function tracks its number, manages to its number, and gets rewarded based on its number. Each function is, in a literal accounting sense, optimizing for a different outcome.

The handoff lives in the gap between those two numbers. There is no metric that captures whether the handoff was good or bad. There is no scoreboard that holds either function accountable for the other’s experience. The handoff is, by structural design, no one’s number.

The single highest-leverage operational change a restoration company can make to fix the handoff problem is to put both functions on the same scoreboard for at least one number that captures the joint outcome. Not instead of their function-specific numbers — in addition to them. The shared number is what makes the prep standard, the photo discipline, and the feedback loop work in concert. Without a shared number, all three of those artifacts can exist on paper and still produce no behavior change.

What the shared number has to be

For a shared metric to work, it has to satisfy three criteria.

It has to be a number that both functions genuinely influence. A metric that is mostly driven by mitigation but slightly affected by reconstruction will be experienced by the reconstruction team as unfair, and vice versa. The number has to be one where both teams can point to specific decisions they make that affect it.

It has to be measurable at the job level, not the function level. Function-level numbers create function-level optimization. Job-level numbers force the two functions to think about the joint outcome on each individual file. Aggregations across jobs are useful for trend reporting, but the number has to live first at the job.

It has to be visible quickly enough to drive behavior. A metric that takes ninety days to settle is too slow to influence the next decision the mitigation tech makes. The number has to close out within a window that lets both teams see the result of their handoff and adjust.

The number that satisfies all three criteria in most restoration companies is total job margin, measured at the job level, with both teams accountable to it.

Why total job margin is the right number

Total job margin captures everything that matters about the handoff. A mitigation crew that demos too aggressively raises the rebuild scope and depresses total job margin even if the mitigation portion looks healthy. A mitigation crew that documents poorly creates rebuild rework that depresses total job margin even if the mitigation portion was efficient. A mitigation crew that prepares the job well for the rebuild produces a job where both portions perform, and total job margin is high.

Conversely, a rebuild team that consistently writes scope that fits the conditions the mitigation crew left will produce healthy total job margins on jobs where the mitigation work was good and surface the handoff problems clearly on jobs where it was not. The rebuild team is also incentivized to communicate clearly with the mitigation team about what kinds of prep work consistently lead to healthy rebuilds, because better prep raises the number they are accountable to.

The mitigation team, in turn, becomes interested in what happens after they leave the job. A mitigation supervisor who sees that their jobs consistently produce lower total margins than peers’ will start asking why. A mitigation supervisor whose jobs consistently produce higher total margins will be asked to teach the rest of the team. The conversation about the handoff stops being political and starts being operational.

Total job margin also has the practical advantage of being a number every restoration company already calculates. The work to put it on a shared scoreboard is mostly the work of presenting it differently — at the job level, visible to both functions, attached to the leadership review of both functions.

Secondary metrics worth sharing

Total job margin is the primary shared metric. Several secondary metrics, used in addition to the primary, sharpen the picture and make the joint accountability more actionable.

Total job cycle time — from first notice of loss to keys-back-to-homeowner — is the most useful secondary metric. It captures whether the handoff added unnecessary days to the timeline. Mitigation crews that hand off cleanly contribute to shorter cycles. Rebuild teams that pick up cleanly do the same. Both teams seeing the cycle time at the job level creates pressure to find the days that are being lost in the handoff.

Customer satisfaction at the close-out, captured through whatever survey or review mechanism the company uses, is a useful third metric. Customer satisfaction is more sensitive to the rebuild experience than the mitigation experience, but it is influenced by both, and putting it on a shared scoreboard prevents the mitigation team from optimizing purely for their own customer interaction at the expense of the longer arc of the homeowner’s experience.

Scope change rate during the rebuild — how often the rebuild team has to write change orders or get scope adjustments approved — is a fourth useful metric. A high scope change rate often traces back to incomplete handoff documentation, undiscovered conditions that should have been flagged at mitigation, or decisions that should have been made differently at the front of the job. Tracking it as a shared number drives both teams to invest in the documentation and prep work that prevents it.

None of these secondary metrics replaces total job margin as the primary. They support it. They give the leadership conversation specificity when the primary number drifts in a direction that needs investigation.

What changes when the scoreboard becomes shared

The companies that have implemented shared scoreboards across the mitigation and reconstruction functions report a similar set of changes.

The first change is in conversation. The mitigation supervisor and the rebuild lead start talking to each other differently. The conversations stop being about whose fault something was and start being about how to make the joint number better. This shift is small in any single conversation and large over hundreds of conversations across a year.

The second change is in decision-making. Mitigation crews start making cut, demo, and documentation decisions with more attention to downstream consequences, because they know the consequences will show up on a number they are accountable to. Rebuild teams start engaging earlier on jobs, sometimes visiting site during mitigation on complex losses, because the early engagement protects the joint number.

The third change is in training and hiring. The standards that govern the work get communicated as joint standards rather than function-specific standards. New hires on either side learn that they are part of a joint operation, not a siloed function. Senior operators on both sides become natural cross-trainers, because the joint number rewards cross-functional fluency.

The fourth change is in technology investment. Software and tooling decisions start being evaluated against their effect on the joint number rather than the local efficiency of one function. This usually leads to better tooling decisions, because the joint outcome is what the company actually cares about.

The fifth change is in leadership focus. Owner and senior leader attention starts following the joint number, which puts the right kind of pressure on the right kind of operational improvements. Function-specific dashboards still exist, but the joint dashboard becomes the one that drives the operating cadence.

Why most companies do not do this

The barriers are not technical. The numbers exist. The systems can produce them. The barriers are political and operational.

The political barrier is that function leaders have built their careers around function-specific metrics. Asking them to share accountability with another function feels like a dilution of their authority and a complication of their performance evaluation. The owner has to be the one who makes the call, and the call has to be made deliberately, with explicit acknowledgment that the function-specific metrics still matter and that the shared metric is additional, not a replacement.

The operational barrier is that most operations software is configured to report function-specific numbers and not configured to surface job-level joint numbers in a useful way. Producing a clean joint scoreboard usually requires either a custom report, a workaround in the existing software, or a small investment in a reporting layer that pulls from the operations system and presents the data the way the joint conversation needs to see it. The work is not large, but it has to be commissioned, and in most companies no one has commissioned it because the conversation about the joint metric has not yet happened.

The cultural barrier, which is the deepest, is that some companies have developed cross-functional dynamics over years that would be uncomfortable to surface. A shared scoreboard makes visible patterns that have been invisible. Some of those patterns will be flattering to one function and unflattering to another. The leadership has to be ready to handle that surfacing constructively, or the scoreboard will become a weapon and the experiment will fail.

How to start

If you run a restoration company and you do not have a shared scoreboard, the path to building one is short.

Calculate total job margin at the job level for the last six months. Most operations systems can produce this with modest effort. Surface it to both function leaders, with the agreement that the conversation about the numbers will be exploratory rather than evaluative for the first quarter. Look for patterns: which jobs produced healthy joint margins and what they had in common, which jobs produced poor joint margins and what they had in common.

From the patterns, identify two or three operational changes that would lift the joint number. Implement them. Continue measuring. After two quarters of exploratory measurement, formalize the shared scoreboard as part of the regular leadership review of both functions, with explicit accountability and explicit linkage to the function leaders’ performance evaluations.

The first quarter is uncomfortable. The second quarter is informative. By the third quarter, both functions have internalized the joint accountability and the conversation has fundamentally changed.

The full stack

The five articles in this cluster describe the full operational stack that the best restoration companies are building around the mitigation-to-reconstruction handoff. The handoff is the most expensive moment in the restoration economic chain. The prep standard is the document that makes the handoff designed rather than accidental. The photo and documentation discipline is what gives the handoff the data the rebuild team needs to perform. The feedback loop is what keeps the standard alive over years. And the shared scoreboard is what holds both functions accountable to the joint outcome and makes all the other artifacts work in concert.

None of this is technology. None of it requires capital. All of it requires operational seriousness sustained over years. The companies that build this stack are quietly creating one of the most durable competitive advantages available in the industry. The companies that do not are paying for the absence on every job, every quarter, every year, in a leak that does not show up as a single line item but that determines whether the company is on the operating-system side of the industry split — or the side that wakes up in 2028 wondering what happened.

This cluster is closed. The next clusters in The Restoration Operator’s Playbook will go deep on AI in restoration operations, on financial operations discipline, on carrier and TPA strategy, and on the senior talent question. Each cluster builds on the others. Each contributes to the same underlying argument: the restoration industry is splitting into two groups, the split is happening on operational discipline, and the window in which the right side of the split can still be reached is open now.

The companies that read this body of work and act on it will know who they are. The rest will find out later.

This is the fourth article in the Mitigation-to-Reconstruction Intelligence cluster under The Restoration Operator’s Playbook. It builds on the handoff piece, the prep standard piece, and the photo discipline piece.

A standard without a feedback loop is a fossil

Almost every restoration company that has ever attempted to write a mitigation prep standard has produced a document that worked for about six months and then quietly stopped working. The standard did not get worse. The world around it changed — new construction styles, new flooring products, new finish trends, new carrier expectations, new failure modes that the standard had not anticipated — and the standard did not change with it. By month nine, the field crew was back to making decisions on instinct, and the rebuild team was back to absorbing the consequences.

The thing that separates the companies whose prep standard is alive in year three from the companies whose prep standard died in month nine is not the quality of the original document. It is the existence of a feedback loop that converts every rebuild surprise into a candidate revision of the standard.

The feedback loop is the second-most underrated operational artifact in restoration. The first, as covered in the prep standard piece, is the standard itself. But a standard without a feedback loop is a fossil. A standard with a feedback loop is a compounding asset.

What a feedback loop actually is

To be useful, the phrase has to mean something specific. A feedback loop in this context is a structured process by which the rebuild team’s discoveries — about what the mitigation team did well, what they did poorly, and what they encountered that the standard had no answer for — flow back to the operator who maintains the prep standard, get evaluated, and either result in a revision to the standard or get explicitly logged as not warranting a revision.

That structure has four parts. The capture mechanism. The triage process. The revision decision. And the redistribution back to the field.

Each part can fail. Most companies fail at the first one and never get to the others.

The capture mechanism

The capture mechanism is the device by which a rebuild team member, encountering something that traces back to a mitigation decision, gets that observation out of their head and into a place where it can be reviewed. The bar is low. It does not need to be sophisticated. It needs to be frictionless.

The companies that have working capture mechanisms tend to have one of three setups.

The simplest is a shared channel — a Slack channel, a Teams channel, a dedicated email address — labeled something like #handoff-feedback or #rebuild-from-mit. When a rebuild estimator opens a file and finds something worth flagging, they post a short note with the job number and a one-line description. When a rebuild lead encounters a condition mid-build that traces back to a mitigation decision, same. The channel is monitored by the operator who owns the standard. Posts are not arguments. They are observations.

The second setup is a structured field in the operations software. A flag attached to the job record, with a short notes field and a few category tags. This is more durable than a chat channel because it lives with the job and gets reviewed by anyone who pulls the job up later. It is also harder to set up and harder to get adoption on, because operations software is rarely designed for this kind of input.

The third setup, which the most disciplined companies use in addition to one of the above, is a regular short meeting — usually fifteen to thirty minutes, weekly or every other week — between the rebuild lead and the mitigation supervisor. The agenda is the open feedback items from the chat channel or the software, walked through quickly, with the standard owner present to take notes on candidate revisions.

The thing all three setups have in common is that they make capturing feedback the path of least resistance. A feedback mechanism that requires the rebuild estimator to file a formal report, fill out a long form, or schedule a meeting will not get used. A feedback mechanism that takes thirty seconds will.

The triage process

Captured feedback is raw material. Not every observation deserves a standard revision. Some observations reflect a one-off situation that will not recur. Some reflect a real recurring pattern that the standard should address. Some reflect a misunderstanding by the rebuild team about what the mitigation team did and why. The triage process sorts the raw input into those buckets.

The triage owner is, in most companies, the same person who owns the standard — the cross-trained operator with credibility on both sides of the work. They review the captured feedback on a defined cadence, usually weekly. For each item, they make one of three calls.

The first call is “candidate revision.” The observation reflects a real pattern, the current standard either does not address it or addresses it wrong, and the next revision of the standard should incorporate a change. The item gets logged in a revision queue.

The second call is “no change, but worth a one-off conversation.” The observation reflects a real issue but is not a pattern that warrants a standard change. Maybe the mitigation crew on that specific job was new, or the conditions were unusual, or the standard already addresses it and the issue was a training gap. The triage owner closes the loop with a brief note back to the originator and, if needed, a one-off training touch with the relevant crew.

The third call is “no change, no action.” The observation reflects either a misunderstanding by the rebuild team, an artifact of conditions outside anyone’s control, or a preference that does not rise to the level of a standard. The triage owner closes the loop politely with the originator. Closing the loop here is critical: the rebuild team has to feel that their feedback was heard and taken seriously even when it does not result in a change, or they will stop sending it.

The revision decision

The revision queue accumulates over a quarter. At the end of the quarter, the standard owner sits down with the queue, the current version of the standard, and any other operational input from the period, and produces the next revision.

The revision is a deliberate document. Not every queued item necessarily makes it into the new version. Some items will have been resolved by other changes. Some items will turn out, on review, to conflict with each other. Some items will require more thought than the quarter allowed and will be deferred to the next cycle. The standard owner is the editor, and the queue is input, not mandate.

The output of the revision is a new version of the standard with two artifacts attached. The first is a changelog — what changed, why it changed, and what the previous behavior was — written in plain language so that anyone reading it understands the reasoning. The second is a short briefing document, usually a single page, that summarizes the most important changes for the field crew so that the revision can be communicated quickly.

The new version replaces the old version in the operational system. The old version is archived, not deleted, because it is sometimes useful to be able to reconstruct what the standard said at the time a given job was performed.

Redistribution to the field

The new revision is useless if the field crew does not know about it. Redistribution is the part of the cycle most often skipped, because by the time the revision is done, the team has moved on to the next set of priorities. Skipping redistribution is the difference between a standard that improves and a standard that drifts.

The companies that handle this well treat each quarterly revision as a small training event. The standard owner walks the field crew through the changelog briefing — usually in a fifteen-minute huddle, on site or remote — and answers questions. The crew acknowledges the new version. The new version becomes the working document.

The redistribution is also the moment to close the loop publicly with the rebuild team. The standard owner names which feedback items resulted in which changes, and credits the originators. This does two things. It demonstrates to the rebuild team that their feedback shapes the standard, which encourages more of it. And it demonstrates to the mitigation crew that the rebuild team is contributing to the document they are now expected to follow, which builds cross-functional respect.

What the loop produces over time

The companies that have run this loop for two or three years tend to describe a similar pattern.

The first six months produce a flood of feedback. The standard, even if it was well written initially, did not anticipate every situation, and the rebuild team has been holding observations they never had a place to put. The first few revisions are substantial.

The next twelve months produce a steady stream of refinements. The standard gets sharper, more specific, more closely matched to the company’s actual operating reality. Recurring failure modes get progressively designed out of the work.

By year two, the volume of feedback drops noticeably, not because the rebuild team has stopped paying attention but because the standard has gotten good enough that fewer things are worth flagging. The feedback that does come in is higher-signal — usually about new conditions the company has started encountering or about edge cases the standard had not yet addressed.

By year three, the standard is a meaningful competitive asset. New hires are trained against it. New software gets configured around it. New service lines extend it rather than starting from scratch. The compound effect of three years of sharpened operational discipline is visible in the company’s margin profile, its customer satisfaction numbers, its program standing with carriers, and its ability to absorb new technology.

None of those outcomes were the goal at the beginning. The goal at the beginning was just to stop making the same handoff mistakes over and over. The compounding happened because the loop was in place to capture and convert every mistake into a permanent improvement.

Why most companies never build the loop

The loop is not technically hard. The reason most companies never build it is cultural.

The first cultural barrier is that mitigation and reconstruction are usually run as separate functions with separate leaders. Each function has its own metrics, its own incentives, and its own sense of identity. A feedback channel where the rebuild team flags mitigation decisions feels, from the mitigation side, like a complaint channel. The leadership of both functions has to actively reframe it as an improvement channel, every time, until the framing sticks.

The second cultural barrier is that the operator who would naturally own the standard and the loop is usually a senior person whose time is already heavily committed. Carving out the weekly triage time and the quarterly revision time requires owner-level intervention to protect the calendar. Companies whose owners do not protect that time end up with standards that drift.

The third cultural barrier is the absence of a feedback culture in the first place. In companies where pointing out a problem is dangerous or pointless, the feedback channel sits empty regardless of how well it is designed. Building the loop, in those companies, is partly a feedback architecture problem and partly a more fundamental cultural problem about whether observations are welcome.

The companies that have built working loops tend to have addressed all three of these barriers deliberately. The leadership reframes the channel publicly and consistently. The owner protects the standard owner’s calendar. And the broader culture of the company has been intentionally shaped so that feedback is treated as fuel rather than threat.

Where to start

If you have a prep standard but no feedback loop, the loop is the next investment, and it is small. Open one channel. Name one triage owner. Hold one meeting per week. Commit to a quarterly revision cadence. Run it for two quarters and see what happens.

If you have neither a standard nor a loop, build the standard first as described in the prep standard piece. Then build the loop. The order matters: the loop without the standard has nothing to revise, and the standard without the loop will be obsolete within a year.

If you have both and they are working, the work in front of you is to keep them working. The loop is not a project. It is a permanent operational capability. The companies that treat it that way produce a standard that gets sharper every quarter and an operating advantage that gets deeper every year.

The standard is the moat. The feedback loop is what keeps the moat from filling in.

Next in this cluster: shared metrics — the operational scoreboard that holds mitigation and reconstruction accountable to the same number, and why getting that number right changes the conversation between the two functions for good.