The California Stewards Handbook

A field manual for community members who have decided to get serious about housing decisions in their city.

A Note Before You Begin

This handbook is for the person who has already shown up.

You’re past the moment of wondering whether you’re allowed to push back. Something landed in your city that shouldn’t have, or you can see something coming that will, and you’ve decided to do the work of understanding it. This document is for you.

It’s written from the assumption that you are intelligent, busy, and unwilling to be patronized. It will not flatter you. It will not pretend the situation is simpler than it is. It will give you the information that makes you genuinely effective, in the order you’ll actually need it, with templates and references for the moments when you can’t think clearly because you’re up against a deadline.

A few things to know up front.

This handbook will not tell you that your council is the villain, or that the state is the villain, or that any single party is the villain. The system that produced your situation is the result of choices made by many actors over many years, and pretending otherwise will make you less effective. The first principle of being effective inside a system is seeing it accurately.

This handbook will not tell you to stop being angry. Anger is fuel. It is also distraction. The work is to channel it into actions that move the system, and to recognize the difference between actions that feel satisfying and actions that actually produce results. They are not always the same.

This handbook is free. You can share it. You can copy from it. You can give it to your neighbors, post it on your local NextDoor, hand it to your council member. The work in it belongs to anyone who can use it.

A final note. By the end of this handbook you will have read about thirty pages of dense civic material. That is a real investment. We do not take it for granted, and we have tried to make every page earn its place. If we have failed in any specific section, write to us and tell us. The handbook is a living document and improves only when its readers push back on it.

—California Stewards

---

Part One: How the System Actually Works

Before you can change a system effectively, you have to see it accurately. This part is the orientation. If you read nothing else in this handbook, read this.

How Housing Actually Gets Approved in California

Most Californians believe that their city decides what gets built in their city. This was largely true a generation ago. It is significantly less true now, and the gap between the public’s mental model and the operating reality is one of the reasons situations like yours feel so disorienting.

What is closer to the truth: the state of California sets housing targets for every region. Regional councils of governments distribute those targets to individual cities. Cities are required to demonstrate, in a document called the Housing Element, how they will accommodate their assigned share. If the state housing agency — the Department of Housing and Community Development, or HCD — does not certify a city’s Housing Element, the city loses much of its discretionary authority over land use. Specific state laws then allow developers to bypass local review for projects that meet certain criteria.

Within that framework, individual project approvals fall into two broad categories. Discretionary approvals are the traditional path: the project is reviewed by city staff, vetted through public hearings, evaluated under the California Environmental Quality Act (CEQA), and ultimately approved or denied by the Planning Commission or City Council. Ministerial approvals are different: if a project meets a defined list of objective standards, the city is legally required to approve it, regardless of public opposition, environmental concerns, or council preference. There is no hearing. There is no CEQA review. The decision is made at a staff counter.

The trend over the last decade has been to convert as many approvals as possible from discretionary to ministerial. The state has done this through a series of laws, each of which we’ll cover in detail. The cumulative effect is that in many cities, in many circumstances, the council you elected has very limited power over the projects that get built.

This shift reflects a coherent policy theory. The theory holds that California has underbuilt housing for decades, that discretionary review has been used in many places to obstruct housing the state has determined is in the public interest, and that predictability and speed in the approval process encourage production. There is real evidence supporting parts of this theory. There are also real costs to the choices it produces, particularly when ministerial pathways are deployed in places where infrastructure has not been planned or funded for the resulting growth. The handbook returns to this tension throughout, because navigating it is the substance of the work.

This is the system. Now let’s look at its parts.

RHNA: What It Is, What It Isn’t

RHNA stands for the Regional Housing Needs Allocation. Every eight years, HCD calculates how much housing California needs to accommodate projected growth, replace overcrowded units, address overpayment for housing, and provide for healthy vacancy rates. That total — currently in the millions of units — is divided among California’s regions.

Each region has a Council of Governments — for Southern California, that’s SCAG; for the Bay Area, ABAG; for the San Diego region, SANDAG; and so on. The COGs distribute the regional allocation to individual cities through a methodology that considers transit access, jobs, environmental constraints, and other factors. Each city receives a number — its RHNA allocation — broken down into four income categories: very low, low, moderate, and above moderate.

A few things to understand about RHNA.

RHNA is a planning target, not a building requirement. Cities are required to plan for and zone for their RHNA numbers. They are not required to build them. This distinction matters because it is the source of much confusion. A city that fails to permit its RHNA over an eight-year cycle has not violated state law, strictly speaking. But it has likely failed to demonstrate adequate sites in its Housing Element, which has cascading legal consequences.

RHNA numbers are calculated, not negotiated. Cities can appeal their allocation through a defined process, but the methodology is set above the city level. By the time you hear about a number, the window to challenge it is usually narrow or closed.

The methodology has been challenged on technical grounds, in both directions. HCD’s calculation methods have been the subject of significant academic and legal critique. Some independent analysts argue the methodology produces numbers higher than underlying need would justify, citing examples of double-counting and questionable assumptions. Other analysts argue the opposite — that the numbers understate true need, particularly for the lower income categories where the gap between planned and actual production is largest. None of this means RHNA is fake. It means RHNA is genuinely contested terrain, and accurate technical analysis sometimes finds errors that affect a city’s allocation. It also means that no one analytical framework, including HCD’s, has the last word.

RHNA exists in a feedback loop with other state laws. A city that fails to certify its Housing Element becomes vulnerable to the override provisions described below. RHNA is not just a number; it is the trigger that activates the rest of the architecture.

HCD: The Agency, Its Role, and Its Posture

The California Department of Housing and Community Development is the state agency responsible for housing policy. It administers RHNA, certifies Housing Elements, allocates state housing funds, and increasingly serves as an enforcement body for state housing laws.

HCD’s posture has shifted significantly over the last decade. It has moved from a relatively passive regulatory role to an active enforcement role, frequently sending letters to cities, threatening loss of funding, referring cases to the Attorney General, and publicly naming cities it considers non-compliant. Cities that receive an HCD enforcement letter are required to respond within specific timeframes. Failure to do so escalates the matter.

