Plan Check Correction Takeover

Plans do not get rejected because of wrong line weights or missing title blocks. Those are first-round comments that resolve in the first response. Plans get stalled because of fundamental disconnects between what the drawings show and what the code requires. After years of takeover and correction-response work across LA County jurisdictions, five patterns produce most of the stalled projects this office sees.

The prior designer checked the base zone and ran the development standards in the table for that zone. They missed an overlay, a specific plan, a Hillside Area designation, a substandard hillside street classification, a Coastal Zone overlay, a Methane Zone, a Very High Fire Hazard Severity Zone, a Hillside Construction Regulation Supplemental Use District, or a zoning administrator interpretation that changes the development standards on this lot. The plans were drawn around the wrong parameters. By the time plan check flags the issue, the entire design has to be reconsidered against the rule that actually applies.

On a hillside lot in particular, the BHO Slope Analysis Survey and Slope Band Analysis Maximum Residential Floor Area Verification Form referenced in LAMC §12.21C.10(b)(1) is not optional supplemental documentation. It is the prerequisite for establishing the maximum allowable floor area on the property. Plans drawn without the City Planning-approved survey attached cannot be finalized at LADBS plan check. A surprising number of stalled hillside projects trace back to this single missing form.

Especially common on multifamily projects, conversions, and lots with multiple existing units. The prior designer classified the building as one occupancy, but the unit count, configuration, sprinkler design, height, or proposed use triggers a different classification under LABC Chapter 3. Everything downstream is affected — fire-resistance ratings under LABC Tables 601 and 602, exiting under LABC Chapter 10, accessibility under LABC Chapter 11A or 11B, structural design loads, and energy compliance pathway.

On ADU projects, this often shows up as confusion between the four ADU pathways available under LAMC §12.22 A.33 and California Government Code §66323: Ordinance Detached, Ordinance Attached, State Detached, State Attached, plus JADU and Movable Tiny House. Each pathway has its own size limits, setback rules, height rules, and unit-combination rules. The ADU Correction Sheet PC/STR/Corr.Lst.20A walks through these as Part II.A through Part II.J. A plan drawn under one pathway and submitted as another is not a small revision — it is a fundamental classification problem that cascades through every sheet.

Every jurisdiction in LA County has its own submittal expectations, its own correction sheet structure, its own clearance requirements, and its own plan check culture. A designer experienced at LADBS may submit to Pasadena and miss that Pasadena requires its own zoning verification before structural review. A designer experienced in single-family work may submit a small multifamily and miss that LABC Section 506.3.4 frontage credits require a yards-for-an-oversized-building affidavit on R1/R2 occupancies. A designer who works mostly in flat areas may not realize that lots in designated Hillside Areas need a Joint Referral Form from City Planning before the BHO calculations finalize.

The result is a correction letter that flags missing clearances, missing forms, missing affidavits, missing supplemental correction-sheet compliance — and a prior designer who responds by adding notes rather than obtaining the actual clearance. Each round closes some items and reopens others. The list grows.

The most frustrating pattern from the owner’s side. The prior designer responds to each round of corrections, but the responses do not substantively address the underlying code issues. They tweak notes, adjust dimensions, add a leader line — and the same correction reappears in the next round, sometimes more pointedly worded. The correction list stays the same length, or grows.

What plan checkers want in a response is not a softer version of the same drawing. They want the code analysis that demonstrates compliance, the dimension that resolves the conflict, the structural detail that closes the loop, the engineering letter that addresses the soils condition, or the planning approval that authorizes what the architectural sheets show. A response that does not provide one of those does not move the project forward, regardless of how politely it is written.

Less common, but the messiest when it happens. The owner kept changing the scope during plan check, the prior designer kept making partial adjustments, and the resulting plan set is internally inconsistent. The structural sheets show one footprint. The architectural sheets show another. The Title 24 calculations were run on a third version. The grading plan does not match the floor plan’s finished floor elevations. The plan checker has flagged the inconsistency without specifying which version they are reviewing.

A takeover here usually requires resetting. Pick one version of the project. Conform every sheet to it. Resubmit clean. Owners do not always want to hear this — they want the cheapest version of the rescue, which is to patch the existing set. Patching almost always extends the stall. A clean reset is faster end-to-end even though it feels like more work upfront.

LA Department of Building and Safety correction sheets are structured documents. They come in standard forms — PC/STR/Corr.Lst.20A for ADUs, PC/STR/Corr.Lst.018 for R1/R2 occupancies, PC/STR/Corr.Lst.106A for Single Family Residential, PC/STR/Corr.Lst.107A for Baseline Hillside Ordinance properties, PC/STR/Corr.Lst.20b as a supplemental sheet for LA Residential Code Prescriptive Design, PC/GRN/Corr.Lst.004 for Green Building, plus the Single Family Dwelling/Duplex master sheet PC/STR/Corr.Lst.20 — with numbered sections corresponding to specific code requirements. A correction letter is not a free-form complaint. It is a structured response keyed to those numbered sections.

