Abstract
A parcel's development potential is only part of an entitlement decision. A team also needs to understand which approvals a proposal requires, what evidence supports that path, and how changes to the proposal affect work already underway. Prebreak's early practitioner discovery suggests that keeping this information connected across disciplines is an important product opportunity. Public agency guidance and research provide a complementary foundation: approval processes vary by jurisdiction and legal pathway, and procedural complexity can create substantial uncertainty. This report develops a framework for connecting entitlement research to project coordination. It presents a research-informed product thesis, not a measured estimate of software-driven savings.
Method and scope
This perspective combines three types of material: Prebreak's internal synthesis of early practitioner discovery; the founders' account of subsequent conversations; and published agency guidance and housing-process research. The available discovery record documents one formative expert conversation, not a representative interview sample. The original transcript and a complete interview register were not available for this review. Interview themes therefore inform questions and product priorities; they do not establish industry prevalence or causal effects. Public sources supply independently attributable context. The framework below is Prebreak's interpretation of that combined material.
The legal examples concern California housing and selected local processes. They are not a parcel-specific eligibility determination. Current law and the responsible agency's procedures must be checked for each proposed project.
1. Development potential depends on the approval path
Two proposals for the same parcel can create different tasks, dependencies, and decision points. A strategy that fits applicable standards may present a different review problem from one that requires a change to those standards. The first research question is therefore broader than what zoning allows: what approvals does this particular proposal require, and why?
California's Office of Land Use and Climate Innovation distinguishes ministerial decisions, governed by fixed standards, from discretionary decisions that involve agency judgment. It explains that ministerial projects are not subject to CEQA. The same guidance describes multiple housing exemptions and streamlining options. A discretionary approval does not, by itself, mean a full environmental impact report is required. 1
Decision authority also varies. Los Angeles City Planning describes zone changes and general plan amendments as legislative applications on which the City Planning Commission makes recommendations to the Mayor and City Council. Other application types are handled by different decision makers. This illustrates why a general statement such as “the city needs to approve it” is too coarse for planning the work. It does not establish a universal approval sequence for every California jurisdiction. 2
| Research question | Decision it supports | Record to preserve |
|---|---|---|
| Does the proposal fit an available approval pathway? | Whether to proceed, revise, or investigate another option | Applicable standards, eligibility conditions, and unresolved facts |
| Does the strategy require a legislative change or discretionary approval? | Whether the expected benefit warrants the additional process | Decision authority, application requirements, and dependencies |
| What environmental review or exemption may apply? | Which studies, consultations, and supporting materials to plan | Basis for the pathway, evidence needed, and responsible reviewer |
| Which project changes could alter that analysis? | Whether an earlier conclusion needs to be revisited | Plan version, changed assumption, and affected work |
This is a planning framework rather than an exhaustive legal checklist. A strategy with more process may still be attractive to a developer seeking a different program or development capacity. Another team may prioritize a path with fewer discretionary decisions. Comparing the alternatives requires making the assumptions explicit rather than treating one route as universally preferable.
2. Environmental review is a branching process
Environmental review should enter project planning early enough to influence the scope of work. It should also be described accurately. CEQA is not a single uniform review duration or an inevitable full EIR. LCI's housing resources cover exemptions and streamlining, and caution that its parcel screening tool is a starting point whose determinations require independent verification. 1
Research design matters here. UC Berkeley's land-use entitlement research combines legal and qualitative methods across selected California cities. Its scope reinforces the importance of examining local processes rather than assigning all delay to one statewide rule. This report does not treat that research as evidence that every project experiences the same constraints. 3
For a project team, the practical implication is to preserve the reasoning behind the selected path. A map result, an agency discussion, and a documented eligibility analysis have different evidentiary roles. When the design or a material assumption changes, the team needs to know which conclusions may no longer apply.
3. The cost of uncertainty extends beyond research
HCD's 2023 San Francisco Housing Policy and Practice Review reports an average of 523 days to entitlement using the city's self-reported 2022 Annual Progress Report data. It separately reports 605 days for a building permit after entitlement. These are historical, city-specific measures of different stages, not current statewide benchmarks or estimates of delay caused by a missed check. The review examines several contributors to procedural complexity and uncertainty. 4, p. 2
Those findings establish context for why the approval process deserves close attention. They do not establish how much of a project's schedule can be changed through software. Agency capacity, statutory requirements, project changes, stakeholder disagreement, and the completeness of the application may all matter. Prebreak's research question is narrower: which avoidable gaps in evidence and coordination can a team identify earlier?
Our early discovery materials describe a practitioner preference for support during execution: keeping the plan, participants, versions, and compliance questions connected. The value of that observation is its specificity. It directs attention toward handoffs and decisions rather than simply producing another report. It remains an early signal to test with additional participants and actual project records.
4. From parcel intelligence to coordinated execution
Prebreak's proposed operating model connects four records: the current proposal, the evidence supporting the approval strategy, the unresolved questions, and the people responsible for the next action. The purpose is to help a project team notice when these records diverge.
Consider a hypothetical design revision that changes an assumption used in an earlier eligibility assessment. A useful workflow would identify the affected assessment, retain the prior plan version, route the question to the appropriate professional, and record the response before the next submission. This example illustrates the intended mechanism. It is not a claim that Prebreak has measured prevention of that failure on a customer project.
The distinction between information and execution is central. A source-backed answer is useful; knowing whether the team acted on it, and whether it still applies to the current proposal, is the next problem to solve.
5. What we intend to measure
A project-based evaluation should capture the baseline approval strategy, dated plan revisions, agency comments, outstanding requirements, and the timing of issue discovery and resolution. Each case should distinguish an agency-required review from a correction associated with an avoidable omission. Cost records should separate estimates from incurred costs and identify the relevant financing and consultant assumptions.
Initial measures could include time to identify a material issue, time to obtain an accountable response, unresolved requirements at submission, and repeated requests for information already held by the team. A small set of case studies can explain mechanisms. Claims about typical savings require a larger sample and a comparison method that accounts for differences between projects.
Implications and limitations
The opportunity is to connect understanding the approval path with carrying out the work it requires. This perspective supports that product direction through early discovery and public context. It does not demonstrate market-wide demand, quantify the share of delay attributable to coordination, or establish that Prebreak reduces entitlement time or cost. Those are empirical questions for the next phase of research.
The strongest next publication would be a documented, permission-cleared case tracing one issue from its first appearance through the team's response and the agency outcome. That would turn a persuasive account of the problem into inspectable evidence about how it occurs.
References
Reference 1
California Governor's Office of Land Use and Climate Innovation. Site Check and Other CEQA Housing Resources. Accessed September 10, 2026.
Reference 2
Los Angeles City Planning. Local Decision Makers. Accessed September 10, 2026.
Reference 3
UC Berkeley Center for Law, Energy & the Environment. Examining California Land Use Entitlements. Publication overview dated February 2018. Accessed September 10, 2026.
Reference 4
California Department of Housing and Community Development. San Francisco Housing Policy and Practice Review. October 2023, printed page 2. Historical data, not a current performance measure.
Reference 5
Prebreak. Internal product discovery synthesis and founder context, reviewed September 10, 2026. Unpublished; interview statements are summarized, not quoted. This synthesis is not a formal qualitative study.