How Town Planning Works | TPW-0103 — The By-Right Approval: How Fixed Standards Turn Development Review From Negotiation Into Compliance

Two buildings can be almost identical and travel through completely different planning systems.

One proposal enters a hearing room. Staff write a recommendation. Neighbours speak. A board weighs compatibility. Conditions are negotiated. The decision can be approved, denied or appealed because somebody has authority to exercise judgment.

The other proposal enters a checklist.

Is the use allowed? Yes. Is the building below the height limit? Yes. Does it meet the setback, floor-area, access, fire, drainage, parking, tree, accessibility and other applicable standards? Yes. Is the site outside the exclusions that would require another pathway? Yes.

Then the authority’s job is not to decide whether it likes the project. Its job is to verify whether the project complies.

That is the central idea behind by-right, as-of-right, ministerial and closely related code-compliance approval systems.

The terminology varies by country and jurisdiction. The mechanism is more general: the planning system makes the important policy choices before the individual application arrives, writes those choices into sufficiently objective rules, and then allows a conforming proposal to move through an administrative approval route without reopening the basic land-use question every time.

The reader job: decide whether an application is a policy question or a compliance question

This article has one narrow job.

It explains how a planning system can separate decisions that require judgment from decisions that should become repeatable compliance checks once the policy has already been settled.

Neighbouring mechanisms already have owners in this series. Zoning and Compatibility owns the broad problem of deciding which uses belong together. The Objective Code owns the design of measurable standards that make development predictable. The Plan Stack owns the hierarchy from strategy to development control. The Permit-Ready Pattern Book owns pre-designed building pathways.

The By-Right Approval owns a different question: once a use and development envelope have already been permitted by policy, how should an authority verify compliance quickly, consistently and safely without recreating a discretionary planning debate for every conforming project?

By-right does not mean rule-free

The easiest misunderstanding is to hear “by right” and imagine deregulation.

A serious by-right system can contain many rules. It may regulate land use, building height, setbacks, floor area, lot coverage, frontage, access, landscaping, stormwater, environmental constraints, fire access, accessibility, building safety, utility connections, construction standards and other matters.

The difference is not the absence of standards. The difference is the location of discretion.

In a discretionary system, a decision-maker may have authority to interpret broad concepts such as neighbourhood character, compatibility, desirability or public benefit in the individual case. In a ministerial system, the relevant questions are largely predetermined. If the applicant satisfies the stated standards, the authority generally cannot replace those standards with a new preference invented during review.

California’s Governor’s Office of Land Use and Climate Innovation describes this distinction directly in its current housing guidance. A project is discretionary when an agency can exercise judgment about whether or how to approve it. Where the agency must act using fixed standards and lacks that discretionary authority, the approval is ministerial. The exact legal consequences are specific to California, but the institutional distinction is useful everywhere.

The code becomes the hearing that happened earlier

A by-right system does not eliminate public choice. It moves much of that choice upstream.

When a city adopts a zoning code, local plan or development standard, it is deciding what kinds of buildings and uses should be acceptable under stated conditions. That is the moment to debate whether six storeys are appropriate on a corridor, whether shops should be allowed beneath housing, how much tree canopy should be retained, whether parking should be required, where flood constraints should exclude fast-track approval and what objective design rules should protect the public realm.

If those questions have been answered through the plan-making process, reopening them parcel by parcel can make the code less meaningful.

A city that says “housing up to six storeys is permitted here” but then requires every six-storey proposal to prove again that six storeys are acceptable has not fully decided what its own map means.

The by-right model asks the government to be explicit earlier. That can make the political argument harder when the rules are written, but it makes later administration clearer.

The first test is use permission

Every by-right review begins with a basic question: is the proposed activity allowed on this land?

A residential building cannot become by-right merely because it meets the height limit if housing is not an allowed use. A workshop cannot rely on dimensional compliance if the zone prohibits that category of industrial activity. A shop may be permitted at ground level but prohibited above a certain floor. A childcare use may be allowed only after meeting additional operational standards.

This is why land-use tables matter. They turn an abstract zone into a machine-readable set of permissions: permitted, conditional, prohibited, accessory, temporary or subject to another pathway.

Good tables also avoid false simplicity. “Commercial” is not one activity. A quiet office, nightclub, supermarket, laboratory and vehicle-repair shop produce different noise, freight, opening-hour, hazard and access conditions. If the categories are too broad, the code pushes uncertainty downstream. If the categories are too narrow, the code becomes difficult to maintain.

The second test is the development envelope

Once the use is allowed, the building must fit inside the envelope the code permits.

