Why plan sets bounce: the patterns we see most

Most plan-check corrections aren't exotic. Across the projects that come to us — including sets other teams drew that we're asked to rescue — the same handful of patterns account for most of the bounce-backs. None of them are hard to prevent; they just have to be looked for before the package ships.

The usual suspects

The set was drawn to a different jurisdiction's rules. Reused details are efficient right up until they carry another AHJ's code cycle, wind exposure, or placard requirements with them. Every sheet needs a pass against the governing jurisdiction, not the last one.

The single-line and the equipment schedule disagree. A mid-design substitution — a different inverter, a bigger battery — that gets updated in one place but not the other. Reviewers diff these two documents; so should the drafter.

Structural assumptions nobody re-checked. Attachment spacing and ballast assumptions that were right for the original roof get carried onto a roof with different framing, decking, or exposure. If the structural sheet can't point to the actual roof data behind it, it isn't done.

The story the sheets tell is inconsistent. Site plan says one array; the string layout says another; the placard schedule references equipment that's no longer in the design. Each sheet may be fine alone — the package fails as a set.

The AHJ's own checklist was never opened. Many jurisdictions publish exactly what they want to see. A set that ignores the published checklist is volunteering for corrections.

What prevention actually looks like

Prevention comes down to sequence. Scope the governing codes at intake. Design to the AHJ's and the utility's published requirements, not from memory. Then run a genuine internal review before delivery: a second engineer, checking the set as a package, with authority to send it back until it's right. That loop is slower by a day and faster by a month.

That internal loop is the heart of our process — and it's why the overwhelming majority of the plan sets we deliver clear plan check on the first submittal. If your team is spending its time on plan-check responses instead of new work, we should talk.