Middle Housing Model Codes: What Cities Can Standardize and What They Still Decide

Middle Housing Model Codes: What Cities Can Standardize and What They Still Decide

A model code is a starting line: it makes recurring decisions legible, then forces a city to decide which local constraints are truly necessary.

Policy conversations often jump from a headline to a claimed outcome. A stronger approach follows the work in between: read the governing rule, map the submittal sequence, test a realistic prototype, and publish what happened. That approach matters because housing policy is implemented parcel by parcel, through ordinary decisions about drawings, fees, utilities, timing, and ownership. Washington Commerce describes middle housing as types from duplexes through sixplexes, townhomes, courtyard apartments, and cottage housing. Oregon’s model code identifies duplexes, triplexes, quadplexes, cottage clusters, and townhouses, while allowing compliant local siting and design regulation that does not create unreasonable cost or delay.[1][2]

Start with the decision the policy actually makes

Define the unit of analysis. A city should decide whether it is evaluating a code amendment, an individual permit, a financing offer, or a recorded long-term obligation. Those are related but not interchangeable decisions. The model code framework is strongest when it treats each as a distinct gate rather than collapsing them into a single promise of faster or cheaper housing. In middle housing model codes: what cities can standardize and what they still decide, the operational question is not whether a label sounds pro-housing; it is whether the application, plan set, staff checklist, and final record use the same terms. Start by naming the decision-maker, the triggering condition, the documents required, and the date on which each step is complete. That discipline helps applicants see what can be resolved early and helps the public distinguish a standards-based decision from a late change in expectations. [1]

Draw the boundary. Every program needs a plain-language boundary. Identify eligible sites, excluded conditions, existing structures, environmental or utility reviews, and the standards that continue to apply. A short eligibility map is more useful than a broad slogan because it exposes the cases that staff and applicants will otherwise rediscover under pressure. In middle housing model codes: what cities can standardize and what they still decide, the operational question is not whether a label sounds pro-housing; it is whether the application, plan set, staff checklist, and final record use the same terms. Start by naming the decision-maker, the triggering condition, the documents required, and the date on which each step is complete. That discipline helps applicants see what can be resolved early and helps the public distinguish a standards-based decision from a late change in expectations. [2]

Build a rule set people can use

Translate policy into a checklist. Write the local checklist in the order an applicant encounters it: baseline rules, base zoning, dimensional limits, access, utility information, plan review, and final conditions. Each line should point to a measurable source or a required drawing. If a reviewer cannot circle the evidence on a plan, the city should ask whether the standard is sufficiently clear for consistent administration. In middle housing model codes: what cities can standardize and what they still decide, the operational question is not whether a label sounds pro-housing; it is whether the application, plan set, staff checklist, and final record use the same terms. Start by naming the decision-maker, the triggering condition, the documents required, and the date on which each step is complete. That discipline helps applicants see what can be resolved early and helps the public distinguish a standards-based decision from a late change in expectations.

Separate baseline from incentive. The baseline tells a household or builder what is allowed without special treatment. The incentive, if one exists, should state exactly what additional flexibility is earned and what obligation earns it. This separation is important for model code: it prevents a voluntary option from being mistaken for a universal entitlement and prevents a condition from being added after feasibility has been assumed. In middle housing model codes: what cities can standardize and what they still decide, the operational question is not whether a label sounds pro-housing; it is whether the application, plan set, staff checklist, and final record use the same terms. Start by naming the decision-maker, the triggering condition, the documents required, and the date on which each step is complete. That discipline helps applicants see what can be resolved early and helps the public distinguish a standards-based decision from a late change in expectations.

Implementation scorecard

Test a prototype. Before scaling model code, use several realistic sites or project types. A test should include an uncomplicated example, a constrained example, and an example likely to use the full flexibility offered. The exercise reveals whether one standard silently defeats another, whether a form requests unnecessary information, and whether an apparent time saving merely moves work to a later counter. In middle housing model codes: what cities can standardize and what they still decide, the operational question is not whether a label sounds pro-housing; it is whether the application, plan set, staff checklist, and final record use the same terms. Start by naming the decision-maker, the triggering condition, the documents required, and the date on which each step is complete. That discipline helps applicants see what can be resolved early and helps the public distinguish a standards-based decision from a late change in expectations.

Make the process visible

Control the clock. Time should be measured from a defined event, not from an informal impression that a project has been waiting. Maintain a date-stamped intake, a completeness notice, a consolidated correction list, and a written final action. For applicants, this creates a predictable response sequence. For administrators, it makes bottlenecks visible enough to fix rather than explain away. In middle housing model codes: what cities can standardize and what they still decide, the operational question is not whether a label sounds pro-housing; it is whether the application, plan set, staff checklist, and final record use the same terms. Start by naming the decision-maker, the triggering condition, the documents required, and the date on which each step is complete. That discipline helps applicants see what can be resolved early and helps the public distinguish a standards-based decision from a late change in expectations.

