City of Yes for Housing Opportunity: UAP, Bonus Floor Area & How MIH Interacts

Before this reform, a New York City lot had essentially four routes to floor area above its base ceiling, and every one of them was expensive. It could take a voluntary inclusionary bonus where the program was available. It could absorb unused development rights from a neighbor through a zoning-lot merger. It could receive a landmark transfer under the Resolution's special-permit machinery. Or it could seek discretionary relief — a rezoning, a special permit, a variance — through a public process measured in years.

The housing amendment added a fifth route with a different shape. Rather than a discretionary approval or a market transaction, it wrote additional floor area directly into the district rules as a conditional row: a ceiling that applies when a development provides permanently affordable housing meeting the Resolution's definition, or qualifying senior housing. The condition is in the rulebook, so meeting it is a design decision rather than an application. That is the mechanical significance of the Universal Affordability Preference, and it is why it is discussed as an as-of-right option rather than a bonus program.

In a structured reading of the current bulk rules, the change is visible as a shape rather than a slogan. Many districts no longer carry a single row. They carry a standard row, often split by whether the lot lies within a set distance of a wide street, and beside it a qualifying-housing row keyed to affordable or senior housing. Some districts carry a further row narrowed to lots outside mapped inclusionary areas, which is the Resolution's way of preventing two affordability regimes from stacking on the same floor area.

The consequence for anyone reading a district's rules is that 'the maximum FAR' is no longer a single number for a great many districts. It is a small table whose governing row is selected by facts about the lot and the project: street width and frontage, position relative to mapped areas, and what the development provides. Reporting one figure from that table without saying which row it came from is the most common way a modern zoning summary goes wrong.

A qualifying row is also more than a floor-area number. Where the Resolution grants additional floor area for qualifying housing it typically states the envelope that goes with it — a minimum base height, a maximum base height, and a maximum building height, all specific to the qualifying case. The bonus and the envelope arrive together. Taking the higher ceiling means building to the envelope stated for it, not to the envelope that applied before.

Mandatory Inclusionary Housing is a mapped program: it applies within areas catalogued in the Resolution's appendix, added one at a time through the public land-use process, and it does not apply outside them. Its options are a defined menu — each specifying an affordable share of residential floor area and an income ceiling expressed as a weighted average of income bands — and the mapping action for each area selects which options govern there. Post-reform the Resolution phrases those ceilings against an 'income index,' the successor term to the older headline metric, which is a vocabulary change worth knowing when comparing current text to older summaries.

The qualifying-housing rules City of Yes added run in the space MIH does not occupy. The clearest example in the current text is a district row that grants additional floor area specifically for developments outside mapped inclusionary areas within a set distance of a wide street. Read structurally, the two regimes are complements: inside a mapped area, the mandatory program's terms govern the affordable floor area; outside one, the citywide qualifying rows are the available route. Which side of that line a lot falls on is a mapping question with a definite answer, and it is the first thing worth establishing.

The same amendment restructured residential parking requirements around named geographies rather than district code alone. The Resolution's definitions chapter now describes an Inner Transit Zone, an Outer Transit Zone, and a Greater Transit Zone that is the union of those two with the special parking areas, each delimited by boundaries the definitions describe and the City publishes as a mapped layer. The requirement attached to each differs in kind: within the Inner Transit Zone the residential minimums are eliminated, within the Outer Transit Zone they are reduced, and beyond the Greater Transit Zone the baseline percentages by district still govern.

Two things follow. First, parking requirement is now a location question before it is a district question — two lots in the same district on opposite sides of a zone boundary carry different obligations. Second, the definitions include an explicit tie-breaker: where the published mapped layer and the textual description of a boundary conflict, the text controls. That is an unusual and useful concession in a rulebook, and it means a boundary dispute is resolved by reading, not by clicking.

A defensible screen runs in a fixed order. Establish the district and pull every bulk row it carries, not the first one. Establish whether the lot lies inside a mapped inclusionary area, because that fact selects between the two affordability regimes rather than merely adding a requirement. Establish the street width the lot fronts on and how much of the lot lies within the relevant distance of a wide street, since that selects among rows within a district. Then read the envelope stated for whichever row a project would rely on, because a ceiling you cannot physically place is not a ceiling you can finance.

What that produces is a range, not a number: the floor area available if a project provides nothing, and the floor area available if it provides qualifying housing and builds to the corresponding envelope. The gap between those two figures is the actual subject of most conversations about this reform. It is also the honest output of a screen — the point at which the question stops being a records question and becomes a design and capital question that no database answers.