5 Keys to Smooth Roofer and Solar Installer Collaboration

Roofer and solar installer collaboration works best when the two trades stop treating each other as someone else's problem. A roof can be perfectly watertight and still be a bad solar platform if its remaining life, penetration plan, drainage, and access were never reviewed by the people who understand them. A solar layout can pencil out beautifully on a satellite image and still wreck a roof if it ignores the shingle's age, blocks a valley, or sits over a deck that should have been torn off first. The fix is not complicated, but it is almost always skipped: the roofer and the solar installer have to talk before either one orders material.

Here is the short version. Get the roof's remaining service life on the table first, because a roof with fewer years left than the array does is the single most expensive mistake in this entire category. Put every roof penetration and flashing detail in writing, with names attached, so nobody inherits a leak they did not create. Respect the fire-code access pathways and ridge setbacks before the panel layout is locked, because the authority having jurisdiction will not bend for a tidy-looking design. Coordinate safety, staging, and electrical boundaries so two crews on one roof do not undo each other's work. And plan for the day a leak shows up under the array, because someone will have to pull modules to find it.

The five keys below are written for roofing contractors, solar installers, project managers, and the homeowners caught in the middle. They are coordination guidance, not electrical, structural, code, warranty, tax, or legal advice. Every project-specific decision belongs to a licensed solar professional, a licensed electrician, a structural engineer when one is needed, the equipment manufacturers, the local code official, and the authority having jurisdiction. What follows is how to keep those decisions from colliding.

One more framing point, because it changes everything downstream. Rooftop solar is a 25-to-30-year commitment bolted to a roof that may have far less life than that. The U.S. Department of Energy's homeowner's guide to going solar lists roof condition as a first-order planning question for exactly this reason. When the two timelines do not match, every other coordination decision gets harder and more expensive. So the timelines are where good collaboration starts.

Key 1: Settle the Roof's Remaining Life Before Anyone Designs an Array

A modern photovoltaic system is built to produce for 25 to 30 years. An asphalt shingle roof does not always have that long. Three-tab shingles often run 15 to 20 years; architectural and so-called luxury laminates can reach 25 to 30 under good conditions and good ventilation, but real-world roofs in hail country, intense sun, or with poor attic airflow age faster than the brochure. The math that governs this whole topic is simple: if the array outlives the roof, the homeowner pays twice, and both contractors look bad.

That is not a scare tactic, it is arithmetic. When a roof needs to be replaced after panels are already up, the modules and racking have to come off, get stored, and go back on after the new roof is finished. Industry cost guides put that remove-and-reinstall work in the rough range of $200 to $300 per panel, which for a typical residential array lands somewhere around $3,000 to $6,000 on top of the reroof itself, per Fixr's solar removal cost data and EnergySage's roof-replacement-with-solar overview. Those numbers move with array size, roof pitch, and how the system was wired, but the direction never changes: doing the roof second is always more expensive than doing it first.

So the first coordination question on any project is not "where do the panels go," it is "how many good years does this roof have left, and does that beat 25?"

The roofer's job here, and its limits

The roofer is the right party to document roof condition, but the honest version of that role has hard edges. A roofer can record covering type, observed age and wear, granule loss, lifting or curling, brittle shingles, prior repairs, soft or spongy deck, attic moisture if it is within scope, ponding on low-slope sections, and drainage paths. A roofer can give a defensible estimate of remaining service life as a range. What a roofer should not do is hand the solar company a one-word "good for solar" verdict that the homeowner later treats as a guarantee. Condition documentation supports the decision; it does not replace the homeowner's choice or the solar engineer's load review.

This is also exactly where age estimation tools earn their keep on the outbound side. A contractor who wants to find homeowners whose roofs are genuinely near the decision point, rather than knocking doors at random, can use a platform like RoofPredict to surface an estimated roof-age range house by house before anyone climbs a ladder. That is a planning range, not an inspection, and it does not certify how many years a roof has left. But it does answer the practical targeting question well enough to skip brand-new roofs and focus a conversation on the homes where the roof-before-solar question is actually live.

The decision framework

Use the table below as a starting conversation, not a rule. The right answer depends on the specific roof, the climate, and the homeowner's plans.

