Choosing a Housing Management System
A vendor-neutral guide for social landlords: what to ask vendors, what to watch for, and how to run an evaluation you can defend to your board and your regulator.
Who this guide is for
This guide is for housing associations, local authorities and ALMOs that are replacing, or thinking about replacing, their housing management system (HMS). It is written for the people who will live with the decision: heads of housing, IT and digital leads, asset and repairs managers, finance, and the programme team that has to make it work.
It is vendor-neutral by design. Use the questions with every supplier on your shortlist — including us.
- 5–8clear outcomes to agree before you go to market
- 10areas a modern HMS should cover
- 18questions to put to every vendor
- 7 yearsthe horizon for judging total cost
1. Why landlords are replacing their HMS now
Most housing management systems in use today were bought for a different era: one where the main job was to collect rent and log repairs. The job has changed.
Regulation
The consumer standards, Tenant Satisfaction Measures and proactive inspections mean you must evidence what happened, when, and who knew — not just record it.
Awaab’s Law
Statutory clocks for damp, mould and other hazards run from the moment you become aware of an issue. Evidence has to be complete and time-stamped.
Building safety
The golden thread requires accurate, accessible information about higher-risk buildings across their life.
Residents
People expect to report, track and get updates online, at any hour, without repeating themselves.
Cost and risk
Ageing on-premise systems, end-of-support versions, bolt-on modules and manual workarounds all carry hidden cost and operational risk.
If several of these apply to you, the question is no longer whether to change, but how to change safely.
2. Signs your current system is holding you back
- Staff keep spreadsheets alongside the system because it cannot hold what they need.
- The same resident or property exists in several systems, and nobody is sure which is right.
- Reports for the board or regulator take days of manual work to assemble.
- Simple changes — a new case type, a new letter, a new field — need a supplier change request and months of waiting.
- Contractors work outside the system and update it late, or not at all.
- You cannot easily show a complete timeline for a complaint, a disrepair case or a damp and mould report.
- Your current contract, hosting or version is approaching end of life.
3. Before you go to market: get your own house in order
The most common reason HMS projects fail is not the software. It is starting the procurement before the organisation has agreed what it needs.
Agree the outcomes
Write down five to eight outcomes the new system must deliver, in plain language and with a measure — for example, “every damp and mould report has an owner and a due date within one working day”.
Map your processes as they really are
Document how tenancy, repairs, voids, income, compliance and complaints actually work today, including the workarounds. This is what vendors should demonstrate against.
Understand your data
Profile volumes, duplicates, gaps and which system is the master for each item. Starting the clean-up before you sign is the most effective way to shorten the programme.
Name the people
Appoint a senior sponsor, a product owner who can make day-to-day decisions, and representatives from each service area — and budget their time.
4. What a modern HMS should cover
Use this as a checklist when scoping. Not every landlord needs every area on day one, but your platform should be able to grow into them without a second procurement.
Tenancy and households
One record from application and offer through to termination, including household members, vulnerabilities and communication needs.
Repairs and maintenance
Self-service reporting, diagnosis, scheduling, contractor portals and live status for residents.
Voids and lettings
Tracked void journeys with clear handoffs and re-let times visible.
Asset management and stock condition
Component-level data, surveys on mobile devices, and long-term investment planning.
Compliance and building safety
Gas, electrical, fire, asbestos, water and lifts tracked to the property and component, with evidence attached.
Case management
Complaints, ASB, disrepair, damp and mould and safeguarding with owners, timescales and an audit trail — configured, not custom-built.
Income, rent and service charges
Accounts, arrears, payment plans and service charge apportionment and reconciliation.
Resident portal
Residents can report, pay, book, track and update their details.
Reporting and analytics
TSM, regulatory and board reporting from live data, not exported spreadsheets.
Integration
Open APIs to finance, CRM, document management, telephony and contractor systems.
5. Questions to ask every vendor
Put the same questions to every supplier, in writing and in the demonstration, and compare the answers side by side.
Fit and flexibility
- Show us how you would configure a new case type. Who does it, and how long does it take?
- What can our own team change without a developer or a change request?
- How do you handle processes that differ between our regions or subsidiaries?
Data and migration
- Who does the data migration, and what is included in the price?
- How many trial loads do you complete, and how is reconciliation evidenced?
- What happens to historic data we choose not to migrate?
Compliance and evidence
- Show us the complete audit trail for a damp and mould case, from first contact to closure.
- How do you support Awaab’s Law timescales and evidence?
- How do you produce Tenant Satisfaction Measures and other regulatory returns?
Technology and security
- Where is the system hosted, and who is responsible for upgrades?
- Which security accreditations do you hold (for example ISO 27001, Cyber Essentials Plus)?
- What APIs are available, and are they documented and included in the licence?
Delivery and support
- Who will actually do the work? Can we meet the delivery team, not just the sales team?
- Show us a realistic plan for an organisation of our size, with dates.
- What does support look like after go-live — hours, response times and escalation?
Commercials
- What is the total cost over seven years, including licences, hosting, support, upgrades and integrations?
- What costs extra — modules, users, environments, API calls, reports?
- What are the exit terms, and in what format will we get our data back?
6. Red flags to watch for
Each of these is common, and each is a warning sign. Here is what a better answer looks like.
| Red flag | What good looks like |
|---|---|
| Demonstrations that follow the vendor’s script. | The vendor demonstrates your scenarios, using your process maps. |
| “That’s on the roadmap” for things you need on day one. | It works today, and they will show you a customer using it. |
| Every change is a chargeable development. | Most changes are configuration your own team can make. |
| Vague migration plans, or migration priced as time and materials. | A fixed migration scope with trial loads and formal reconciliation. |
| No comparable references, or references you can’t speak to alone. | Landlords like you, who you can call without the vendor on the line. |
| Licence models that penalise growth, users or new modules. | Clear pricing that scales predictably as you grow. |
7. Running the evaluation
A structured, evidence-based evaluation is easier to run — and far easier to defend to your board and your regulator.
Long list to short list
Use a short written questionnaire based on your outcomes, not a 1,000-line requirements matrix.
Scripted demonstrations
Give each shortlisted vendor the same three or four real scenarios from your process maps, and score them against the same criteria.
Hands-on time
Ask for a sandbox where your own staff can try key tasks.
Reference calls and visits
Speak to landlords who went live in the last two years, and ask what they would do differently.
Weighted scoring
Agree weights in advance — functionality, delivery approach, seven-year cost, supplier viability — and record the reasons for each score.
8. Planning a safe migration
Most of a migration is agreeing what the data means, not moving it. Plan for that.
Phase the rollout
Where you can, so each go-live is smaller and risk is easier to manage.
Run trial loads
Several trial data loads, with formal reconciliation, before the final cut-over.
Plan the cut-over
A clear cut-over plan, with a rollback position agreed in advance.
Train on real work
Train people on their real processes, not generic features, close to go-live.
Plan hypercare
Extra support for the first weeks after each go-live.
Data migration is usually the longest and riskiest part of an HMS replacement. Start the clean-up before you sign anything.
9. Questions to answer before you sign
- Can we describe, in one paragraph, why this platform and this partner?
- Do we have a signed-off plan with dates, roles and our own resource committed?
- Is the full seven-year cost understood and approved?
- Have we spoken to at least two reference customers on our own?
- Is our data clean-up already under way?
How Neo Technology can help
Neo Technology works with housing providers to replace legacy housing management systems with Propsys360, a single platform covering tenancy, repairs, assets, compliance, income and case management. We carry out the data migration ourselves and configure the platform to how you work.
What housing providers say
Named people at named organisations, in their own published words.
“We realised that we had a gap around the golden thread of data, in terms of the availability and accessibility of the data we held in seventeen different systems… That meant colleagues could immediately see all non-compliant properties.”
Jake Le Page Head of Building Safety Regulations Notting Hill Genesis
“Neo brought strong Dynamics 365 expertise, worked collaboratively with our internal teams and applied Microsoft best practice within a live operational environment… We would be pleased to recommend them as a Microsoft Dynamics 365 partner within the housing sector.”
Wayne Human Head of IT Change Sage Homes
“The successful deployment of this solution has significantly increased transparency and improved the operational efficiency of our contact centre, allowing us to deliver greater value to our customers.”
Philip Wragg Infrastructure Programme Manager
“The Neo Technology model allows us to scale our development capacity, accelerating our transformation programmes while future-proofing our business, while achieving substantial industry cost savings.”
Group CIO Notting Hill Genesis
Related proof
Planning an HMS replacement?
Thirty minutes, walked through by the people who deliver it. Bring your shortlist and your questions.