Use one correction cycle well. A correction letter should identify the standard, the missing evidence, and a practical path to cure. It should not substitute a new preference for the rule already published. This is where local calibration becomes concrete: a disciplined correction process can improve quality while preserving confidence that the review is based on known requirements. In middle housing model codes: what cities can standardize and what they still decide, the operational question is not whether a label sounds pro-housing; it is whether the application, plan set, staff checklist, and final record use the same terms. Start by naming the decision-maker, the triggering condition, the documents required, and the date on which each step is complete. That discipline helps applicants see what can be resolved early and helps the public distinguish a standards-based decision from a late change in expectations.

Finance, ownership, and delivery still matter

Do not confuse entitlement with feasibility. Legal permission is only one input to delivery. Land cost, borrowing terms, utility upgrades, insurance, construction capacity, sales or rental assumptions, and household cash flow can still determine whether a permitted project proceeds. Policymakers should explain this openly. A better rule can remove friction without guaranteeing that every site will pencil out. In middle housing model codes: what cities can standardize and what they still decide, the operational question is not whether a label sounds pro-housing; it is whether the application, plan set, staff checklist, and final record use the same terms. Start by naming the decision-maker, the triggering condition, the documents required, and the date on which each step is complete. That discipline helps applicants see what can be resolved early and helps the public distinguish a standards-based decision from a late change in expectations.

Match records to the commitment. Where the policy trades flexibility for an affordability, occupancy, maintenance, or ownership obligation, the record must identify who performs it, how long it lasts, and what happens when the property changes hands. The paperwork is not an afterthought. It is the mechanism that lets future owners, lenders, and administrators understand what was approved. In middle housing model codes: what cities can standardize and what they still decide, the operational question is not whether a label sounds pro-housing; it is whether the application, plan set, staff checklist, and final record use the same terms. Start by naming the decision-maker, the triggering condition, the documents required, and the date on which each step is complete. That discipline helps applicants see what can be resolved early and helps the public distinguish a standards-based decision from a late change in expectations.

Measure outcomes, then revise deliberately

Publish a small dashboard. Track applications, completeness dates, corrections, approvals, denials, withdrawals, and issued permits. Break results out by project type and by the pathway used. For model code, numbers should be paired with a short narrative about unusual cases so a raw average does not hide a recurring barrier. Do not claim causation from a single quarter; use the data to identify questions for the next review. In middle housing model codes: what cities can standardize and what they still decide, the operational question is not whether a label sounds pro-housing; it is whether the application, plan set, staff checklist, and final record use the same terms. Start by naming the decision-maker, the triggering condition, the documents required, and the date on which each step is complete. That discipline helps applicants see what can be resolved early and helps the public distinguish a standards-based decision from a late change in expectations.

Protect equity and accessibility. Clear rules can reduce informational advantage, but they do not erase unequal access to capital, technical assistance, land, or time. Provide plain-language guides, translated materials where needed, accessible digital and non-digital intake options, and a path for questions before a costly application is assembled. Evaluate whether the people intended to benefit can realistically use the pathway. In middle housing model codes: what cities can standardize and what they still decide, the operational question is not whether a label sounds pro-housing; it is whether the application, plan set, staff checklist, and final record use the same terms. Start by naming the decision-maker, the triggering condition, the documents required, and the date on which each step is complete. That discipline helps applicants see what can be resolved early and helps the public distinguish a standards-based decision from a late change in expectations.

Adopt with a revision trigger. A sound ordinance or program sets a review date and identifies what evidence will trigger adjustment: repeated waiver requests, a high incompleteness rate, a costly standard, or a mismatch between recorded commitments and actual outcomes. This is more credible than declaring the policy finished on adoption day. It also helps councils make later changes from evidence rather than anecdotes. In middle housing model codes: what cities can standardize and what they still decide, the operational question is not whether a label sounds pro-housing; it is whether the application, plan set, staff checklist, and final record use the same terms. Start by naming the decision-maker, the triggering condition, the documents required, and the date on which each step is complete. That discipline helps applicants see what can be resolved early and helps the public distinguish a standards-based decision from a late change in expectations.

A practical closing checklist

• Can a reader identify eligibility without contacting staff?
• Can every applicable standard be verified from submitted evidence?
• Are timing milestones date-stamped and communicated?
• Do incentives, obligations, and records match?
• Will the city publish outcomes and revisit the rule?

The best model code policy is not the one with the most ambitious label. It is the one that gives applicants a readable path, gives staff defensible criteria, and gives the public a record of results. Begin with the rule, test it on real sites, watch the handoffs, and revise when evidence shows that the path is not doing what the policy promised.

• [1] https://www.commerce.wa.gov/growth-management/housing-planning/middle-housing/
• [2] https://www.oregon.gov/lcd/Housing/Documents/OAR660046_EXHIBIT_B-Large_Cities_Middle_Housing_Model_Code_20201209.pdf