Estimated roof age (architectural asphalt)	Typical condition	Reasonable coordination path
0 to 5 years	Near-new	Proceed to solar design; document condition for the as-built record
6 to 12 years	Mid-life, ventilation-dependent	Inspect; if sound, proceed with attachment plan that respects warranty
13 to 18 years	Aging; wear becoming visible	Strongly consider replace-first; weigh remove/reinstall cost against new roof
19+ years	Late life	Replace before solar in almost every case
Any age, active leaks or soft deck	Failing regardless of age	Repair or replace first; do not panel over a known defect

The ConsumerAffairs guidance on whether to replace a roof before going solar lands in the same place: homeowners with roofs 10-to-15-plus years old should get a professional look before committing to panels. The point of putting it in a table is that the roofer and solar installer can agree on the path in one meeting instead of discovering the disagreement on install day.

Material type changes the math

Not every roof ages on the same clock, and the collaboration plan should account for the covering, because the replace-first calculus shifts with it. Asphalt is the common case, but the others come up often enough that both trades should know the patterns.

Roof covering	Typical service life	Solar coordination note
Three-tab asphalt	15 to 20 years	Often near or past its life when solar is considered; lean replace-first
Architectural / laminate asphalt	25 to 30 years	Best match to array life if mid-life and sound
Standing-seam metal	40 to 70 years	Excellent platform; clamp-on mounts avoid penetrations entirely
Concrete or clay tile	50+ years	Long life but fragile to walk; tile-replacement mounts and breakage planning required
Wood shake	20 to 40 years	Brittle and fire-sensitive; many AHJs and installers avoid; verify acceptability early
Single-ply membrane (low-slope)	20 to 30 years	Ballasted or specialized attachments; membrane-compatible flashing is critical

Standing-seam metal is worth a special mention because it removes the single biggest fight in this whole category. Clamp-on mounts that grip the seam do not penetrate the roof at all, which eliminates most of the leak-responsibility argument and is part of why metal is a favorite among installers who want clean, penetration-free attachments. Tile is the opposite case: it is durable but breaks underfoot, so the plan has to budget for cracked tiles during access and a tile-replacement mount detail, and the roofer is the right party to stock matching tile for repairs the solar crew will inevitably need.

What the roofer documents, in detail

The condition note should be specific enough to act on. A useful one captures: covering type and approximate age; granule loss and any bald or eroded areas; lifting, curling, or cupping shingles; cracked, blistered, or missing pieces; the condition of valleys, hips, and ridge; flashing condition at walls, chimneys, and existing penetrations; visible decking condition from the attic where accessible; signs of prior repair or overlay; ventilation adequacy; and any active leak history the homeowner reports. Photos beat adjectives. A note that says "roof in fair condition" helps nobody; a note with twelve dated photos and a remaining-life range gives the homeowner and the solar team something they can actually decide on. Agreeing on this path in one meeting beats discovering the disagreement on install day.

Sequencing when both scopes are happening at once

Many of the best outcomes happen when the reroof and the solar install are sold together and sequenced on purpose. A workable order looks like this: tear off and inspect the deck, repair or replace sheathing, dry-in with underlayment, complete the new roof covering, pass the roofing inspection, then mount racking into the finished assembly with manufacturer-approved flashing, then run electrical and pass the electrical and utility inspections, then close out. Doing it in that order means the penetrations land in a brand-new, properly flashed field instead of in a roof that is already on borrowed time. It also means the panels never have to come off for a reroof during their design life, which is the whole point.

Key 2: Put Every Penetration, Flashing Detail, and Warranty Boundary in Writing

The second key is where most real disputes are born. Solar attaches to a pitched asphalt roof through dozens of penetrations, and every one of them is a potential leak if the flashing is wrong. The trades have to agree, in writing and before work starts, on who selects the attachment method, who installs it, who inspects it, and whose warranty covers the roof field around it.

How a comp-shingle attachment is supposed to work

It helps for both trades to share the same mental picture of a correct attachment, because vague language is what causes finger-pointing later. On a composition shingle roof, a proper flashed mount drives a lag bolt into a rafter or solid blocking, seats a metal flashing that slides up under the shingle course above the bolt and laps over the course below, and seals the penetration under that flashing so water sheds over the top of it. Manufacturers such as IronRidge specify that flashings like their FlashFoot2 underlap multiple shingle courses for exactly this reason, and Unirac offers compression-seal alternatives like FlashLoc that protect the penetration without lifting shingles. The detail that matters for collaboration is not which brand wins, it is that the bid names the approved flashing product and states who is responsible for installing it correctly.

