What Is a Code Analysis Sheet?

You flip through your permit set and every sheet makes sense — a site plan, floor plans, elevations, all recognizable drawings. Then you hit one that's nothing but text, tables, and checkmarks. No walls, no rooms, no drawing at all. Just dense notes referencing code sections and numbers you don't understand. That's a code analysis sheet, and almost nobody explains what it is, because almost nobody outside the industry has heard of it.

Here's the plain-language version: a code analysis sheet — sometimes called a zoning analysis sheet, code compliance sheet, or code review sheet — is a written explanation of how your project complies with local building and zoning code. Where your drawings show what you're building, the code analysis sheet explains how it satisfies every applicable requirement. It's not a drawing. It's documentation, built specifically to make a plan checker's job faster and your approval more likely. Here's what's actually on one and why it matters.

Below is an annotated excerpt showing what a typical code analysis sheet looks like.

Why building departments want code analysis sheets

A code analysis sheet exists because it makes verification faster and more reliable for everyone involved, not because it's a bureaucratic hoop to jump through.

Speed. Without one, a plan checker has to manually verify every code requirement themselves — measuring setbacks off the site plan, calculating room sizes off the floor plan, cross-referencing egress requirements against window schedules. With a well-prepared code analysis sheet, that work is already done and documented. The plan checker reviews the analysis instead of recalculating everything from scratch.

Completeness. A thorough code analysis sheet demonstrates that the drafter or architect actually worked through every applicable requirement, rather than designing first and hoping it happens to comply. A missing or thin analysis often signals missing research behind it.

Clarity. When a requirement is satisfied, a good code analysis sheet says exactly how and points to exactly where on the drawings that's shown — "see Site Plan, Sheet S1.1, dimension A-1." That specificity heads off a lot of the back-and-forth that otherwise turns into a corrections letter.

Verification. Building departments are required to verify code compliance before issuing a permit. A detailed code analysis sheet is the evidence that this verification has actually happened, in a form the department can review efficiently.

Here's a concrete example of what this saves in practice: instead of a plan checker manually measuring your setback off the site plan and calculating whether it meets the requirement, the code analysis sheet states directly: "Setback from north property line is 25 feet. Required setback is 15 feet per [applicable code section]. Requirement satisfied. See Site Plan, Sheet S1.1, dimension A." That's a calculation the plan checker doesn't have to redo — and a calculation that isn't easy to overlook.

What's actually on a code analysis sheet

Project identification. Project name, address, owner, and the architect or drafter of record — basic information identifying exactly which project this analysis belongs to.

Zoning compliance. States the property's zoning district and the key requirements tied to it — minimum lot size, required setbacks, maximum lot coverage — compared directly against the proposed project. Something like: "Property is zoned R-1. Minimum lot size 7,500 sq ft; property is 10,000 sq ft ✓. Minimum setback 25 feet from street; proposed setback is 30 feet ✓. Maximum lot coverage 45%; proposed coverage is 40% ✓."

Setback calculations. A closer look at the specific distances from your structures to each property line, checked against the requirement — the single most commonly violated item in residential permitting, and the one this sheet exists partly to catch before submission rather than after.

Building code compliance. References to the applicable building code sections — commonly the International Building Code (IBC) or your state's adopted version of it — and an explanation of how the design satisfies each one. For instance: "Egress window required for bedrooms per code. Proposed bedroom includes a 3'0"x4'0" window with a 3'6" sill height above the floor. Requirement satisfied. See Floor Plan, Sheet F2.1, Window W-3."

Room size and dimension verification. Minimum room sizes required by code, checked directly against the proposed dimensions — "Master bedroom: minimum 70 sq ft required, proposed is 150 sq ft ✓."

Egress analysis. Verification that emergency exits meet code — minimum number of exits, adequate door width and height. A safety requirement the building department has to independently confirm, and one this sheet documents directly rather than leaving to be inferred from the floor plan alone.

Energy code compliance. Documentation that windows, insulation, and HVAC systems meet the applicable energy code — commonly referencing a state-specific standard like California's Title 24. Something like: "All windows: U-factor 0.32 (requirement: maximum 0.33 ✓). Wall insulation: R-19 (minimum required: R-13 ✓)."

Accessibility compliance, where it applies — verification against accessibility requirements for building types that require it, such as public or multi-family structures.

Fire and life safety. References to fire code sections relevant to the project — for example, the fire-rated wall assembly required between a garage and adjacent living space, and a note confirming the proposed wall assembly meets that rating.

Utility and drainage notes. Confirmation that drainage patterns and utility connections comply with applicable code — often a brief note about how site grading maintains existing drainage direction.

How a code analysis sheet connects to your drawings

A code analysis sheet isn't a standalone document — it's directly linked to the drawings, and that linkage is what makes it useful. When it states a requirement is satisfied, it points to exactly where on the drawings that's shown: "Setback from north property line: 25 feet required, 28 feet proposed. See Site Plan, Sheet S1.1, dimension A-1."

That reference means exactly what it says: go to the site plan, find the dimension labeled A-1, and you'll see the measurement being referenced. A well-prepared code analysis sheet makes every claim independently verifiable this way. A poorly prepared one lists requirements without pointing anywhere specific, leaving the plan checker to hunt through the full drawing set to confirm each item — which slows the whole review down and increases the odds something gets questioned.

Common elements you'll see

