Jeremy T., a partner at Argo Property Group, wanted 4 numbers out of his property management system (PMS): "rent collection status, OpEx budget tracking, cash-on-cash return, and tenant retention status." To see them, he had to memorize "a script of click-throughs that felt like a never-ending wiki site," as he wrote in a LinkedIn post.
At a U.S. residential community, building the reports by hand would take the front desk team "like six hours a week," so the person in charge built a Gemini bot to do it. She's a Communications and Creative Services Manager, and she told me in September 2026: "I can't pull custom reports in a way that actually works for our team here."
In both cases the PMS had every number. Neither had a property management dashboard that put them in one place.
That gap is why operators search for a property management dashboard. Whether anyone trusts that dashboard depends on writing down, for each number, where it comes from and who fixes it when it's wrong.
TL;DR: A property management dashboard earns its keep when every number on it answers a recurring decision and traces to one source. AI makes the screen cheap to build. Before you build it, write a "number card" for each metric: the decision it supports, the source system, how often it refreshes, which source wins when 2 systems disagree, and who owns the mismatch.
- A property management dashboard is a set of recurring decisions
- Your PMS holds the numbers in 5 different places
- The screen is now the cheap part
- Write a number card before you build a chart
- Decide which source wins before 2 systems disagree
- Report builder, BI tool, or a custom data layer
- Keep the PMS, build the layer
- Start with one report you build by hand
- FAQ
A property management dashboard is a set of recurring decisions
A property management dashboard is one screen that shows the numbers an owner or manager acts on every week or month, pulled from the systems where those numbers live. Each tile should answer a decision you make again and again: which tenants to call about rent this week, whether to approve the next work order, which leases get a renewal offer 90 days out.
Most dashboard guides start with a list of key performance indicators (KPIs): occupancy, delinquency, net operating income, turnover. A KPI with no decision attached is a number someone looks at and closes.
Owners and residents ask for different things from the same PMS, so start from the person who acts on the screen. An asset manager deciding whether to refinance needs different tiles from a leasing manager deciding which unit to show first. Our app on top of C.I.A. Services' own system serves 3 groups: owners, board members, and employees.
Your PMS holds the numbers in 5 different places
The data for one report sits in more than one place. Take a monthly owner pack, which draws on 5 sources:
- Rent roll and receipts: in the PMS ledger
- Operating expenses (OpEx): in the general ledger, coded by whoever entered the invoice
- Bank deposits: in the bank feed, a day or more behind the ledger
- Maintenance: in a work order tool, sometimes a separate vendor
- Budget and investor equity: in a spreadsheet the owner keeps
For a fintech advisory SaaS client, a KPI report fed from an accounting integration stalled on one gap: no map from each KPI to a field in the accounting tool. Until that map existed, there was no way to confirm the calculations were correct.
Commercial real estate leaders plan to spend here. In Deloitte's 2025 commercial real estate outlook, 81% of more than 880 executives across 13 countries named data and technology as the area they were most likely to focus spending, as Facilities Dive reported. Data spending is one of the proptech trends for 2026 our proptech development team tracks.
The screen is now the cheap part
If you think you could build a dashboard yourself with AI, you're probably right. A chart on top of a PMS export takes an afternoon now, and in our piece on whether property managers should build their own software I put portfolio dashboards in the "build it yourself" column.
The people closest to the data draw the line in the same spot. Rob Teel, CEO of Yardi, said in an interview that as a client he'd be vibe coding pieces specific to his company, and added: "I would not want to vibe code a new financial report." Alik Levin, who works in property management and built his own interface with Claude on top of a commercial platform, wrote under Jeremy's post: "The data integrity part is never solved."
Both are talking about the numbers. A wrong chart color gets fixed the same day. A cash-on-cash return that quietly counts a refinance as income can sit on an investor update for a quarter.
Write a number card before you build a chart
A number card is a 5-line definition for one metric, written before anyone designs a tile. If you can't fill all 5 lines, the metric isn't ready for a dashboard. The lines:
- Decision: what you do differently when this number moves
- Source: the system and the field it comes from
- Refresh: how often it updates, and when it counts as final
- Which source wins: the rule when 2 systems show different values
- Owner of a mismatch: the person who investigates and corrects it
Here are cards for the 4 numbers Jeremy wanted on one screen: "rent collection status, OpEx budget tracking, cash-on-cash return, and tenant retention status." The answers below are a starting point. Yours depend on how your books are set up.
| Metric | Decision | Source | Refresh | Which source wins | Owner of a mismatch |
|---|---|---|---|---|---|
| Rent collection | Which tenants to call this week | PMS receipts | Daily | Bank deposit, once it clears | Accounting |
| OpEx against budget | Approve or hold the next work order | General ledger and the budget sheet | Weekly, final at month close | The closed month in the ledger | Controller |
| Cash-on-cash return | Hold, refinance, or sell | Ledger cash flow and investor equity records | Monthly, after close | Investor records for equity | Asset manager |
| Tenant retention | Which leases get a renewal offer | Lease records in the PMS | Weekly | The signed lease | Leasing manager |
[IMAGE 1: media/property-management-dashboard--number-card.png | alt: A number card for rent collection showing the decision, source, refresh, which source wins, and the owner of a mismatch]
The cards also expose definitions that were never written down. Does a tenant who moves to a bigger unit in the same building count as retained, and does a security deposit applied to rent count as collected? Decide once, write it on the card, and every tile built from it agrees.
Decide which source wins before 2 systems disagree
Two systems will disagree. Decide in advance what the dashboard does when they do.
We built this for a logistics and fintech client, a U.S. mail-haul trucking contractor that needed to catch underpayments and overpayments too hard to spot by hand. Their numbers came from 5 kinds of files: loads, rates, a fuel matrix, payments, and vouchers. The product calculates what each trip should have paid, compares it with what was paid, and labels every trip cleared, minimal, underpaid, overpaid, or error.
The rule that made it work fits on one line: a manual final value beats an imported one, and an imported one beats a calculated one. Staff can lock a value, and every change is logged with who made it. The hard cases (backdated rate changes, duplicate loads, one voucher covering 2 or more trips) were settled in 2 workshops with the client.
Rent rolls, ledgers, and bank feeds disagree the same way loads and payments do.
Report builder, BI tool, or a custom data layer
You have 3 ways to get the numbers on one screen: your PMS report builder, a business intelligence (BI) tool, or a custom data layer over your PMS's API (the connection it offers so other software can read its data). The right one depends on how many sources a single number needs.
| Option | Good for | Breaks when | Who maintains it |
|---|---|---|---|
| Report builder in your PMS | Numbers that live entirely inside the PMS | A number needs the bank feed, a budget sheet, or a second system | The PMS vendor |
| BI tool on exports | A few sources, refreshed weekly or monthly | Someone has to export, clean, and upload files by hand every cycle | Whoever runs the exports |
| Custom data layer over the API | 3 or more sources, daily refresh, rules for which source wins | Your PMS plan gives you no API access | An engineer, yours or ours |
A data layer is a small database that pulls from each source on a schedule, applies the number-card rules, and feeds the dashboard. It's the part of the build that holds the definitions, so the screen on top can stay simple.
Check whether your PMS plan includes API access before anyone quotes a build. If it doesn't, exports are your only source.
If your portfolio is under about 100 units, the reports your PMS already has plus one spreadsheet are usually enough. I gave similar advice to a villa manager with about 23 villas who asked about a custom PMS: off-the-shelf software was enough.
Keep the PMS, build the layer
Rob Teel's advice to Yardi's own clients: "Buy the platform, build the fringe." A dashboard is the fringe. The ledger, payments, and lease records stay in the PMS, and the dashboard reads them.
We've done this on a system we didn't write. C.I.A. Services has managed community associations since 1984 and runs over 150 of them on software it wrote itself.
Before the app, owners got invoices and payment plans "by mail, email, or fax." We built an owner, board, and employee app as a progressive web app on top of that system, and the system stayed in place as the source of record.
We haven't yet built a dashboard on the Yardi, AppFolio, or Buildium API, so on those platforms the first step is checking what your plan's API exposes. That's the shape of our application modernization work: a rebuild that fixes what has to be correct and leaves the rest alone.
Start with one report you build by hand
Pick the report your team rebuilds most often, the monthly owner pack or the Monday delinquency list. Then:
- List every number on it.
- Write a number card for each one.
- Mark every step someone does by hand: an export, a copy-paste, a formula fixed in a spreadsheet.
- Count the sources. One source means your PMS report builder may be enough. Three or more with a daily refresh means a data layer.
If you'd rather not do it alone, send us that one report. We'll map where each number comes from, write the cards with you, and quote the layer that produces it, at a fixed price for that one report.
FAQ
What should a property management dashboard show? A dashboard should show the numbers you act on every week or month, each tied to a decision. For most rental portfolios that starts with rent collection, operating expenses against budget, occupancy, and tenant retention. Owners reporting to investors add cash-on-cash return or net operating income.
Can AppFolio, Yardi, or Buildium build these dashboards for me? Your PMS can build part of it. Built-in report builders handle numbers that live entirely inside the PMS. Once a number needs the bank feed, a budget spreadsheet, or a second system, you need exports into a BI tool or a data layer over the API, so check whether your plan includes API access.
How long does a custom property management dashboard take to build? The screen takes the least time. The estimate depends on how many sources each number draws from and how many mismatch rules you need, so map one report first and price from that.
Is a custom dashboard worth it for a small portfolio? Under about 100 units, it usually isn't. Your PMS reports plus one well-kept spreadsheet cover most decisions at that size.
How often should a portfolio dashboard refresh? Refresh each number as often as the decision it supports: rent collection daily, expenses weekly with a final figure at month close, and returns monthly. Refreshing faster than the decision adds cost and no new information.