Reading one correctly means doing four things in order:

The first page of the correction letter names it. PC/STR/Corr.Lst.20A means the project is being reviewed against the ADU correction sheet. The corrections that follow are numbered against the sections in that document. If the project is a multifamily building reviewed against the R1/R2 sheet, the corrections will reference different numbered sections. Knowing which sheet applies tells the design team which baseline document the plan checker is working from. On hillside ADU projects, both the master ADU sheet and the BHO supplemental 107A apply. On a hillside SFD, the 106A and 107A both apply. Compounding sheets compound corrections.

Every correction on the sheet ends with a code citation. “Provide minimum 4-foot setback from rear property line and 4-foot setback from side property line” is followed by “(GC §66323(a)(2))” or “(LAMC 12.22 A.33(c)(8))” depending on which rule the plan checker is invoking. The citation is the answer key. It tells the takeover team which statute or ordinance the plan checker is reading the project against. The next step is opening that section and reading it word-for-word.

Surface corrections — missing notes, dimension call-outs, code-cycle references, energy form numbers, smoke-detector locations, drain detail callouts — resolve quickly. Structural corrections in the sense used here are not always about the structural sheets; they are corrections that reflect a fundamental problem with the project as designed. A wrong setback under the rule that actually applies is structural in this sense. A missing slope band analysis is structural. A wrong occupancy classification is structural. The difference between a 30-day rescue and a 6-month rescue usually comes down to how many of the open corrections are surface and how many are structural.

What was promised in the response to round one? Was it delivered in round two? What did round two flag that round one did not? When the same correction appears across multiple rounds, the response history tells the takeover team where the prior designer was stuck — whether on understanding the code, on getting client decisions made, on coordinating with engineering, or on producing the document that actually closes the item. The pattern in the response history is often more diagnostic than the corrections themselves.

The examples below describe patterns this office sees repeatedly. They are presented abstractly — no client names, no jurisdictional specifics where naming would burn an active relationship, no plan checker names. The point is the diagnostic pattern, not the war story.

The four patterns above produce most of the takeover work this office handles. The framework for executing a takeover is consistent regardless of which pattern is in play.

Plans, structural calculations, Title 24 reports, soils reports, surveys, all correspondence with the city including every correction letter, the prior designer’s response packages, and any clearance documents from other departments. Anything less is incomplete. A takeover proposal made without the complete file is a guess.

Before opening the plans. The correction letters tell the design team where the plan checker’s concerns are, which code sections are being cited, and how the prior designer’s responses have been received. The most recent letter is usually the most useful. The first letter often reveals whether the project entered plan check on solid ground or whether the issues started at the beginning.

The corrections show where the plan checker found problems. Reading the plans against the actual applicable code sections often shows additional issues the plan checker has not flagged yet but will, or shows that some flagged items are connected through a single underlying issue that, once resolved, closes multiple corrections at once.

Three categories of outcome: salvageable with targeted revisions; salvageable with substantial revisions but cheaper than starting fresh; not salvageable, where starting from scratch is faster and cheaper than continuing to patch a flawed set. The honest answer matters more than the comfortable one. An owner who keeps paying a takeover firm to patch a fundamentally flawed plan set ends up spending more than the redesign would have cost, with an unpredictable timeline. Saying that out loud at the assessment meeting is part of the work.

Resubmittals, plan check correction responses, clearance coordination, engineering coordination, and any required parallel approvals (City Planning, Coastal Development, HPOZ board, Cultural Heritage Commission) handled by the takeover firm. The owner does not have to manage the design team and the plan checker simultaneously. That is the entire value proposition of bringing in a takeover.

The takeover’s job is the most efficient path from where the project sits today to a permit in hand. Sometimes that is targeted fixes to existing plans. Sometimes that is a clean reset. The right call is whichever gets the owner to permit faster and cheaper, and the only way to know which is to read the file first.

Every working firm in Los Angeles County eventually lands on a desk that does not move quickly. This happens at every department, in every jurisdiction, with every workload. It is not unique to any one city or any one plan checker. It is a feature of any large permitting system staffed by humans with different review styles, different code interpretations, different caseloads, and different days.

Owners rarely hear this discussed openly. The reason is simple: the next submittal is on someone’s desk. Always. A firm that publicly criticizes a specific plan checker — by name, by department, even by reference — has just made every future project on that desk harder. Careful firms do not do this. The plan checker is not the story. The project is.

What a careful firm does instead is design for the system, regardless of who is reviewing. That means specific structural choices in how the plans are prepared, how responses are written, and how the project moves through plan check. None of these depend on who the plan checker is. All of them help the project regardless.

Every response to a correction includes the specific code section the plan checker cited and the specific code section the response invokes. Side by side, with the page numbers from the relevant correction sheet noted. A response that says “please see attached” without grounding the change in the code leaves room for the next round to flag the same issue. A response that quotes the code, applies it to the project, and shows the resolution does not.

