TSMs Without the Headache: Turning Tenant Satisfaction Measures From an Annual Chore Into a Continuous Insight Stream
Ask anyone who's been through a TSM submission what the hardest part is, and it's rarely the tenant survey itself. It's everything around it — chasing management information from three or four systems, reconciling it against survey responses, checking definitions match what the regulator actually wants, and doing it all against a deadline that always seems to land at the busiest point in the year.
Two data sets, one deadline, and not enough time
Tenant Satisfaction Measures were designed to combine two very different things: what tenants say through perception surveys, and what the organisation's own records show through management information — repairs completed in time, complaints handled, safety checks carried out. On paper, that's a sensible way to balance opinion against evidence. In practice, it means pulling together data that usually lives in separate systems, owned by separate teams, refreshed on separate schedules.
For most providers, that turns TSM reporting into a project rather than a routine task. Someone has to manually extract repairs data, cross-check it against survey timing, reconcile definitions that don't quite line up, and then do it all again next year almost from scratch. It's slow, it's resource-heavy, and worst of all, it only produces a useful picture once a year — long after the moment to act on a dip in satisfaction has passed.
What changes when the data is already connected
A unified data layer doesn't change what TSMs require. It changes how much manual effort sits between your source systems and a submission-ready report. When repairs, complaints, safety and survey data all sit in one searchable environment:
Reconciliation stops being a manual task performed once a year and becomes something that happens continuously, in the background
Management information updates in real time, so a slipping repairs timescale or a rising complaint volume shows up while there's still time to respond, rather than in next year's return
Survey results can be cross-referenced against operational data immediately, revealing not just that satisfaction has dropped, but where and why
Submission becomes a case of pulling an accurate, ready-made report, rather than assembling one from scratch under deadline pressure
That last point matters more than it sounds. When TSM reporting takes weeks of manual reconciliation, most organisations only look closely at the numbers once a year — at submission time. When the same data is available continuously, TSMs stop being a compliance exercise and start being an operational dashboard: a live read on whether services are actually working, updated constantly rather than reconstructed annually.
The real prize isn't easier reporting. It's earlier warning.
The organisations getting the most value from TSMs aren't the ones with the slickest submission process. They're the ones using the same underlying data to spot problems in month three, not month twelve — because by the time a formal TSM return shows satisfaction has fallen, the tenants behind that number have often been unhappy for a long time.
How Connexica can help
Connexica's CXAIR platform brings your repairs, complaints, safety and survey data together into a single, search-based view — removing the manual reconciliation that makes TSM reporting such a headache, and giving you continuous visibility rather than an annual snapshot.
If TSMs still feel like a once-a-year scramble for your organisation, get in touch with Connexica to see how our solutions can turn that scramble into an ongoing insight stream.
