The 4,600-Application Problem: How One Local Authority Cleared a Social Housing Waitlist in a Week

When we started working with our first Local Authority housing customer, the housing department had a backlog of 4,600 social housing applications waiting for assessment. Some of those applications had been sitting for over six months. The review queue was growing faster than the housing officers could clear it, and the political pressure on each individual case was uncapped.

Eighteen months later that same authority let 500 units in 90 days, with the same staff team. This is the case study, in some detail, because the lessons are useful for every other Local Authority in Ireland in a similar position.

Names are anonymised by agreement. The numbers are real.

The starting point

The authority had three problems running in parallel:

• 4,600 applications, ranging from fully complete to fragments scribbled on a form ten years ago, sitting in a paper-and-PDF mix
• Allocation decisions made one at a time on a unit-by-unit basis, with the corresponding paperwork generated by hand
• A NOAC reporting cycle that depended on manually reconciling housing officer activity against finance records

The pressure point was the new build coming online: 500 units delivered as a single estate, all due to be let within a fixed window. At the existing throughput, that would have taken 12-18 months.

What changed

Three things, in order.

Intake hygiene. Before any allocation work could be parallelised, the application data had to be machine-readable. We onboarded the historical applications in a six-week data-cleaning sprint, with housing officers reviewing only the records that the system flagged as incomplete or contradictory. About 1,200 applications were discharged as duplicate, lapsed or no-longer-eligible. The remaining 3,400 became a clean cohort.

Eligibility automation. Rentalize Select ran the income test, household composition test and disregard rules against each application using the local scheme. The output was a priority order, with reasons. Housing officers reviewed the priority order rather than each application individually.

Allocation as workflow. The allocation of an individual unit, paperwork, lease, RTB registration, rent setup, became a single workflow in Rentalize Core. What was an afternoon of paperwork per unit became a 15-minute confirmation.

What it actually took

The honest answer is that the migration was harder than the eventual operation. The data sanitisation work in the first six weeks was a real lift, requiring close cooperation with the housing officers who knew which ‘this looks like a duplicate’ actually was a duplicate. After that, throughput climbed steadily.

The team did not grow. The technology did the throughput multiplication. The housing officers spent their time on the cases that genuinely required judgement: hardship assessments, complex household compositions, anti-fraud follow-up. The system handled the rest.

The 90-day let

When the 500-unit estate came online, the cohort was already prioritised. Allocations went out in waves of 50 a week, with viewings, lease signings and tenancy starts running in parallel. RTB registration was automatic on tenancy creation. Rent collection through Rentalize Pay was set up at lease signing.

The political pressure shifted from ‘why is the waitlist not moving’ to ‘when is the next batch’. That is the right shift.

What this means for other Local Authorities

The pattern is repeatable. Most Irish Local Authorities have similar starting conditions: a big backlog, a paper-and-PDF mix, a NOAC reporting cycle that consumes too much capacity. The migration cost is the same in shape, scaled to the unit count. The operational gain is the same in shape, scaled to throughput requirements.

If you are a Director of Housing reading this, the conversation we usually have is about phasing: do not try to migrate every legacy file in one go. Start with new applications, run the old cohort in parallel, converge over 6-12 months. The 4,600 number was unusual; the playbook is not.

How Rentalize handles this for you

For Local Authority customers we run the migration as a fixed-scope project: data sanitisation sprint, scheme configuration, parallel run, cutover. Total elapsed time is typically 12-16 weeks. The platform is then the system of record for housing allocation, tenancy management, rent collection and NOAC reporting.

Frequently asked questions

Is the 4,600-application case real?

Yes. Names anonymised by agreement, numbers exact. The starting point and the 90-day let outcome are real.

Did the staff team grow?

No. The same housing officers handled the throughput. The technology absorbed the volume.

How long did the migration take?

Six weeks of data sanitisation, six weeks of parallel run, two weeks of cutover. About 14 weeks total.

What was discharged from the backlog?

About 26% of the original 4,600 were duplicates, lapsed or no longer eligible. The clean cohort was around 3,400.

Does this work for smaller authorities?

Yes. The shape is the same, scaled. A 500-unit authority sees the same proportional gains as a 5,000-unit one.

Can AHBs use the same playbook?

Yes. AHB-specific scheme rules and AHBR audit requirements are configured into the platform.

If you would like to see how Rentalize handles this in practice, you can book a 20-minute walkthrough. We will use one of your own properties as the worked example.