By-Right vs Discretionary Approvals: What Actually Changes for Your Project

The difference between by-right and discretionary approvals is usually described in simple terms: one is predictable, the other is political. In practice, the distinction changes how projects evolve, where risk shows up, and how much control developers actually retain over design and outcomes. The approval path you fall into reshapes the project in ways that aren't obvious when you're underwriting the deal.

By-right projects are often treated as "safe" because the use and form are technically allowed. What changes is not whether risk exists, but how it enters the process. Instead of risk showing up in hearings and votes, it shows up through staff-level interpretation of code provisions. Small differences in how frontage standards, parking access, loading zones, fire separation, or accessibility are read can force redesigns late in the process. These are not denials. They are quiet changes that ripple into unit counts, circulation, and construction costs after the project has already been modeled and marketed internally.

The practical effect is that teams tend to lock designs earlier on by-right projects. The assumption that approvals are mechanical encourages tighter optimization around initial interpretations. When those interpretations shift, the project has less slack to absorb the change. The friction feels technical, but the impact is economic.

Discretionary approvals are commonly framed as political risk. That's true, but they also create a formal arena for negotiation. Conditions of approval become the mechanism through which cities shape outcomes. This makes the process visible and, importantly, tradeable. Developers can often agree to one design concession in exchange for flexibility elsewhere. The negotiation is explicit, documented, and part of the approval record.

In by-right processes, there is rarely a comparable forum for tradeoffs. Each interpretation stands on its own. If a standard is applied conservatively, there is limited room to negotiate without escalating procedurally. The outcome may be predictable, but it is also rigid. The project becomes shaped by a series of narrow readings rather than a negotiated balance of interests.

Lenders and investors respond to approval paths in different ways. Discretionary approvals signal visible entitlement risk, so timelines and contingencies tend to be priced in earlier. By-right approvals appear cleaner on paper, which can compress pre-development schedules and tighten contingency assumptions. When late-stage design changes arise under a by-right path, they tend to collide with financing that was structured around the assumption of minimal entitlement friction.

This mismatch can be more disruptive than discretionary delay. A discretionary project that takes longer than expected is often underwritten with that possibility in mind. A by-right project that changes scope late in the process forces re-underwriting when teams thought entitlement risk was already resolved.

Approval type also changes how project teams allocate attention. Discretionary processes push teams toward early involvement of land use counsel and external advisors who manage hearings, conditions, and public process. By-right projects push teams toward technical optimization: detailed code compliance, circulation studies, fire access, and design guideline interpretation. The project becomes dependent on how well the team anticipates the specific friction points that staff will focus on during review.

The non-obvious risk is that by-right projects become more brittle. They are optimized tightly to a particular reading of the code. When a single requirement is reinterpreted, it can cascade through the design in ways that are harder to unwind than a condition negotiated in a discretionary process.

The most important difference between by-right and discretionary approvals is not speed. It is optionality. Discretionary processes introduce uncertainty but preserve room to negotiate outcomes. By-right processes reduce uncertainty at the macro level but constrain flexibility at the micro level. Once a staff interpretation is embedded in the approval path, reversing it is procedurally difficult and often costly.

This matters when market conditions, construction costs, or financing terms shift mid-entitlement. Projects in discretionary review can sometimes adjust scope or design during hearings. By-right projects may technically be allowed but practically locked into design commitments that were made earlier in the process under different assumptions.

In practice, few projects are purely by-right or purely discretionary. Many "by-right" developments still involve design review, administrative adjustments, or minor variances. The mistake is treating by-right as a frictionless path and discretionary as a binary hurdle. Both paths introduce risk; they simply distribute it differently across the life of the project.

Understanding where and how that risk will surface is more important than the label attached to the approval process. The projects that move most smoothly are not the ones that avoid discretionary review at all costs, but the ones that choose an entitlement path with a clear-eyed view of how it will reshape design, timing, and decision-making throughout the project lifecycle.