Treat the three constraints as a system
An early development concept can appear straightforward: estimate how much area a site permits, fit parking, and select a building height. In practice, these decisions affect one another. A taller form may change core and circulation requirements. Parking layout affects access, site coverage, and usable open space. A density target can be constrained by geometry, setbacks, operations, infrastructure, or approval conditions.
The owner should not treat a single maximum figure as the answer. Instead, ask the design and land use team to show how the relevant requirements apply to the actual parcel and how the concept responds. Separate standards already confirmed from interpretations, design assumptions, and approvals still required. A requirement can be clear in writing while its application to a particular concept remains a question for qualified professionals or the appropriate authority.
Consider a hypothetical owner evaluating a site with a preferred residential program. The first sketch may show a large building and a parking count that fits on paper. Before relying on it, the owner needs to know how area was measured, whether parking spaces and circulation physically work, whether the height includes rooftop or mechanical elements as defined locally, and whether the site can support the proposed access and services.
An owner-side development feasibility study can organize these questions alongside cost, schedule, and approval dependencies. It does not substitute for architectural, engineering, legal, or authority review. Its purpose is to help ownership understand how assumptions connect and what must be verified next.
Define the density measure before comparing plans
State the calculation basis
Density can refer to different things depending on the use, rules, and analysis. A team may discuss floor area, units per site area, occupants, bedrooms, or another measure. Ask everyone to state the measure and calculation method. If two concepts use different definitions, an apparent increase may be a spreadsheet artifact rather than a meaningful program change.
Review what areas are included or excluded, how site area is defined, and which parcel boundaries or dedications apply. Ask the architect to show both the governing calculation and the areas needed to make a functional building. Net usable, rentable, or sellable area may not track directly with gross building area because of cores, corridors, mechanical rooms, amenity space, loading, and other support functions.
Test the parcel, not just the maximum
Examine the concept against the site's shape and constraints. A theoretical amount of floor area is only useful if a feasible arrangement can accommodate access, fire and life safety, servicing, circulation, light and ventilation needs, open space, and the intended program. The responsible design team should explain which constraints are known and which require additional analysis.
Ask for a small number of clearly differentiated test fits rather than many uncoordinated sketches. For each, document the program, area definition, building form, assumptions, and unresolved questions. A controlled comparison helps ownership understand whether a higher density depends on greater height, a different footprint, a changed mix, or a design interpretation that remains unconfirmed.
Understand how height changes the building
Height is not only a skyline question. It can influence structural approach, vertical circulation, elevators, fire and life safety, building systems, construction sequence, and the relationship between floor-to-floor dimensions and usable program. A small change in the number of levels may create implications beyond the added floor area.
Ask the team how height is measured and which elements count. Definitions may treat grade, parapets, rooftop equipment, and mechanical levels differently. Do not transfer another project's method; identify the applicable source and any interpretation needing confirmation.
Height also interacts with context and approval procedure. Identify any required review, study, or design response with local professionals, and distinguish a permitted standard from a request for relief. An application or discussion is not approval.
For a hypothetical alternative, a more compact taller building might preserve ground area for access or open space. It might also require a different core, structural system, or review path. A lower, broader building could reduce some vertical demands while affecting parking layout and site coverage. The design team should show the tradeoffs and the owner should avoid endorsing a form based only on a headline floor-area figure.
Test parking as geometry and operation
Parking is not just a count or surface-area allowance. A useful test includes spaces, aisles, turning movements, ramps, columns, accessible routes, loading, pedestrian paths, and building connections. It should reflect users, operations, and applicable requirements.
Ask how the count was produced and which spaces are included, including relevant user, accessible, loading, bicycle, or service needs. If relying on shared or off-site parking, a reduction, or a transportation strategy, identify the evidence or approval needed before treating it as certain.
Study parking location and building design together. Above-grade parking affects frontage and occupied area; structured parking affects columns, ramps, and integration; underground parking depends on site conditions and excavation; surface parking uses land that might serve buildings, drainage, or open space. Designers and engineers should assess project-specific feasibility.
Owners should request drawings that demonstrate circulation, not just shaded rectangles. Ask the design team to identify where vehicles enter and exit, how service and emergency access work, and whether a layout creates conflicts with pedestrian movement or building operations. A parking count that fits on a diagram may not be a practical plan.
Reconcile regulations with design alternatives
Create a constraints matrix linking each requirement to its source, reviewer, and status. Record the parcel condition, standard, proposed response, and outstanding interpretation or approval. Update it as survey, title, and concept information changes.
If a plan depends on relief, exception, variance, or another discretionary process, make that dependency explicit. Ask counsel and the land use team to explain the applicable process and evidence requirements. Do not model a favorable decision as a certainty simply because it is a desired outcome or because a similar request appears to have been made elsewhere.
Compare alternatives consistently. A test-fit summary can show building area, program, parking, circulation, open space, core and support needs, approval dependencies, and information gaps. Pair it with qualified cost review using consistent scope and schedule assumptions.
Where a concept needs adjustment, define the tradeoff rather than saying only “add density” or “reduce parking.” A change could affect unit mix, amenity space, parking location, access, or building form. The owner should understand what value the option is intended to preserve, what it changes, and what new approvals or technical analysis may be triggered.
Connect the test fit to the project model
Do not enter a test fit in the pro forma as a completed design. State its maturity, estimating assumptions, and unresolved issues. Ask the cost professional to identify scope coverage, exclusions, allowances, and schedule assumptions. Reconcile differences before comparing options.
Track how each design scenario affects both the project and the owner's decision. A parking strategy may change excavation, structure, site work, operations, or approval needs. A height option may alter vertical transportation and systems. A higher floor-area concept may demand more utility service or change the project's delivery sequence. The model should show those connected effects only to the degree supported by current information.
Use sensitivity tests for assumptions most likely to change the decision. Compare the current concept with a lower-density fallback or different parking configuration while keeping other inputs consistent. The aim is to show whether further study is warranted if a preferred assumption fails.
If the pro forma has stopped working, a structured pro forma review can help trace which program, cost, schedule, and capital assumptions are driving the result. The design options should be validated by the appropriate project professionals before they are adopted as a new basis for decision-making.
Manage authority and provider questions early
Use early communication with agencies and providers to learn process and documentation needs, distinguishing informal guidance from formal decisions. If an interpretation is material, ask whether a written determination or application is appropriate and record the source and limits of information.
Do not assume infrastructure capacity follows from a density concept. A larger program may change demand for utilities, access, loading, or transportation. Identify providers, studies, connection points, review steps, and dependencies, then confirm service and timing with the responsible party.
The owner can improve coordination by assigning one accountable lead to maintain the constraints matrix and schedule. The architect, engineers, counsel, cost professional, and land use advisor each have defined responsibilities. An owner's representation advisor can help keep decisions, dependencies, and action items aligned without replacing those technical or legal roles.
Make a decision from evidence, not a maximum
Before advancing a preferred option, ask what is confirmed, what remains an assumption, and what could change the result. The owner should understand the distinction between a code or zoning standard, a conceptual fit, an application under review, and a formal approval. Those are different states, and the project record should describe them accurately.
Set decision gates based on evidence. For example, ownership might require a confirmed parcel survey, a documented interpretation, a viable circulation plan, and an updated cost review before authorizing the next design phase. The exact gate depends on the project and purchase terms. Counsel and the project professionals should advise on requirements and contractual consequences.
The most useful concept is not necessarily the one with the largest area, greatest height, or maximum parking count. It is the option the team can explain, verify, price, and advance with a reasonable understanding of remaining exposure. Density, parking, and height are not isolated targets. They are linked decisions that need to be tested together.
Frequently asked questions
Which should I solve first: density, parking, or height?
Define the applicable measures and parcel conditions first, then ask the design team to test the three together. The order of analysis depends on the site and program because a change in one can affect the others.
Does a zoning limit tell me how much area I can actually build?
Not by itself. The applicable rules are one input. Parcel geometry, design, access, parking, infrastructure, technical requirements, and required approvals can further shape a workable concept.
Can a parking reduction or height exception be assumed in an early model?
Treat it as an unresolved scenario unless the appropriate authority has formally confirmed it. Ask qualified local professionals to identify the process, evidence, schedule, and design alternatives before relying on the outcome.
About the author
Sam Castelan
Chief Consultancy Officer (Senior Architect, Master Planner, MBA, MPL, MPA)
Brings development, master planning, and value engineering experience.
Meet the PVA teamKeep reading
Related insights
Development & Feasibility
Data Center Land: Why Power Capacity Drives Value
8 min read
Development & Feasibility
How a Parking Plan Can Cap Your Unit Count, and How to Unlock It
8 min read
Development & Feasibility
How to Evaluate a Development Site Before You Buy It
8 min read