The failure mode to ban outright is a glob of sealant over a bare lag bolt with no flashing. Sealant is a backup, never the primary water barrier. If a layout forces a mount into a spot where proper flashing cannot lap correctly, that is a design conflict to resolve before install, not a thing to caulk over on the roof.

Hitting structure, not only the deck

There is a structural side to attachment that the two trades have to align on, because a mount that grips only the sheathing is a mount that pulls out in a wind event. Lag bolts are meant to land in a rafter or truss top chord, or in solid blocking added for the purpose, not in the half-inch deck alone. That means the solar crew has to find and hit framing, and on many roofs the framing is not where the layout wishes it were. When mounts cannot land on framing at the spacing the racking needs, the answer is blocking installed from the attic or an engineered detail, not a longer lag into plywood.

This is also where added dead load enters the conversation. A panel array plus racking adds a few pounds per square foot across a large area, and on an older or marginal roof structure that can matter, especially in snow-load regions where the array load stacks on top of the design snow load. Structural adequacy is an engineering question, not a roofing or sales question, and on any roof where it is in doubt the correct step is a structural review before the design is locked. The roofer's contribution is honest reporting of what the deck and framing look like; the determination belongs to a qualified engineer and the AHJ.

Wind uplift and exposure

Wind is the load that finds bad attachments. The array changes how wind interacts with the roof, and edge and corner zones see the highest uplift pressures, which is why manufacturers publish attachment spacing tied to wind speed and exposure category. Coastal and high-wind jurisdictions enforce this hard. The roofer and solar installer should confirm that the racking layout's attachment spacing matches the local design wind speed and that edge-zone mounts are not stretched to the maximum spacing just to save a few brackets. A penetration that holds in calm weather and lets go at 90 miles per hour is worse than no panel at all.

Attachment responsibility matrix

Write the responsibilities down. A short matrix in the contract or scope document prevents the most common version of this argument.

Task	Who decides	Who performs	Who inspects	Who warrants
Mount type and flashing product	Solar engineer with roofer input	Solar crew (or roofer if agreed)	Roofer or third party	Per written agreement
Penetration into deck/rafter	Solar design	Solar crew	Roofer or AHJ	Solar for attachment, roofer for surrounding field if specified
Flashing integration into roof covering	Roofer input required	Whoever is qualified and named	Roofer	Roofer if roofer installs; solar if solar installs to spec
Conduit, standoffs, wall penetrations	Solar/electrical	Solar/electrical crew	AHJ	Solar
Repair of any roof damage during install	Roofer	Roofer	Roofer	Roofer

Leave none of these blank. A blank cell is a future leak with no owner.

What a solar install actually does to a roof warranty

Homeowners and even some crews believe that putting solar on a roof automatically voids the shingle warranty. That is usually not true, but the real answer has nuance that both trades should understand and convey accurately. Owens Corning, for example, takes the position that its shingle warranty stays in place when solar is installed, but that damage caused by the solar installation itself is not a manufacturing defect and is therefore not covered, as summarized in Solar Power World's reporting on solar and roof warranties. In plain terms: the shingles are still warranted against shingle defects, but if the solar crew cracks a shingle or botches a flashing, that is the solar crew's problem, not the manufacturer's.

The larger warranty risk is the workmanship and installation side. Manufacturers like GAF and Owens Corning condition their enhanced warranties on certified installation following exact specifications, and using off-brand flashing or non-approved components can jeopardize coverage. So the bid should answer three questions explicitly: which roof warranty documents apply, whether the chosen solar flashing is compatible with those documents, and which trade the homeowner calls first if a leak shows up near the array. The IRC and IBC roof-assembly chapters give the underlying assembly rules, and ICC publishes both the 2024 IRC roof assemblies chapter and the 2024 IBC roof assemblies and rooftop structures chapter as reference points, though local amendments always govern the actual job.

The penetration record that ends arguments

The single most valuable artifact this collaboration can produce is a penetration record. For every mount, conduit support, and wall transition, capture a photo before, a photo of the flashing or seal during, and a final photo, plus the product used, the installer's name, and the date. If a leak appears three years later, that record is what lets the service team tell old roof condition apart from solar-related work, and it is what keeps the homeowner from suing both contractors over a mystery stain. Whether this lives in a shared drive, a project-management app, or a roof record platform like RoofPredict, the requirement is the same: the photos and notes have to outlive the install crew and reach the people who will service the roof later.

Key 3: Honor Fire-Code Access Pathways and Setbacks Before Locking the Layout

