The 11-Step Playbook
Step-by-step guide to fixing data consistency across platforms
A repeatable operating model: define the metric, identify the source system, map the data, standardize the calculation, validate the report, document the rules, and monitor exceptions over time.
01
Start with the business question, not the dashboard
Before building or fixing a dashboard, define the decision the metric is supposed to support. This prevents teams from creating dashboards full of metrics that look useful but do not answer the real operating question.
| Business question | Required metric |
|---|
| Is leasing performance improving? | Leased percentage, net new leases, traffic-to-lease conversion |
| Is revenue quality improving? | Effective rent, concessions, bad debt, delinquency |
| Is the property losing NOI to operations? | Expense variance, controllable expenses, R&M, utilities, payroll |
| Is the manager executing turns efficiently? | Days vacant, make-ready time, turn cost, vacant-ready count |
| Is the portfolio outperforming peers? | Benchmarked rents, occupancy, expenses, NOI, renewal performance |
Best practiceEvery dashboard tile should connect to a business decision.
02
Create a portfolio metric dictionary
A portfolio metric dictionary is the foundation of data consistency across platforms. For each KPI, define metric name, business definition, calculation formula, source system, source table or extract, required fields, timing rule, inclusion and exclusion rules, responsible owner, validation method, and known exceptions.
Example: physical occupancy
| Field | Definition |
|---|
| Metric name | Physical occupancy |
| Business definition | Percentage of rentable units physically occupied as of the reporting date |
| Formula | Occupied rentable units ÷ total rentable units |
| Timing rule | Month-end snapshot |
| Exclusions | Non-rentable units, admin units, model units if classified as non-rentable |
| Validation | Compare occupied unit count to PMS rent roll |
| Owner | Asset management / operations |
Operating principleThe dictionary should be treated as a living operating document, not a one-time implementation artifact.
03
Separate raw source data from standardized reporting data
A common mistake is building dashboards directly from raw PMS exports. A better structure has three layers — raw, standardized, and reporting — that protect the original data while making reporting consistent.
Raw data layer
- Raw rent roll
- Raw lease table
- Raw unit table
- Raw resident ledger
- Raw GL transactions
- Raw work orders
- Raw marketing source data
Standardized data layer
- Standard unit status
- Standard lease status
- Standard occupancy category
- Standard financial category
- Standard concession type
- Standard work order category
- Standard property hierarchy
Reporting layer
- Portfolio dashboard
- Investor report
- Regional manager dashboard
- Property scorecard
- Budget variance dashboard
- Asset management report
04
Map each PMS to a common data model
Real estate data integration becomes scalable when each PMS maps into a common data model. For multifamily, the core entities usually include property, unit, lease, rent roll, financials, work orders, leads, renewals, and occupancy — each with a defined set of common fields.
| Entity | Common fields |
|---|
| Property | Property name, code, address, market, submarket, unit count, owner, manager |
| Unit | Unit number, floorplan, bedroom count, square footage, unit status, market rent |
| Lease | Lease start, lease end, move-in, move-out, resident status, lease status, rent |
| Rent roll | As-of date, unit, resident, rent, balance, status, lease dates |
| Financials | GL account, amount, property, period, budget, actual, accrual/cash basis |
| Work orders | Open date, completion date, category, priority, cost, status |
| Leads | Lead source, traffic date, tour date, application date, lease date |
| Renewals | Expiration date, offer date, signed date, effective date, rent change |
05
Standardize unit status and occupancy definitions
Occupancy is the most over-reported and under-defined metric in multifamily. Standardizing unit status lets dashboards calculate occupancy, exposure, availability, and vacancy consistently across platforms.
Standard unit statuses
- Occupied — physically occupied
- Occupied on notice — occupied but resident has given notice
- Vacant ready — vacant and available to lease
- Vacant not ready — vacant but not yet ready
- Leased not occupied — signed lease, no move-in yet
- Down unit — offline, excluded or separately tracked
- Model / Admin / Non-rentable — excluded from rentable inventory
Common occupancy metric definitions
| Metric | Formula |
|---|
| Physical occupancy | Occupied rentable units ÷ total rentable units |
| Leased percentage | Leased rentable units ÷ total rentable units |
| Exposure | Vacant units + units on notice not preleased |
| Availability | Vacant ready + vacant not ready + notice units available to lease |
| Vacant ready percentage | Vacant ready units ÷ total rentable units |
The pointThe goal is not choosing the only possible definition. It is choosing the standard definition and applying it consistently.
06
Normalize financial data and chart of accounts
For portfolio-level NOI reporting, financial normalization is essential. Map each property’s chart of accounts into a standard reporting hierarchy. Once accounts are mapped, rental portfolio analytics can compare performance across properties even when source accounting systems differ.
Standard income categories
- Gross potential rent
- Loss to lease
- Concessions
- Vacancy loss
- Bad debt
- Other income
- Effective gross income
Standard expense categories
- Payroll
- Repairs and maintenance
- Turn costs
- Utilities
- Contract services
- Marketing
- Administrative
- Management fees
- Taxes and insurance
- Controllable vs non-controllable splits
07
Establish timing rules for every report
A trustworthy dashboard must answer: “As of when?” Timing rules should be defined for every metric.
| Metric type | Recommended timing rule |
|---|
| Rent roll | Month-end snapshot or daily snapshot |
| Occupancy | As-of date snapshot |
| Financials | Closed accounting period |
| Delinquency | As-of date balance |
| Work orders | Opened/completed during selected period |
| Leasing | Activity date during selected period |
| Renewals | Expiration month and signed date tracked separately |
| Budget variance | Actuals through closed period only |
Common timing issueA rent roll pulled April 30 and again May 3 may differ because corrections, move-outs, transfers, payments, or status updates were posted after the original snapshot. The fix is to store snapshots and label them clearly: “April month-end snapshot,” “April final close snapshot,” “Current live rent roll.”
08
Reconcile dashboard outputs to source-system reports
Validation is where trust is built. Every new dashboard should be reconciled against source-system reports before it is released. Validation should identify whether differences are caused by mapping error, timing difference, source-system configuration, exclusion rule, manual adjustment, report filter, data extraction issue, or dashboard calculation error.
Recommended validation checklist
- Unit count matches rent roll or property setup
- Occupied count matches PMS occupancy report
- Vacant count — vacant-ready and vacant-not-ready mapped correctly
- Scheduled rent matches rent roll scheduled charges
- Resident balance matches aged receivables
- Actual income matches the income statement
- Operating expenses reconcile to the GL
- NOI reconciles to source financials after mapping
- Budget variance — versions and periods aligned
- Leasing activity matches source reports
09
Build exception reporting into the process
Data consistency does not mean every number will match perfectly every time. It means differences are identified, explained, and resolved through a repeatable process.
| Exception | Why it matters | Action |
|---|
| Unmapped GL account | Expense category may be understated | Map account to standard category |
| Missing rent roll snapshot | Occupancy dashboard may be incomplete | Request or reload source file |
| Unit count changed | Occupancy denominator may be wrong | Confirm property setup change |
| Large delinquency swing | May be real or caused by timing | Validate against aged receivables |
| Unknown unit status | Vacancy metrics may be wrong | Add status to mapping table |
The shiftException reporting turns data quality from a monthly fire drill into a managed workflow.
10
Create dashboard certification rules
Before a dashboard is used in executive or investor reporting, it should be certified. A certified dashboard should meet a clear set of standards — especially important when onsite, regional, asset management, accounting, and executive teams all use the same dashboard for different decisions.
Certification standards
- Metric definitions are documented
- Source systems are identified
- Mapping logic is approved
- Timing rules are clear
- Reports reconcile to source-system totals
- Exceptions are documented
- Data refresh schedule is known
- Users understand the intended use case
- Ownership is assigned for ongoing maintenance
11
Document ownership and governance
Every key metric needs an owner. Ownership of unit status, rent roll, financials, GL mapping, leasing activity, renewal metrics, work orders, marketing sources, dashboard logic, and investor reporting should be assigned and documented.
| Data area | Recommended owner |
|---|
| Unit status | Operations |
| Rent roll | Operations / asset management |
| Financials | Accounting / asset management |
| GL mapping | Accounting |
| Leasing activity | Operations / marketing |
| Renewal metrics | Operations / asset management |
| Work orders | Maintenance / operations |
| Marketing sources | Marketing |
| Dashboard logic | Data / BI team |
| Investor reporting | Asset management / ownership |