Inside Operations

Solar Quality Assurance

A code inspection confirms the minimum. This confirms the installation matches the approved design, the manufacturer's instructions and a written workmanship standard — and that whatever it finds is actually reworked.

Two different questions about the same roof

A jurisdiction's inspector asks whether the installation complies with the adopted code. That is a floor, it is enforced by somebody with no contractual relationship to the workmanship standard, and it is satisfied by the minimum the code permits. A quality assurance programme asks a different question: does this installation match the set that was approved, the instructions the equipment shipped with, and the standard the customer was sold?

The gap between those two questions is where warranty callbacks come from. It is also where the commercial exposure sits, because the party that carries a defect is frequently not the party that created it — and a passed inspection is not a defence to a homeowner who can see the problem from the driveway.

What the jurisdiction's inspection is not looking for

This is not a criticism of inspectors. They are testing compliance with an adopted code, which is precisely their remit and no more than it. Solar inspection services covers that track in full — what the inspector checks, which scopes add reviewers, and how a field change becomes a re-inspection.

What falls outside it is a consistent list. The manufacturer's installation instructions, which carry the equipment warranty and are not the code. The detail on the approved plan set, where the installed work satisfies code by a different method than the one drawn and reviewed. Anything requiring an instrument, torque most obviously. Anything already covered by the time the inspector arrives. And the entire category of finish and workmanship that generates homeowner complaints without ever being a code matter.

What a solar installation quality audit checks works through the six areas an audit covers and how they differ from the inspection checklist. This page is about the programme around that audit — who owns it, how the sample is built, and what happens to a finding after it is written down.

Quality sits with the wrong party by default

In the common residential shapes, the party that performed the work and the party that carries the consequence are different people, and nothing automatically connects them.

A sales organisation that sells and hands off owns the brand the homeowner complains about and holds no workmanship warranty. The installing crew holds the warranty and has usually been paid and demobilised. Where a contractor of record engages installing partners as subcontractors, the obligation stays with the contractor of record whatever the crew did — which is the arrangement in which a quality programme is not optional, because the exposure is already owned.

The practical test of who should commission the programme is simple: whoever will be paying for the rework in two years should be choosing the sample today. A programme commissioned by the party being measured is a weaker instrument, which is the same reason vetting an installation partner works better before the first project than after the first complaint.

What a working programme has in it

Six components. A programme missing the last two produces reports rather than improvement.

A written standard, not a judgement call

The audit references the approved plan set, the manufacturers' installation instructions and a documented workmanship standard. Without a written referent, an audit is one person's opinion and is impossible to enforce against a subcontractor.

A designed sample with escalation triggers

New crews, new equipment, unusual roof types, new jurisdictions and any crew with a recent confirmed defect are sampled at a higher rate. A serious finding raises that crew's rate until a clean run brings it back down.

Evidence that survives a dispute

A structured, dated photo set on every project and a physical visit on the sample. Photographs establish what was visible on a date; they cannot establish torque, or anything already covered.

Defects classified by consequence

Safety and code compliance, durability and performance, and cosmetic are three different problems with three different clocks. Collapsing them into one list means the urgent items queue behind the trivial ones.

Rework with an owner and a verification step

Every finding carries a named owner and a due date, and closure requires evidence the work was done. A finding closed on assertion is not closed, and that single step is what separates a programme from a report.

Findings that reach the sourcing decision

Defect trends by crew, by equipment and by jurisdiction feed back into which partners receive future work. An audit that produces no consequence produces no improvement.

The step that is always dropped

Programmes fail at closure far more often than at detection. Finding defects is the easy half — a competent auditor on a roof will find them. What decays is the loop afterwards: a finding is raised, assigned, acknowledged, and then closed on somebody saying it was handled.

Closure needs evidence that the rework happened, not confirmation that it was scheduled. Without that, the defect rate that gets reported is the rate of defects recorded, which drifts steadily away from the rate of defects present, and the programme becomes a source of false comfort that is worse than no programme at all — because decisions get made on it.

The second decay is quieter. Where findings never reach the sourcing decision, the same crew produces the same defect on the next twenty projects and the programme catches all twenty individually. Trend data by crew, by equipment and by jurisdiction is what turns a detection cost into a reduction. It is also what makes partner selection an evidenced decision rather than a relationship one.

Where Seamless Home fits

Seamless Home is a licensed contractor. Where we are the contractor of record, the workmanship obligation is ours — so the quality programme exists because we carry the consequence, not as a service bolted onto someone else's risk.