The third key is the one that most often forces a redesign on install day, because it is governed by the fire code rather than by what looks efficient on a sales rendering. Firefighters need to get on the roof, move across it, and ventilate it, and the code reserves space for that whether or not the layout likes it. The authority having jurisdiction enforces these requirements, and an array that ignores them does not pass inspection.

The numbers both trades should know

The access and pathway rules live in the fire code, broadly tracked in International Fire Code Section 1205 (numbering and adoption vary by jurisdiction; the related IBC residential appendix is published by ICC as Appendix Chapter P, Section P-1205). The figures that drive layout are consistent enough to design around:

Requirement	Typical figure	Notes
Ridge setback, array ≤ 33% of roof plan area	18 in (457 mm) clear on each side of the ridge	Standard, non-sprinklered
Ridge setback, array > 33% of roof plan area	36 in (914 mm) clear on each side of the ridge	Standard, non-sprinklered
Ridge setback with NFPA 13D sprinklers, array ≤ 66%	18 in (457 mm)	Sprinklered alternative
Ridge setback with NFPA 13D sprinklers, array > 66%	36 in (914 mm)	Sprinklered alternative
Access pathways	Not fewer than two, on separate roof planes, ≥ 36 in wide, edge to ridge	At least one on the street or driveway side
Pathway structural note	Over areas able to support firefighters	Not over fragile or non-bearing surfaces

These are summarized in code-reference guides such as UpCodes' roof access and pathways section. Local amendments change specifics, and some jurisdictions are stricter, so the AHJ is always the final word.

Why does this belong in a roofing-and-solar collaboration discussion rather than a pure solar one? Because the roofer knows the roof geometry, the ridge lines, the valleys, and where a firefighter could actually stand, and the solar designer is often working from imagery. When the roofer flags the real ridge and edge conditions early, the solar team can lay out pathways and setbacks that survive inspection on the first try instead of cutting modules out of the design in front of the homeowner.

There is a real tension baked into these rules that both trades feel: every inch of setback and every pathway is roof area that cannot hold a panel, which reduces system size and the production the homeowner was sold. That tension is exactly why the conversation has to happen at design time. A solar designer who maximizes coverage in a vacuum and a roofer who knows the code will collide, and the homeowner is the one who hears "we have to remove four panels" on inspection day. Resolving it early means setting realistic production expectations against a code-compliant layout from the start, rather than promising a number the roof geometry cannot legally deliver.

Setbacks are about ventilation and access, not decoration

It helps crews respect these rules when they understand why they exist. The ridge setback gives firefighters a place to cut a ventilation hole during an attic fire without standing on energized modules. The pathways give them a route to get there and to access other parts of the roof. The requirement that pathways sit over structurally sound, firefighter-supporting areas is not a formality; a pathway drawn over a fragile skylight or a non-bearing section is not a pathway. The roofer's read on which roof areas can actually bear a firefighter is genuinely useful design input here, and it is input the solar designer usually does not have from a satellite view.

Rapid shutdown and the roof, briefly

Electrical rapid shutdown is a solar and electrical responsibility, not a roofing one, but the roofer benefits from understanding it because it affects equipment locations and conduit routing. Under the 2023 National Electrical Code, Article 690.12 generally requires conductors inside the array boundary to drop to a safe voltage quickly after shutdown is initiated, with specific approaches and exceptions, as covered in Solar Power World's summary of the 2023 NEC rapid shutdown changes. For the roofer, the practical takeaway is narrow: module-level electronics and conduit routing add small penetrations and equipment that need waterproofing coordination, and the roofer should know where they land so the flashing plan accounts for them. The electrical compliance itself stays with the licensed solar and electrical professionals.

Key 4: Coordinate Safety, Staging, Access, and Electrical Boundaries

Two trades on one roof multiply the hazards, and a coordination plan that does not address safety and staging is incomplete. Roofing and solar work both carry fall and electrical risk, and the work has to be sequenced so one crew does not damage the other's work or walk into a hazard the other created.

Fall protection and electrical hazards

Fall protection is the dominant construction hazard and it applies to both trades. OSHA's construction fall-protection requirement, 29 CFR 1926.501, and OSHA's roofing-worker guidance in Protecting Roofing Workers set the baseline expectation. Solar adds live electrical exposure, addressed in OSHA's electrical safety topic page and the construction electric-shock rule, 29 CFR 1926.416. The plan should name anchor points, ladder and lift locations, and the electrical lockout and energization steps so a roofer is never near energized DC conductors and a solar tech is never relying on an anchor the roofer was about to remove.

