Housing dashboard · Occupancy is not an outcome

Build a housing dashboard that sees past occupancy.

Sopact reads every intake assessment, survey, and case note the moment it arrives — and links it to one resident record, so the dashboard shows whether residents are stably housed and improving, not just whether the unit is filled. A housing dashboard that reports 96% occupancy while a quarter of self-sufficiency residents fall behind is a number that satisfies a property manager and fails a funder. This page is the step-by-step method, for the affordable housing operators, public housing authorities, and community development teams who have to show resident outcomes.

By Unmesh Sheth · Founder & CEO, Sopact · Updated May 25, 2026

Bring one dashboard you report on See: Program dashboard

7 dashboards Worked examples, source to report

Qual + quant On one resident record

Read on arrival Not a six-system reconcile

2014 Building for impact data since

Definition

What is a housing dashboard?

Plain definition

A housing dashboard is a single view that shows whether residents of an affordable, public, or supportive housing program are stably housed and improving — not just whether units are occupied. It tracks resident outcomes across five domains, pairs each metric with the resident's own words, and updates as data arrives rather than at the HUD deadline.

Level 1 · An occupancy rate

"96% occupied"

The units are full. It says nothing about whether the residents are stably housed.

Level 2 · A dashboard

"Occupancy and rent roll, refreshed monthly"

Property metrics in motion. The resident's life — stability, income, well-being — is still invisible.

Level 3 · A housing dashboard

"Housing stability, economic mobility, and the resident's own words — every figure traced to the resident."

A funder renews on this one.

The gap

Why most housing dashboards fail

A housing organization typically runs four to six disconnected systems — property management, case management, surveys, compliance spreadsheets. Most housing dashboards fail before a chart is drawn, for four reasons.

Failure 1

Occupancy is not an outcome

The dashboard shows units filled and rent collected. It never shows whether residents are housed stably, employed, or moving forward — the evidence a funder asks for.

Failure 2

The "Which Maria?" problem

One resident is Unit 4B in property management, Case #7742 in case management, Respondent #389 in the survey. Matching her across six systems by hand takes weeks.

Failure 3

The resident voice goes unread

Why a satisfaction score fell from 7.8 to 6.2 lives in open-ended responses and case notes. With no one to code them, the reason never reaches the dashboard.

Failure 4

Compliance, not learning

The dashboard is built for the HUD deadline. It answers "did we meet the metric" — never "are residents better off" or "which intervention worked."

Bottom line

A housing dashboard fails when it reports occupancy instead of outcomes, and when one resident cannot be followed across the systems that hold her data. Fix the resident record first — the dashboard follows.

The approach

Immediate, continuous, and learning — not at the deadline

The fix is not a prettier chart. It is a change in when the dashboard reads its data, and what it does with the resident's story once it has it. Sopact builds housing dashboards on three principles.

Principle 1 · Immediate

Read on arrival

An intake assessment, a survey, a case note is themed, scored, and joined to the resident record the moment it arrives — not held for a quarterly reconcile. The metric and its reason land together.

Principle 2 · Continuous

One resident, one record

Every resident keeps one Persistent Contact ID from intake through follow-up. The dashboard shows a resident journey — not six disconnected snapshots stitched together by hand.

Principle 3 · Learning

Why it moved, what we changed

Every metric is paired with a why-it-moved annotation and a visible what-we-changed log. The dashboard becomes a continuous learning loop — not a report assembled for an auditor.

Why it matters

A quarterly occupancy report tells you the units were full. An immediate, continuous, learning dashboard flags the self-sufficiency residents falling behind while they are still housed with you — in time to act.

The data layer

A dashboard is only as reliable as the data underneath it

Before any chart, two questions decide whether a housing dashboard can be trusted: where the data comes from, and whether the system can follow one resident across every place her data lives. This is the layer Sopact owns.

Step 01 · Sources

Where the data comes from

Primary — you collect it

Intake assessment Resident survey Open-ended feedback Case note

