PROPERTY
PERPETUITY
Log inSign up

Property · Originally published

Social housing software: test the resident journey first

A procurement checklist focused on repairs, complaints and usable records rather than unsupported product rankings.

Property Perpetuity editorial illustration for “Social housing software: test the resident journey first”
Illustrative artwork · Property Perpetuity

Sign in to save this for later →

Choosing social housing software is an operational decision with consequences for residents and staff. A successful demonstration should show how a concern reaches the right person and stays visible until it is resolved. This archive guide was revised on 16 October 2026 to replace unsubstantiated best-product claims with a practical assessment process.

Follow one repair from report to resolution

Create an invented demonstration case involving a resident reporting a recurring problem. Ask the supplier to record the initial contact, identify previous reports, assign responsibility and show the next appointment. Then change the appointment and check whether both the resident-facing record and the staff task update.

MRI’s UK social housing offering describes housing and tenancy management, finance, asset and repairs functions. That breadth is useful to explore during procurement, but a list of modules is not evidence that your particular processes are configured correctly or that residents will receive a better service.

Make unresolved issues visible

Test what happens when a contractor marks a job complete but the resident says the problem remains. Ask whether staff can reopen the case without losing the earlier history. Check how photographs, correspondence and follow-up actions are connected, and whether colleagues can distinguish a complaint from the underlying repair request.

Include staff who handle telephone calls and face-to-face contact in the trial. Residents who cannot or do not wish to use a portal still need a workable route into the same service. Ask users to find the next promised action without assistance from the demonstrator.

Set acceptance criteria before migration

Write down the reports and checks that must work before the new system becomes the operational record. Reconcile a sample of open cases, appointments and contact preferences after import. Agree how errors will be corrected and who can authorise closure.

Evaluate support arrangements, accessibility, permission controls and the ability to export records alongside subscription costs. Keep the assessment focused on demonstrable outcomes. A system should help staff understand what a resident needs, what has already happened and who is accountable for the next step.

Reference source ↗