Staging that does not crush the roof

Staging is an underrated cause of roof damage. Pallets of modules, racking, ladders, and carts create traffic the original roofing scope may not have planned for, and a steep architectural roof or a low-slope membrane can be damaged by careless staging. The plan should state where material can be set, how it moves across the roof, which areas are off limits, and whether walkway pads or protection boards are required. The roofer is the right party to designate fragile zones, skylights, brittle sections, and traffic routes; the solar lead is the right party to confirm the equipment weights and footprint.

TWO-TRADE PRE-WORK SAFETY AND STAGING BRIEF

Project / address:
Date:
Roofer lead (name / phone):
Solar lead (name / phone):
Electrician of record (name / phone):

FALL PROTECTION
[ ] Anchor points located and shared with both crews
[ ] Ladder / lift positions agreed
[ ] Edge / skylight / fragile zones marked

ELECTRICAL BOUNDARIES
[ ] System de-energized / locked out before roof work near conductors
[ ] No roofer handles solar electrical components
[ ] Conduit / penetration locations confirmed before drilling

STAGING
[ ] Material staging area(s) designated (roof or ground)
[ ] Off-limits roof areas marked
[ ] Walkway pads / protection boards in place where required
[ ] Weather limits / stop conditions agreed

STOP-WORK TRIGGERS (pause and escalate)
[ ] Hidden deck damage found
[ ] Planned attachment conflicts with roof condition
[ ] Flashing detail cannot be installed per spec
[ ] Layout conflicts with fire-code pathway or setback

ESCALATION CONTACT: ____________________

Electrical boundaries are non-negotiable

The boundary is simple to state and important to hold: roofers do not handle solar electrical components unless they are separately qualified and authorized, and solar crews do not alter roof flashing or covering details without roofing coordination. Where electrical routing needs roof penetrations, conduit standoffs, attic access, or a wall transition, the location and the waterproofing responsibility go in writing before anyone drills. Field improvisation at the boundary between water and electricity is how the worst outcomes happen.

The stop-work discovery

Build a stop-work expectation into the plan. If the roofer opens a section and finds rotten deck, the right answer is to pause and get the deck repaired, not to mount racking over it on schedule. If the solar crew finds that planned attachments hit a rafter location that conflicts with roof condition, the right answer is an RFI, not a field guess. A short escalation list with names and numbers keeps a five-minute discovery from becoming a five-thousand-dollar dispute.

Key 5: Design for the Roof's Future Service, Not only Today's Install

The fifth key is the one everyone forgets because it pays off years later: the roof still has to be drained, inspected, and repaired with panels on it, and the array still has to be maintained. A layout that maximizes production while burying every drain, valley, and service path under modules creates a roof nobody can take care of. Good collaboration plans for the people who show up after the install crew leaves.

Drainage and access review

Before the layout is final, walk it for drainage and service access. Panels should not block drains, scuppers, gutters, valleys, crickets, or the routes a worker needs to clear debris and inspect ponding. The roofer can mark drainage paths, known leak-prone areas, and the sections most likely to need future access; the solar designer can adjust the layout or escalate the conflict. A row of modules that looks efficient on paper can make it impossible to clear a valley after a storm, and that trapped debris is a slow leak waiting to happen.

The leak-under-the-array protocol

Decide now what happens when a leak appears under or near the array, because it will eventually happen on some percentage of jobs and an emergency is the worst time to negotiate roles. Put these answers in the contract and warranty documents:

• Who removes and reinstalls modules if the leak is under the array, and at whose cost under what circumstances?
• Who protects and, if needed, disconnects the electrical components during roof repair?
• Who restores and recommissions the solar system afterward?
• Who documents roof condition before and after the repair?
• Which trade does the homeowner call first for a suspected roof leak versus a suspected solar fault?

Answering these in writing is not pessimism, it is the difference between a clean warranty call and a two-contractor standoff while a ceiling stains.

Consider a hypothetical that plays out somewhere every week. Say a homeowner notices a brown ring on a bedroom ceiling four years after a combined roof-and-solar job. The roofer says it is a solar penetration; the solar company says it is the roofer's flashing. Without a penetration record, nobody can prove which mount is over that bedroom, so both point fingers and the homeowner pays out of pocket. With a penetration record, the service team pulls the two modules over that room, finds the mount, checks the dated flashing photo against what they see, and assigns the repair in an afternoon. Same leak, completely different experience, and the only variable is whether the record existed.

