The Roof That Wouldn't Get Approved.
A real-world project management case study
4-5 months. Multiple insurance setbacks. Two denials. Four adjusters. A disengaged stakeholder. An unexpected construction issue. One project manager responsible for keeping the project moving.
4-5
Months
2
Denials
4
Adjusters
1
Completed project
Project Manager
I was effectively the face of the company for this project. Most communication between the homeowner and our team went through me. I did not manage the roofing workers directly, the crew was a third-party company directed by their own captain.
- Homeowner communication
- Insurance communication
- Scheduling coordination
- Escalation
- Project follow-up
- Scope discussions
- Unexpected issue communication
- Crew communication
- Quality monitoring
- Final walkthrough
- Closeout
- Stakeholder cooperation
- Project momentum
- Insurance communication
- Homeowner decision-making
- Communication quality
- Insurance approval
- Adjuster decisions
- Independent appraiser decisions
- Third-party crew workers
- Backend estimating decisions
“I couldn't control every variable in the project. I could control how I responded to them.”
Eleven parties, four organizations, almost no formal authority
Select any stakeholder to see their role. None of these parties reported to me. The work was coordination across different levels of authority.
Project Manager
Center of communication
Homeowner
The client and the decision maker. Unfamiliar with the insurance process, hesitant after other roofers had failed, and frequently not engaging with the insurer's communications. Most of my communication effort went here.
Expected path
01
Initial inspection
02
Insurance claim
03
Adjuster inspection
04
Approval
05
Construction
06
Final walkthrough
07
Closeout
That isn't what happened.
See what actually happenedEighteen phases, four to five months
Select any phase to expand it. Switch to PM Lens to see what each event demonstrates.
- PM Lens
Stakeholder trust is built with evidence and honest framing, not promises. Attending the adjuster appointment was scheduled in from day one as a deliberate risk control.
The unexpected structural condition
No conventional decking underneath, only an older stub-post structure. I had never seen it before, so the first move was escalation, not an answer.
Option B, leave the existing structure and proceed with the roof
- Avoids unnecessary additional expense
- Avoids major additional work
- Better chance of completing the project that day
- Less disruption for the homeowner and his family
- Less ideal than fully replacing the existing structure
Persuasive stakeholder communication
I did not simply present the options and say pick one. I had a preferred option, and my persuasion strategy relied first on trust. I led with the negative information about the option I preferred, telling him honestly that the existing structure was not ideal and could cause problems later. Someone selling you something does not usually volunteer that. Acknowledging the downside first is what made the recommendation credible.
Then I gave the alternative a fair hearing and explained what doing it now actually meant: removing the structure, ordering and waiting on decking, installing it, shingling over it, and another day of construction for a family that had already lived through months of this.
“I wasn't simply trying to win an argument. I was translating a technical project decision into the consequences that mattered most to the stakeholder.”
- “I'd feel awful putting that kind of stress on you and your family, especially everything you guys have gone through in the past couple of months.”
- “All the stress and anxiety can't be easy.”
- “The sooner we finish, the sooner the weight off your shoulders will be dropped off and you can finally sit back and relax without a single worry about this anymore.”
He had everything he needed to decide, including the argument against my recommendation. He trusted my judgment and chose to proceed with the existing structure.
Project closeout
The interior work was handled separately because it could not be completed at the same time as the roof. The company handled the insurance paperwork, and the homeowner was told to contact me when the final check arrived.
Major project decisions
The six moments where the project's direction was actually determined.
What threatened the project, and the response
Applied retrospectively. Select a risk to see how it was handled at the time.
Clear expectations, repeated follow-up, prompting him to check mail, email and phone, and three-way communication when needed.
Experience / PM Lens
The same five moments, told two ways.
"The adjuster stopped responding."
"The homeowner wanted to quit."
"The crew discovered the unusual roof structure."
"The homeowner was months behind on his mail."
"I waited approximately two hours and nobody came."
What this project demonstrates
Each capability is tied to a specific event from this project, not a definition.
Stakeholder management
Eleven distinct parties across four organizations, from a disengaged homeowner to insurance HQ, with almost no formal authority over any of them.
Communication
The insurer was reaching out by mail, email and phone. The homeowner was months behind on his mail. I became the working channel between them.
Escalation
Two escalations to insurance HQ: one that surfaced denial #1, one that replaced an unresponsive adjuster with a fourth who completed the inspection.
Risk management
Attending the first inspection personally, after other roofers had already failed on this property, was a deliberate control on a known risk.
Problem solving
Appraisal was blocked until a second inspection happened, so the plan changed from disputing the denial to satisfying the prerequisite.
Decision making
Decking versus the existing stub-post structure: options evaluated with my boss, tradeoffs explained, decision left with the homeowner.
Conflict management
The homeowner's negativity after denial #2. I did not match it, I redirected the conversation toward what was still possible and what he owned.
Change management
Tear-off revealed a structure nobody had planned for. Scope, schedule and cost all had to be reconsidered mid-execution.
Quality control
Material checks before work, correction of mistakes observed during work, and cleanup, nail and debris checks afterward.
Adaptability
Four adjusters, two denials, a vacation, a no-show, an early arrival and an unplanned structure. The plan changed roughly every phase.
Leadership without direct authority
The crew worked for a third-party company and reported to their captain. I moved the work through communication and monitoring, not command.
Resource escalation
When the technical question exceeded my knowledge I brought in my boss rather than improvising an answer in front of the crew and client.
Closed, and closed properly
Project status
Completed
Homeowner retained
Yes
Insurance approval
Yes
Roof replacement
Completed
Unexpected issue
Resolved
Quality control
Completed
Final walkthrough
Completed
Homeowner satisfaction
Positive
Project closeout
Completed
Five things this project taught me
Communication is a project risk.
A project can have the right people and still fail if information is not reaching the right person. Everything on this project was being sent. Almost none of it was being received.
Escalation is not failure.
When the current process repeatedly fails, a project manager has to recognize the pattern and change the process rather than working harder inside a path that cannot produce the outcome.
Stakeholder accountability matters.
You cannot successfully manage a project entirely on behalf of a stakeholder who refuses to participate. I could fight for the project. I could not participate in it for him.
Know when you do not know.
When the unexpected roof condition appeared I did not pretend to have the technical answer. I escalated to someone with the appropriate knowledge and came back with real options.
Stay calm under pressure.
When a project becomes chaotic, slowing down and thinking clearly is worth more than reacting emotionally. The moment after denial #2 decided the whole project.
The interactive walkthrough isn't the whole story.
The complete chronological narrative, from how the homeowner was acquired through documentation, final payment and closeout.
The project didn't fail because the roof was difficult. It nearly failed because communication, stakeholders, insurance decisions and unexpected conditions kept changing the path. My job was to keep the project moving without losing the objective.
I couldn't control every variable.
I could control how I responded to them.
Retrospective disclaimer
This case study reconstructs a real roofing project I personally managed as a Project Manager. Formal project-management frameworks such as stakeholder mapping, risk analysis, decision logs and timeline visualization have been applied retrospectively to demonstrate the management principles present in the project.
The original project did not necessarily operate from a formal RACI, WBS, Gantt chart or PM software environment. This case study does not claim that those artifacts were formally created during the project.