You should know that HCD’s interpretations of state housing law are not always upheld in court. Cities have prevailed against HCD in litigation more than once. HCD’s letters carry administrative weight but are not, in themselves, judicial determinations. This is not a reason to ignore them. It is a reason to understand that “HCD says so” is not the end of an argument.

The State Streamlining and Preemption Provisions

This is the part that produces most of the cases that bring people to handbooks like this one. Here are the major streamlining and preemption provisions you will encounter, in plain language. These laws have a coherent rationale — to accelerate housing production by reducing local discretion in defined cases — and they have produced real effects, including some additional housing in places where it would otherwise have been blocked. They have also, in other cases, produced projects that exceed local infrastructure capacity. Both sides of that picture are real.

Builder’s Remedy. When a city’s Housing Element is out of compliance with state law, developers can propose projects that include a percentage of affordable units (typically 20% lower-income or 100% moderate-income). For these projects, the city cannot deny the application based on inconsistency with the city’s General Plan or zoning. The project can be substantially larger and denser than what the city’s own rules allow. Builder’s Remedy projects can still be reviewed under CEQA and for objective health and safety standards, but the discretionary basis for denial is largely removed.

SB 35 (now superseded by SB 423). Allows ministerial — that is, non-discretionary — approval of multifamily housing projects in cities that have not met their RHNA progress, provided the project meets specified objective standards including affordability, labor, and zoning consistency. No CEQA. No hearings. The city must approve within statutory timeframes if the project qualifies.

SB 423. The successor to SB 35, expanding ministerial approval to additional project types and tightening timelines. This is currently the most active ministerial pathway in the state.

AB 2011. Allows ministerial approval of multifamily housing in commercial zones, subject to affordability and labor requirements. Has activated significant development potential in commercial corridors.

Density bonus law. Permits developers who include affordable units to exceed the city’s base zoning by significant percentages, with reductions in parking requirements and other standards. Stacks with the above provisions in some cases, producing projects substantially larger than base zoning would allow.

There are others, and the list grows. The pattern is consistent: a state law identifies a category of project that the legislature has decided is in the state interest, and removes local discretion to deny it.

Where Responsibility Actually Sits

Most activated neighbors arrive at this handbook with a hypothesis about who is to blame. The hypothesis is usually one of these:

The council failed us. They didn’t fight hard enough.

The state overreached. They took away local control.

The developer is greedy and exploiting loopholes.

The agency is captured by industry.

Each of these is sometimes true. None of them is the whole story. The honest map looks more like this.

The state has, through a decade of legislation, narrowed local discretion deliberately and substantially. This is real. It is also a deliberate policy choice driven by the diagnosis that local control was producing too little housing. Whether you agree with that diagnosis or not, it is the operative theory of the laws now on the books.

Many cities have, through their own choices over a longer time horizon, contributed to the conditions that justified state intervention. Exclusionary zoning, refusal to plan for growth, and resistance to affordable housing in particular have a long history in California, and the state’s current posture is partly a response to that history.

Many cities have, however, been swept into a regime that does not distinguish between the cities that genuinely failed and the cities that did the work in good faith. This is also true. The streamlining framework is blunt. It treats Beverly Hills and Bell Gardens with the same instruments. The result is that even cities operating in good faith now face significant loss of authority.

Developers operate within the rules they’re given. Some are good actors. Some are not. The pattern of project siting, project sizing, and project type that you observe in your city is largely the predictable response to the incentive structure created by current state law.

HCD operates within its statutory authority but with significant interpretive latitude. Its current posture is more aggressive than its historical posture. This is a choice made by current leadership.

The point of this map is not to defuse your anger. It is to point it accurately. Different actors are responsible for different parts of the situation, and the response that works for each is different. Trying to challenge a state law at a city council meeting will fail. Trying to change a city decision through letters to your Assembly member will fail. The work of being effective begins with knowing which lever moves which part.

The next part of the handbook is about leverage — where it sits, how it works, and how to recognize what kind of move you are making at any given moment.

---

Part Two: Where Your Leverage Actually Is

This is the shortest part of the handbook. It is also the most important.

Every system has places where a small push produces a small change, and places where a small push produces a large change. The places where small pushes produce large changes are called leverage points. Most of what feels urgent in any complex system has very little leverage. Most of what has real leverage feels too distant, too abstract, or too slow to be worth your time.

This is the trap. You will spend the next weeks and months of your life being pulled toward urgent, low-leverage activity, while the high-leverage moves sit available and ignored.

The job of this handbook is to give you tools at every level, and to be clear with you about which is which. Here is the rough ordering, from least to most powerful, of the kinds of moves you can make.

Adjusting numbers. Trying to get a project reduced from 120 units to 90 units. Trying to get a setback increased by ten feet. Trying to get a height limit reduced by one story. These are real and sometimes worth doing. They almost never change the trajectory of anything. The system continues producing the same kinds of projects with slightly different parameters.

Working feedback loops. Submitting a public records request. Filing a CEQA comment that forces the city to respond. Sending evidence to the Fire Marshal. These restore information to places where it was missing or distorted. Information flows are surprisingly powerful — they often change behavior without any rule changing — but they only work when the information is accurate, well-targeted, and reaches someone with both the authority and the incentive to act on it.

Changing the rules. Getting a city ordinance amended. Getting a council to adopt a new policy. Getting a state law modified. These are slower, harder, and more politically expensive than the moves above. They are also where most durable change happens. Most local engagement ends without ever reaching this level, because the participants have exhausted themselves arguing over numbers and setbacks long before they get here.

Changing who has the power to make rules. Electing a different council. Recalling a member. Passing a ballot measure that reorganizes authority. These moves are rare but disproportionately powerful. They are also the moves that the activated neighbor is best positioned to contribute to — your council member’s reelection depends on a couple thousand votes from people in your neighborhood. Your vote and your time matter at a scale that they don’t at any higher level.

Changing the goal of the system. This is what reform efforts try to do, and almost all of them fail. The current goal of California’s housing system is, roughly, “produce housing units, particularly market-rate, as quickly as possible, by removing local barriers.” A different goal — for example, “produce balanced communities with infrastructure adequacy and equity as preconditions” — would produce a completely different set of laws, agencies, incentives, and outcomes. Goals are set by paradigms, and paradigms shift slowly.