Maintenance access the array did not erase

A roof with panels still needs the same maintenance a bare roof does, plus the array's own upkeep, and the layout should leave room for both. Gutters still fill with debris. Valleys still need clearing after storms. Skylights, vents, and chimney flashings still need inspection. The array adds panel cleaning, connector checks, and occasional inverter or optimizer service. If the layout buried the only path to a chimney or left no way to reach the gutters without walking on modules, the homeowner is stuck choosing between neglecting the roof and damaging the array. The roofer is the right party to insist on those access lanes during layout review, because the roofer is the one who knows what the roof will need over the next two decades.

Recordkeeping that survives the project

Future serviceability depends entirely on records that outlast the crews. Roofing closeout should include roof material data, the warranty documents, repair and final photos, and maintenance notes. Solar closeout should include equipment data, permits, inspection approvals, operating instructions, and utility records. And critically, the as-built has to capture what changed from the original plan: every relocated penetration, every layout shift made to clear an obstruction, every added service pathway, every deck repair. A shared, durable project record, whether a folder, a PM tool, or a roof-record platform like RoofPredict, lets the future service team and the homeowner find the truth instead of guessing. The record has to reach the service side of the business, not only the sales side, because the people who sell the job are rarely the people who fix it.

Stay in your lane on performance and money

A closing discipline that protects both trades: do not make production, savings, incentive, or payback promises that depend on factors outside roofing. The DOE's page on planning a home solar electric system is a good homeowner resource precisely because it frames production and savings as location- and design-dependent. The roofer's lane is roof readiness, waterproofing coordination, documentation, and service access. Wandering into financing math or tax treatment is how a roofer ends up owning a promise it cannot keep.

Climate and Region Change the Coordination Plan

The same array on the same roof needs a different coordination plan in Phoenix than it does in Buffalo or Tampa, and the two trades should name the regional drivers up front rather than discover them in the field.

Hail country (the Plains, the Front Range, parts of the Southeast). Frequent hail is hard on shingles and on the array glass, and it is the regional pattern that most often pushes the replace-first decision. A roof that has already absorbed a couple of hail seasons may have less life left than its age suggests, which is exactly the kind of wear that age-and-storm modeling on the outbound side, such as RoofPredict, is built to flag house by house before a crew ever climbs up. For the install itself, the coordination question is whether the roof should be replaced before the array goes on, since a hail event after install means inspecting and potentially repairing both the roof and the modules under them.

High-wind and coastal zones (the Gulf and Atlantic coasts). Uplift governs, design wind speeds are high, and AHJs enforce attachment spacing and edge-zone detailing strictly. Salt air also corrodes fasteners and flashing faster, so material selection matters. The roofer and installer should confirm corrosion-resistant attachment hardware and tighter mount spacing, and expect a more demanding permit review.

Snow-load regions (the Northeast, Upper Midwest, mountain West). Added array dead load stacks on design snow load, which makes the structural review more important. Snow sliding off panels can also damage gutters and create ice-dam dynamics at the eave, so drainage and gutter protection deserve extra attention in the layout review.

High-heat, high-UV regions (the Southwest). Sun degrades shingles and ages the roof faster than the calendar suggests, and roof-deck temperatures under the modules run high. The replace-first decision skews earlier here, and ventilation adequacy becomes a bigger part of the roofer's condition note.

None of these changes the five keys; they change the weighting. In hail and sun country, Key 1's replace-first decision dominates. On the coast, Key 2's wind and corrosion detailing dominates. In snow country, the structural and drainage reviews dominate. Naming the regional driver in the preconstruction meeting is how the plan gets tuned to the actual roof's actual climate.

How the Business Models Actually Fit Together

The collaboration question has a structural layer underneath the technical one, and it is worth naming because it shapes who has authority on the roof. There are three common arrangements, and each changes the coordination plan.

Roofer as subcontractor to the solar company. The solar company holds the customer relationship and brings in a roofer for the reroof or for flashing work. Here the roofer needs the scope and the penetration responsibilities pinned down tightly, because the solar company controls sequencing and the roofer can otherwise get blamed for layout-driven leaks.

Solar installer as subcontractor to the roofer. The roofer holds the relationship, often through a reroof, and adds solar by partnering with or subcontracting a solar EPC. This is increasingly common because roofers already have the homeowner's trust and the roof access. The roofer's exposure here is the opposite: owning the customer means owning the complaint, so the electrical and design boundaries with the solar sub have to be airtight.

