Which code cycle is your jurisdiction on? A pre-submittal checklist

Different jurisdictions adopt code editions on different schedules, and a plan set drawn to the wrong cycle usually comes back as a full resubmittal rather than a redline. Confirming the governing codes takes minutes at intake; missing them costs weeks after submittal. This is the checklist we run before a single line is drawn.

Before the first line is drawn

• Confirm the adopted NEC edition for the specific AHJ — not the state default. Local adoption often lags the state, and a handful of jurisdictions amend individual articles.
• Confirm the building and residential code cycle the structural sheets will be reviewed against, including any local wind and seismic amendments.
• Check the energy code (in California, the Title 24 cycle in force for the permit application date — the vintage follows the application, not the construction date).
• Pull the AHJ's own solar submittal guide if one exists. Many publish a checklist of required sheets, placards, and notes — reviewers use it, so we design to it.
• Confirm utility interconnection requirements in parallel. The AHJ and the utility review different things; a set that passes plan check can still stall at interconnection if the point of interconnection or protection scheme wasn't designed to the utility's standards.

The details that most often trigger corrections

• Rapid-shutdown and labeling requirements that changed between code cycles — placards drawn from the wrong edition are one of the most common redline sources we see.
• Load calculations that reference the wrong article year.
• Structural attachment details reused from a prior jurisdiction with different wind exposure or snow-load assumptions.
• Single-line diagrams that don't match the equipment schedule after a mid-design equipment substitution.

Make it someone's job

None of this is difficult — it just has to actually happen, on every project, before design starts. Whether you run it in-house or hand it to us, the pre-submittal check belongs at project intake, not at plan-check response time.

If you'd rather have a team that lives in these requirements carry it, that's what we do — start a project and we'll scope it against the governing AHJ and utility from day one.