When a Solar Removal Proposal Should Include Decking Contingencies and Flashing Updates

Q: Should the roofer and solar company coordinate directly?

Yes. Homeowners get better outcomes when the trades coordinate attachment, flashing, timing, and documentation directly instead of making the homeowner translate technical details between vendors.

If your roof has solar and you are planning a replacement, one of the easiest mistakes is treating the solar removal proposal like a simple labor ticket: take the panels off, stack the parts, and put everything back later.

We do not think that is enough.

Featured snippet answer: A solar removal proposal should include decking contingencies and flashing updates when the reroof could expose rotten or weakened sheathing, old attachment locations may need repair, the new roof assembly may change flashing details, or the reinstall plan depends on conditions that cannot be confirmed until tear-off. A good detach-and-reset scope should explain what happens if the roof structure or penetration details change after the panels come off.¹²³

At Go In Pro Construction, we think homeowners usually get into trouble when the solar scope is written as if the roof underneath is fully known before the old shingles are removed. On real projects, the roof deck, flashing details, old attachment points, and water-management conditions often become clearer only after tear-off. If the proposal has no contingency logic, the job can get expensive and confusing fast.

If you are already comparing roof-plus-solar sequencing, our guides on how to compare solar detach-and-reset bids before roof replacement starts, what homeowners should know about decking repairs before solar panels go back on, how to tell if a solar layout change will affect your reroof scope or shingle warranty, and what homeowners should ask the solar company before a reroof starts are strong companion reads.

Why can a basic solar removal proposal be too thin for reroof work?

Because detach-and-reset work touches a roof that may be changing underneath it.

A simple proposal may cover:

panel removal,
rail and hardware handling,
temporary storage,
panel reinstallation,
and basic system restart.

What it often does not explain is what happens if tear-off reveals:

soft or rotten decking,
abandoned or poorly sealed old penetrations,
flashing details that should not be reused,
attachment locations that no longer make sense,
or a roof assembly change that affects how the array should go back on.

That gap matters. The National Renewable Energy Laboratory has long noted that reroofing and rooftop solar are connected lifecycle decisions, not separate maintenance events.¹ We think homeowners should expect the proposal to reflect that reality.

When should decking contingencies be written into the proposal?

Not on every job as a scare tactic. But definitely when the risk is real.

Older roofs or unclear leak history

If the roof already has leak history, soft spots, staining, sagging, or multiple repair layers, we think the detach-and-reset scope should acknowledge that the deck condition may change the reinstallation plan.

That does not mean the contractor has to predict every damaged sheet in advance. It means they should explain:

whether decking repairs could delay reinstall,
whether old attachment zones will be reevaluated,
whether new blocking or fastening conditions may be needed,
and who approves schedule or scope changes if the roof substrate is worse than expected.

Existing solar attachment areas with unknown substrate condition

Solar penetrations can hide history. If older mounts, lag locations, or patched penetrations have been sitting on an aging roof for years, the deck condition around those zones may not be obvious until everything is opened up.

We think that is one of the clearest moments when a decking contingency belongs in writing.

Roofs already near the end of service life

The U.S. Department of Energy advises homeowners to consider roof age and roof condition before moving forward with solar decisions because roofing work and solar value are closely linked.² We think the same logic works in reverse during reroofing: if the roof was already at the end of its life, the removal proposal should not pretend the substrate will be drama-free by default.

Why do flashing updates belong in the same conversation?

Because flashing is where a lot of future arguments start.

The old flashing details may no longer fit the new roof condition

A reroof can change more than shingles. It can change:

underlayment layers,
edge details,
vent or penetration treatment,
mount locations,
and the exact way water sheds around attachments.

If the solar proposal assumes the old attachment and flashing strategy will go right back exactly as before, we think that is too casual.

A stronger scope should explain whether reinstall includes:

updated flashing at mount points,
replacement versus reuse of specific components,
photo documentation before and after reattachment,
and responsibility boundaries between roofer and solar installer.

Hidden leaks often become flashing questions later

When leaks show up near a solar mount after reroofing, the debate is rarely abstract. It usually becomes a very practical question: was the flashing updated correctly for the new roof, or did everyone assume the old detail was good enough?

That is why we think flashing language belongs in the removal proposal before the system ever comes off.

What project conditions are the strongest signs you need both contingencies and flashing updates?

We would pay extra attention if any of these are true:

Project condition	Why it matters
The roof has prior leak history	Tear-off may reveal damaged substrate or failed penetrations
The array has older mounting hardware	Reuse assumptions may not match the new roof assembly
The reroof includes deck replacement risk	Reinstall timing and attachment plans may need to change
The roof-to-wall or valley details are complex	Water-management details matter more than a simple reset schedule
Solar layout may shift during reinstall	Old flashing and attachment points may not map cleanly to the new plan
Multiple trades are involved	Responsibility gets fuzzy fast without written scope boundaries

In our experience, proposals that skip these conditions tend to sound cheap and easy up front, then become change-order machines later.

We think homeowners should look for language that answers actual production questions.

A useful proposal should clarify

What happens if tear-off reveals damaged decking?
Who determines whether attachment locations need to change?
Whether reinstall can proceed immediately after repairs or must pause for review
How schedule changes are communicated
Whether photo documentation of exposed conditions will be provided