Secondary — systems you run

Property management system HUD reporting system Case management system

→

Step 02 · The join

Persistent Contact ID + data dictionary

One record per resident Qual + quant on one row Read on arrival

The data dictionary maps Unit 4B, Case #7742, and Respondent #389 to one resident. The "Which Maria?" problem is solved at the join — not by hand every quarter.

→

Step 03 · Output

A five-domain housing dashboard

Resident outcomes HUD report Occupancy Funder view

Every figure opens back to the resident record it came from — traceable to source.

Primary data — collected directly in Sopact Sense Secondary data — integrated from systems you already run

Approach A

The primary-data approach

Sopact Sense collects intake assessments, resident surveys, and open-ended feedback clean at source — one record per resident, with a persistent ID assigned at intake. Lead with primary data when the question is about resident outcomes and the why: housing stability, economic mobility, well-being, and what a resident actually said.

Approach B

Integrating primary + secondary

Occupancy, rent roll, and HUD compliance fields live in the property-management and reporting systems you already run. Integrate secondary data when the question needs those records. The data dictionary maps each system's identifier to the one resident record — so occupancy and outcomes read together.

The proprietary layer

Sopact's layer is the combination — qualitative data, quantitative data, and the data dictionary that resolves one resident across six systems. It is what stops the failure every housing team knows: 80% of staff time spent matching records, and a dashboard that is weeks old by the time it loads.

The method

How to build a housing dashboard, step by step

Here is the build, in the order Sopact runs it — six steps from the resident-outcome question to a dashboard that refreshes itself and produces the HUD report as a by-product.

1

Name the resident-outcome question

Start from what a funder or board will ask. "Are residents in the self-sufficiency program advancing on income?" beats "build a housing dashboard." The question names the outcome domains to track and the residents to follow.

2

Write the logic model and data dictionary first

Map the program theory — housing stability enables economic mobility, education, health, and engagement — then define every field and, critically, map each system's resident identifier to one record. This is the step that resolves the "Which Maria?" problem.

3

Collect primary data clean at source

Run intake assessments, resident surveys, and check-ins through Sopact Sense. Each resident gets one Persistent Contact ID at intake; every later survey links to it; residents can correct their own information, so the cleanup cycle ends.

4

Integrate the property and HUD systems you run

Connect the property-management system, HUD reporting fields, and case management through the data dictionary. Occupancy and compliance map to the resident record — so occupancy and resident outcomes finally read on one dataset.

5

Read on arrival, build the five-domain view

Sopact reads every response the moment it lands — theming open text, scoring outcomes, flagging the property that is slipping. The view is assembled across housing stability, economic mobility, education, health, and community engagement. An AI build tool finishes it in minutes.

6

Set it to refresh — and generate the HUD report from it

The dashboard updates as data arrives. The HUD-compliant report is a filtered view of the same dataset — not a separate assembly project. Every metric carries a why-it-moved note and a what-we-changed log.

Time

A 6-to-9-month implementation collapses to days — the first resident response is dashboard-ready.

Money

The 80% of staff time spent matching records is reclaimed — and compliance reporting drops by most of its hours.

Risk

Every resident-outcome claim opens back to the resident record — defensible to HUD, a funder, or a board.

The output

What a finished housing dashboard looks like

The method produces a report that behaves like a live dashboard — resident outcomes across five domains for a sample affordable housing operator. Every figure traces back to a resident record. Sample data, illustrative.

Housing dashboard · live

Housing dashboard

Sample affordable housing operator · 1,840 residents · 6 properties · FY2026

What occupancy hides

96%

Occupancy — the metric that looks fine on its own

Source: property management system

23%

Self-sufficiency residents falling behind on plan, flagged this quarter

Source: outcome survey, primary

71

Resident well-being index, of 100 — lowest at two properties

Source: resident pulse, primary

Residents on track, by outcome domain

Housing stability

91%

Economic mobility

64%

Education & youth

78%

Health & well-being

73%