Changing the underlying paradigm. The deepest level. The unstated assumptions that make the current system feel inevitable. That density alone solves affordability. That local discretion is the primary cause of underproduction. That state mandates, by themselves, produce supply. Each of these contains a partial truth, which is why they have such hold. Density does help affordability, in some markets, in some forms. Local discretion has been used to exclude. Mandates do produce some additional supply, particularly in jurisdictions that were previously the most restrictive.

The error is not in any of these claims. The error is in treating any of them as the whole answer. California’s housing failure is not a problem of local control versus state control. It is a problem of balance — between authority and capacity, between mandates and the infrastructure that makes mandates real, between market production and affordable production, between speed and adequacy. The current framework has tilted hard toward one set of answers, and the partial truths inside those answers have been treated as complete ones. The visible failures of the resulting system are what created the conditions you are now reading this handbook to address.

Paradigms shift when their assumptions become available for examination. You are reading this handbook, most likely, because the existing paradigm has just produced a visible failure in your city. Use that.

Here is the practical takeaway. As you go through this handbook, every tool you encounter sits at one of these levels. We will tell you which. The tactical chapters that follow — reading a project, understanding CEQA, public comment, council relationships, legal remedies — give you what you need for the situation in front of you. They are necessary. They are not, by themselves, sufficient. Part Five looks at the system that produces these situations in the first place. Both kinds of work matter. The mistake is to do only one.

---

Part Three: Reading a Project Like an Insider

The single largest gap between effective and ineffective community participation is project literacy. The activated neighbor who has never read a project file shows up to the council meeting with feelings. The activated neighbor who has read the project file shows up with specific findings, citations, and questions that staff cannot wave off. The difference is enormous, and almost no one outside the development industry teaches it.

This part teaches it.

Discretionary vs. Ministerial: The Distinction That Determines Everything

Every project approval in California falls into one of two basic categories. Knowing which category your project is in is the first thing you must determine, because everything else flows from it.

A discretionary approval is one where the city has the legal authority to approve, deny, or condition the project based on its judgment. Discretionary approvals require public hearings. They require CEQA review. They produce a record that can be challenged in court. They are the traditional way most projects have been approved in California for the last fifty years.

A ministerial approval is one where the city has no choice. If the project meets a defined list of objective standards, the city must approve it. There is no hearing in the traditional sense. There is no CEQA review. The decision is made by staff at a counter, on the basis of a checklist.

How do you tell which kind of approval you’re looking at?

Look at the application. Look at what state law the developer is invoking. If the application references SB 423, AB 2011, density bonus law, or specifies that the project is being submitted under a ministerial pathway, you are dealing with a ministerial approval. If the application is for a Conditional Use Permit, a Variance, a General Plan Amendment, or a Tentative Tract Map, you are very likely dealing with a discretionary approval.

The strategic implications are vastly different.

For a discretionary project, your tools are public comment, CEQA review, council politics, and traditional advocacy. You have a hearing. You have standing. Your voice is part of the record. The council’s vote can be challenged in court if the record supports the challenge. This is the territory most activated neighbors imagine they’re operating in, and it is where the traditional playbook of public participation actually works.

For a ministerial project, your tools are different and narrower. You cannot stop the project through public comment, because public comment is not part of the decision. You cannot challenge the project under CEQA, because there is no CEQA review. Your tools are limited to: (1) demonstrating that the project does not actually qualify for ministerial approval because it fails to meet the objective standards, (2) ensuring the city correctly applies the objective standards including any safety standards that remain applicable, and (3) addressing the structural issue at a different level entirely (state legislation, ballot measure, or litigation challenging the underlying law).

This is the most important single piece of information in this handbook. If you do not know whether your project is discretionary or ministerial, you cannot push back effectively. Find out first. Everything else follows.

CEQA: What It Is, What It Requires, and the Clocks You Need to Know

The California Environmental Quality Act is the single most powerful tool available to community members in discretionary project review. It is also the single most misunderstood, and it operates on timelines that, if missed, cannot be recovered.

CEQA requires public agencies to disclose and consider the environmental impacts of discretionary projects before approving them. The required documents range from a simple Categorical Exemption for projects that fall into defined low-impact categories, to a Mitigated Negative Declaration when impacts can be reduced to insignificance through mitigation, to a full Environmental Impact Report (EIR) for projects with potentially significant environmental impacts.

Each level produces a public document. Each level has a comment period. Each level has a statute of limitations during which the document can be legally challenged. These deadlines are short and unforgiving.

The most important deadlines for you to know:

For projects approved with a Notice of Determination filed by the city, the statute of limitations to file a CEQA challenge is 30 days from the filing of the Notice. Not from the project’s approval. From the filing of the notice.

For projects approved without a Notice of Determination, the statute is 180 days.

For projects with a Notice of Exemption filed by the city, the challenge period is 35 days from filing.

Miss these deadlines and the project is, for CEQA purposes, beyond challenge. There is no extension. There is no good cause exception in most circumstances. The clock runs from the filing date, which means you must monitor your city’s CEQA noticing system actively if a project is in your sights.

What CEQA requires the city to evaluate includes, at minimum: traffic, air quality, noise, biological resources, cultural resources, geology and soils, hydrology and water quality, hazards including wildfire, public services and utilities, and greenhouse gas emissions. The depth of evaluation depends on the document type.

Where CEQA is most powerful is in the intersection of two facts: the city must make findings that are supported by substantial evidence in the record, and a CEQA challenge is decided on the record. If the record does not contain evidence supporting the city’s findings — for example, if the city concluded that fire evacuation impacts were less than significant, but the record contains no evacuation analysis — the city’s approval is vulnerable.

This is where your work as a community member becomes legally significant. What you put in the record during the public comment period is what a court will see if the project is later challenged. Comments that point to specific deficiencies, cite specific evidence, and make specific demands for additional analysis become the foundation of any later legal action. Comments that express general opposition do not.

We will return to public comment as a tactical practice in Part Four. For now, understand this: every comment letter you write during a CEQA review period is a small contribution to a potential future legal record. Write accordingly.

Reading the Project File

