Data dashboards for housing production help city staff, elected officials, builders, advocates, and residents see whether homes are being approved and completed fast enough to meet demand. In practice, a housing production dashboard is a public reporting tool that turns permit records, planning approvals, inspections, and affordability data into a shared picture of what is being built, where, at what price point, and how long it takes. I have worked with municipal reporting systems where basic questions such as “How many homes were permitted last quarter?” or “Which neighborhoods are adding deed-restricted units?” still required manual spreadsheet work. A well-designed dashboard replaces that friction with consistent metrics, common definitions, and routine publication. For cities facing high rents, rising homelessness, workforce shortages, and pressure on infrastructure, that transparency matters because production problems are rarely caused by one issue alone. They emerge from land constraints, approval delays, financing gaps, utility limits, labor shortages, and policy choices. A public dashboard does not solve those problems by itself, but it does make them measurable, comparable, and harder to ignore. That is why every city serious about housing policy should publish a housing production dashboard with clear definitions, frequent updates, and metrics that connect planning intentions to completed homes.
What a housing production dashboard should measure
The first job of a city dashboard is to define the housing pipeline from entitlement to completion. Many cities publish only building permits, which is useful but incomplete. A stronger dashboard tracks sites submitted, units proposed, units approved, permits issued, construction starts, units under construction, certificates of occupancy, and completed homes. Those stages reveal where projects stall. If approvals are high but starts are low, the bottleneck may be financing, utility capacity, or construction costs. If permits are rising but completions lag badly, inspection staffing or contractor availability may be slowing delivery. If applications are dropping, the problem may be zoning feasibility or weak project economics.
Cities should also publish tenure and structure type because not all units serve the same needs. Single-family homes, townhomes, duplexes, accessory dwelling units, small multifamily buildings, and large apartment projects respond to different household types and land conditions. Rental and ownership units should be reported separately. Student housing, senior housing, supportive housing, and mixed-income developments should also be identifiable. In my experience, staff often know these distinctions internally, but public reports collapse them into a single total, which hides whether the market is producing family-sized homes, deeply affordable units, or mostly studios in a narrow set of districts.
Geography matters just as much as totals. Every housing production dashboard should break results down by neighborhood, council district, transit station area, and zoning category. Cities often adopt ambitious growth strategies around transit, job centers, or corridors, then fail to show whether actual production matches those plans. Publishing maps and district-level summaries makes that gap visible. It also reduces political argument about whether growth is “concentrated everywhere” or “all in one place” by replacing anecdote with counts, rates, and trends.
Core metrics every city should publish monthly or quarterly
The most useful dashboards pair volume metrics with speed, affordability, and capacity indicators. Volume metrics include units proposed, approved, permitted, started, under construction, and completed. Speed metrics include median days in entitlement review, median days from approval to permit issuance, median days from permit issuance to start, and median days from start to certificate of occupancy. Affordability metrics include total income-restricted units, units by area median income bands, inclusionary units, voucher-accepting units where tracked, and preservation outcomes for expiring affordability covenants. Capacity metrics include zoned capacity, remaining pipeline capacity in specific plans, available sewer or water capacity where that is a constraint, and public land identified for housing.
Cities should report these metrics as counts, shares, and rates per 1,000 residents. Raw totals answer one question; rates enable comparison across districts and over time. A city adding 2,000 homes a year may look productive until population growth or household formation requires 4,000. Likewise, a district producing 300 units may be outperforming a larger district once land area, transit access, or prior underproduction are considered. Whenever possible, the dashboard should show trailing twelve-month figures alongside monthly or quarterly numbers to smooth volatility from large projects landing in a single reporting period.
| Metric | What it shows | Why it matters |
|---|---|---|
| Units permitted | Homes legally cleared for construction | Best near-term indicator of future supply |
| Units completed | Homes ready for occupancy | Direct measure of delivered housing |
| Median review time | Typical duration of entitlement or permit processing | Shows administrative bottlenecks |
| Income-restricted units | Homes reserved at defined affordability levels | Distinguishes market-rate growth from affordable delivery |
| Geographic distribution | Where production occurs by district or neighborhood | Tests fairness, plan alignment, and transit-oriented goals |
| Pipeline attrition | Difference between proposed and completed units | Reveals fallout caused by costs, delays, or policy friction |
A strong dashboard also distinguishes net new units from gross production. Demolitions, condominium conversions, mergers of small units into larger ones, and loss of regulated affordable homes can erase a meaningful share of apparent growth. Net units completed is the number residents feel. If a city permits 1,000 units but loses 180 through demolition and covenant expiration, the net addition is 820. That number should be visible, not buried in a separate report.
Why process metrics matter as much as unit counts
Housing production is not just a quantity problem. It is a throughput problem. I have seen cities celebrate annual permit totals while ignoring that median review times doubled, appeal rates rose, and projects needed several rounds of corrections before approval. Those conditions eventually suppress applications, especially from smaller builders with less capital to carry delays. Publishing process metrics gives cities an early warning system before unit production weakens.
The most important process measures are median and percentile review times by project type, number of review cycles, approval path, and resubmittal frequency. A median can hide severe delays on complicated projects, so dashboards should also show the 75th or 90th percentile. For example, if the median site plan review takes 95 days but the 90th percentile is 260 days, the city has a reliability problem even if the average appears manageable. Builders price uncertainty into land offers and financing assumptions. Long, unpredictable timelines can make moderate-income or mixed-income projects infeasible even when zoning technically allows them.
Appeals and discretionary review should be transparent too. Cities should report how many units entered ministerial review versus discretionary review, how many projects were appealed, average days added by appeal, and outcomes after hearings. If design review boards or environmental review processes consistently extend timelines, that should be visible. The point is not to eliminate public process automatically. It is to quantify its effect. Good policy balances design quality, environmental standards, and neighborhood input against the cost of delay.
Inspection and occupancy data often get overlooked, yet they are critical. Permits do not house people. Final inspections, temporary certificates of occupancy, and full occupancy signoff determine when units become usable. If projects are completing construction but waiting weeks for inspection or utility energization, the city can fix that operational bottleneck faster than it can rewrite zoning. Dashboards should therefore include average days from final inspection request to occupancy approval and backlog counts by inspection type.
Affordability, equity, and neighborhood outcomes
A city should never publish housing production totals without affordability context. Residents want to know not just how many homes are being built, but whether those homes are affordable to workers, families, seniors, and people exiting homelessness. The dashboard should categorize income-restricted units by affordability bands such as up to 30 percent, 50 percent, 60 percent, 80 percent, and 120 percent of area median income. It should also separate newly constructed affordable units from preserved units, because extending an affordability covenant is valuable but different from adding new supply.
Equity reporting should examine where homes are being added relative to opportunity. A useful dashboard overlays production with access to transit, jobs, schools, parks, and historically exclusionary zoning patterns. If nearly all affordable housing is concentrated in lower-income neighborhoods while high-opportunity districts add little, the city should say so plainly. Likewise, if growth is disproportionately occurring in areas facing displacement risk, the dashboard should pair production data with anti-displacement indicators such as eviction filings, rent burdens, and preservation investments. Housing dashboards work best when they do not pretend supply, affordability, and displacement are unrelated topics.
Unit mix also affects neighborhood outcomes. Publishing bedroom counts shows whether a city is producing family-sized homes or mostly smaller units. Studio and one-bedroom apartments are important, especially near transit and job centers, but cities also need two-bedroom and three-bedroom units for households with children, multigenerational families, and roommates sharing costs. In recent dashboard work, I found that a city appearing strong on overall apartment production was materially underperforming on larger unit types. Without bedroom-level reporting, that gap stayed hidden.
Data sources, definitions, and governance standards
The best dashboard in the world fails if its definitions are inconsistent. Cities should publish a data dictionary that defines every metric, update frequency, source system, and known limitation. “Approved units” may mean planning commission approval in one city and final building permit signoff in another. “Affordable” may refer to deed-restricted units, subsidized rents, or merely below-market asking rents. Without definitions, comparisons are misleading and public trust weakens.
Most housing production dashboards pull from permitting software, planning case management tools, tax assessor parcels, geographic information systems, utility records, and affordability compliance databases. Common platforms include Accela, Tyler EnerGov, Cityworks, ESRI ArcGIS, and Power BI or Tableau for visualization. Integrating these systems takes careful record matching because project names, parcel numbers, and addresses are often entered differently across departments. Cities should assign a persistent project identifier that follows a development from application to occupancy. That single change improves reporting more than most redesign efforts.
Governance matters too. One department should own publication, but multiple departments should validate the feed. Planning, building, housing, public works, and finance all hold part of the story. Establishing a monthly reconciliation process reduces errors such as duplicate project counts, outdated affordability statuses, or completed buildings still listed as under construction. When cities revise prior data, they should note the reason and preserve archives. Transparent revisions build credibility because users can see that corrections reflect stronger quality control, not manipulation.
How cities can make dashboards genuinely useful to the public
Public usefulness depends on design choices as much as data quality. Dashboards should answer common questions in one or two clicks: How many homes were completed last year? Which districts added the most affordable units? How long does approval take for a mid-rise apartment building? Are accessory dwelling units increasing? A dense interface filled with technical charts may satisfy analysts while frustrating residents. The best municipal dashboards provide a summary view for casual users and downloadable data for researchers, journalists, and advocates.
Context is essential. Every chart should include a short explanation of what changed and why it matters. If completions dip because several large projects were delayed by interest rates, say so. If permit issuance rises after a code amendment or staffing increase, note the operational cause. Numbers without interpretation invite confusion or political spin. At the same time, interpretation should stay factual and avoid advocacy language. A city dashboard is a reporting instrument, not a campaign document.
Cities should also link the dashboard to related pages on zoning reform, affordable housing programs, accessory dwelling unit guidance, housing element implementation, and capital planning. That helps users move from outcomes to policies and actions. Accessibility standards matter as well. Charts should be readable on phones, tables should be downloadable, maps should have text alternatives, and color choices should work for color-blind users. Publishing an API or open data export further increases trust because outside analysts can test the numbers independently.
From reporting to action: using dashboard signals to improve production
The real value of a housing production dashboard is operational. Once metrics are public, cities can set targets and manage to them. If permit review for small multifamily projects is taking 40 percent longer than adopted service levels, managers can add plan reviewers, standardize comments, or expand pre-application support. If a transit station area has high zoned capacity but low applications, planners can examine parking rules, setback standards, fees, and infrastructure constraints. If affordable housing approvals are healthy but starts are weak, the gap may be subordinate financing, tax credit timing, or prevailing wage costs.
Benchmarking against peer cities is particularly useful when definitions are standardized. Comparing median entitlement days, units permitted per 1,000 residents, and share of production near high-frequency transit can reveal whether a city is lagging because of market conditions or local process. During periods of high interest rates, for example, production may slow regionwide. A city whose pipeline is holding up better than peers may have stronger by-right zoning, lower fees, or faster inspections. Those lessons can be replicated.
For city leaders, the practical takeaway is simple: publish the full pipeline, publish process times, publish affordability and geography, and publish the definitions behind the numbers. Then use the dashboard in budget, staffing, and policy decisions. For residents and builders, transparent metrics make housing debates more honest because everyone can see where projects advance, where they stall, and who benefits from current patterns. If your city does not yet publish a housing production dashboard, start with a limited set of reliable metrics, commit to regular updates, and improve from there. The first step toward better housing outcomes is making production visible.
Frequently Asked Questions
What metrics should cities publish on a housing production dashboard?
A strong housing production dashboard should publish metrics that help people understand the full development pipeline, not just the number of building permits issued at the end. At a minimum, cities should show applications submitted, projects approved, permits issued, units under construction, certificates of occupancy, and completed homes. Those counts should be broken down by housing type, such as single-family, multifamily, accessory dwelling units, supportive housing, senior housing, and mixed-use projects with residential units. It is also important to show unit totals by bedroom count, tenure, and affordability level so the public can see whether the city is producing the kinds of homes residents actually need.
Cities should also publish time-based metrics. For example, how many days does it take to move from application to entitlement, from entitlement to permit issuance, and from permit issuance to completion? Median review time is usually more useful than averages because it reduces distortion from unusually delayed projects. In addition, dashboards should include geographic metrics, such as units approved by neighborhood, council district, transit area, or zoning category. That makes it easier to identify whether housing growth is concentrated in only a few places or being distributed more broadly.
Finally, the best dashboards include performance and capacity indicators. These might include approval-to-completion conversion rates, projects withdrawn or expired, inspection pass rates, inclusionary units delivered, fee waivers used, and public land projects underway. When cities publish these metrics consistently, they create a shared factual basis for policy conversations. Instead of debating anecdotes, staff, elected officials, and residents can look at the same numbers and ask better questions about bottlenecks, equity, and whether local housing goals are actually being met.
Why is it important to track both approvals and completions instead of just permits?
Tracking only permits gives an incomplete and sometimes misleading picture of housing production. A permit is an important milestone, but it does not guarantee that a home will be built, delivered on schedule, or reach the price points that local residents need. Many projects are approved and permitted but stall because of financing problems, construction cost changes, legal challenges, labor shortages, or market shifts. If a city publishes permit totals without showing what happens afterward, the public may assume production is stronger than it really is.
Approvals matter because they reveal how much capacity the local process is creating. If approvals are low, the city may have a zoning, planning, or political bottleneck. Completions matter because they show what actually reached the market and became available for occupancy. Comparing approvals, permits, construction starts, and completions helps cities see where projects are getting stuck. For example, if entitlements are rising but completions are flat, the problem may be in building plan review, utility coordination, financing, or inspections rather than land use policy alone.
This full-pipeline approach is especially valuable for decision-makers. Elected officials can see whether policy reforms are improving real delivery, not just paper approvals. Builders and lenders can better understand timelines and project risk. Advocates and residents can evaluate whether promises about affordable housing and neighborhood growth are becoming actual homes. In short, approvals tell you what the city has allowed, while completions tell you what the city has delivered. A useful dashboard should show both clearly and consistently.
How should cities report housing affordability on a public dashboard?
Affordability reporting should go beyond a simple label that says a project is “affordable” or “market rate.” Cities should report affordability by income level, typically using area median income bands such as extremely low income, very low income, low income, and moderate income. If possible, dashboards should also show the number of deed-restricted units, naturally occurring lower-cost units preserved, inclusionary units delivered, and publicly subsidized units in development. This makes the data much more meaningful because it shows who the homes are intended to serve rather than relying on vague categories.
Cities should also distinguish between proposed affordability and delivered affordability. A project may be approved with affordable units, but those units may not be completed for several years. A well-designed dashboard should show affordability commitments at approval, affordability at permit issuance if relevant, and affordability at completion or occupancy. Where local rules allow, cities can also report rents or sale price ranges, affordability term lengths, and whether units are family-sized, supportive, or accessible. These details help residents and policymakers understand whether the housing pipeline aligns with the city’s stated goals around displacement prevention, fair housing, and economic inclusion.
Clarity and consistency are essential. Definitions should be published directly on the dashboard so users know exactly what counts as affordable, income-restricted, subsidized, or below-market. If the city changes methodology, it should note the change publicly to preserve trust. Affordability data can be politically sensitive, but that is exactly why it should be presented carefully and transparently. Good affordability reporting does not just answer how many units are being built; it answers whether the city is creating homes that people across income levels can realistically afford.
What time-to-approval and time-to-completion indicators are most useful?
The most useful timing indicators are the ones that break the development process into clear, understandable stages. Cities should report median days from application submission to completeness determination, from completeness to planning decision, from planning approval to building permit issuance, from permit issuance to construction start, and from construction start to certificate of occupancy. Reporting only one total duration hides where the real delays occur. Stage-by-stage timing gives staff and the public a practical way to identify bottlenecks and target process improvements.
It is also helpful to segment timeline data by project type and review path. Small infill projects, accessory dwelling units, large multifamily buildings, and 100 percent affordable developments often move through very different processes. Ministerial projects may have shorter and more predictable timelines than discretionary projects. By breaking out review times by category, a dashboard can show whether delays are broad-based or concentrated in certain kinds of housing. Cities may also want to show percentiles, not just medians, so users can understand both typical performance and the share of projects experiencing especially long delays.
Another valuable indicator is predictability. Builders and community stakeholders care not only about whether approvals are fast, but whether they are reliable. A dashboard can publish on-time review rates, resubmittal frequency, inspection turnaround times, and the number of projects waiting beyond a target threshold. This kind of reporting supports management accountability. If the city says permits should be issued within a certain number of business days, the dashboard should show whether that target is being met. The goal is not to simplify a complex process into one number, but to make timing visible enough that process reform can be grounded in evidence rather than guesswork.
How can cities make a housing production dashboard credible, useful, and easy for the public to understand?
Credibility starts with clean definitions, regular updates, and visible methodology. Users should be able to tell where the data comes from, how often it is refreshed, and what each metric means. If permit records, planning approvals, inspections, and affordability data come from different systems, the city should explain how they are matched and where limitations exist. A dashboard becomes much more trustworthy when it openly notes data gaps, duplicates, lag times, and known quality issues instead of pretending the numbers are perfect. Public confidence grows when cities treat data transparency as an ongoing operational practice rather than a one-time technology project.
Usefulness depends on organization and comparability. The dashboard should let users filter by year, geography, project type, affordability level, and stage in the pipeline. It should show trends over time, not just a current snapshot. Comparisons against housing goals, regional targets, prior-year performance, or adopted plans help users interpret whether the numbers are strong or weak. Narrative annotations are also helpful. For example, if completions fall in one quarter because of seasonal construction patterns or delayed inspections, the city can briefly explain that context. Good dashboards combine charts, tables, and concise written interpretation so the numbers are understandable to non-specialists while still being detailed enough for analysts and practitioners.
Ease of understanding comes from thoughtful design. Plain-language labels, downloadable data, mobile-friendly layouts, and accessibility features all matter. So does avoiding overloaded screens. A strong dashboard usually begins with a simple summary view showing key indicators and then allows deeper exploration for users who want more detail. Ultimately, the most effective housing production dashboards are not built just to display data. They are built to support better decisions. When cities publish consistent, transparent, and policy-relevant metrics, they make it easier for staff, elected officials, builders, advocates, and residents to work from the same factual baseline and focus on solutions.
