What to do when a solar plan reviewer is wrong

Start from the assumption that the correction is right. Most of the time it is, and the three usual causes have nothing to do with the reviewer being mistaken: a local amendment you were not designing to, a code edition the jurisdiction adopted that is not the one you had in mind, or a submittal requirement specific to that department.

That is not deference for its own sake. It is because the ladder above resubmission is slow, and climbing it for a correction that turns out to be correct costs the project weeks it did not need to spend.

But some corrections are genuinely wrong, and when one is, there is a documented route rather than an argument. This is that route, and the test for whether to use it.

First, get the correction in writing with its provision

Before anything else: obtain the correction as a written comment that identifies which provision of which adopted edition it rests on.

This single step resolves a large share of disputes, in one of two directions. Either the reviewer cites something that settles the question — usually a local amendment, which is exactly the category of requirement that is invisible unless you went looking for it — or it becomes apparent that no provision is being cited, which tells you what kind of correction you are actually dealing with.

The most common version of the third category on solar work is an edition mismatch: a correction citing a requirement from an edition the jurisdiction has not adopted, or one it adopted and then amended. Which edition applies is settled by what the jurisdiction adopted, not by what is current, and that cuts both ways — it is as often the reason a correction is right as the reason it is wrong.

The four routes, in order

1. A written clarification from the reviewer

Ask which provision the correction rests on, and state the provision you designed to. No argument, no position, just the two citations side by side.

Most genuine misapplications end here, because putting two provisions next to each other tends to resolve them without anyone having to be wrong out loud. It is also the rung that makes the later ones usable: an appeal that arrives without evidence that the reviewer was asked first is a weaker appeal.

2. A supervisory or building-official interpretation

A plans examiner performs the review. In most administrative schemes the authority to interpret the adopted code, and to decide questions about how it applies, rests with the building official or an equivalent designated position.

So a disagreement with a reviewer is not the end of the department's own process, and requesting an interpretation is a normal request rather than a confrontation. It is also fast relative to what comes next, often days rather than weeks.

3. A request to approve an alternative design

This is the rung most people do not know exists, and it is the right one more often than an appeal.

Most adopted building codes contain an administrative provision permitting the building official to approve a material, design or method of construction not specifically prescribed by the code, where it is shown to be equivalent to the prescribed approach in quality, strength, durability and safety. It is the documented path for a design that meets the intent of a provision without matching its prescriptive text.

Two things distinguish it from the earlier rungs. It is decided on submitted evidence — listing documentation, test data, an engineer's analysis — rather than on discussion, which means preparing one costs engineering time. And it produces a decision on the design rather than on the interpretation, which is frequently the outcome you actually wanted.

Confirm the provision, the evidence the jurisdiction expects, and who may submit it, because all three vary.

4. An appeal to the board of appeals

Where a jurisdiction constitutes one, a board of appeals typically hears claims that the code was wrongly interpreted or applied, or that an alternative was wrongly refused. What such a board generally cannot do is waive a requirement it considers clearly applicable.

That is the test for whether an appeal is your route at all. It is available for this is not what the adopted code requires. It is not available for this requirement is unreasonable. Filing the second as the first wastes the filing and the calendar.

Whether a board exists, how it is constituted, what it may hear and how long it takes are all jurisdiction-specific, and worth establishing before you need them rather than during.

The commercial test

Every rung above resubmission is slower than complying. That is the fact that should drive the decision, and it usually does not, because being right is satisfying and calendar is abstract.

While the file is open, design, engineering and permit fees are outlaid and no funding milestone has been reached, so the party carrying the working capital is paying for the argument regardless of who wins it.

Two conditions, both of which have to hold:

1. The correction materially changes the project. A smaller array, a service upgrade, a relocation that reduces production, an added cost the sales agreement does not cover. If the correction is a drawing change, make the drawing change.
2. You can cite the adopted text. Not how the requirement is handled in the next county, not what the current edition says, not what is normal. The provision, in the edition this jurisdiction adopted, as amended locally.

If both hold, escalate, and start at rung one. If either fails, comply and move the project. A correction that reduces the system size does trigger a third question — whether the homeowner has to re-sign and whether financing has to be re-papered — which is the design-change problem rather than the review one.

The record that makes any of this work

Nothing above is usable without a file. What it needs is unglamorous:

• The written correction, with its cited provision or the absence of one.
• Confirmation of the adopted edition and local amendments, obtained in writing during jurisdiction research rather than reconstructed afterwards.
• The submittal log: what was submitted, when, in what version, and what came back.
• Your own provision and calculation, in the plan set, legible to someone who did not draw it.

Assembled at intake, this is a few lines of research. Assembled during a dispute, it is a week of archaeology, and the outcome depends on the half of it that survived.

The bottom line

Most plan-review corrections that look wrong are not, and the cheapest response to almost all of them is to make the change. The ones that are wrong have a documented route above resubmission, running from a written clarification through a building-official interpretation and an alternative-design request to an appeal, and each rung answers a different kind of question.

Which route applies is decided by what kind of disagreement you are in, and whether to use any of them is decided by whether the correction costs more than the calendar does. Both answers are easier when the adopted edition, the local amendments and the correction process were established before the plan set was drawn — the same research pass that stops most corrections from being issued in the first place.

If plan review, corrections and the escalation record are things your projects currently improvise, that is part of the design and permitting layer Seamless Home runs for its partners. Get in touch.