Every project of any significance generates a public file that you have a right to access. The file contains, at minimum:

The application itself, including the developer’s narrative and proposed plans

The site plan, showing how buildings, parking, landscaping, and access are arranged on the site

Floor plans and elevations, showing the building’s interior layout and exterior appearance

Traffic studies, if required

Environmental documents, depending on the project type

Staff reports, which are the city planner’s analysis of the project

Public correspondence received to date

Any technical reports the developer has submitted to address specific issues (geotechnical, hydrology, biological, fire access, etc.)

Most cities make these files available online through a planning department portal. Some require an appointment to view in person. All are subject to the Public Records Act. Request the complete file early. You will need it.

When you receive the file, the documents that repay close reading vary by project type. For a typical residential project, prioritize in this order:

The site plan. This is the highest-information document in the file. It shows you the entire project at a glance — building footprints, setbacks, parking layout, vehicle access, pedestrian circulation, landscaping, and how the project meets the property line on every side. Look at it for at least an hour the first time. Look at the access points. Look at where vehicles enter and exit. Look at how the building relates to neighboring properties. Look at what isn’t shown — projects often omit features that would highlight problems.

The traffic study. If the project is large enough to require one, the traffic study is the document that quantifies the project’s vehicle impacts. Read the methodology. Read the assumptions about trip generation. Read what intersections were studied and what intersections were not. Traffic studies have known methodological weaknesses — comparison sites that don’t match the project’s actual context, peak-hour analyses that miss the true peak, baseline data that is years out of date, cumulative impact analyses that omit recently approved projects. None of these reflect bad faith on anyone’s part; they reflect the constraints of the methodology and the budget for any given study. They are also, often, where the most successful project challenges have been built.

The fire access drawings. This is often where the most consequential and least examined information sits. The fire access drawings show how emergency vehicles will reach the site, what the turning radii are, how the project meets fire code requirements. They do not, in most cases, show how residents will evacuate during an emergency. We’ll return to this in the next section.

The environmental document. If the project is being processed under CEQA, the environmental document is the city’s formal evaluation of impacts. Read every section. Pay particular attention to the impacts identified as “less than significant” — these are the conclusions most likely to be vulnerable if the supporting analysis is thin.

The staff report. When this is published, read it carefully. The staff report tells you how the city is planning to characterize the project to the council. It will identify the issues staff considers significant and the issues staff considers minor. The disagreements between the staff report and the actual evidence in the file are where your most effective comments will come from.

The Fire Safety Review Most Cities Skip

This section deserves its own header because it is the single most consequential gap in California project review, and the one most activated neighbors don’t know to look for.

When a city approves a residential project in or near a fire-prone area, the city is required to evaluate fire safety. In practice, what gets evaluated is fire access — can fire trucks reach the site, can hydrants be serviced, do roads meet minimum widths. This evaluation is conducted by the local Fire Marshal, typically based on submitted plans.

What is much less consistently evaluated is fire egress — can residents leave the site during an emergency. Egress is a different problem from access. Access is about getting fire trucks in. Egress is about getting residents, in their cars, out — sometimes simultaneously with fire trucks coming in, sometimes against a wall of traffic from upstream developments, sometimes through corridors that were designed for the original community’s population and have been progressively overloaded by every project added since.

California has a state law — AB 747 — that requires cities to identify evacuation constraints during their Safety Element updates. Compliance with this law has been spotty. Many cities have addressed it perfunctorily, identifying evacuation corridors without analyzing their actual capacity under emergency conditions.

What you should do, for any project in or near a fire-prone area:

Request the fire access analysis from the project file.

Request any evacuation analysis the city has performed for the project, the corridor, or the city as a whole.

Request all Alternative Materials and Methods Requests (AMMRs) filed for the project. We cover AMMRs in detail later in this part — they are often where the most consequential fire safety trade-offs are buried.

Examine whether the analysis includes external approach roads — the roads that residents would actually use to leave the area, not just the internal site roads.

Ask the Fire Marshal directly, in writing, whether the project’s evacuation impacts have been evaluated and on what basis.

In many cases the answer will reveal that no actual evacuation analysis has been performed. This is significant. Under CEQA, fire safety is an environmental impact. A finding of “less than significant” without supporting evacuation analysis is vulnerable.

We will return to a specific tool — JOSH — that is being used in California to fill this gap, in Part Four.

Alternative Materials and Methods Requests (AMMRs)

This is the section most likely to be unfamiliar even to readers who have been involved in local land use for years. It is also one of the most consequential places where fire safety analysis routinely falls short.

The California Fire Code contains prescriptive requirements — specific numerical standards — for many fire safety conditions. Maximum hose pull lengths from fire apparatus to building portions. Minimum fire apparatus road widths. Maximum dead-end road lengths and required turnaround dimensions. Hydrant spacing. Defensible space distances. These numbers exist because they encode operational requirements that have been validated through decades of fire department experience. They are the redundancy and margin that emergency response depends on.

When a project cannot meet a prescriptive requirement as designed, the path forward is an Alternative Materials and Methods Request, or AMMR. The applicant — typically through a fire protection engineer — submits a formal request to the local fire authority proposing an alternative that is intended to provide equivalent protection. The fire authority, usually through the Fire Marshal, evaluates the request and approves, denies, or conditions it.

AMMRs are a legitimate and necessary tool. Site conditions, building configurations, and project constraints sometimes make strict prescriptive compliance impossible, and the alternative-equivalence path allows projects to proceed with engineered solutions rather than rigid rule application. The mechanism itself is sound.

The structural problem is one of scope. AMMRs are evaluated narrowly — at the boundary of the specific code requirement being waived. The analysis does not, in most cases, extend to the systems-level consequences of the prescriptive failure. Two examples make this concrete.

Sprinklers as compensation for excessive hose pull length. A project cannot meet the maximum hose pull length from fire apparatus to portions of the building. The AMMR proposes additional sprinklers as the equivalent protection. The fire authority approves on the theory that sprinklers reduce the need for hose deployment. The narrow argument is reasonable — sprinklers do reduce fire severity. But the analysis treats fire suppression as the only relevant function. It does not address what hose pull length means for initial knockdown during the period before sprinkler activation, for fire department operational tactics, or for the redundancy that prescriptive standards exist to provide. The single-issue equivalence substitutes for systems-level analysis.