Checkmarks (✓) indicate a requirement is satisfied. An unsatisfied requirement, marked with an X or "not satisfied," generally shouldn't appear on a set that's actually ready to submit — if you see one, that's a sign the project isn't fully compliant yet. You'll see specific code section references (a city code section number, or an IBC section), direct cross-references to drawing sheets ("see Sheet F2.1, dimension A"), and often comparison tables laying out the requirement, the code minimum, the proposed figure, and the compliance status side by side. These formatting conventions exist to make the sheet fast to scan and easy to verify, not to make it look more technical than it needs to be.

Why some permits don't include one

Code analysis sheets aren't universally required. Some cities specifically require them as part of a complete submission. Others accept them without mandating them. Smaller jurisdictions may rarely see one at all.

Even where it's optional, a well-prepared code analysis sheet still helps: it speeds up plan check because the verification work is already done, it reduces the odds of a rejection because gaps get caught before submission rather than during review, and it signals to the plan checker that the project was actually researched rather than assembled and hoped for. Because of this, experienced drafters and architects tend to include one even when the local jurisdiction doesn't strictly require it — it's cheap insurance against a slower, more contentious plan check.

How to read a code analysis sheet

You don't need to understand every code citation on the page to check whether the sheet is doing its job. Look for:

• Every line ends in a checkmark or the word "satisfied" — any X or "not satisfied" is a real problem that needs resolving before submission, not something to submit and hope gets overlooked
• Cross-references point to actual sheet numbers that exist in your set — if it says "see Sheet F2.1," confirm that sheet is actually included
• Setbacks look roughly in line with what you'd expect for your property
• Room sizes look reasonable for their stated use
• Any heights or dimensions you recognize match what's shown on the corresponding drawings

You're not expected to independently verify every code citation is technically correct — that's the drafter or architect's job. You're checking that the analysis is complete, internally consistent, and free of obvious red flags.

Common mistakes in code analysis sheets

Missing entirely. Some drafters skip this sheet altogether, which shifts the full verification burden onto the plan checker — slower review, and a higher chance something gets questioned that a clear analysis would have preempted.

Incorrect calculations. The analysis states a 25-foot setback, but the actual measurement on the site plan is 20 feet. This kind of internal contradiction gets caught at plan check and causes a rejection.

Missing sections. No mention of egress or energy compliance at all — the plan checker has to request the missing documentation separately, adding a full resubmittal cycle.

No drawing references. The sheet claims "setback is 25 feet" without saying where that's shown, forcing the plan checker to hunt for it manually and slowing the whole review.

Incorrect code references. Citing the wrong code section or the wrong requirement entirely — a clear signal of rushed or incomplete research behind the analysis.

Why this should matter to you

A thorough code analysis sheet speeds up your approval, reduces the odds of a rejection, and gives you a genuine, readable confirmation that your project actually meets the requirements it's supposed to. A missing or sloppy one does the opposite — it slows down the process, raises your rejection risk, and leaves you wondering whether code compliance was ever really checked in the first place, or just assumed. See 7 Reasons Building Permits Get Rejected and Plan Check Corrections: How to Respond and Get Approved Faster for what happens when gaps like these aren't caught before submission.

Questions to ask your drafter or architect

Before you hire someone to prepare your permit set, ask directly: "Will you include a code analysis sheet?" "How do you verify setbacks and code compliance during design?" "Can you walk me through the code analysis for my specific project?"

A professional with a solid process will answer these without hesitation. If someone seems unfamiliar with the concept, or dismisses it with "most jobs don't need one," that's worth treating as a signal about how carefully they approach jurisdiction research generally — see Draftsman vs Architect: Which One Do You Actually Need? for the broader picture of what to look for when hiring.

FAQ

Do I need a code analysis sheet?

It depends on your jurisdiction — some require it, some don't, though it's increasingly common practice regardless. Even where it's optional, a good one speeds up approval and reduces the odds of a rejection, so it's worth asking for even if your city doesn't strictly mandate it.

Who creates a code analysis sheet?

Typically the architect or drafter preparing your permit set, sometimes with input from a specialized code consultant on more complex projects.

What's the difference between a code analysis and a drawing?

Drawings show what you're building — the physical layout, dimensions, and appearance. A code analysis sheet explains how that design complies with code, in written and tabular form, with references pointing back to where each requirement is demonstrated on the drawings.

How do I know if a code analysis sheet is correct?

Check that every line shows compliance (no X marks), that cross-references point to sheets that actually exist in your set, and that the numbers look reasonable given what you know about your property. You're not expected to verify every code citation yourself — that's the professional's responsibility.

Does my building department require a code analysis sheet?

It varies by jurisdiction. Call your building department directly and ask, or ask your drafter or architect whether it's standard practice for your city regardless of the formal requirement.

What if my code analysis sheet has an error?

Flag it to your drafter or architect immediately — an incorrect calculation here (a wrong setback figure, a miscited code section) can cause a rejection at plan check just as easily as an error on the drawings themselves.

Can I create my own code analysis sheet?

It's possible for a very simple project, but it requires accurately researching and citing the applicable code sections for your specific jurisdiction — work that's genuinely the drafter or architect's expertise. For most projects, this is better left to the professional preparing your permit set.

The bottom line

A code analysis sheet looks intimidating because it's dense with text and code references instead of familiar drawings, but the concept underneath it is simple: it's the written proof that someone actually checked your project against every applicable requirement, laid out so a plan checker can verify it quickly instead of redoing the work themselves. A good one speeds up your approval. A missing one just shifts that verification burden onto the building department — and onto your timeline.

If you want your code compliance documentation done thoroughly — every requirement checked, every claim tied to a specific drawing reference — that's built into how we prepare permit sets, not treated as an afterthought. Start with permit drawing services, or for the fuller picture of everything in a complete set, see What Is a Permit Set?