Community engagement

58%

Resident outcomes by property — the gap occupancy hides

Property	Occupancy	Self-sufficiency on track	Well-being index	Exits to stable housing
Property A	97%	71%	76	88%
Property B	95%	52%	64	71%
Property C	98%	69%	74	85%
Property D	94%	58%	66	74%

Why it moved, and what we changed

Why it moved

Economic mobility rose where financial coaching offered flexible scheduling — named by 78% of residents who advanced.
Vacancy days fell 21% after resident follow-up forms were embedded in the dashboard.
Well-being at Property A rose after a post-maintenance pulse caught issues the same week.

What we changed

Childcare added to the employment-services schedule — cited by 64% of non-participants as the barrier.
Text reminders for missing documents at pre-lease — missed paperwork down 38%.
A two-question well-being pulse embedded after each maintenance closeout.

Sample data, illustrative · every figure traces to a resident record under one Persistent Contact ID

Read it together

Property B reports 95% occupancy and looks healthy. The dashboard says only 52% of its self-sufficiency residents are on track, well-being sits at 64, and the resident voice says childcare is why. Occupancy never would have shown it.

The examples

Seven housing dashboards, and the data behind each

Five dashboards for the resident-outcome domains, two for compliance and operations. Each names its data sources, whether they are primary or secondary, and the risk it is built to catch.

Primary — collected directly Secondary — integrated from a system you run

1

Housing stability dashboard

Prop A

91%

Prop B

79%

Prop C

88%

Sources

Lease and tenancy records (secondary) plus the intake assessment (primary).

Surfaces

Lease compliance, length of tenancy, eviction prevention, exits to permanent housing.

Risk caught

An eviction the occupancy rate never warned you about.

2

Economic mobility dashboard

Employment & income survey Program participation

Surfaces

Employment status, income growth, financial-literacy completion, self-sufficiency milestones.

Risk caught

A self-sufficiency program nobody can prove works.

3

Education & youth dashboard

Youth program records School data

Surfaces

School attendance, academic progress, and afterschool participation for resident youth.

Risk caught

Youth outcomes a funder asks for and the org cannot produce.

4

Health & well-being dashboard

Well-being pulse Open-ended feedback

Surfaces

Healthcare access, well-being self-reports, and referral completion — with the themes underneath.

Risk caught

A well-being score with no reason and no property cut.

5

Community engagement dashboard

Program & event participation Resident feedback

Surfaces

Program participation, leadership development, and social connection by property.

Risk caught

Engagement that flows to residents who were already connected.

6

HUD & compliance dashboard

HUD reporting fields Resident records

Surfaces

Occupancy, waitlist, recertification timeliness, and inspection status — mapped to HUD formats.

Risk caught

A compliance scramble at every reporting deadline.

7

Occupancy & operations dashboard

Property management system

Surfaces

Occupancy, vacancy days, make-ready cycle time, and work-order status by property.

Risk caught

Occupancy read as program health, with no resident outcome beside it.

The build tools

Build the view with the AI tools you already have

The dashboard view itself — the charts, the five-domain layout, the funder summary — is no longer the hard part. Claude, Google's analytics stack, Microsoft Power BI, and Tableau all turn clean, linked resident data into a working housing dashboard in an afternoon.

So the value is not in the chart-building. It is in what those tools assume but cannot supply: resident data that is clean at source, one resident followed across six systems, and a data dictionary that maps every identifier to one record. Point an AI build tool at fragmented property, case, and survey exports and it builds a fast, confident dashboard on data that is weeks old and partially matched. Point the same tool at the layer Sopact maintains and it builds a housing dashboard a funder can act on.

What AI build tools do well

Build the five-domain view fast — charts, layout in an afternoon.
Write the funder-ready and board-ready narrative.
Re-cut a view for an operator, a board, or a HUD audience on request.
Handle the analysis once the resident data is clean and linked.

What they cannot do for you