Internal road width remediation that ignores the full operational route. A project’s internal fire apparatus roads do not meet width requirements. The AMMR addresses the width issue at specific internal locations. The fire authority approves. But the analysis takes the project as the unit of evaluation and ignores the route fire apparatus must traverse to reach the project — city streets, choke points, intersections — and ignores the cumulative effect of similar AMMRs granted to neighboring projects. The internal road width is technically remediated. The system-level question of whether emergency response actually works at the scale of the larger infrastructure is unasked.

The pattern generalizes. AMMRs are typically granted on narrow analytical grounds that miss systemic consequences — most importantly, the consequence that residents have to evacuate through the same substandard infrastructure, sometimes simultaneously with fire apparatus coming in. The AMMR document, in most cases, contains no evacuation analysis at all. It contains a narrow equivalence argument about fire suppression.

For any project of significance in or near a fire-prone area, you should:

Request all AMMRs filed for the project. They are public records. The fire authority and the city building department will both have copies.

For each AMMR, identify the specific code requirement being waived and the specific compensating measure proposed.

Examine what the AMMR analysis considered and what it did not consider. Did it address the systems-level consequences of the prescriptive failure, or did it stop at the boundary of the specific issue?

Examine whether the AMMR addressed evacuation at all. In most cases it will not have. This is a legitimate question to raise in writing to the Fire Marshal and in public comment.

Examine cumulative AMMR patterns. If the same project, or projects in the same corridor, have multiple AMMRs each addressing different prescriptive failures, the cumulative effect on system-level emergency response capacity may be significant even if each individual AMMR is defensible.

This is one of the highest-leverage technical investigations available to a community member, because it operates inside the existing regulatory framework, uses public documents, and produces findings that are difficult to dismiss. A specific, written question to the Fire Marshal — did the AMMR analysis for this project consider evacuation impacts, and if so, on what basis? — forces a written answer that becomes part of the public record.

Mitigation Monitoring and Reporting Programs (MMRPs)

Separate from AMMRs, but worth knowing about, is the CEQA-required Mitigation Monitoring and Reporting Program, or MMRP.

When CEQA review identifies a significant environmental impact, the city is required to adopt mitigation measures to reduce or avoid that impact. The mitigation measures and the monitoring obligations associated with them are codified in the MMRP. The MMRP specifies what mitigation is required, when it must be implemented, who is responsible, and how compliance will be verified.

The MMRP is part of the project approval record. It can and should be requested as part of any project file review. Two questions to ask of any MMRP:

Are the mitigation measures specific and enforceable, or vague and aspirational? A measure that requires “the applicant shall reduce traffic impacts to the extent feasible” is not a real mitigation — it has no objective standard for compliance. A measure that requires “the applicant shall install a traffic signal at [specific intersection] prior to issuance of the 50th certificate of occupancy” is enforceable. The difference matters because mitigation measures that are vague at adoption tend to disappear in implementation.

Is there a compliance reporting mechanism? Cities are required to monitor mitigation compliance, but the rigor varies enormously. Some cities track MMRP compliance actively. Others adopt MMRPs at approval and never revisit them. Asking your city’s planning department for documentation of mitigation compliance for past projects is a useful exercise; the answer reveals how seriously the city treats its own conditions of approval.

If a project was approved with mitigation measures that were never implemented, the city’s failure to enforce its own conditions becomes a legitimate and actionable issue.

Infrastructure Adequacy

The last category to evaluate is whether the infrastructure to support the project actually exists. The categories to examine:

Water supply. Does the project have a will-serve letter from the water district? Has the water district demonstrated supply adequacy for buildout, or is the city relying on planning-level estimates that have not been validated against actual hydrology and entitlement?

Wastewater capacity. Does the sewer system have capacity for the projected flow? Are there capacity constraints downstream that would require upgrades?

Roads. Has the project’s traffic study evaluated cumulative impacts including all approved-but-unbuilt projects in the vicinity?

Schools. What is the projected student generation, and does the school district have capacity? School impact fees are a separate matter from capacity.

Fire protection. Beyond the access and evacuation analysis, does the local fire department have capacity to serve the additional units? What is the projected response time?

For each of these, the question is not whether the project pays its proportional share through fees. The question is whether the actual capacity exists. Fees do not, by themselves, produce infrastructure. A project that pays full impact fees in a city that has been deferring infrastructure upgrades for a decade is still a project being added to a system that cannot adequately serve it.

This is a transition into the structural diagnosis we’ll come back to in Part Five. For now, understand: infrastructure capacity is a legitimate issue to raise, and most CEQA documents address it superficially. Pushing for substantive evaluation of capacity is one of the more productive lines of inquiry available to you.

---

Part Four: Tactical Tools

This part is a working toolkit. Each tool is presented with its purpose, when to use it, when not to, and how to actually deploy it.

Public Records Requests

Under the California Public Records Act, you have the right to request, and the city has the obligation to provide, most documents in the city’s possession that relate to public business. This is one of the most underused tools available to community members.

When to use it. When the project file you’ve been shown is incomplete. When you suspect documents exist that haven’t been published. When you need correspondence between staff and the developer, between the city and HCD, between the Fire Department and Planning. When the city has produced a finding and you need to see what evidence supports it.

How to deploy. Send a written request, ideally by email, to the City Clerk. Specify the records you are seeking with as much precision as possible. Cite the Public Records Act (Government Code Section 7920.000 et seq., formerly 6250 et seq.). State your preferred format (email, electronic copies). The city has 10 calendar days to respond, though they can extend in defined circumstances.

A template:

Dear City Clerk:

Pursuant to the California Public Records Act (Gov. Code §§ 7920.000 et seq.), I am requesting copies of the following public records:

[Specific document or category] [Specific document or category] [Specific document or category]

I prefer to receive these records electronically, by email if possible. If any portion of these records is exempt from disclosure, please provide the non-exempt portions with the exempt portions redacted, and identify the legal basis for each redaction.

Thank you for your assistance.

[Name] [Address] [Email]