That envelope can include height, floor-area ratio, plot ratio, lot coverage, setbacks, step-backs, frontage, minimum open space, maximum building depth, daylight planes, tower separation or other measurable controls.

The important word is measurable.

“Maximum height: 24 metres” can usually be tested. “Appropriate height for the neighbourhood” requires interpretation unless the code defines how appropriateness is determined. “At least 60 per cent active frontage” can be measured if active frontage is defined. “An engaging street edge” is harder to administer without additional criteria.

A by-right system therefore reveals whether the development code is actually written as an operating specification or merely as a collection of aspirations.

Objective does not mean simplistic

There is a temptation to assume that objective rules can only control easy geometry.

That is not true.

A rule can require entrances every stated number of metres, a minimum proportion of transparent frontage, upper-storey step-backs above a defined height, specified tree-retention calculations, a maximum blank-wall length, minimum bicycle storage, solar-ready roof area, a stormwater performance target or a documented accessibility route.

Complexity can be objective if the test is clear enough that two competent reviewers should normally reach the same answer from the same evidence.

The design challenge is to write rules that protect real public outcomes without accidentally standardising every building into the same shape. That is why the by-right pathway and objective design standards are related but not identical. One is the approval mechanism. The other is a way to write some of the rules that mechanism depends on.

A fixed standard is only useful if the measurement method is fixed too

Consider a 20-metre height limit.

From where is height measured? Natural ground? Finished ground? Average grade? The highest point of a sloping site? Does a lift overrun count? What about mechanical equipment, parapets, roof gardens, antennas or solar panels?

A number without a measurement rule is only partly objective.

The same problem appears with setbacks, floor area, landscaping percentages, building frontage and parking counts. Applicants optimise against definitions. Reviewers need common methods. Courts and appeal bodies need to know what the code intended.

Good by-right administration therefore depends on definitions, diagrams and measurement conventions that are treated as part of the code, not as explanatory decoration.

The third test is whether another planning layer overrides the base permission

A parcel rarely has only one rule.

The base zone may permit apartments, while a heritage overlay changes demolition rules. A flood layer may restrict ground-floor occupancy. An airport safeguarding surface may limit height. A habitat overlay may require ecological review. A contaminated-land rule may require investigation. A coastal hazard layer may exclude the site from a fast-track pathway.

This is why “zoned for housing” is not the same as “every housing proposal is ministerial.” The planning stack must be resolved in the correct order.

New South Wales provides a useful current comparison. Its complying-development system fast-tracks straightforward residential, commercial and industrial projects that meet specified standards, but the pathway contains land-based exclusions and special rules for environmental constraints. The NSW Planning Portal states that approvals can be issued rapidly without a full development application when the proposal satisfies the relevant development standards. Its 2026 reform material also reports that complying development already accounts for a substantial share of planning approvals in the state.

The lesson is not to copy NSW. It is that a fast pathway can coexist with detailed eligibility gates. Speed comes from predefining the gates, not from pretending constraints do not exist.

By-right is an approval path, not the end of building regulation

A project can be by-right for zoning and still need many approvals.

Building plans may still be checked for structural safety. Fire authorities may review access and life-safety systems. Utility providers may impose connection requirements. Drainage plans may need engineering approval. Subdivision may require mapping. Construction inspections still occur. Accessibility standards still apply. Environmental or heritage laws may create separate obligations.

Confusing “no discretionary zoning hearing” with “no regulatory review” creates bad expectations and weakens public trust.

A mature system tells applicants exactly which approvals are ministerial, which remain technical, which require discretion and which can run in parallel.

The real product is certainty

People often describe by-right reform as a speed reform.

Speed matters, but certainty is usually more fundamental.

A developer deciding whether to buy a site needs to estimate what can be built. A lender needs to assess entitlement risk. An architect needs a reliable envelope. A neighbour needs to know what the plan already permits. A planning department needs to allocate staff time. A public agency releasing land needs to forecast delivery.

If a technically compliant project can still be rejected for broad subjective reasons, the legal maximum on the map is not the practical development capacity of the site.

By-right approval narrows that entitlement uncertainty. It does not guarantee finance, construction or market success. It makes the planning part of the risk more legible.

Time has a carrying cost

Planning delay is not simply an inconvenience measured in calendar days.

Land can carry interest. Consultants remain engaged. Construction prices can change. Financing commitments expire. Buyers wait. A school, clinic or housing project that exists only on paper delivers no service while the approval is unresolved.

That does not mean every review should be shortened. Some decisions genuinely require investigation, alternatives and public judgment.

