A building can comply with every numeric zoning rule and still make a poor piece of city.
It can meet the height limit and place a blank wall along the footpath. It can satisfy setbacks and create a hostile windswept plaza. It can provide the required entrance but hide it behind a parking ramp. It can meet floor-area limits while breaking the rhythm of an important street. It can technically preserve a heritage façade and make the addition above it look unrelated to everything below.
Design review was created to examine questions like these: not simply is the building legal?, but does the building make a good place?
That extra layer of judgment has obvious value. It also creates one of planning’s hardest governance problems. Quality is partly measurable and partly contextual. Review can improve projects, but it can also add uncertainty, time, redesign cost and bargaining power that is difficult to predict from the zoning code alone. If the process becomes too subjective, “good design” can become an unwritten code whose rules are discovered only after an applicant has spent millions.
This article has one reader job: explain how discretionary urban design review works, what it can do that objective standards cannot, where it becomes unpredictable, and how cities can preserve design quality without turning personal taste into a second invisible zoning system.
1. Design review is not the same as zoning
Zoning usually establishes the development envelope: permitted uses, height, setbacks, floor area, lot coverage, parking, density and other defined controls.
Design review operates inside or alongside that envelope. It examines how the building meets the street, how massing responds to context, how entrances work, how façades are composed, how open space functions, how service areas are screened, how heritage is treated, and how multiple design choices work together.
The distinction matters because design review should not quietly erase development rights that the zoning code appears to grant unless the legal framework clearly authorises that result.
2. Design review is also not the same as objective design standards
An objective standard says something like: ground-floor glazing must cover at least 60 per cent of the primary street frontage; a blank wall may not exceed a stated length; the main entrance must face a public street; upper floors must step back a defined distance above a defined height.
Design review may instead ask whether the façade creates an appropriate human scale, whether the entrance is legible, whether the massing responds to context or whether the public realm is sufficiently engaging.
Objective standards trade flexibility for predictability. Discretionary review trades predictability for contextual judgment.
For the measurable-code owner, see TPW-0056 — The Objective Code. This article owns the discretionary review mechanism, not the standards themselves.
3. Design review is not the same as form-based zoning
Form-based codes regulate urban form directly through frontage types, building placement, height, massing, street relationships and public-realm rules. They attempt to encode desired form before an application arrives.
Design review evaluates a particular design against guidelines and context after an application exists.
For that separate regulatory model, see TPW-0108 — The Form-Based Code.
4. Design review is not the same as site plan review
Site plan review often coordinates practical site functions: access, circulation, drainage, parking, loading, landscaping, utilities and public-realm connections.
Design review may overlap, but its distinctive job is qualitative urban and architectural design judgment.
For the site-coordination owner, see TPW-0111 — The Site Plan Review.
5. Why cities created design review
Numeric codes cannot anticipate every site.
A 12-metre setback can create a gracious plaza in one project and a useless leftover lawn in another. A 20-storey building may fit comfortably on one corner and overwhelm a narrow historic street elsewhere. The same façade percentage can produce a beautifully proportioned shopfront or a chaotic glass wall.
Design review lets the city evaluate relationships that are difficult to capture in one universal number.
6. The core tension: discretion is both the feature and the risk
Design review is useful precisely because the reviewer can say, “this site is different”.
That is also what makes applicants nervous.
If every site is different, what can a developer know before buying land? If one board accepts a design and another rejects a similar one, is the standard really public? If a guideline says “respond to neighbourhood character”, which neighbourhood features count, and who decides?
The quality of a design-review system depends on how well it converts legitimate discretion into a repeatable decision process.
7. A current live policy debate: Portland in 2026
Portland provides an unusually current case study. In May 2026 the city published a Design Review Reform Report outlining options to streamline design and historic-resource review while maintaining Comprehensive Plan objectives.
On August 18, 2026, Portland released a proposal to temporarily suspend most mandatory design review for approximately two years and allow qualifying projects to use existing clear and objective design standards instead. Design review would remain optional for applicants seeking flexibility, with selected cases still requiring review. As of September 13, 2026, the proposal was scheduled for a Portland Planning Commission hearing on September 22, 2026.
The significance is not that Portland has decided design review is worthless. Its reform programme is explicitly trying to preserve design quality while improving predictability, speed and development feasibility. That is the central tension this entire article examines.
8. Seattle shows a second live reform path
Seattle’s design-review programme has also entered a major transition. The city states that temporary rules adopted October 26, 2025 paused required Design Review and made the process voluntary while Seattle develops long-term updates required by Washington State House Bill 1293.
Seattle’s current Design Review Program page still describes design review as a tool for shaping new multifamily and commercial buildings, but the temporary legal framework demonstrates how strongly states and cities are reconsidering the balance between subjective review and housing delivery.
When two experienced West Coast cities are simultaneously reforming design review, the topic is not a niche procedural dispute. It is an active question about how modern planning should govern urban quality.
9. The design guidelines are the constitutional document of the process
Good design review should not begin with the reviewer’s personal preference. It should begin with adopted guidelines.
Seattle describes its design guidelines as the backbone of the Design Review Program. The guidelines direct designers and reviewers to study context and evaluate how projects contribute to their surroundings.
The more discretion a system allows, the more important it becomes that the decision can be traced back to published guidance rather than taste.
10. Guidelines should express objectives, not merely adjectives
“Create attractive architecture” is nearly useless as a decision rule.
A stronger guideline identifies the design problem: strengthen pedestrian activity at the primary frontage; reduce the apparent bulk of long façades; preserve important public views; transition massing toward lower-scale neighbours; place service functions where they do not dominate public space.
Those objectives still require judgment, but they tell applicants what urban outcome the review is protecting.
11. Too many guidelines can make the process less clear
A city may accumulate citywide guidelines, neighbourhood guidelines, historic-district guidelines, plan-district guidelines and project-specific expectations.
When dozens of principles overlap, nearly any design choice can be praised under one guideline and criticised under another. The review record then becomes a contest over which guideline should dominate.
A mature system should identify priority guidelines early and explain how conflicts are resolved.
12. Early design guidance can save expensive redesign
The best time to change massing is before structure, unit plans and engineering are fixed.
Many design-review systems therefore include an early-design-advice stage. The applicant presents site analysis, massing alternatives, access concepts and public-realm ideas before developing the full architectural package.
Early advice can identify the one or two design questions that truly matter and prevent late-stage review from becoming expensive aesthetic surgery.
13. Early advice is useful only if later reviewers respect it
If a board endorses Option A at the early stage and then a later board effectively asks for Option B after months of design development, the early process loses value.
Design guidance should therefore be recorded clearly: preferred massing, unresolved issues, accepted principles and items still open to change. Later review can respond to new information, but it should explain why an earlier direction is being revisited.
14. Who should review: staff or board?
Design review can be carried out administratively by professional staff, by an appointed design commission or neighbourhood board, or through a tiered system using both.
Staff review can be faster and more consistent. A multi-member board can bring design expertise, local knowledge and public legitimacy. Boards can also create scheduling delays and greater variation between reviewers.
The correct structure depends on project scale and public significance. A modest infill building may not need the same review machinery as a civic tower or major waterfront project.
15. Seattle’s board composition illustrates deliberate pluralism
Seattle’s current design-review structure divides the city into geographic districts and uses volunteer boards with seats representing design, community or residential, development, and business or landscape-design perspectives.
That structure acknowledges that good urban design is not owned by one profession. Yet plural representation also requires clear guidelines so the board does not become five different private definitions of quality sitting at one table.
16. Thresholds decide which projects pay the process cost
Design review is rarely required for every shed, extension and small house. Jurisdictions usually establish thresholds based on floor area, dwelling count, building height, zone, overlay or project type.
Threshold design is a policy choice. If set too low, small projects bear disproportionate professional and time costs. If set too high, many buildings with major urban impact avoid qualitative review entirely.
A tiered system can route smaller projects to administrative review, larger projects to board review, and the most consequential projects to a fuller process.
17. Threshold cliffs can distort project size
If crossing from 49 to 50 units triggers months of additional review, a developer may build 49 units even when the site and zoning could support more.
That is not necessarily proof that the review is wrong. It is proof that review costs become part of development economics.
Planners should monitor whether projects cluster just below thresholds and whether the public benefit of the added review justifies that behavioural effect.
18. The pre-application meeting and design review should not duplicate each other
A project may already have discussed access, zoning, utilities, heritage and infrastructure in a pre-application conference. Design review should build on that record rather than restart the whole application.
For the broader early-risk process, see TPW-0180 — The Pre-Application Conference.
19. Context analysis should be evidence, not theatre
Design-review applications often contain pages of photographs, diagrams and neighbourhood descriptions. The important question is whether that analysis leads to a design decision.
If the surrounding street has a consistent cornice height, does the project respond? If a major pedestrian flow approaches from one corner, is the entrance placed there? If an important view exists, does massing preserve or frame it?
Context analysis should explain cause and response: because the site has X condition, the design does Y.
20. “Neighbourhood character” is a dangerous phrase without decomposition
Character can mean block size, street wall, roof form, materials, building age, tree canopy, shopfront rhythm, setbacks, topography, cultural history or simply familiarity.
If reviewers use “character” without naming the relevant physical or social attribute, the phrase can become a veto against change itself.
A strong decision says what characteristic matters and why: fine-grained shopfronts support pedestrian activity; a consistent street wall defines an important civic space; mature trees create a recognised landscape structure.
21. Good design review should permit contrast as well as compatibility
Contextual design does not require imitation.
A contemporary building can respect scale, rhythm and public-realm relationships without copying historic ornament. A distinctive civic building may appropriately contrast with its surroundings while still handling entrances, edges and massing well.
If design review equates “fits in” with “looks like everything nearby”, it can freeze architecture into stylistic repetition.
22. The massing question should come before the material question
A badly massed building cannot usually be rescued with better brick.
Review should first examine the large decisions: where the building sits, how tall parts relate, where open space goes, how the base meets the street, where entrances and service areas occur, how the project transitions to neighbours.
Materials, detailing and colour come later. This sequencing keeps review focused on decisions with the greatest urban consequence.
23. Public realm should be reviewed as a system
A plaza can be beautiful in plan and unusable at lunchtime because it is windy, shaded and disconnected from active uses. A wide pavement can still feel hostile if blank walls line it. A landscape strip can become a barrier if every entrance sits behind it.
Design review should connect ground-floor use, entrances, weather protection, seating, landscape, lighting, visibility and movement rather than checking each element separately.
24. The blank-wall problem is a classic design-review job
A code can limit blank-wall length objectively. But a reviewer can also ask whether a service-dominated frontage belongs on the most important pedestrian street, whether landscape can soften an unavoidable wall, or whether the building programme can be reorganised.
This is where discretionary review can solve the actual urban problem rather than merely count metres.
25. Design review can trade departures for better design
Some systems allow the review body to approve departures or modifications from selected development standards when the alternative better satisfies design guidelines.
This is one of design review’s strongest arguments. A rigid code may require a setback that produces worse urban form on a particular site. Discretion can permit a better solution.
It is also a source of complexity. Applicants may enter design review not because they want subjective scrutiny but because review is the only way to obtain flexibility from an otherwise rigid rule.
26. Optional design review can become a flexibility market
Portland’s August 2026 reform proposal is instructive. During the proposed temporary suspension of most mandatory review, design review would remain available voluntarily, including for applicants seeking design flexibility that objective standards cannot provide.
This creates a useful structural separation: applicants who can meet objective standards get a predictable route; applicants who want a different design can choose discretionary review and demonstrate why the alternative better serves design objectives.
That model makes discretion an option rather than a universal tax on every qualifying project.
27. But optional review can create two design classes
If objective standards are weak, projects may choose the fast route and produce mediocre buildings. If objective standards are too rigid, nearly every ambitious project may still need discretionary review.
The success of a dual-track system depends on the quality of the objective baseline. The standards must be good enough to produce acceptable buildings without review and flexible enough that ordinary projects can actually comply.
28. Public participation belongs in design review—but needs a defined scope
Residents can identify local conditions that drawings miss: a dangerous corner, a cherished view, a noisy loading route, a shortcut used by children, a public space that fails after dark.
That information can improve design.
The problem arises when design review becomes a second referendum on whether development should occur at all. If zoning already permits housing at a certain density, design review should not covertly relitigate the existence of that housing through endless requests to reduce scale.
29. The public comment should be translated into design issues
“I hate this building” is not a design finding.
“The loading entrance is directly opposite a residential lobby and will create conflict during the evening” is a design issue. “The tower is too big” may need to be translated into shadow, transition, view or street-wall concerns that the design guidelines actually address.
Reviewers add value when they convert public concern into an analysable urban-design question.
30. The hearing should not reward whoever has the most free evenings
Public meetings can overrepresent people with time, confidence and professional familiarity. Renters, shift workers, younger residents and future residents may be underrepresented.
Design review should therefore combine public comment with adopted citywide policy and technical design expertise rather than treating meeting attendance as a direct proxy for public interest.
31. The board should state findings, not simply preferences
A defensible design-review decision explains:
- which adopted guideline applies;
- what existing site or context condition is relevant;
- how the proposal responds;
- what deficiency remains;
- what condition or revision is necessary;
- why that response is proportionate.
“The board did not like it” should never be the operative record.
32. Conditions of approval should be buildable
A condition saying “improve the architecture” creates a future argument. A condition requiring a revised ground-floor treatment addressing a named guideline, with specified design intent and review route, is more workable.
Design conditions should be precise enough that architects, permit reviewers and inspectors can tell when the requirement has been satisfied.
33. Design review needs a stop rule
Without a stop rule, a project can become an endless sequence of “one more improvement”.
A well-designed process limits meeting rounds, sets decision timelines and distinguishes essential changes from optional recommendations. If the application satisfies the guidelines to the legal standard, review should end even if a reviewer can imagine a different building they personally prefer.
34. Time is a design variable because projects change while waiting
Long review can change construction pricing, interest rates, lender commitments and tenant demand. A project designed under one market can become infeasible before approval.
The cost of delay may then produce value engineering after design review: cheaper materials, smaller windows, reduced landscape or lost amenities. Ironically, a process intended to improve design can indirectly weaken it if time costs consume the project’s quality budget.
35. Predictability is itself a public planning value
Predictability is sometimes framed as a developer convenience. It is more than that.
When rules are predictable, land prices can reflect obligations, financing can be arranged, smaller developers can compete, public expectations are clearer and similar projects receive similar treatment.
Discretion should therefore be reserved for questions where contextual judgment creates enough public value to justify the uncertainty it introduces.
36. Small developers feel uncertainty more than large developers
A large firm may have in-house planning counsel, architects experienced with the board and capital to survive several redesign rounds. A small builder may not.
Complex discretionary review can therefore concentrate development in the hands of firms capable of carrying regulatory uncertainty. This competition effect is easy to miss when review is evaluated only project by project.
37. Repeat applicants can develop an informal advantage
Experienced local teams learn what particular reviewers prefer, which arguments succeed and how to frame departures. That knowledge can become an unwritten procedural asset.
A transparent system tries to move that knowledge into public guidance, precedent libraries, staff reports and clearly stated findings so newcomers do not need private institutional memory to navigate review.
38. Precedent should inform without becoming a frozen style book
Publishing successful design-review cases can improve predictability. Applicants can see how guidelines were interpreted and how departures were justified.
But precedent should describe principles, not require every future project to copy the previous façade. The purpose is consistent reasoning, not aesthetic replication.
39. Reviewer training matters
Design expertise does not automatically equal regulatory expertise.
Reviewers need training in the governing code, adopted guidelines, legal limits, housing policy, accessibility, climate design, cultural context and decision writing. They also need discipline in distinguishing a personal design preference from a finding supported by adopted policy.
40. Conflicts of interest must be managed visibly
Design-review boards can include practising architects, developers, landscape designers and local business representatives. That expertise is valuable, but members may know applicants, consultants or competitors.
Clear recusal and disclosure rules protect the legitimacy of the process.
41. Design review can become an unofficial affordability cost
Every month of carrying land, consultant teams and financing costs money. Required façade upgrades, structural changes and redesign also cost money.
Some quality investments create long-term value. Others may simply shift cost into rents, sale prices or lower land bids. The public-benefit question is therefore whether the marginal design improvement is worth the marginal cost and delay.
This is particularly important where the same city is simultaneously asking development to provide inclusionary housing or other public benefits. Regulatory demands interact even when each individual rule appears reasonable.
42. Design review can also protect long-term value
The opposite argument deserves equal weight. Buildings last for decades. A poor street edge, hostile public space or insensitive heritage response can impose public costs long after the developer has left.
Good review can catch site-specific failures that a generic code misses and can produce buildings that contribute more to the city over their lifetime.
The rational debate is therefore not “design quality versus development”. It is which design questions deserve discretionary review, and how can that review be made proportionate and predictable?
43. Heritage review needs a different calibration from ordinary design review
A building in a protected historic district may affect a legally recognised heritage resource. The review may need to evaluate significance, compatibility, demolition, material authenticity and preservation standards beyond ordinary urban-design questions.
Portland’s 2026 reform discussion treats design and historic-resource review together in some respects but retains distinctions and targeted exceptions. A city should not assume every design-review reform can be applied identically to heritage protection.
44. Civic buildings may justify stronger design scrutiny
A courthouse, major station, waterfront cultural building or central public plaza has a public role beyond an ordinary private building. Stronger review, design competitions or specialised panels may be proportionate.
Proportionality cuts both ways: small ordinary projects should not automatically face the same process as city-shaping projects, and city-shaping projects should not necessarily receive only a checklist review.
45. The environmental-performance boundary
Design review can consider shade, landscape, façade performance, passive design and public comfort, but it should not duplicate energy codes or technical environmental standards unnecessarily.
Where a measurable technical code already controls energy or stormwater performance, design review should focus on urban-design consequences rather than rerun the engineering approval.
46. The accessibility boundary
Universal access is not an aesthetic preference. It is a functional and often legal requirement.
Design review can improve the dignity and integration of accessible routes—placing them at the main entrance rather than around the back—but should not treat minimum accessibility compliance as negotiable design character.
47. The safety boundary
A reviewer may prefer a more open stair, fewer barriers or a different façade. Fire safety, structural safety and emergency egress remain governed by technical codes.
Good interdepartmental coordination prevents design review from asking for architectural changes that later become impossible under building or fire requirements.
48. The shadow and wind problem shows why technical evidence still matters
A board may reasonably care about a tower’s effect on a plaza. But visual intuition alone is a poor substitute for measured shadow or wind analysis where those effects are material.
Design judgment should sit on top of technical evidence: the study shows what happens; the design-review process decides whether the effect is acceptable and how the project should respond under adopted policy.
49. A board should not redesign the project from the dais
Reviewers can identify problems and desired outcomes. They should be cautious about dictating an exact architectural solution unless necessary.
“Make the entrance visible and directly connected to the plaza” preserves design authorship better than “move the door three metres left and use a red canopy”.
The first statement regulates performance. The second risks turning reviewers into unpaid project architects.
50. Applicants should present alternatives honestly
Early design review often asks for several massing options. If two options are deliberately weak so the preferred option looks inevitable, the exercise becomes theatre.
Alternatives should test real design choices: courtyard versus perimeter block, tower location A versus B, retained building versus replacement, different public-space structures.
The point is to reveal trade-offs before the project locks itself into one path.
51. Review comments should distinguish “must”, “should” and “could”
Applicants need to know which comments are legally necessary for approval, which are strong design recommendations and which are optional ideas.
When every suggestion sounds mandatory, design teams overreact and the process accumulates unnecessary cost. When essential findings are phrased casually, projects can return without resolving the actual problem.
52. The decision record should survive staff turnover
A project can last years. Board members rotate. Planning staff change. Architects change firms.
The written record must therefore state the design rationale clearly enough that a new reviewer understands which decisions were settled and which remain open.
53. Appeals should review findings, not conduct a fresh beauty contest
An appeal body needs a defined standard of review. Did the decision apply the adopted guidelines correctly? Were findings supported? Was procedure fair? Was the condition within legal authority?
If appeal simply substitutes one set of aesthetic preferences for another, predictability gets worse.
For the general machinery of land-use appeals, see TPW-0182 — The Planning Appeal.
54. Post-approval amendments should not reopen settled design unless the change matters
Construction inevitably changes details. A new cladding supplier or plant layout should not automatically trigger full design review if the approved design intent remains intact.
But a “minor” amendment that removes a public arcade, changes tower proportions or replaces a carefully reviewed landscape edge can undermine the basis of approval.
See TPW-0185 — The Approved-Plan Amendment for the post-permission change test.
55. Value engineering is the final design-review stress test
A project can win approval with high-quality materials, deep window reveals, landscape and public-space details, then seek cheaper substitutions during construction.
The approval should identify which design features are essential enough to remain controlled and which details can evolve. Over-controlling every material creates inflexibility; under-controlling the key features allows the approved quality to evaporate.
56. Design review should measure its own performance
A city should be able to answer:
- How long does review add?
- How many meetings does the average project require?
- How often are projects sent back?
- Which guidelines generate the most disputes?
- How often are departures approved?
- Do similar projects receive similar findings?
- What measurable design improvements result?
- How many projects abandon or shrink after entering review?
A process justified by quality should collect evidence about the quality and cost it produces.
57. The reform spectrum is wider than “keep it” or “abolish it”
Cities can reform design review in many ways:
- raise project thresholds;
- move more projects to staff review;
- reduce the number of meetings;
- simplify guidelines;
- create objective alternatives;
- reserve boards for major or sensitive sites;
- make review voluntary where applicants want departures;
- publish precedent decisions;
- impose decision deadlines;
- digitise submissions and standardise staff reports.
Portland’s 2026 temporary-suspension proposal represents one point on that spectrum: temporarily rely on objective standards for most projects while retaining optional review and selected mandatory cases, then use the period to design longer-term reforms.
58. Temporary suspension can be a policy experiment
A temporary pause creates a natural comparison period.
Did permit timelines shorten? Did more projects proceed? Did design quality measurably decline? Did applicants still choose voluntary review for flexibility? Which objective standards proved weak? Which review functions turned out to be indispensable?
If the city measures those outcomes, a temporary reform can produce evidence for permanent policy rather than merely a political pendulum swing.
59. Seattle’s temporary voluntary system creates another experiment
Seattle’s October 2025 interim change likewise makes formerly required review voluntary while permanent programme changes are developed.
The city can compare projects using voluntary review with projects proceeding without it and can observe which kinds of applicants still value the flexibility and public process.
The long-term opportunity is to rebuild design regulation around evidence rather than inherited procedure.
60. Objective standards should absorb recurring review lessons
If design boards repeatedly complain about the same problem—blank parking podiums, hidden entrances, weak corner treatment, poor weather protection—that is evidence the code may be missing a predictable standard.
Design review should therefore feed code maintenance. Recurring lessons can be translated into objective baseline requirements, leaving discretionary review to genuinely contextual questions.
This is how a planning system learns instead of solving the same problem project by project forever.
61. Conversely, standards should identify where discretion is still necessary
Some sites are too unusual for a universal rule: steep slopes, complex heritage ensembles, major civic spaces, waterfronts, significant public views, unusually large blocks or projects combining multiple towers and public spaces.
A strong system does not pretend every design problem can be solved by a spreadsheet. It reserves discretion for the places where contextual intelligence is worth the cost.
62. A worked example: the compliant but hostile podium
A 20-storey apartment tower complies with height, FAR and setback rules. The first four floors are parking, wrapped only partially by active uses. Along one street, pedestrians face 60 metres of ventilation grilles and vehicle ramps.
An objective code could solve much of this through frontage and blank-wall standards. If those standards are weak, design review can ask the project to reorganise uses, wrap parking, relocate access or articulate the base.
The lesson is not that discretion is always necessary. It is that the city needs a mechanism—objective or discretionary—that owns the ground-floor urban consequence.
63. A worked example: the heritage corner
A new building beside a protected theatre meets all numerical rules but proposes a blank party wall rising far above the theatre roofline.
Design review may explore tower placement, setbacks and massing transitions in ways a generic citywide rule cannot fully anticipate. The review should tie its request to the recognised significance of the theatre and adopted heritage or design guidelines rather than to an abstract preference for “less bulk”.
64. A worked example: the board asks for fewer homes
A housing project fits the zoning envelope, but reviewers dislike its apparent mass and suggest removing an entire floor.
This is where process boundaries matter. If the same design objective can be achieved through articulation, upper-level setback, material hierarchy or mass redistribution, reducing permitted housing may be a disproportionate response.
Design review should solve design problems with design tools before it silently becomes density control.
65. A worked example: the objective route is too rigid
A code requires a fixed street setback. On a triangular site, following the setback produces a tiny unusable wedge of open space and weakens the corner.
An optional design-review route may allow the building to move closer to the street if the alternative creates a better public realm and satisfies the relevant guidelines.
Here discretion creates value by allowing the project to depart from a rule whose general logic does not fit the specific site.
66. A worked example: endless material debate
A project’s massing, entrances and public space are strong. The review process spends three meetings debating whether the upper façade should be brick, terracotta or metal.
Unless material choice affects an adopted heritage, durability or public-realm objective, the process may be consuming time without proportionate public value.
A mature system knows when design judgment has crossed into personal authorship.
67. The applicant’s preparation checklist
- Identify the applicable design-review route and thresholds before land acquisition is final.
- Read the guidelines before designing the building.
- Map the few site conditions that genuinely drive design.
- Use early guidance before structural and unit plans are fixed.
- Present real alternatives, not straw options.
- Link every departure request to a stronger guideline outcome.
- Track board and staff comments in a response matrix.
- Distinguish mandatory findings from optional advice.
- Preserve the approved design intent through construction changes.
- Maintain a decision record that future team members can understand.
68. The reviewer’s checklist
- Identify the adopted guideline before stating the concern.
- Describe the real urban consequence, not personal taste.
- Prioritise massing, public realm and access before cosmetic detail.
- Respect settled guidance from earlier review stages unless new evidence requires change.
- Translate public comments into relevant design issues.
- Do not use design review to relitigate development rights already granted by zoning.
- State conditions precisely enough to be implemented.
- Use departures proportionately and explain the better design outcome.
- End review when the legal design standard has been met.
- Feed recurring issues back into objective code improvements.
69. The city’s reform checklist
- Measure existing review time, redesign rounds and outcomes.
- Identify which project types benefit most from discretionary review.
- Move recurring design problems into objective standards where possible.
- Simplify and prioritise design guidelines.
- Create a predictable staff-review path for ordinary projects.
- Reserve boards for projects with genuinely public or contextual significance.
- Publish decisions and precedent examples.
- Set review timelines and stop rules.
- Monitor housing production, design quality and applicant diversity after reform.
- Revise the system again when evidence shows it is not working.
70. What the 2026 reform moment is really testing
Portland and Seattle are both testing whether more development can move through objective standards without unacceptable loss of urban design quality.
The answer will not be found in ideology. It will be found in the buildings, permit timelines, public spaces and development pipelines produced under the new rules.
If objective standards prove capable of handling most ordinary projects, discretionary review can become narrower and more strategic. If important design failures appear repeatedly, those failures can either justify targeted review or be translated into better objective standards.
That is how regulatory reform should work: test, observe, encode what is repeatable, preserve discretion where context genuinely demands it.
71. The core idea
Design review exists because cities are more than legal envelopes.
Buildings shape streets for generations. Their ground floors affect whether people walk. Their massing changes sunlight and views. Their entrances decide whether public space feels connected. Their service areas can make a block work or fail. Some of those relationships cannot be reduced perfectly to numbers.
But discretion is powerful. If the city cannot explain why one design passes and another fails, design review begins to resemble an unwritten zoning code. That uncertainty has real costs: time, money, fewer competitors, delayed housing and distrust.
The best system therefore divides the work intelligently. Put repeatable expectations into objective standards. Use design guidelines for genuinely contextual questions. Make findings traceable. Keep public participation relevant. Give applicants early direction. Stop when the required design outcome is achieved. Then feed what the city learns back into the code.
Good design review does not ask a city to choose between beautiful buildings and predictable rules. It asks the city to decide which parts of beauty can become rules—and which parts still require judgment.
Authoritative reference points
- Seattle Department of Construction and Inspections — Design Review Program, including the current temporary voluntary-review framework adopted in 2025.
- Seattle — Design Review Guidelines, explaining the role of citywide and neighbourhood design guidelines.
- Seattle — 2025 Design Review Program Changes, documenting the interim suspension of required review and the state-law reform context.
- City of Portland — Design Review Reform Report announcement, May 14, 2026.
- City of Portland — Proposal to temporarily suspend mandatory design review, August 18, 2026, with the Planning Commission hearing scheduled for September 22, 2026.