A recent conversation with a social housing resident made me think about how much knowledge we assume people have about their rent accounts.

He pays his rent every month and believed he was paying what was required.

But his rent is charged weekly.

And a calendar month isn’t four weeks.

Take a simple example.

If the weekly rent is £150, paying £600 a month might look right.

£150 × 4 = £600.

But over a standard 52-week rent year, the annual rent is £7,800.

Spread equally across 12 months, that’s £650 a month.

Pay £600 each month and the account will be £600 short by the end of the year, despite the resident making a payment every month and believing he is keeping up.

The exact amount will depend on the tenancy, including whether there are rent-free weeks or an additional rent week in that year.

But the principle doesn’t.

Residents should not need to understand rent-account mathematics to know whether they are paying the right amount.

An arrears balance doesn’t tell us why

There are many reasons why someone might fall into arrears.

Financial hardship. A change in circumstances. Benefit delays. Competing household costs.

But misunderstanding can be one too.

Universal Credit adds another dimension because it is normally paid monthly while many social housing rent accounts are charged weekly.

That can create a predictable rise and fall in the rent balance as weekly charges accumulate before a monthly payment is made. Government research describes this as a ‘saw-tooth’ pattern, where short-term arrears can appear as weekly charges accumulate before the next payment.

Now imagine three residents whose accounts all show £300 in arrears today.

One may have stopped paying.

Another may be maintaining an agreed payment pattern.

Another may simply be paying the wrong monthly equivalent of his weekly rent.

The dashboard could show exactly the same number for all three.

But the reason behind that number, and therefore the appropriate intervention, is completely different.

That’s an important distinction for analysts too.

A metric can be technically correct and still lead you towards the wrong conclusion.

Before building the dashboard, understand the problem

As analysts, it’s easy to start with the data we’ve been given.

Account reference. Current balance. Weekly charge. Payment received. Arrears value.

Then we build measures, create categories and visualise the results.

But the more important questions come before any of that.

  • How is the rent actually charged?
  • How do residents pay?
  • What does an arrears balance represent at different points in the payment cycle?
  • What happens when someone pays monthly against a weekly charge?
  • When should an account genuinely be considered to be deteriorating?
  • And what action is someone expected to take because of the analysis?

You don’t answer those questions by knowing more DAX or writing a better SQL query.

You answer them by understanding the business process that created the data.

That’s the part of analytics I think we sometimes overlook.

The technology matters. But knowing how to manipulate a dataset isn’t the same as understanding what it represents.

The data already exists

Housing providers already hold much of the information needed to understand these differences.

Weekly charges. Payment frequency. Payment dates. Universal Credit cycles. Existing repayment arrangements. Historical account movements.

Bring those things together and the question becomes more useful.

Instead of simply asking:

Who is in arrears?

We can start asking:

Why is this resident in arrears, and what is the most useful intervention?

That could mean identifying residents whose monthly payments consistently fall below their annualised rent.

It could mean recognising predictable payment-cycle movements rather than treating every temporary balance increase as worsening debt.

It could highlight repayment arrangements that are no longer reducing the balance.

Or it could identify automated warning letters being generated shortly before an expected payment.

None of those require a particularly exotic technology stack.

They require us to understand what the data represents.

Turn the balance into something useful

Better analysis should ultimately lead to better communication.

Instead of a resident receiving:

“Your account is in arrears. Please contact us immediately.”

Imagine receiving:

“Your rent is £150 a week. To cover your rent through equal monthly payments, you need to pay £650 a month. You’re currently paying £600, which would leave your account approximately £600 short over a full year.”

Same underlying data.

Completely different information.

The first tells the resident there is a problem.

The second helps them understand the problem and what they can do about it.

That difference matters.

Because the purpose of analysis shouldn’t just be to make the organisation better informed.

It should help the organisation make a better decision or take a better action.

What should good rent data actually do?

Good arrears management isn’t only about identifying who owes money.

It’s about understanding why the balance is moving and intervening before a small, understandable shortfall becomes a much larger problem.

For the resident, a rent account should make three things obvious:

  • What do I owe?
  • What should I pay and when?
  • If I’m behind, what will get me back on track?

For the analyst, I’d add a fourth:

Do I understand what created this number before I report it?

Because if the data is technically correct but the resident cannot understand what they need to do, or the organisation cannot distinguish between different reasons for the same arrears balance, the problem isn’t necessarily the data.

It may be what we’ve done with it.

Sources and further reading