Two independent contractors, homeowner coordinates. The homeowner hires each trade separately. This is the most failure-prone arrangement because no single party owns the seam between them, which is exactly why the preconstruction meeting and the shared record matter most here.

None of these is wrong, but the coordination documents change with each. The matrices and checklists in this piece are written to work under any of the three, as long as the blanks get filled in before work starts.

Common Coordination Failures, and How to Prevent Each One

The failures in this category are predictable, which means they are preventable. Here are the recurring ones with the specific countermeasure for each.

Late discovery of roof condition

The most common and most expensive failure is selling a solar plan before anyone documented active leaks, brittle shingles, soft deck, or ponding. The countermeasure is a short, photo-backed roof condition note produced before the layout is finalized, giving the homeowner and solar team a real chance to choose repair, replacement, redesign, or further review while it is still cheap to change course.

Unclear staging

Material and crews creating roof traffic the roofing scope did not anticipate damages membranes, shingles, gutters, and skylights. The countermeasure is the staging section of the pre-work brief: designated areas, off-limits zones, defined movement routes, and protection boards where required.

Weak penetration records

When mounts and conduit go in without before/during/after photos and product data, a later leak becomes an unsolvable argument. The countermeasure is the penetration record from Key 2, captured for every penetration and stored where the service team can reach it.

Drainage conflicts

A layout that buries drains, valleys, or service routes traps debris and hides ponding. The countermeasure is a dedicated drainage and access review before layout lock, with the roofer marking paths and the solar designer adjusting or escalating.

Warranty ambiguity

Homeowners assume a roof warranty plus a solar warranty equals total coverage. The countermeasure is stating in the project file which documents apply, which activities may need manufacturer review, and which trade to call first for a suspected leak versus a fault.

No change protocol

Field changes without updated records are the root of most future service problems. The countermeasure is a simple rule: if an attachment moves, a damaged area is found, a layout shifts, or an inspector requests a change, someone updates the photos and the written as-built before the crew leaves.

Questions Each Party Should Ask Before Work Starts

A short list of pointed questions surfaces most coordination gaps before they cost anything. Bring these to the preconstruction meeting.

A homeowner should ask both contractors:

• How many good years does my roof have left, and is that more than the array's design life?
• If a leak shows up under the panels, who removes the modules, who fixes the roof, and who pays under what circumstances?
• Which flashing or mount product are you using, and is it compatible with my roof warranty?
• Will the layout meet fire-code pathways and setbacks, and how many panels does that cost me versus the sales estimate?
• What records will I get at closeout, and where will the penetrations be documented?

A roofer should ask the solar installer:

• Where exactly do the penetrations land, and have you confirmed they hit framing or blocking?
• What is the attachment spacing, and does it match our local design wind speed at the edges and corners?
• Does the layout clear my drains, valleys, and the access I will need to service this roof later?
• Who owns the flashing install and its warranty, in writing?

A solar installer should ask the roofer:

• What is the roof's real remaining life, and should it be replaced before we mount anything?
• Which areas are fragile, off-limits for staging, or unsafe to anchor to?
• Are there warranty or manufacturer requirements that constrain how we attach or where we walk?
• Where are the existing penetrations and known leak-prone spots I should design around?

If any of these draws a shrug, that is the gap to close before material is ordered.

Coordination Checklist

Use this as the agenda for the preconstruction meeting and the closeout review.

ROOFER + SOLAR COORDINATION CHECKLIST

BEFORE DESIGN
[ ] Roof remaining-life range documented (covering, age, wear, deck, drainage)
[ ] Replace-first vs. mount-now decision made and recorded
[ ] If reroofing too: sequence agreed (tear off > deck > dry-in > roof > inspect > mount > electrical > close)
[ ] Business arrangement clear (who holds the customer, who subs to whom)

DESIGN
[ ] Fire-code pathways and ridge setbacks confirmed against actual roof geometry
[ ] Drainage, valleys, drains, and service routes kept clear in layout
[ ] Approved flashing / mount product named in writing
[ ] Attachment responsibility matrix filled in (no blank cells)

SAFETY + FIELD
[ ] Two-trade safety and staging brief completed
[ ] Electrical boundaries and lockout/energization steps set
[ ] Stop-work triggers and escalation contact agreed