A contractor does not need to know every future condition on day one. But they should know what the decision path looks like if the roof deck is not as clean as hoped.

GreenLancer’s overview of solar removal and reinstallation for roof work makes the same general point from the trade side: reroof coordination is not just about lifting panels off and back on, because attachment conditions, roof repairs, and scheduling dependencies all affect the reset.³

Red-flag proposal language

We would slow down if the proposal sounds like this:

“remove and reinstall solar after roofer finishes”
“customer responsible for any unforeseen roof issues”
“existing flashing reused as needed”
“timing subject to roof completion”

Those phrases are not always wrong, but by themselves they are too thin. They usually tell you the contractor has left the most expensive uncertainty sitting outside the written scope.

What should the proposal say about flashing updates?

We think flashing should be specific enough that the homeowner can compare bids intelligently.

Ask whether the proposal covers

updated flashing at all new or reused attachment points,
replacement of worn or incompatible flashing components,
coordination with the roofer on penetration sequencing,
documentation of any relocated attachments,
and the final responsibility path if a leak appears near a reinstalled mount.

Solar Power World has written about the importance of mounting and substrate considerations because attachment quality depends on what is actually happening at the roof structure level, not just the visible surface.⁴ We think homeowners should read flashing language with that same mindset.

Why “reuse where possible” can be risky

Sometimes reuse is appropriate. Sometimes it is just lazy language.

If the roof assembly changes, if mount spacing shifts, or if the old flashing detail was part of the original problem, reuse should not be treated as the automatic default. We would rather see a contractor explain the criteria for reuse than hide behind a vague assumption.

How should homeowners compare detach-and-reset proposals when one is much cheaper?

Usually by asking what the cheaper scope is excluding.

The lower proposal may be leaving out:

deck-related pause or review logic,
updated flashing allowances,
documentation requirements,
storage and hardware handling detail,
coordination meetings with the roofer,
or responsibility for schedule disruption if tear-off reveals more work.

We think the smarter comparison is not just “What does the reset cost?” It is “Which proposal still makes sense if the roof is more complicated than the sales visit suggested?”

If you are comparing related planning issues, you may also want our articles on how to compare bids when roofing and solar scopes are separated across contractors, how to compare timelines when roof replacement, gutter work, and solar are all in one project, and how roof warranties and solar workmanship warranties should fit together.

What questions should homeowners ask before signing?

We think these questions expose proposal quality fast:

If tear-off reveals bad decking near old mount locations, what changes in your reinstall plan?
Are flashing updates included at every attachment point that gets reused or relocated?
Who decides whether the old layout still works on the new roof assembly?
Will I receive photo documentation of exposed decking and final flashing details?
If the roof deck changes, does the reinstall schedule automatically change too?
Who takes the first call if a leak later appears near a reinstalled mount?
Are you coordinating directly with the roofer, or am I expected to relay technical details between trades?

A confident contractor should be able to answer those without acting annoyed.

Why this matters for cost, warranty, and project coherence

A thin proposal does not just create pricing surprises. It creates accountability problems.

If deck repairs show up and the removal proposal never explained how that affects the reset, homeowners can get stuck between trades. If flashing gets updated inconsistently, a future leak can turn into a blame exchange. If the array goes back on before the roof conditions are properly documented, the whole project file gets weaker.

We think the goal is not to make the proposal longer for the sake of paperwork. The goal is to make it honest enough to survive real roof conditions.

Why Go In Pro Construction recommends written contingency logic

At Go In Pro Construction, we think solar removal scopes should be judged by how they handle uncertainty, not just by how simple they sound before tear-off. Roof decking, flashing, attachment zones, and water-management details are where the real project risk lives.

Because we think in terms of connected exterior systems, we approach roofing, gutters, siding, paint, and solar coordination as one planning problem instead of five disconnected appointments. That is usually what keeps the reroof coherent when field conditions change.

If you want a practical review of a detach-and-reset scope before you sign, start with our homepage, browse recent projects, learn more about our team, or talk with us about the roof, the array, and the risk points that should be in writing before panels come off.

Need help reviewing a solar removal proposal before reroof work begins? Contact Go In Pro Construction if you want a practical read on decking contingencies, flashing updates, roof-plus-solar sequencing, and the scope language most likely to cause trouble later if it stays vague.

Frequently asked questions about solar removal proposals, decking contingencies, and flashing updates

Does every solar removal proposal need decking contingencies?

Not every job needs a large contingency section, but proposals should address it when roof age, leak history, visible soft spots, prior penetrations, or reroof complexity make substrate surprises realistic.

Why are flashing updates such a big deal during solar reinstall?

Because the new roof assembly, attachment locations, and water-shedding details may not match the old setup. If flashing expectations are vague, leak accountability gets much harder later.

Can a contractor price decking repairs exactly before tear-off?

Usually not. But they can still explain the decision path, documentation process, and schedule impact if damaged decking is found.

What is a red flag in a detach-and-reset proposal?

A red flag is a proposal that promises removal and reinstall dates but says almost nothing about substrate condition, flashing updates, attachment changes, or who handles scope changes after the roof is opened.

Should the roofer and solar company coordinate directly?

We think yes. Homeowners get better outcomes when the trades coordinate attachment, flashing, timing, and documentation directly instead of making the homeowner translate technical details between vendors.