The better question is whether each day of review is buying information or judgment that the decision actually needs.

If the authority is repeatedly checking the same objective questions manually, process design may be the problem. If the project raises a site-specific hazard or unanticipated impact, more review may be exactly what responsible planning requires.

Discretion has value—but it also has a cost

Discretion is not automatically bad.

It can respond to unusual sites, new technologies, complex heritage settings and impacts a code writer could not anticipate. It can allow negotiation that produces a better project. It can preserve judgment where a rigid rule would be crude.

But discretion also introduces variance between decision-makers. It can make outcomes less predictable. It can reward applicants who can afford longer negotiations. It can make ordinary development depend on meeting schedules, political cycles or the rhetorical skill of opponents and supporters.

The question is therefore not “objective rules or human judgment?” A functioning system needs both.

The design problem is to place judgment where it adds value and remove it where policy has already settled the answer.

Public participation changes location in the process

When more development becomes by-right, residents can feel that a hearing has been taken away.

Sometimes that criticism is fair because governments have created fast tracks without investing enough public attention in the rules that define them.

A legitimate by-right system must therefore strengthen upstream participation. The public should be able to understand what the plan permits before a specific project creates urgency. Maps should be legible. Height and use changes should be explained. Development scenarios should be visualised. Infrastructure implications should be tested. Review periods should be real rather than ceremonial.

The planning bargain is simple: if individual conforming applications will receive less discretionary debate, the code-writing process must carry more democratic weight.

A neighbour may still need notice even when the decision is ministerial

Notice and discretion are different things.

A jurisdiction can notify neighbours that a conforming project has been submitted without giving the decision-maker authority to deny it for reasons outside the code. Notice may help identify factual errors, boundary mistakes or overlooked constraints. It can also prepare neighbours for construction impacts.

NSW’s complying-development system illustrates this distinction. Certain projects require neighbour notification even though the pathway remains standards-based. The notice does not automatically convert a compliance decision into a popularity contest.

This distinction matters because transparency should not be confused with discretionary veto.

Design review must know what kind of decision it is

Design review often sits awkwardly between objective and discretionary planning.

If a review board can require whatever changes it considers aesthetically preferable, the pathway is not fully by-right even if the underlying use is permitted. If the reviewer checks compliance with stated frontage, materials, articulation, entrance and public-realm standards, the design stage can remain largely ministerial.

Neither model is universally correct.

Places with exceptional civic, heritage or landscape significance may deliberately retain qualitative review. Routine infill may benefit from greater predictability. The mistake is pretending a discretionary design process is objective merely because it has a checklist, or pretending an objective standard guarantees good design merely because it is measurable.

The code must distinguish an interpretation from a waiver

Every code eventually meets an ambiguous case.

Does a rooftop structure count as a storey? Is a covered walkway part of floor area? Which lot line is the front on a corner parcel? Does a mixed business fit one use category or another?

An administrative interpretation can clarify what an existing rule means. A waiver changes what the rule requires for one case. Those are different institutional acts.

If staff routinely “interpret” standards by allowing departures that the text does not support, the by-right system becomes discretionary in practice. If every ambiguity requires a full political process, administration becomes brittle.

Good codes create a transparent interpretation process and a separate route for actual relief. The next articles in this series examine two of those relief mechanisms: conditional permissions and variances.

Automation can help only after the rules become computable

Digital permitting is often sold as a software project.

The hard part is frequently regulatory structure.

A computer can compare a proposed height with a numeric maximum. It can test whether a parcel intersects an overlay. It can calculate floor area if inputs and definitions are standardised. It can check whether required documents are present.

It cannot reliably automate a rule whose real content is “make this fit the neighbourhood appropriately” unless the government decides what evidence and criteria make that judgment operational.

This is why by-right reform and digital planning are linked. Clean data cannot compensate for an incoherent rule system. Software makes the structure of the rules visible.

A pre-application check should identify pathway risk, not become a hidden discretionary stage

Pre-application meetings can save enormous time.

Staff can identify missing surveys, utility constraints, overlay requirements and likely code interpretations before an applicant completes expensive drawings. This is especially useful on complicated sites.

But a pre-application meeting should not become the place where an otherwise conforming project is informally redesigned because somebody dislikes what the code permits.

The purpose is to expose requirements early, not invent new ones privately.

Completeness review and merits review should be separated

A common source of delay is the repeated discovery that an application lacks information.

A mature process first asks whether the submission is complete enough to review. Are the drawings present? Is the survey current? Are calculations signed where required? Are reports included? Has the correct fee been paid?

Only then should the authority decide whether the project complies.