Installing partners are engaged as our subcontractors, which is what makes a finding actionable: it routes into a live commercial relationship with a named owner, a due date and a verification step, rather than to a company that has been paid and has moved on. Findings feed the sourcing decision, and the audit sits in the sequence before project closeout rather than after it, so rework happens while access is already arranged.

Coverage is confirmed per service area rather than promised as blanket availability.

Frequently Asked Questions

What is solar quality assurance?+

It is a programme that checks completed installation work against the approved design, the equipment manufacturers' installation instructions and a written workmanship standard — and routes whatever it finds to rework before the project closes. It is distinct from the jurisdiction's inspection, which tests compliance with the adopted code and is satisfied by the minimum the code permits. The two ask different questions of the same roof. A quality assurance programme is also a programme rather than an event: it has a defined sample, a defined evidence standard, a defect classification, an owner for rework and a feedback path into which crews get future work.

Why is a passed inspection not enough?+

Because the inspector is testing a different thing. A code inspection establishes that the installation satisfies the adopted code, which is a floor rather than a specification, and the inspector is not contractually able to enforce the manufacturer's instructions, the approved plan set's detail, or a standard of finish. Attachment spacing that meets code but departs from the structural design, a flashing installed to a different manufacturer's method than the one specified, torque never verified, or cosmetic work that will generate a homeowner complaint are all invisible to a code inspection and all expensive later.

Who should commission a quality assurance programme?+

Whoever carries the consequence of a defect, which is often not the party that performed the work. Where a sales organisation sells and a separate crew installs, the defect surfaces as a homeowner complaint against the brand that sold it, while the workmanship warranty sits with the installing contractor. Where a contractor of record engages installing partners as subcontractors, the contractor of record carries the obligation regardless of who held the tools. In both shapes the party with the exposure should own the programme, because a programme commissioned by the party being measured is a weaker instrument.

Should every installation be audited, or a sample?+

A sample, designed rather than arbitrary, with defined triggers that escalate to full coverage. Auditing everything is expensive and, past a point, produces less information per unit of cost than a well-constructed sample. What makes a sample work is that it is not purely random: new crews, new equipment, new jurisdictions, unusual roof types and any crew with a recent defect are sampled at a higher rate, and a confirmed serious defect escalates that crew's rate until a run of clean results brings it back down. That structure is what converts an audit from a report into a control.

Can a quality audit be done from photographs?+

Partly, and the limits matter. Photographs are good evidence of what is visible and dated — labelling, conduit routing, module layout, visible flashing, site condition — and a structured photo set captured by the crew is a reasonable base layer for a large volume of projects. What photographs cannot establish is anything that is covered, anything that requires a measurement or an instrument, and anything about torque. A programme that relies on photographs alone measures the quality of photography. The workable arrangement is a structured photo set on every project and a physical visit on the sample.

What happens when a quality audit finds a defect?+

It gets classified and routed, and the classification is what makes the difference. A useful programme separates defects that affect safety or code compliance, defects that affect durability or performance, and defects that are cosmetic — because they carry different urgency, different owners and different commercial consequences. Each finding then needs a named owner, a due date, and verification that the rework was actually performed rather than merely scheduled. A finding closed on assertion is not closed. The verification step is the one most often dropped and the one that makes the programme credible.

Does a quality assurance programme reduce warranty callbacks?+

That is the case for it, and the mechanism is worth being precise about rather than asserting a number. Defects found before closeout are corrected while access is already arranged, the crew is still mobilised, and nobody has to negotiate entry to a home. The identical defect found two years later is a truck roll, a homeowner relationship problem and often a dispute about who owns it. The saving is in the difference between those two costs, multiplied by the proportion of defects a programme catches early — which depends on the programme's design, so no general figure would be honest.

Can Seamless Home run quality assurance on my projects?+

Yes. Seamless Home is a licensed contractor, and where we are the contractor of record the workmanship obligation is ours, which is the reason the programme exists rather than an add-on to it. Installing partners are engaged as our subcontractors, so findings route to a crew inside a commercial relationship that can act on them, and the results feed back into which crews receive future work. Coverage is confirmed per service area rather than promised as blanket availability.

Find the defect while the crew is still on site

Seamless Home carries the workmanship obligation where we are the contractor of record, so quality assurance is part of the scope rather than an add-on. Tell us what your defect and callback picture looks like.

Get In Touch