Property management dashboard: occupancy and collections

Your property management dashboard shows a strong leased percentage, but the rent review still has vacant units and unpaid September charges. Signed leases, physical occupancy, billing, and collections describe different records. Keep them separate in the portfolio view, then retain the property-level evidence needed to explain where they disagree.

Start with unit and lease records from your property operating system, charge and payment-application records, and finance-approved reporting definitions. A daily or hourly dashboard can put those inputs into a recurring review. It needs to show the period and cutoff for each measure, since a current occupancy snapshot and a prior-month collections review do not share the same time basis.

Keep property and unit identities behind the portfolio totals

Use an owner or legal-entity scope with the property ID, then map each source property code to that identity. Two managers can use the same building name for different properties, and one property can change its name during a manager handover. Preserve the original source keys so a mapping correction has a reviewable basis.

Unit records need their own property-scoped IDs. A lease renewal and an upcoming replacement lease can both refer to the same unit; counting leases instead of distinct units inflates the leased total. Aggregate unit snapshots separately from charges and payment applications before joining the property summaries, because a unit can have several charge rows and several receipts.

Define the eligible unit inventory with the operations owner. Record approved exclusions, such as units removed from rental inventory, rather than dropping every vacant or down-status unit. For broader definitions, the existing property management KPI scorecard covers eligibility, source references, and owners across operating and financial measures.

Compare leased units, occupied units, and applied collections

This synthetic example uses two properties at October 5, 2026, 23:59:59 America/Chicago. Unit, charge, and payment-application exports complete at 06:00 on October 6. Both properties retain all rental units in the eligible denominator. The figures illustrate reporting choices and arithmetic; they are not customer results.

Occupied units require an actual move-in and no completed move-out at the snapshot. Leased units count distinct eligible units with a signed active or upcoming lease, including occupied units once. Harbor Court has six leased but unoccupied units, and Cedar Square has five. Those commitments can explain future occupancy, but they do not establish that residents were living there on October 5.

Portfolio physical occupancy is (90 + 40) / (100 + 50) = 86.67%. The leased-unit rate is (96 + 45) / 150 = 94%. Keep the eleven-unit gap visible instead of presenting leased units as occupied units. Both results use the same eligible inventory, which allows you to inspect the difference without changing the denominator.

September rent due covers eligible rent charges with due dates from September 1 through September 30. Receipts applied to September include only payments applied to that charge cohort through October 5, net of reversals. The example has no credits, deposits, or fees; those items would need their own approved treatment in a production report.

The collection rate is ($90,000 + $35,000) / ($100,000 + $50,000) = 83.33%. Harbor Court is at 90% and Cedar Square at 70%, but their equal-property average of 80% would give Cedar Square the same weight despite its smaller rent cohort. Add the comparable dollar inputs before dividing, and label any equal-property average as a separate measure.

Download the synthetic property dashboard data for these same property-level inputs and source references. The file contains no resident names, unit numbers, or payment identifiers. Replacing the sample figures requires the same eligibility and application rules, with sensitive charge evidence retained in its restricted source location.

Separate billed rent, applied cash, and the overdue balance

A charge records an amount billed; a receipt records money received; an application records which charge the money paid. A receipt for an earlier balance must not improve September's collection rate. Unapplied cash needs a separate review state until its charge allocation is established, so its presence in the bank does not become evidence that a particular rent cohort was collected.

Unpaid September rent is $150,000 - $125,000 = $25,000. Earlier overdue rent contributes another $23,000, giving a September-and-earlier overdue balance of $48,000 at the October 5 cutoff. Harbor Court contributes $15,000 + $10,000 = $25,000, while Cedar Square contributes $8,000 + $15,000 = $23,000.

Label that balance as September-and-earlier rent, not the full resident-account balance. October charges are outside this review, even if their due dates have passed. A separate current-account delinquency view would include every eligible past-due rent charge through its cutoff. Keep those views identifiable so an October charge cannot change the explanation of September collections.

Retain each included charge's due date, approved credits, applied payments, and remaining balance in the restricted detail. Group aging by the charge due date rather than the property export date. An older balance and an unpaid September charge can add to the same total while requiring different follow-up from the collections owner.

Show freshness and enforce owner and property access

Put the business cutoff and extraction timestamp beside each result. Occupancy in the example is an October 5 snapshot, while collections describe a September charge cohort updated with applications through October 5. A page refresh on October 6 does not make either measure an instant view of October 6 activity.

If Cedar Square's payment feed is stale, show that limitation with its property totals. Keep the last completed snapshot identifiable rather than mixing it into a portfolio rate labeled current. Missing collections are not zero collections, and removing a missing property changes the reporting population. Preserve a coverage indicator and resolve the gap before interpreting the portfolio movement.

Scope access by owner and property before publishing the dashboard. A regional operator may need summaries for both properties, while an outside owner should see only the approved ownership scope. Test direct evidence access as well as the visible filters; hiding a property in a selector does not establish that its records are inaccessible.

Use the separate property management reporting workflow when the review needs a period report with an issued snapshot. The dashboard supports repeated exception review against available inputs; a period report preserves what the reader received at a declared cutoff.

How Permute builds recurring property dashboards

Permute sells connected data and custom reporting software for businesses with fragmented operating and financial records. We combine supplied property exports with accounting and spreadsheet sources, preserve their references, and apply approved property and unit mappings. Renamed properties and conflicting status labels require declared resolution rules rather than matches inferred from a dashboard label.

We encode the agreed occupancy, charge-cohort, and payment-application definitions in reusable reporting logic. A portfolio operator can inspect the property counts behind an occupancy change, while an authorized collections reviewer can inspect the evidence behind an overdue balance. The view uses the available source records and their current permissions; its coverage depends on the sources supplied and configured.

Our real estate reporting work starts with a bounded operating or financial report. Define the owner and property scope, source coverage, and refresh cadence before widening the dashboard. Resident-level evidence should enter only the approved workflow and remain restricted to the people who need it.

Keep resident actions and accounting decisions in their workflows

This dashboard reads source records for management reporting. It does not alter leases, apply payments, issue collection notices, or write changes back to a property operating system. Your operations and finance owners approve eligibility, cohort scope, and account classifications. We are not a forecasting engine and do not choose professional accounting treatments.

Daily or hourly reporting is bounded by source availability and refresh completion. It does not establish instant occupancy, guarantee rent recovery, or replace legal review of resident action. Treat an unresolved charge dispute as a recorded exception (with its owner and supporting evidence), rather than assuming that the dispute removes the charge from every calculation.

A property management dashboard makes occupancy and collections reviewable when each result keeps its population, period, and source evidence. The example separates leased units from occupied units and September collections from older balances. Pooled rates use the combined inputs, while property detail explains which records need attention. You can then investigate vacant leased units and unpaid rent without treating signed commitments or billed charges as completed performance.

Questions about property management dashboards