A correction that requires a structural change should be accompanied by a brief letter from the structural engineer confirming the analysis. A correction that requires a Title 24 reanalysis should arrive with the updated CFIR form already attached. Plan checkers should not have to ask for the consultant’s confirmation a second time. When they do, the resubmittal slows.

A clouded revision marker on every sheet, a written summary of changes by sheet number, a clean response sheet that addresses each correction by number with the resolution and the sheet/detail/note where the change appears. This makes the verification appointment short and the result clean. A messy resubmittal package, regardless of how good the design is, invites the next round of corrections.

Even when the previous round felt pointed. The response addresses the technical point, not the framing. If the design team disagrees with the plan checker’s reading of the code, the response cites the alternative reading respectfully and presents both interpretations alongside the request for clarification. This is harder than it sounds. It is also load-bearing. The tone of the response is read by the same desk that will read the next round, and the round after that.

If a correction does not resolve after a careful, code-cited response, the appropriate next step is sometimes a conversation with the plan check supervisor. Not as a complaint about the plan checker. As a request for a reading on the code interpretation. The supervisor’s call may agree with the plan checker, in which case the design changes. The supervisor’s call may agree with the design team, in which case the project moves. Either outcome is faster than another round of escalating responses on the original desk. This step is for genuine code-interpretation conflicts, not for routine corrections, and it is used sparingly. Burning the supervisor route on small disagreements removes the option when it is genuinely needed. The full escalation playbook — supervisors, plan check chiefs, council offices, and the rare cases where escalation goes higher — is a separate piece. This pillar is about the takeover.

The point of all of this is that a careful firm protects the project against the variability of the system. The plan checker is not the variable the firm controls. The project, the plans, the responses, and the tone are. A takeover that lands on a difficult desk does not become a faster takeover by attacking the desk. It becomes a faster takeover by being careful enough that the desk has nothing left to flag.

Not every stalled project is worth rescuing. Some are. Some are not. The decision rests on a small number of diagnostic questions answered honestly after reading the file.

Zoning research at the outset was complete and the underlying classification is correct. The fundamental design — footprint, occupancy, structural system, site placement — is compliant with the rule that actually applies. The corrections in the most recent round are surface or moderate, not structural in the sense used in this pillar. The prior designer’s responses, even if superficial, did not actively damage the relationship with the plan check desk. The owner has a realistic budget for resubmittal cycles and is willing to wait the additional weeks the rescue requires.

Where these are met, salvage is usually the right call. Targeted revisions, code-cited responses, careful resubmittal package. The project finishes.

The underlying zoning classification is wrong, and changing it would require redrawing fundamental aspects of the project. The occupancy or building classification is wrong, and the cascading effects on fire-rating, exiting, accessibility, structural, and energy are extensive. The prior plan set is internally inconsistent across structural, architectural, and Title 24, and reconciling them takes more effort than redrawing clean. The original feasibility analysis missed a discretionary review trigger (HPOZ, Coastal, Mulholland, §12.24 X.28), and the project cannot proceed without that approval running in parallel — at which point starting fresh under the right framework is often faster than retrofitting. The prior designer is no longer reachable, the plan set was never fully delivered to the owner, or the digital working files have not been provided. Rebuilding on incomplete inputs is unreliable.

Where these are present, restart is usually the right call, even though it feels worse. The honest framing for the owner: the money already spent is gone regardless of what the next decision is. The only question that matters now is which path produces a permit faster and cheaper from today forward.

The sunk cost is not part of the decision. The decision is which path from here ends in permit. Sometimes that is patching forward. Sometimes that is restarting. A careful takeover firm will tell the owner which one applies before any new work begins.

A takeover firm’s answers to these questions reveal whether they will run the diagnostic carefully or treat the takeover as new work that happens to start with someone else’s plans.

The honest answer is yes. A takeover quote produced without reading the correction letters is a guess. Any firm willing to quote without seeing the file is also willing to discover the structural problems after the contract is signed.

The honest answer is yes, with the framing that the recommendation is a recommendation, not a refusal. A takeover firm that will only ever recommend salvage — because salvage is the engagement that pays — is not running the diagnostic in the owner’s interest. A firm that lays out both paths and recommends one with reasons is running the diagnostic correctly.

The honest answer involves code citations, coordination with consultants, restrained tone, and clear summaries by sheet. A firm whose answer is “we will get it through” without describing how is not describing a process. They are describing a hope.

The honest answer involves a careful escalation pathway, code-interpretation conversations with supervisors when warranted, parallel approvals where they apply, and continued substantive responses. A firm whose answer involves complaining about the plan checker, or whose answer assumes that the project will simply clear because the new firm is involved, is not engaging with how LA County permitting actually works.

The owner of the firm should be involved in the diagnostic and the response strategy on a stalled project, not just in the original sales conversation. Stalled projects are senior work. They benefit from the firm’s most experienced reading. Asking the question explicitly is reasonable.