A note on cost. Cities can charge for the direct costs of duplication. They cannot charge for the time staff spends locating, reviewing, or redacting records. If you receive a cost estimate that appears to include staff time, push back in writing.

A note on timing. Records requests take time. If you need documents for a hearing, file the request well in advance. If the city is delaying, write back. If they continue to delay, the next escalation is a letter that cites the specific PRA timelines and notes that further delay may be considered a denial subject to legal challenge. Most cities respond at this point.

Public Comment That Lands

Public comment is the most accessible and the most misunderstood tool. Done well, it places specific findings into the public record, signals organized opposition to decision-makers, and in CEQA contexts contributes to a record that supports later legal challenge if needed. Done poorly, it produces a frustrating experience for the speaker and very little change in the outcome.

The principles of comment that lands:

Be specific. Not “this project is too big” but “this project is 47% larger than the General Plan permits, and the staff report does not address how it qualifies for that increase.” The specific comment forces a specific response. The general comment is absorbed into the noise.

Cite the document. Comments that reference specific pages of the staff report, specific sections of the EIR, specific findings in the application have weight. Comments that don’t reference documents are treated as opinion.

Make a specific demand. Not “we need to study this more” but “we request that a supplemental traffic analysis be prepared evaluating cumulative impacts including [list of projects], and that the public hearing be continued until that analysis is available.” Demands that can be granted or denied force a decision. Demands that are vague produce no decision at all.

Coordinate with neighbors. If five people speak, each on a different specific issue, with citations and demands, the cumulative effect is far greater than one person speaking on all five issues. The 1-3-1 framework is useful here: one problem statement, three pieces of supporting evidence, one specific recommendation. Per speaker. Pre-coordinated so the issues don’t overlap.

Speak to the council, not the room. The applause from the audience is gratifying. It does not affect the vote. The four people sitting on the dais, looking at their packets, are the only audience that matters. Speak to them.

Submit your comment in writing as well. Verbal comments at the hearing are part of the record, but they’re transcribed and easily lost. A written submission, ideally in advance of the hearing, is more durable and easier to cite later.

Council Member Relationships

Most activated neighbors approach their council members the wrong way. They show up in opposition, accuse the council of failing them, and then are surprised when the relationship is hostile thereafter.

A different approach. Your council member is, in most cases, a part-time elected official who depends on community input to understand what is happening in their district. They are typically overwhelmed, under-resourced, and operating with limited information. They will be more effective on your issues if they have better information, and they will be more receptive to your input if you treat them as a partner rather than an adversary.

How to actually have a relationship:

Request a meeting. Most council members will meet one-on-one with constituents, usually at City Hall, sometimes for coffee. Ask. The first meeting should be relationship-building, not advocacy. Tell them who you are, what you care about, and why you are getting involved. Ask them about their priorities. Listen.

Be useful. When you find something — a deficiency in a staff report, a concerning pattern in the project file, a specific question they should ask staff — share it directly. Become the source they go to when they need ground truth. Your value to them is intelligence and analysis they can’t get anywhere else.

Be reliable. When you say you’ll send something, send it. When you commit to attending a meeting, attend. When you tell them how many people you can mobilize, deliver. Reliability is the currency of political relationships.

Don’t surprise them. If you are going to oppose them publicly on something, tell them first. If you are going to organize a comment campaign on a particular issue, give them a heads-up. Surprise is the fastest way to lose access.

Recognize when they have no choice. On ministerial approvals, they truly cannot deny. On state-mandated rezoning, they truly are constrained. A council member who is forced to vote yes on a Builder’s Remedy project, while you scream at them at the dais, will not be your ally next time. A council member who you treat with understanding when the law gives them no choice, and who you support publicly when they push the boundaries of the law on your behalf, becomes a long-term partner.

When to Involve Lawyers, and When Not To

Legal action is the highest-cost tool in your kit, and it is the one most often deployed wrongly.

The honest framing: most local situations do not benefit from litigation. Most that do, benefit only from the threat of litigation, not its execution. A small number — usually those involving CEQA defects, procedural violations, or specific statutory breaches — genuinely require a lawyer to be effective. Knowing the difference is critical.

Categories of legal action you may encounter:

Writ of mandate (mandamus). The most common vehicle for challenging a city’s land use decision. A petition asking the court to compel the city to set aside an approval that violates law. The grounds are typically procedural (the city failed to follow required process), substantive (the city’s findings are not supported by substantial evidence), or both. CEQA challenges are usually brought as writs of mandate.

CEQA challenge. A subset of writ proceedings, with specific procedural rules, short statutes of limitations, and significant fee-shifting provisions in some circumstances. CEQA challenges are technical. They require lawyers with CEQA experience.

Inverse condemnation, due process, takings. Less common in the housing context but occasionally relevant. These typically involve constitutional claims about the city’s actions affecting property rights.

Equal protection or discrimination claims. Rare and difficult, but occasionally available where a city’s land use pattern has a documented discriminatory effect.

The decision tree:

Is there a specific procedural or substantive violation? Not “we don’t like this project” but “the city failed to perform required environmental review” or “the project does not actually qualify for ministerial approval under SB 423 because [specific reason].” If there is no specific violation, litigation will not help you.

Are you within the statute of limitations? CEQA is 30/35/180 days depending on the noticing. Most other land use challenges are 90 days or less from the decision. If you’re outside the window, the question is moot.

Do you have standing? This usually means living near the project, paying property taxes in the city, or having participated in the public process.

Have you exhausted administrative remedies? Most claims require that the issue have been raised during the public comment period at the local level. If you didn’t raise it then, you generally cannot raise it in court.

Can you afford it? Initial CEQA litigation typically runs $25,000 to $100,000 in attorney fees through the trial court level. Appeals add more. Some firms work on contingency or reduced fees for community groups. Some cases are eligible for fee recovery if you prevail. Many are not.

When to consult a lawyer. Early. As soon as you suspect a procedural or substantive violation that might be actionable. The cost of a one-hour consultation is small. The cost of missing a statute of limitations is total.

When not to consult a lawyer. When your complaint is fundamentally about the merits of the project rather than a specific legal violation. When you are still within the public process and can resolve the issue through public comment, council action, or political means. When you are looking for validation rather than counsel.