Collect resident feedback — they are downstream of collection.
Resolve one resident across property, case, and survey systems.
Link an intake assessment to an outcome measured a year later.
Read the resident voice that explains why a score moved.

The analysis got easy. The resident record did not. That is the layer to own.

Where each tool stops

What it takes to track the resident, not just the unit

A property-management system tracks units and leases. A survey bolt-on collects feedback but fragments it. A BI dashboard renders whatever it is handed. A working housing dashboard follows one resident across every system and reads the outcome, not the occupancy rate alone.

Capability	Property mgmt system (Yardi, RealPage)	Spreadsheet + survey bolt-on	BI dashboard (Power BI, Tableau)	Sopact
Tracks resident outcomes, not just units	No — units and leases	Partial — one survey at a time	Depends on the source	Yes — five outcome domains
One resident ID across every system	Within the property system only	No — the "Which Maria?" problem	Partial — manual matching	Yes — Persistent Contact ID
Continuous refresh	Yes — for occupancy	No — updated by hand	Partial — needs a pipeline	Yes — reads on arrival
Reads the resident voice	No	No — sits unanalyzed	No — quantitative only	Yes — themed on arrival
Qualitative + quantitative on one record	No	No	No — separate tools	Yes
Pre-post outcome tracking	No	Not across survey cycles	Partial — if a pipeline exists	Yes — intake to follow-up
HUD report from the same dataset	Property metrics only	Manual assembly	Manual formatting	Yes — a filtered view
Data cleanup before it is usable	Low — but wrong layer	High — weeks of matching	Medium — ETL pipeline upkeep	Clean at source
Best audience	Property managers	One analyst	Data and IT teams	Housing operators, PHAs, funders

A property-management system answers "is the unit filled." A housing dashboard answers "is the resident better off." A funder increasingly asks the second — and only one tool here can answer it.

See it on your own data

Bring one housing report your team produces today.

We follow one resident across your systems, trace an outcome to its source, and rebuild the view live — your data, not a demo account.

Book the walkthrough

FAQ

Housing dashboards, answered.

What is a housing dashboard?+

A housing dashboard is a single view that shows whether residents of an affordable, public, or supportive housing program are stably housed and improving — not just whether units are occupied. It tracks resident outcomes across housing stability, economic mobility, education, health, and community engagement, pairs each metric with the resident's own words, and updates as data arrives rather than at the HUD deadline.

What is an affordable housing dashboard?+

An affordable housing dashboard tracks both property performance — occupancy, vacancy days, rent roll — and resident outcomes — housing stability, employment, income, well-being — across an affordable housing portfolio. It combines quantitative program data with qualitative resident feedback, so an operator can show a funder that the housing improves lives, not only that the units are filled.

How do you build a housing dashboard?+

Build a housing dashboard in six steps: name the resident-outcome question, write the logic model and data dictionary, collect primary data clean at source under one resident ID, integrate the property-management and HUD systems you already run, read every response on arrival, then assemble the five-domain view and set it to refresh. The resident ID is assigned at intake, so every later record links without manual matching.

What is a public housing dashboard?+

A public housing dashboard is designed for a public housing authority. It tracks HUD-required metrics — occupancy, waiting-list management, recertification timeliness, inspection status, voucher utilization — alongside resident outcomes for programs such as Family Self-Sufficiency. The strongest versions combine compliance metrics with longitudinal evidence that the supportive programs actually improve residents' economic mobility and well-being.

What metrics should a housing dashboard track?+

A housing dashboard should track resident outcomes across five domains: housing stability (lease compliance, length of tenancy, exits to permanent housing), economic mobility (employment, income, self-sufficiency milestones), education and youth (school attendance, academic progress), health and well-being (healthcare access, well-being self-reports), and community engagement (program participation, leadership). Each is paired with the qualitative reason behind any change.

How is a housing dashboard different from property management software?+