Mixing completeness and compliance creates endless cycles in which a reviewer raises a new document request after months of substantive review. A standards-based pathway needs a standards-based intake system too.

The review clock needs rules of its own

A statutory time limit can improve discipline, but only if everyone knows when the clock starts, when it can stop and what happens when information is missing.

Does the clock begin on submission or completeness? Can the authority pause it while awaiting revisions? Can applicants extend time voluntarily? Is there a consequence for missing the deadline? Does approval become automatic, or is another remedy available?

Without those details, a promise of “30-day approval” can hide months of pre-clock negotiation.

Process metrics should therefore measure total applicant journey time as well as official review time.

Fast review requires enough staff capacity

Objective standards do not review themselves.

Plans must still be read. Calculations must be checked. Site conditions must be verified. Agencies need trained reviewers, functioning software, reliable parcel data and clear responsibility for cross-department comments.

If a jurisdiction creates a new by-right housing law but gives the planning department no additional capacity, the legal entitlement may improve while administrative delay remains.

Approval reform is therefore partly an organisational-design problem.

The standards should be tested against real parcels before adoption

A code can look coherent in a policy document and fail when applied to actual lots.

A height limit, rear setback, landscaping rule, fire access requirement and parking geometry can each be reasonable alone but impossible together on common parcel shapes. A density bonus can exist on paper while another rule prevents the extra floor area from fitting. A frontage requirement can clash with utility easements.

Before making a pathway by-right, planners should prototype the rules on representative parcels: narrow lots, corner lots, sloping sites, shallow lots, irregular lots and sites with overlays.

This is regulatory unit testing. It finds contradictions before applicants discover them with real money at stake.

A code that produces constant waivers is not actually objective

Watch what applicants repeatedly ask to waive.

If half the projects need relief from the same setback, parking rule or frontage standard, the problem may not be a collection of unusual sites. The rule may be miscalibrated.

A by-right system should therefore publish variance and exception data. Repeated departures are feedback about the code.

This does not mean every frequently challenged standard should be weakened. Some standards protect a real public interest that development economics regularly pushes against. The data tells planners where to investigate, not what conclusion to reach.

A ministerial pathway can still contain hard exclusions

Fast-track approval is strongest when the eligibility boundary is honest.

A city may decide that ordinary infill housing on serviced land can proceed by right, while projects affecting designated heritage assets, severe hazard areas, protected habitat or major infrastructure require another process.

The exclusion is not evidence that the fast track failed. It is evidence that the government distinguished routine cases from cases where additional judgment or evidence is justified.

The danger appears when exclusions become so broad, vague or numerous that almost no project qualifies. Then the by-right pathway exists rhetorically but not operationally.

Infrastructure capacity must be connected without becoming an invisible veto

A project can satisfy zoning and still depend on water, sewer, electricity, road access and other systems.

If infrastructure agencies can reject projects through unpublished capacity rules, the planning entitlement is less certain than it appears. If the zoning code ignores real capacity constraints, approval can outpace delivery.

The solution is not to hide infrastructure judgment. It is to map it.

Service thresholds, upgrade requirements, capacity reservations and applicant obligations should be as visible as possible. Where major infrastructure must arrive first, the time layer should make that sequence explicit.

The building permit is not a second zoning hearing

After planning approval, technical building review should test technical building rules.

If the building-permit stage informally reopens land-use questions already settled by zoning, applicants face duplicated review and unclear authority. Conversely, planning approval should never be treated as proof that structural, fire or accessibility requirements have been satisfied if those matters belong to another code.

Each approval layer needs a defined owner and scope.

The reader should always be able to answer: What question is this reviewer authorised to decide?

Certifiers need independence as well as speed

Some standards-based systems allow qualified private certifiers to issue approvals.

This can expand capacity and reduce queues, but it creates an institutional question: the applicant pays the professional who verifies compliance.

That model requires licensing, audit, professional obligations, conflict controls, documentation standards and meaningful consequences for improper certification. Otherwise competition can drift from “who provides the best service?” toward “who asks the fewest questions?”

Speed without verification quality is not planning reform. It is delayed failure.

Inspection closes the loop

A perfect plan set does not guarantee a compliant building.

Construction changes. Materials are substituted. Site conditions differ from drawings. Drainage is rerouted. Landscaping is postponed. A required access route becomes storage space.

A by-right approval therefore needs a completion system: inspections, certificates, as-built information and enforcement where necessary.

The more confidence the system gives applicants at the front end, the more credible its back-end verification must be.

Enforcement protects the legitimacy of predictable approval