A note on pro se litigation. Filing a writ of mandate without a lawyer is technically possible. Doing it well is essentially impossible without legal training. The procedural rules are unforgiving, the briefing standards are demanding, and the consequences of a procedural error can be permanent. If you cannot afford an attorney, look for a public interest firm, a law school clinic, or a pro bono arrangement. Do not file pro se on a CEQA matter unless you have legal training.

JOSH and the Evacuation Analysis Question

One more tactical tool worth knowing about, because it addresses the gap we identified in Part Three.

JOSH is an open-source software tool developed to perform standardized evacuation analysis at the project, corridor, and city scale. It models how long it takes residents to evacuate a given area under various emergency conditions, including the contributions of approved-but-unbuilt development. The tool is licensed under the AGPL — meaning it is free to use, modify, and distribute, with the requirement that improvements be shared back.

JOSH was built specifically to address the AB 747 compliance gap — the requirement that cities evaluate evacuation constraints during Safety Element updates, which many cities have addressed perfunctorily. The methodology behind JOSH (the “ΔT” methodology, which measures the difference between baseline evacuation time and post-development evacuation time) is being published as peer-reviewed academic work through Worcester Polytechnic Institute.

Why this matters to you. When you ask your city to evaluate the evacuation impacts of a project or a corridor, the city’s first response will often be that no standardized methodology exists. JOSH is a standardized methodology. It is open. It is documented. It has been used by cities including Encinitas, Solana Beach, and Del Mar in their AB 747 compliance work. Your city can use it. There is no licensing barrier and no cost to deploy the tool itself. A city with technical staff can stand it up directly from the documentation. Cities that want assistance with city-specific maps, data preparation, and implementation can engage CSA for professional services in the range of $75,000 to $95,000 — well within the budget cities routinely spend on consultants for less consequential analyses, but optional. The tool is free either way.

How to deploy this. When pressing your city on evacuation analysis, point at JOSH specifically. Ask whether your city has considered using it for its Safety Element update or for project-specific evacuation analysis. Provide the website. Provide the documentation. Take the “no methodology exists” answer off the table.

The tool is at https://twgonzalez.github.io/josh/. The methodology documentation is published. JOSH is free to deploy, and the AGPL license guarantees it cannot be made proprietary.

---

Part Five: Why the System Keeps Producing Situations Like Yours

Stand back from your specific situation for a moment and look across California. The situation you are in is not unusual. Cities up and down the state are absorbing similar projects, with similar deficiencies, on similar timelines, producing similar damage to similar infrastructure. The names change, the addresses change, the project type changes, but the underlying pattern is the same.

This is not accidental. The pattern is being produced by the system. Understanding why matters, because it changes what you are actually pushing back against.

The Diagnosis

Everyone agrees California has a housing affordability crisis. The disagreement is over the diagnosis.

The dominant theory — the one that produced the legislation described in Part One — holds that cities are the obstacle: local resistance, NIMBY politics, exclusionary zoning. The prescribed treatment is to override cities, mandate growth, remove planning authority, and apply stronger doses of the same medicine each time the last round fails. The current legislative session contains 132 housing bills. They sit on top of more than 400 already on the books.

A decade of results is now in. Median home prices have nearly doubled. Housing production falls short by roughly 100,000 units per year. Homeownership has barely moved in thirty years. The 6th Cycle RHNA allocated 1.4 million units, with 58% of the allocation directed to households who cannot afford market-rate housing. HCD’s own February 2026 data shows what was actually permitted: very low income at 4.4% of allocation. Low income at 12%. Moderate at 8.4%. Market-rate at 27.1%.

The families with genuine need are being permitted at a fraction of the rate of luxury product. That is not a compliance failure. It is a structural inevitability. You cannot extract affordable housing from luxury land economics.

When the same drug requires stronger doses and the patient keeps getting sicker, the honest diagnosis is that the drug doesn’t treat the disease.

The reason it doesn’t treat the disease is not mysterious. It is what economic theory actually predicts when you concentrate density mandates on the most expensive land in the state without funding the infrastructure that growth requires.

The standard rebuttal to any critique of densification mandates is “Economics 101: more supply reduces prices.” That framing isn’t wrong. It just doesn’t go far enough.

When the state mandates upzoning on land near jobs, transit, and amenities, it doesn’t just allow more housing — it transfers value to whoever owns the land. A $500,000 parcel that suddenly permits a 40-unit building is worth several million overnight. The development that pencils out on that newly expensive land is the development priced for buyers who can afford it. That is not market failure. It is the predictable result of mandating density without capturing any of the value the mandate creates.

Without that counterforce, the spiral runs in one direction. Rich places attract more investment. Land values rise further. More workers are priced out. Poverty concentrates at the periphery. This is not contested economics — it is what mainstream economic theory has predicted for over a century. Markets, left alone, diverge.

The terminal state is spatial lock-in. Workers who cannot relocate absorb progressively worse conditions rather than move. When the market externalizes its failure entirely, the result is what California has already produced: municipal governments busing homeless residents to vacant lots in low-income jurisdictions with no water, no services, and no economic base. That is not a policy anomaly. It is the predicted endpoint of a system with no propagation mechanism.

A second-order failure has been accumulating in parallel. Mandates have been imposed without measurement of whether the receiving infrastructure can support them. Water systems have been strained beyond their service plans. Evacuation corridors have approached theoretical impossibility. Schools have reached capacity. Cities have absorbed the legal and operational consequences while the families inside the new units arrive into systems that cannot adequately serve them. The mandate framework was designed without a capacity question. The capacity question has not gone away because the framework ignored it.

The diagnosis is not that growth is bad or that California has too much housing. The diagnosis is that policy designed around a single mechanism — density mandated onto the most expensive land in the state — cannot solve a problem that is fundamentally distributional, structural, and grounded in physical capacity. The current framework is administering a treatment that economic theory predicted would not work, and the data now confirms has not worked. The response is not a stronger dose. It is a different theory of the case.

What This Means for Your Local Work

Solving this at the local level is not possible. Cities do not have the authority to mandate state funding. They cannot change RHNA. They cannot change HCD’s posture. They cannot rewrite the underlying theory the framework rests on. The most they can do is push back on the worst projects, navigate the rest, and absorb the cumulative strain on their infrastructure and their legal budgets.

