HR owns the retention report, not the retention

In the microfinance company where I head learning and development, infant attrition - people leaving within 90 days of joining - touched 118% before it came down to 53% over the last three quarters of FY2025-26. It raises a question every HR team should sit with: everyone owns the report. Who owns the retention?

What a report can do, and what it cannot

A good report does real work. It shows which region is bleeding, which branch, which month. It puts a hard number in front of people who would otherwise trade in impressions. That matters.

But a report cannot ask a new field officer how he is settling in. It cannot notice that he has gone quiet in week three. The report is a map - and somewhere along the way, head offices start treating the map as the territory. The number gets reviewed, presented, discussed. The discussion starts to feel like action. It is not.

The handover that hurts retention

When HR is seen to own retention, the branch waits. A red number becomes HR's problem, and the fix everyone expects is a programme - a new onboarding design, a new engagement initiative, something with a name and a budget.

Retention is not a programme. As I wrote here last week, a new field officer does not experience "the company"; he experiences one branch, one target sheet, one manager. Keeping him is daily work that happens - or does not happen - in that branch. Belonging is built in small moments, long before it shows up in any retention report.

What HR should actually own

None of this lets HR off the hook. The fix I would argue for: hold the function to three jobs that make retention possible:

1. A number nobody can ignore. Reported fast, in plain language, branch by branch - not a quarterly post-mortem.

2. A name next to every red number. Retention fails anonymously. It starts improving when a specific person is asked: what will you do differently with this month's joiners?

3. A closed loop. When a branch acts, someone follows up and asks what changed. Without the loop, the report is a complaint register.

What HR cannot own is the daily conversation. That belongs to the line. Confusing the two is how you get excellent reports and steady attrition.

The emotion in the report

A red number creates emotion before it creates action - defensiveness in the branch, pressure from head office. The EmoShift lens applies to functions as much as to people: notice the emotion the report creates before choosing the response. A report used to blame produces hidden numbers. A report used to help produces honest ones.

Did our report bring the number down? I cannot prove one cause - retention is never one thing. What I believe is this: a report matters most when it starts conversations in branches, not when it ends them in head office.

One question for you

In your organisation, who owns retention - and does the person who owns the report know the difference? I would like to hear.