DOCUMENTATION
[ ] Penetration record (before/during/after photo + product + installer + date) for every penetration
[ ] Roof closeout: material data, warranty, repair + final photos
[ ] Solar closeout: equipment data, permits, inspections, utility records
[ ] As-built updated for every field change
[ ] Leak-under-array protocol written into contract/warranty
[ ] Records delivered to homeowner AND to the service team

The difference between a roof that gets serviced cleanly in year eight and one that triggers a two-contractor blame match is almost always whether these boxes were checked before the crews showed up. The technical work is not the hard part. The coordination is, and it is entirely within both trades' control.

Sources checked: June 18, 2026.

FAQ

Should I replace my roof before installing solar panels?

Match the roof's remaining life to the array's. Solar systems are built to produce for 25 to 30 years, so if your asphalt roof is older than about 13 to 18 years or shows real wear, replacing it first usually beats paying to remove and reinstall the panels for a reroof later. Roofs younger than 10 years that are sound generally do not need replacement first. Get a professional condition assessment for anything in between rather than guessing from the roof's age alone.

Does installing solar panels void my roof warranty?

Usually not automatically, but the nuance matters. Manufacturers like Owens Corning keep the shingle warranty in place when solar is installed, while excluding damage caused by the solar work itself, since that is not a manufacturing defect. The bigger risk is workmanship: using non-approved flashing or non-certified installation can jeopardize enhanced warranty coverage. Confirm in writing that the chosen mount and flashing are compatible with your roof warranty, and keep a record of who installed each penetration.

Who is responsible for roof leaks around solar mounts?

It depends on who installed and inspected the attachment, which is exactly why it must be assigned in writing before work starts. Generally the party that performs a flashing or penetration owns leaks at that penetration, but vague scopes turn this into a standoff. Fill in an attachment responsibility matrix covering who selects the flashing, who installs it, who inspects it, and which trade the homeowner calls first for a suspected leak versus an electrical fault. Leave no responsibility blank.

What fire-code clearances does a rooftop solar array need?

Fire codes reserve space for firefighters. Typical requirements include an 18-inch clear setback on each side of the ridge when the array covers 33 percent or less of the roof plan area, and 36 inches when it covers more, plus at least two access pathways at least 36 inches wide on separate roof planes from edge to ridge, with one on the street or driveway side. Sprinklered homes have alternative thresholds. Local amendments vary, so the authority having jurisdiction is the final word.

How much does it cost to remove and reinstall solar panels for a roof replacement?

Cost guides put remove-and-reinstall work in the rough range of $200 to $300 per panel, which for a typical residential array often lands around $3,000 to $6,000 on top of the reroof itself. The figure rises with array size, steep pitch, and complex wiring. Because this cost only exists when the roof is replaced after panels are up, replacing an aging roof before installing solar is almost always cheaper than doing it in the wrong order.

Should a roofing contractor design the solar electrical system?

No. A roofer documents roof condition, access, drainage, and waterproofing, and coordinates flashing details, but solar design, electrical work, structural review, and code determinations belong to licensed solar professionals, electricians, engineers, and the authority having jurisdiction. The boundary protects everyone: roofers should not handle solar electrical components unless separately qualified, and solar crews should not alter roof flashing or covering details without roofing coordination. Keeping each trade in its lane is what makes the collaboration defensible.

What is the right sequence when reroofing and installing solar at the same time?

Do the roof first. A clean order is: tear off and inspect the deck, repair sheathing, dry-in with underlayment, complete the roof covering, pass the roofing inspection, then mount racking with manufacturer-approved flashing into the finished roof, then run electrical and pass the electrical and utility inspections, then close out with full records. This lands every penetration in a brand-new, properly flashed assembly and means the panels never have to come off for a reroof during their design life.

What records should a homeowner keep after a combined roof and solar project?

Keep roof condition and final photos, the roof warranty documents, solar equipment data sheets, all permits and inspection approvals, utility interconnection records, and a penetration record showing where every mount and conduit went with before, during, and after photos. Also keep the as-built showing any layout changes and a written protocol for who handles a leak found under the array. Store it where a future service crew can find it, not only in a sales folder.

How can a roofing contractor find the right homes to offer solar coordination?

Target by roof age and condition rather than knocking doors at random. Tools that estimate a roof-age range house by house, such as RoofPredict, help a contractor skip brand-new roofs and focus on homes where the roof-before-solar decision is genuinely live. That is a planning range, not an inspection, and it does not certify remaining roof life, but it sharpens outbound effort and gives a canvasser a real per-home reason to start a conversation about timing the roof and the array together.