The work at the local level is necessary. It buys time, protects the worst sites from the worst projects, and builds civic capacity. Every CEQA-deficient project documented, every unfunded infrastructure mandate surfaced, every evacuation corridor that fails capacity analysis is also a data point that contributes to the larger record — evidence that the framework is producing predictable failures. That record matters. It is what makes structural reform, eventually, conceivable.

But the structural effort is a longer horizon than most local situations have. Yours will resolve, one way or another, on its own timeline. The diagnosis above is not a reason to stand down from it. It is a reason to engage with it with clear eyes — to know, when you win, what you have actually won, and to know, when you lose, that the loss is not a verdict on you. The framework was producing this outcome before you arrived and will produce another like it after. What you control is the quality of the work you do on the ground in front of you.

There is a structural answer being built. We are part of an effort to amend the California Constitution to require that the state measure infrastructure capacity and fund the systems growth requires before it can mandate that growth — preserving local decision-making while taking the affordable housing crisis seriously rather than displacing it onto cities that cannot solve it alone. If you want to know what that looks like, it is at balancedhousing.org. We mention it here because by this point in the handbook you have earned the right to know that someone is working on the problem at the level it actually sits.

That effort is for another day. The work in front of you is what the next part is about.

---

Part Six: Your Toolkit and 90-Day Plan

The final part of this handbook is a working plan. You can adapt it. You can ignore parts of it. The structure assumes you are starting from approximately zero and want to be operating at significant capacity within three months.

The First Week

Day 1. Read Parts One and Two of this handbook. If your situation has urgent timing — a hearing in the next 30 days — read the rest of the relevant sections immediately. Otherwise, the first week is about orientation.

Day 2. Tell us what you’re working on. A short note through the Stewards portal: your city, the project or issue, where it is in the process, what timeline you’re operating under. We will respond within 48 hours with specific resources for your situation.

Day 3. Submit your first public records request. The request should cover (a) the complete project file, (b) all correspondence between staff and the developer, (c) all correspondence between the city and HCD relating to the project, and (d) any environmental documents prepared or in preparation. Use the template in Part Four.

Day 4-5. Begin reading the project file as it arrives. Site plan first. Spend at least an hour with it.

Day 6-7. Identify your council member and their committee assignments, voting record on housing, and staff contacts. Begin drafting an introduction letter to them — not an advocacy letter, a relationship letter.

The First Month

Week Two. Complete your reading of the project file. Identify the three or four most significant deficiencies — specific findings unsupported by evidence, missing analyses, inconsistencies between documents. Write each one up as a paragraph that can become part of a public comment letter.

Week Three. Submit your public comment letter, both in writing and verbally if there is a hearing. Coordinate with at least two other neighbors using the 1-3-1 framework from Part Four — one problem statement, three pieces of evidence, one specific recommendation per speaker, with non-overlapping issues across speakers.

Week Four. Send the letter to your local council member or planning commissioner. Request a meeting. Have it within the next two weeks. The first meeting is relationship-building, not advocacy. Tell them who you are, what you care about, why you are getting involved. Ask them about their priorities. Listen.

By the end of month one, you should have: a complete understanding of the project file, a public comment letter on the record, an established line of communication with at least one local elected official, and the foundation of a coordinated neighbor group.

The First Quarter

Month Two. Continue the local engagement: hearing-by-hearing presence, additional public records requests as the file develops, regular coordination with your neighbor group. If there are cumulative AMMRs, evacuation analysis questions, or infrastructure adequacy issues you have not yet pressed, this is the month to develop them. Each becomes a written question to the relevant staff — Fire Marshal, Public Works, Planning — that creates a public record.

Month Three. Continue local engagement. By the end of month three, you should be a recognized, informed presence in your city’s planning process: someone the council members know by name, whose written comments staff read carefully, whose questions have a track record of being substantive.

After 90 Days

The local situation will resolve on its own timeline. The skills you have built — project literacy, public records mastery, public comment that lands, council relationships — are durable. They remain useful whether or not you ever apply them again.

If at any point the work becomes overwhelming, scale it back. There is no badge for burnout. The work is durable only if you are durable. Pace accordingly.

Templates and References

The following templates are provided in a separate appendix file, available for download alongside this handbook:

• Public Records Act request (general and project-specific)
• Public comment letter (CEQA-focused, 1-3-1 structure)
• Letter to local elected official (relationship-building structure)
• Information request to Fire Marshal (evacuation analysis focus)
• CEQA challenge timing checklist
• Project file evaluation worksheet

Connecting to the Network

If your city does not yet have an active Stewards node, you may be the person to start one. The starting bar is not high: one person who is willing to be the local point of contact, one regular communication channel (email list, group chat, monthly meeting), and a willingness to share what you learn with others doing the same work.

We provide:

• Onboarding for new local coordinators
• Connections to other nodes in your region
• Regular statewide calls to share what’s working and what isn’t
• Visibility for your city’s situation in the broader network

We do not provide:

• Direction on which projects you take on
• Approval over your local strategy
• Funding of local operations
• Membership infrastructure

The network is horizontal. It is connective tissue, not management. You retain full local autonomy.

---

A Closing Note

You started this handbook because something specific is happening in your city. The handbook has tried to give you what you need to engage with it effectively.

The work is hard. The local situation will not be resolved in a week, and the pattern that produces these situations — described in Part Five — will not be undone in a year. Most readers of this handbook will engage with one project, one decision, one round of the work. That is enough. The handbook is built to make that engagement as effective as it can be.

If you want to follow the structural effort that would interrupt the pattern Part Five describes, you can find it at balancedhousing.org.

That is what this handbook is for. The rest is up to you.

---

The California Stewards Handbook is a publication of California Stewards, a project of the California Stewardship Alliance and the Balanced Housing Foundation. The handbook and all associated tools are released free of charge for public use. This is version 1.0; we expect to revise it as the work develops. Feedback, corrections, and suggestions are welcome at the Stewards portal.

Nothing in this handbook constitutes legal advice. Specific legal questions should be addressed to a licensed attorney with relevant expertise.