People accept predictable development more readily when they trust that the rules are real.

If a restaurant is permitted by right only under stated noise limits but violations are never enforced, neighbours experience the system as one-sided. If landscaping required for approval is routinely omitted, compliant applicants are penalised relative to those who ignore the rule.

Predictability must apply to both permission and obligation.

Appeals should challenge the decision that was actually made

In a discretionary case, an appeal may argue that the decision-maker weighed policy or evidence incorrectly.

In a ministerial case, the central dispute is usually narrower: did the project meet the applicable standards, were the correct standards applied, and was the process lawful?

An appeal system that allows a by-right application to be reheard as an open-ended policy question can restore the very uncertainty the pathway was designed to remove.

That does not remove legal accountability. It aligns the scope of review with the scope of the original decision.

Repeated edge cases should feed code maintenance

No code survives contact with a city unchanged.

New building types appear. Household patterns change. Climate evidence changes. Technology creates new uses. Staff discover ambiguous clauses. Courts clarify statutory meaning. Infrastructure standards are updated.

A by-right system therefore needs a maintenance cycle. Track questions. Publish interpretations. Amend definitions. Remove contradictions. Test changes against real parcels. Preserve version history so applicants can determine which rule applied when.

Predictability is not achieved by freezing the code. It is achieved by changing the code transparently.

The 2026 signal: fast pathways are being refined, not merely expanded

Current planning reforms show that the next problem after creating a fast pathway is often handling small departures without forcing an applicant into a completely different system.

New South Wales consulted in May and June 2026 on changes to its complying-development system. The government’s explanation says the current pathway can require a full development application when even a minor development standard is not met, adding substantial assessment time. The proposed reform explores a more proportionate route for minor variations while keeping the fast-track framework.

This is a mature planning question. Once a system draws a hard compliance boundary, what should happen one centimetre outside it?

The answer cannot be “ignore the standard,” because then the standard stops being objective. It also need not always be “restart the entire planning process.” A well-designed system creates a distinct, bounded relief mechanism. That is where variance and modification systems enter.

A by-right approval audit

Use: Is the proposed activity permitted on the parcel without discretionary land-use approval?
Definitions: Are the use categories and technical terms clear enough to classify the proposal consistently?
Envelope: Does the proposal satisfy height, floor area, setbacks, coverage, frontage and other dimensional controls?
Measurement: Does the code state exactly how each standard is measured?
Design: Are applicable design requirements objective, or does a separate discretionary review remain?
Overlays: Are heritage, environmental, hazard, airport, infrastructure or other overlays applicable?
Eligibility: Does any overlay or site condition exclude the project from the by-right pathway?
Infrastructure: Are utility and access requirements published and testable?
Subdivision: Does land division create a separate approval question?
Building code: Which technical approvals remain after planning compliance is confirmed?
Completeness: Is there a definitive document checklist before substantive review begins?
Clock: When does the review period start, pause and end?
Interpretation: Is there a transparent process for genuine ambiguity?
Relief: Is a waiver or variance clearly separated from interpretation?
Notice: Are neighbours notified where appropriate without confusing notice with discretionary veto?
Data: Can parcel and code information be checked reliably in digital systems?
Capacity: Does the reviewing authority have enough trained staff or regulated certifiers?
Inspection: Who verifies that the completed work matches approved plans?
Enforcement: Are operational and physical requirements enforced after approval?
Appeal: Does any appeal remain focused on compliance and lawfulness rather than reopening settled policy?
Feedback: Are repeated exceptions, delays and interpretations used to improve the code?
Public legitimacy: Was there meaningful participation when the rules and maps were adopted?

The fastest approval is the one that does not need the same argument twice

Town planning has two kinds of difficult work.

The first is deciding what should be allowed.

The second is administering what has already been decided.

When those two jobs are mixed together, every application can become a miniature plan-making exercise. The map says one thing, the hearing may say another, and the practical capacity of land becomes difficult to know until somebody tests it with an expensive proposal.

A by-right system tries to make the contract clearer.

Debate the important policy choices when the plan and code are written. Define the development envelope carefully. Build in exclusions for places that genuinely require more judgment. Publish the measurement rules. Keep technical safety review intact. Give applicants a predictable checklist. Give the public a clear map of what the checklist permits. Audit the certifiers. Inspect the building. Enforce the conditions that remain.

Then a conforming application can become what it should be: not another referendum on the existence of the rule, but evidence that the applicant has met it.

That is the deeper purpose of by-right planning.

Not less planning.

Planning early enough, clearly enough and precisely enough that routine compliance no longer needs to be renegotiated.