If you manage properties for a community housing provider, you already know: the software options are frustrating. Agency tools like PropertyMe are built for private landlords and real estate agents. Enterprise systems like Chintaro carry price tags that only large providers can justify. And spreadsheets — the fallback for everyone else — silently break as your portfolio grows.
The result is that small and mid-sized CHPs — the organisations doing some of the most important housing work in Australia — are stuck cobbling together tools that were never designed for them.
The problem with “close enough” software
Community housing is not private rental. The compliance obligations are different. The tenant relationships are different. The reporting requirements are different. When you use software built for a different industry, you end up maintaining workarounds for everything the software doesn’t understand:
- VHR compliance — Agency software has no concept of Victorian Housing Register KPMs. You calculate them manually from exported data, every quarter, hoping nothing was missed.
- Centrepay and RTBA bonds — Deduction schedules and bond lodgement are core to community housing but absent from agency platforms. You track them in a separate spreadsheet.
- Income reviews — Rent in community housing is income-based. Agency software assumes market rent. You run the calculation outside the system and manually update the lease.
- Tenant support — Your tenants may have support plans, MARAM screenings, cultural considerations, and NDIS requirements. None of this exists in a rent-collection tool.
- Funder reporting — When your board or funder asks for a report, you pull data from three systems, reconcile it in Excel, and hope the numbers match.
Each workaround costs time. Collectively, they cost weeks every quarter — weeks your team could spend on the work that actually matters.
What “purpose-built” actually means
Purpose-built doesn’t mean a generic system with a community housing label applied. It means the compliance rules, the tenant relationships, and the reporting requirements are in the data model — not in a workaround document.
When software is built for community housing from the ground up:
- VHR KPMs calculate automatically from the tenancy, maintenance, and compliance data you’re already entering. No export-and-calculate step.
- Income-based rent reviews are a workflow, not a workaround. The system tracks review dates, calculates adjustments, and generates the notice.
- Centrepay deductions and RTBA bonds are tracked alongside rent — same ledger, same reconciliation, same reports.
- Tenant support plans, cultural considerations, and accessibility needs sit in the tenant record, not in a separate case-management tool.
- Board and funder reports pull from live data. No reconciliation step, no data migration, no prayer.
The cost of waiting
Every quarter you spend on manual compliance reporting is a quarter you’re not spending on tenant outcomes. Every missed income review is revenue your organisation is entitled to but isn’t collecting. Every inspection done on paper and transcribed later is a duplicated effort and a delayed maintenance response.
The question isn’t whether purpose-built software costs money. It’s whether the workarounds cost more.
What to look for
If you’re evaluating property management software for a community housing provider, here’s a practical checklist:
- Does it calculate VHR KPMs natively? If you have to export data and calculate in a spreadsheet, it’s not built for you.
- Does it handle income-based rent? Market-rent assumptions break community housing workflows.
- Does it track Centrepay and bonds? These are not edge cases — they’re core operations.
- Can your team use it in the field? Inspections happen on-site. If the system only works at a desk, your team is transcribing paper notes.
- Does it handle tenant support alongside tenancy management? Community housing tenants often have complex needs. A system that separates “property” from “person” creates gaps.
- Can you try it before you commit? A system that requires a sales process and a six-month implementation before you see it working is a system that’s optimised for the vendor, not for you.
Chenashe PMS is purpose-built for Australian community housing — VHR compliance, income-based rent, Centrepay, bonds, inspections, tenant support, and funder reporting in one system. Start a free trial — your account comes preloaded with sample data so you can explore properly.