# Episode 21: Objective Standards and the Processing Clock

Separates objective standards from discretion and tracks review deadlines that change local process.

## Sources and attribution

- [Housing Elements and Housing Accountability Unit Guidance](https://www.hcd.ca.gov/housing-element) by California Department of Housing and Community Development; published by State of California.
- [Toolbox Tuesday Training Archive](https://scag.ca.gov/toolbox-tuesday) by Southern California Association of Governments; published by Southern California Association of Governments.

This episode is an independent study production based on the sources listed above. Source attribution does not imply affiliation, approval, sponsorship, or endorsement by any author, publisher, or institution.

## License

No broad open license identified; original summary and attribution only

## Production notes

Preparation only. Not legal, planning, or financial advice. The narration is an original synthesis. Verify current law, guidance, course requirements, and source terms before relying on it.

Stable episode ID: `fe59ca72-bd62-5ead-a401-0f210867375b`

## Transcript

Imagine a housing proposal on a Torrance corridor. The elevations are unfamiliar. A commissioner wants the facade to feel more compatible with nearby buildings. Staff points to a state streamlined pathway and asks a different question: does the proposal comply with the objective standards that were in effect when the application became subject to review? In that setting, taste is not a standard, and delay can change the legal result. The commission needs a method that works before the clock expires.

This episode is preparation, not legal advice about any application or deadline. California processing laws contain definitions, exceptions, tolling rules, and pathway-specific timelines. They change often. The current statute, HCD guidance, local ordinance, complete project record, and advice from the Torrance city attorney control.

An objective standard involves no personal or subjective judgment by a public official. A developer, staff member, commissioner, and court should be able to apply the same text to the same facts and reach a predictable result. Dimensions, ratios, listed materials, mapped areas, measurable performance levels, and clearly defined procedures can be objective. Words such as harmonious, high quality, appropriate, or compatible usually need measurable content before they can do that work.

Objectivity is not the same as simplicity. A standard can use a formula, reference a map, or require a technical measurement. But the inputs and decision rule must be knowable. A standard that says preserve privacy is subjective. A standard that limits specified upper-story window placement within a measured distance of a residential property line is more likely to be applied objectively.

Objective standards still express policy. A city can decide where entrances belong, how blank walls are limited, what setbacks apply, how trees are replaced, or how ground floors meet sidewalks. The legislative stage is where officials debate those choices. Once a qualifying ministerial application arrives, the job is consistent application, not project-by-project redesign.

Build every standard from four parts. First is the trigger. State exactly which projects, lots, frontages, or building elements are covered. Second is the rule. Use a number, defined category, or test. Third is the measurement method. State where measurement begins and ends and which document supplies the input. Fourth is the consequence. Explain what revision or condition resolves noncompliance.

Test a draft standard against edge cases. What happens on a corner lot? Which street is primary? How are slopes measured? What if two maps disagree? Does a percentage apply to the entire facade or only the ground floor? If staff has to invent an answer during review, the standard was not finished.

Avoid hidden discretion. A list of acceptable materials followed by or similar gives the reviewer a subjective gate. A requirement for substantial variation is unclear unless variation is quantified. A design-review body cannot transform an objective pathway into a discretionary one by asking whether the building is attractive.

The processing clock makes this drafting discipline operational. Different laws use different starting points and deadlines. The Permit Streamlining Act governs many applications. The Housing Accountability Act creates timing and consistency rules for housing development projects. The streamlined ministerial approval process associated with Senate Bill 35 and Senate Bill 423 has its own review periods. Other ministerial pathways have separate clocks.

Never begin with a remembered number. Begin with the pathway and the event that starts the period. Is it receipt of an application, determination that an application is complete, submission of a preliminary application, or another statutory event? Then identify what the agency must complete: completeness review, written inconsistency findings, design review, or final approval.

HCD's current streamlined ministerial materials explain that, for qualifying projects of 150 units or fewer, a jurisdiction generally has 60 days after receiving the application to determine consistency with objective standards and 90 days to complete design review. Larger projects generally receive 90 days for the consistency determination and 180 days for design review. Review of specified resubmittals is generally required within 30 days. Those numbers belong to that pathway and remain subject to current law and facts. Do not paste them onto every housing application.

The consequence of missing a statutory consistency-review period can be serious. Under the streamlined process, a project may be deemed consistent with objective standards if the jurisdiction does not provide the required written documentation on time. A late list of concerns is not equivalent to a timely, specific explanation.

Good written feedback identifies the exact adopted standard, states the project fact being compared, explains the measurement, and describes the conflict. It avoids general requests to improve character. If a minor correction can bring the project into compliance, say precisely what must change. Preserve one coordinated agency response rather than a trail of inconsistent comments.

Objective does not mean inflexible administration. Staff may verify facts, perform calculations, and apply definitions. The city may impose compliant conditions that implement an objective standard. The boundary is judgment untethered to a measurable rule.

For practical application, run a clock-and-standard drill. Choose a fictional 120-unit mixed-use project on Hawthorne Boulevard. Assume only for the exercise that counsel confirms a particular streamlined pathway applies. Create a clock sheet with the submission date, statutory trigger, consistency deadline, design-review deadline, resubmittal deadline, responsible reviewer, and required written product. Then choose five local standards and complete a compliance matrix.

The matrix has five columns. Cite the standard. Copy only the minimum operative language. Record the project fact. Show the measurement or evidence. Mark comply, conflict, or insufficient information. For every conflict, draft one sentence that identifies the specific mismatch without adding a new preference.

Commissioners can improve the system even when a particular application is ministerial and never reaches them. During ordinance work, ask whether each standard survives the edge-case test. Ask staff to conduct mock reviews before adoption. Request diagrams that illustrate measurement without replacing the governing text. Ask whether standards conflict across zoning, specific plans, fire requirements, and public-works manuals.

Do not solve uncertainty by adding layers of approval. A required consultation can itself become a source of delay. Define who makes the determination and what document closes the step. Keep a versioned library of the standards in effect on relevant dates.

Also separate objective planning standards from building, fire, and other health and safety rules. A project may be ministerial under planning law while still requiring code-compliant construction permits. The existence of later technical review does not authorize discretionary land-use denial.

The city should audit outcomes. If every applicant misunderstands the same rule, clarify it legislatively. If a standard unexpectedly blocks the housing form the element assumed, evaluate the constraint. If staff repeatedly grants ad hoc interpretations, replace them with text. Predictability benefits residents as well as applicants because the public can understand what the adopted policy permits.

Details change, especially effective dates and pathway-specific procedures. A timeline in a training script is a prompt to verify, not authority for a motion.

Now three recall questions.

Question one. What makes a development standard objective?

Answer. It can be applied without personal or subjective judgment, using defined facts, measurements, categories, or tests that produce a predictable result.

Question two. What should a timely inconsistency notice contain?

Answer. The exact standard, the relevant project fact, the method of comparison, and a specific explanation of the conflict.

Question three. Why must you identify the pathway before calculating a deadline?

Answer. Different statutes use different triggers, tasks, time periods, exceptions, and consequences. A number remembered from one pathway may be wrong for another.

Your learner artifact is the clock sheet and five-row compliance matrix for the fictional project. Include a box labeled assumptions requiring counsel confirmation. Put every date in calendar form. End with one proposed clarification to an objective standard that would reduce future disagreement without weakening the policy.

This lesson draws from current California Department of Housing and Community Development materials on objective design and development standards, the Housing Accountability Act, and the Streamlined Ministerial Approval Process under Senate Bill 35 and Senate Bill 423, including HCD's 2026 fact sheets and guidance. It also uses the current Permit Streamlining Act framework and public local-planning practice. The narration is original and does not reproduce source prose, slides, maps, recordings, or proprietary data. Confirm every clock and standard against current statute, current HCD guidance, the applicable Torrance code, and city-attorney advice.