In the last decade we’ve designed and permitted over 1,500 projects across Los Angeles County. A significant number of those started with a phone call from someone whose project was already in trouble — plans rejected, corrections piling up, designer out of answers. And in almost every case, when we pull back the layers and look at what went wrong, the root cause is the same: the designer misread the zoning code.
Not misread in the sense of getting a number wrong. Misread in the sense Plan Check Corrections Los Angeles of treating the code like a checklist instead of a system. They looked up the setbacks, checked the height limit, confirmed the lot coverage — and thought they understood what could be built. But the zoning code doesn’t work that way. It’s a web of interacting rules, overlays, definitions, and exceptions. Understanding any single provision in isolation is almost useless. Understanding how they interact is everything.

The Checklist Problem

Most designers approach zoning the way you’d approach a recipe: gather the ingredients, follow the steps, get the result. Setbacks are 5 feet on the side, 15 feet in the rear. Height limit is 35 feet. Lot coverage maxes out at 45 percent. They plug these numbers into their design, draw something that fits within the lines, and submit it to the city.
Then the correction letter comes back, and it says things they didn’t expect. The project is in a specific plan area that modifies the base setbacks. The height is measured differently because of the slope. The lot coverage calculation excludes certain areas but includes others that the designer didn’t account for. The garage counts toward floor area in this zone but not in that one.
None of these issues are hidden. They’re all in the code. But they’re not in the section the designer checked. They’re in the overlay, or the definitions chapter, or a footnote in the specific plan, or a zoning administrator interpretation from 2019 that the city still enforces.

Zoning Is a System, Not a Spreadsheet

What separates a competent designer from an experienced one is understanding that zoning provisions don’t exist independently. Setbacks interact with lot coverage. Lot coverage interacts with FAR. FAR interacts with density. Density interacts with parking. Parking interacts with the site plan, which loops back to setbacks. Change one variable and everything downstream shifts.
When I look at a property, I’m not reading the code line by line. I’m reading it as a system — looking for where rules intersect, where definitions create flexibility, and where overlays modify the base zoning in ways that might open up possibilities or shut them down. I’m asking: what does the code actually allow here when you read all of it together?
This is not something you develop from reading code summaries or attending a weekend seminar. It comes from submitting plans to dozens of different jurisdictions, getting corrections back, understanding why the examiner flagged what they flagged, and learning the nuances that each city cares about. A thousand projects teaches you things that no manual ever will.

When the Code Creates the Opportunity

Here’s what most people don’t understand about the zoning code: it doesn’t just restrict development. It creates opportunities — if you know where to look.
A client came to us in the City of LA wanting to add ADUs to a property. Every other designer they’d talked to approached it the obvious way — adding the units as part of one structure on the lot. The problem was that approach pushed the entire project into multi-family classification, which triggered more expensive construction type requirements and a significantly longer permitting timeline.
We read the code differently. By restructuring the project as individual duplexes rather than one multi-family building, we kept each structure in a simpler building classification. Same number of units. Same lot. Dramatically reduced construction costs and a permitting process that moved fast. The code allowed it — but only if you understood how building type classifications interact with the zoning provisions for the site.
This isn’t a loophole. It’s a legitimate code-compliant strategy that requires understanding how multiple sections of the code work together. A designer who reads the zoning as a checklist would never find it.

When the Code Blocks Everyone Else

The flip side is properties where the code appears to prevent development — and most designers take the code at face value and walk away.
We had a project on a slope lot where multiple designers had told the client an ADU couldn’t be built. The issue was the relationship between the retaining wall and the setback-from-slope requirement. On paper, it looked like a dead end. But when we actually analyzed the grading code alongside the zoning provisions, we found that if we could demonstrate the retaining wall met the required setback from the descending slope, the ADU was permissible at the toe of the hill.
Nobody else had done that analysis. They saw “slope” and “setback” and assumed the answer was no. We saw a technical question that had a technical answer — and once we demonstrated compliance on the plans, the city approved it.

Why This Matters for Your Project

If you’re a property owner or developer in LA County, the designer you hire is making code decisions that directly affect your costs, your timeline, and what you’re ultimately able to build. A designer who treats zoning as a checklist will give you a design that fits within the most obvious reading of the rules. A designer who understands zoning as a system will find the approach that maximizes what the code actually allows.
The difference between those two outcomes can be tens of thousands of dollars in construction costs, months of permitting time, and in some cases the difference between a project that’s feasible and one that isn’t.
We don’t skim the code. We study it. We read the overlays, the specific plans, the definitions, the zoning administrator interpretations. We cross-reference provisions across different chapters. And we do this before we draw a single line — because the code shapes the project more than the design does.

Start With a Real Analysis

If you have a property and you want to understand what’s actually buildable — not what a quick Google search suggests, but what a thorough code analysis reveals — call us. We’ll pull the zoning, review the overlays, evaluate the site constraints, and give you a straight answer about what’s possible. That conversation is free, and it’s the most valuable step you’ll take before spending money on design.