Property management software tracks units, leases, and maintenance — it answers whether the unit is filled and the rent is collected. A housing dashboard tracks what happens to the people living in those units — housing stability, economic mobility, well-being. Occupancy is a property metric; resident outcomes are the impact metric. A funder increasingly asks for the second, and an occupancy rate cannot answer it.

Should a housing dashboard use primary or secondary data?+

Lead with primary data — intake assessments, resident surveys, open-ended feedback, case notes you collect directly — because resident outcomes and the reasons behind them live in primary data. Integrate secondary data from the property-management system, HUD reporting systems, and the case-management system when the question needs occupancy, compliance, or service records. The data dictionary maps every system's ID to one resident record.

What are housing dashboard examples?+

Housing dashboard examples include the five outcome-domain views — housing stability, economic mobility, education and youth, health and well-being, and community engagement — plus a HUD and compliance dashboard and an occupancy and operations dashboard. Each draws on a mix of primary resident data and secondary property and compliance data, and pairs every metric with the resident voice.

Can a housing dashboard support HUD compliance reporting?+

Yes. When the housing dashboard and the HUD report draw from one connected dataset, the compliance report is a filtered view rather than a separate assembly project. Occupancy, recertification, and inspection metrics map to HUD formats through the data dictionary, so the live operational dashboard and the periodic compliance report share one source of truth and one set of numbers.

Can you build a housing dashboard with Power BI, Tableau, or Yardi?+

Power BI and Tableau build the dashboard view well once the data is clean and joined, but they do not collect resident feedback or resolve one resident across six systems. Yardi and similar property-management tools track units and leases, not resident outcomes. Each is useful for its layer — none produces the clean, linked resident record a housing dashboard depends on.

What is affordable housing business intelligence?+

Affordable housing business intelligence is the practice of using data analysis to decide how to design housing programs, allocate resources, and deliver resident services. It combines property performance data, resident outcome metrics, and qualitative feedback to reveal which programs work, for whom, and why — so program improvement is based on evidence, not on the occupancy rate alone.

How does Sopact build a housing dashboard?+

Sopact assigns one resident ID at intake, then links every assessment, survey, case note, and follow-up to it and reads each one on arrival. Qualitative and quantitative data sit on the same record, so a well-being score shows next to the themes that explain it. The five-domain dashboard and the HUD-compliant report are both filtered views of one connected dataset — no six-system reconciliation, no duplicate preparation.

Related guides

Guides that pair with the housing dashboard.

Bring one dashboard you report on

We'll follow one resident across your systems, on screen.

Sixty minutes with someone who builds these for a living. Bring one housing report or dashboard your team produces today. We follow one resident across the systems that hold her data, trace an outcome to its source, and rebuild one view live. No slideware, no demo accounts — your data, read live.

Bring a dashboard Watch the 3-minute demo

No slideware. No demo accounts. Your own records, read live.

Format

Live walkthrough · 60 min

With

Unmesh Sheth · Founder & CEO

Bring

One housing report or dashboard you produce now

Leave with

One resident journey rebuilt, and a map of where every figure comes from

Housing Dashboard: AI-Native Resident Outcomes

Build a housing dashboard that sees past occupancy.

What is a housing dashboard?

"96% occupied"

"Occupancy and rent roll, refreshed monthly"

"Housing stability, economic mobility, and the resident's own words — every figure traced to the resident."

Why most housing dashboards fail

Occupancy is not an outcome

The "Which Maria?" problem

The resident voice goes unread

Compliance, not learning

Immediate, continuous, and learning — not at the deadline

Read on arrival

One resident, one record

Why it moved, what we changed

A dashboard is only as reliable as the data underneath it

The primary-data approach

Integrating primary + secondary

How to build a housing dashboard, step by step

What a finished housing dashboard looks like

Seven housing dashboards, and the data behind each

Build the view with the AI tools you already have

What AI build tools do well

What they cannot do for you

What it takes to track the resident, not just the unit

Housing dashboards, answered.

Guides that pair with the housing dashboard.

We'll follow one resident across your systems, on screen.

Company

Resources

Agents & Solutions