Objective design standards: what cities can still make you do

"Objective" is a defined term, not a vibe. A standard is objective when it involves no personal or subjective judgment and is uniformly verifiable by reference to an external benchmark available to applicant and official alike before submittal — a definition that appears in Gov. Code § 65913.4(a)(5) (the SB 35/SB 423 statute) and in the Housing Accountability Act (§ 65589.5).

The definition carries the load because of what hangs on it: under HAA § 65589.5(j), a housing project consistent with the applicable objective standards cannot be denied or approved at lower density unless the city makes written findings of a specific, adverse health-or-safety impact with no feasible mitigation, and SB 330 froze the imposition of new subjective standards on protected projects. Cities responded by writing their design opinions down as numbers — the objective design standards (ODS) documents that now govern massing, articulation, materials and frontage across much of the state. HCD's HAA advisory polices the line.

Objective standards read like engineering: setbacks in feet, height in feet or stories, stepbacks as dimensioned planes, articulation as a percentage of facade length, materials from an enumerated palette, frontage types mapped block by block. Subjective standards read like judgment: compatibility with neighborhood character, high-quality design, appropriate massing. The first category binds a protected housing project; the second cannot lawfully be the basis for denying or shrinking one.

The definition bites at three checkpoints: HAA consistency (a project is deemed consistent if substantial evidence would let a reasonable person conclude it is), eligibility for the ministerial paths that require compliance with objective standards (HCD's SMAP advisory applies the same definition for SB 35/SB 423), and SB 330's vesting freeze, which locks the standards in effect on the preliminary-application date.

• Underwriting watch-outs:
• Written does not mean objective: a codified requirement for high-quality materials is still subjective; materials from the listed palette is objective. Test each standard for whether two reviewers are compelled to the same answer.
• Standards hiding in guidelines, commission resolutions or staff-report conditions cut against the city — if it was not a published objective standard at submittal, it cannot support an inconsistency finding.
• HCD enforcement letters routinely call out mislabeled subjective standards; citing one in a comment letter is often enough to make a city drop the standard.
• Log the ODS version in effect on your preliminary-application date — later amendments do not apply to a vested project.

SB 330's freeze on new subjective standards did not deregulate design — it changed its form. What survives for protected projects: numeric standards (dimensions, percentages, counts), mapped standards (height and frontage by street segment), and pre-adopted plans whose requirements are stated objectively. What does not: neighborhood-character compatibility findings, discretionary design-review vetoes, and any criterion that needs the reviewer's taste to apply — against a protected project those survive only as suggestions.

The ODS documents cities adopted in response are real regulation: ground-floor height minimums, required frontage types, upper-story stepbacks, facade-articulation intervals, entry spacing, materials palettes. Each is enforceable against a protected project precisely because it is objective — which means the ODS document, not the zoning summary table, is where your unit count actually gets set.

• Underwriting watch-outs:
• Pull the ODS document during diligence, not after site control — stepback and frontage rules routinely delete units the zoning math said you had.
• The expensive standards are rarely height or FAR; they are the articulation and stepback geometry that shrinks upper floor plates. Model them against your massing early.
• Watch for ODS provisions that are secretly subjective (articulation that provides visual interest) — flag them in writing as unenforceable against a protected project.
• Specific plans and overlay districts can carry their own objective standards on top of the citywide ODS — reconcile every layer before pricing the land.

Treat the ODS as a pro forma input. Standards that cost money linearly — materials palettes, glazing minimums — get priced per square foot; standards that cost units — stepbacks, frontage-type mandates, open-space geometry — get modeled as yield loss before you set land basis. On small infill parcels the discipline matters most, where a single stepback plane can decide whether the top floor exists.

Where an ODS provision physically precludes the project, the Density Bonus Law supplies the override: the city must waive development standards that would physically preclude construction of a density-bonus project, waivers are unlimited in number, and they do not consume your concessions (see the concessions and waivers guide). Build the preclusion record with drawings, pair the waiver requests with the application, and remember the HAA backstop: a denial dressed up as an ODS-consistency finding still has to survive the reasonable-person test — and in a city with a noncompliant housing element, the builder's remedy calculus.