Reporting and Analytics for Lettings: A Guide for Agents
Monday morning in lettings often looks the same. One applicant is waiting on an employer reference, another still hasn't uploaded ID, a landlord wants an update, and your negotiator is trying to work out whether a deal is moving or drifting towards collapse. The information exists, but it's scattered across inboxes, call notes, spreadsheets and memory.
That's where most agencies get stuck. They don't have a referencing problem so much as a visibility problem. People are working hard, but nobody can see the full picture quickly enough to intervene at the right moment.
That's why reporting and analytics matter in day-to-day lettings. Not as a boardroom concept, and not as another admin layer. They matter because they help you spot stalled applications earlier, reduce avoidable chasing, and make cleaner decisions about applicants, workload and compliance. If your team is still piecing updates together by hand, the process is already costing you time and probably placements too.
This shift is bigger than the lettings sector. The UK data economy generated £343 billion in gross value added in 2023, according to the UK government's data and AI opportunities mapping, which underlines that data work now sits at the centre of modern business rather than at the edges (UK data economy overview). For agents reviewing tools built around that reality, passref for letting agents is one example of how referencing has moved from manual chasing into live operational tracking.
Beyond the Spreadsheet An Introduction for Letting Agents
The old way of running references depends on individual effort. A negotiator remembers to chase an employer. Someone else rings a previous landlord. Another colleague updates a spreadsheet if they get a spare minute. It works, until volume rises or a key person is off sick.
Then the cracks show.
A tenancy can look fine on the surface, but underneath it's sitting still because one check hasn't moved for hours. If nobody spots that delay early, the applicant gets frustrated, the landlord loses confidence, and your team ends up firefighting instead of progressing the let.
What the spreadsheet never shows properly
A spreadsheet can tell you that a case is open. It rarely tells you enough about why it's still open, what needs attention first, or which delays are becoming risky. That's the gap between recording activity and managing performance.
In practice, agents need a clearer operational view:
- Live status visibility so the team can see which cases are moving and which are stalled
- Shared ownership so updates don't live with one person's inbox or notebook
- Early warning signs that flag avoidable delays before they become fall-throughs
- A cleaner audit trail for identity, right to rent and screening activity
Practical rule: If your team has to ask three people for a status update, you don't have reporting. You have reconstruction.
Why this matters commercially
Lettings margins are shaped by speed and certainty. A faster, cleaner pre-tenancy process protects income because it shortens the gap between offer and move-in, and it cuts the number of deals that drift off due to poor follow-up. Landlords notice it as well. They may never ask about your analytics setup, but they do care whether you keep tenancies moving.
Good reporting also changes management behaviour. Instead of asking, “Has anyone chased this?” you can ask, “Which step is causing delay across the pipeline?” That's a better question, and it leads to better action.
For agents and landlords, the point is simple. Data only becomes useful when it helps you protect a tenancy that might otherwise be lost.
Reporting vs Analytics What Agents Need to Know
Most confusion starts because people use the two terms as if they mean the same thing. They don't.
Reporting tells you what has happened or what is happening now. Analytics helps you understand why it's happening and what to do next.
The simplest way to think about it
Use the car analogy. Reporting is your dashboard. It shows speed, fuel and warning lights. Analytics is what happens when a mechanic connects the diagnostic tool and works out why the warning light came on.
In lettings terms, reporting might show:
- How many references are in progress
- Which cases are complete
- How long cases are taking
- Where applications are sitting right now
Analytics goes further:
- Which stage causes the longest delay
- Whether delays are linked to manual chasing
- Whether certain applicant types need more intervention
- Whether one branch or team member has a process bottleneck
The operational difference inside a lettings business
If your report says turnaround time is slipping, that's useful but incomplete. You know there's a problem, but not what to fix. Analytics is what lets you break that delay apart and see whether it comes from slow employer replies, incomplete applicant uploads or slow internal follow-up.
That distinction matters because the remedy changes depending on the cause. If applicants are slow to upload documents, you need better prompts and clearer requests. If employer replies are holding things up, you need automated chasing and less dependence on phone calls. If your own team is the bottleneck, the issue is workflow, not applicant quality.
The strongest approach is to layer the second on top of the first. As noted in a technical explanation of the four levels of analytics, the most useful insight comes from combining descriptive reporting with diagnostic analysis by joining workflow timestamps and applicant history so delays can be traced back to their real cause.
Reporting without analytics gives you a queue. Analytics tells you which part of the queue needs changing.
What doesn't work
Three habits usually create noise instead of clarity:
-
Over-reporting everything
Teams collect dozens of figures and still can't answer basic operational questions. -
Looking only at monthly summaries
By the time a monthly report shows a problem, the tenancy may already be gone. -
Treating all delays as equal
They're not. A missing payslip needs a different response from an unreturned landlord reference.
Once agents understand that split, reporting and analytics stop sounding technical. They become a practical way to manage progression.
Key Referencing Metrics Every Agent Should Track
Most agencies track too little or the wrong things. They know how many lets they've agreed, but they can't easily see what's happening between offer accepted and tenancy secured. That's the expensive blind spot.
A useful referencing dashboard doesn't need endless KPIs. It needs the few measures that tell you whether deals are moving, stalling or becoming risky.
The core metrics worth tracking
The table below covers the measures that usually reveal the health of a referencing process fastest.
| Metric | What It Measures | Why It's Important |
|---|---|---|
| Turnaround time | How long a reference takes from submission to decision | Shows whether your process is fast enough to keep applicants and landlords engaged |
| Status by stage | Where each application currently sits in the workflow | Helps the team spot stalled cases before they go cold |
| Pass, Conditional, or Refer outcome | The final recommendation on each applicant | Gives a practical view of applicant quality and decision patterns |
| Source of delay | Which task or party is holding progress up | Points directly to the process issue that needs fixing |
| Applicant completion speed | How quickly applicants provide documents and answers | Reveals whether delays start with communication and document collection |
| Employer response timing | How quickly employment checks come back | Shows whether manual chasing is dragging cases out |
| Previous landlord response timing | How quickly landlord references are returned | Helps identify common hold-ups in the chain |
| Fall-through rate after offer | How many agreed tenancies fail before move-in | Connects referencing performance to lost revenue and landlord dissatisfaction |
| Compliance completion status | Whether identity, screening and right to rent checks are complete | Reduces the risk of progressing a tenancy with missing compliance steps |
| Team workload by case volume | How many live references each negotiator or branch is handling | Helps managers rebalance work before service standards slip |
What each metric tells you in practice
Turnaround time is the headline number because it affects everything else. If cases take too long, applicants start looking elsewhere and landlords start asking uncomfortable questions.
Status by stage is often more useful day to day than a final summary report. It tells you whether a case is waiting on the applicant, employer, landlord or internal review. That lets your team prioritise properly instead of chasing every case in the same way.
Pass, Conditional, or Refer outcome gives managers a cleaner view of application quality. If a branch is seeing a high volume of conditional outcomes, that may point to affordability issues, poor pre-qualification or inconsistent instructions before the application starts.
For agencies comparing digital workflows, this becomes easier to manage when the process runs through dedicated reference check software rather than a mix of calls, inboxes and ad hoc notes.
The metric many agents overlook
Fall-throughs deserve closer attention than they usually get. Teams often log them as isolated disappointments instead of analysing the operational pattern behind them.
Watch the handoff, not just the headline. A tenancy rarely falls through because of one dramatic event. More often, it dies through silence, delay and uncertainty in the days after the offer.
That's why the strongest metrics are the ones tied to action. If a number can't help your team decide what to chase, change or automate, it probably doesn't belong on the main dashboard.
Turning Data into Decisions Practical Use Cases
A metric on its own doesn't improve anything. The value comes from linking that signal to a specific operational response. In lettings, the best reporting and analytics setups do this quickly enough for the team to intervene before a tenancy is lost.
The cost of slow intervention is real. 24% of UK tenancies fail post-offer due to referencing delays, and a failed tenancy costs an average of £1,200, based on the figures provided in the brief from the UK Government's Housing: Fairness and Efficiency report and the National Landlords Association. That's why live visibility matters. It's not just a management convenience. It helps agents act while the deal is still recoverable.

When turnaround time starts creeping up
A rising turnaround time should trigger a second question immediately. Which stage is slipping?
If the delay sits at applicant document upload, the fix is usually communication. Tighten the request list, remove ambiguity, and make sure applicants know exactly what's outstanding. If the delay sits with employment checks or landlord references, the stronger move is to reduce manual chasing and standardise follow-up.
A useful response pattern looks like this:
-
If cases are waiting on applicants
Review your request wording, timing and reminders. -
If employers are the slow point
Reduce dependence on staff phone calls and use structured follow-up. -
If cases pause after checks return
Look at internal review workload and assignment.
When fall-throughs increase
Not every fall-through is avoidable, but many are predictable. The key is to stop treating them as a final outcome and start treating them as a process signal.
Look back at the final days before a failed deal. Was there a long silence? Did the applicant wait too long for updates? Was one missing item left unresolved without escalation? Once you track that pattern consistently, you can build rules around it.
For example:
- Flag cases with no movement for too long
- Escalate stalled applications before the applicant disengages
- Give landlords proactive updates on delayed cases
- Prioritise near-complete tenancies that only need one remaining check
When affordability issues keep appearing
If your team sees repeated conditional outcomes linked to affordability, don't just accept that as “the type of applicant we get”. Check where those applicants are coming from and how they were qualified before application.
That may lead to changes such as:
- Improving pre-application affordability screening
- Training negotiators to set expectations earlier
- Adjusting marketing language so unsuitable applicants self-select out
- Preparing guarantor routes sooner when needed
The best decisions usually come from one extra layer of questioning. Not “What happened?” but “What pattern keeps producing this result?”
When team workload becomes the bottleneck
Sometimes the referencing system is fine and the pressure sits inside the branch. One negotiator may be holding too many live cases, or one branch may be running a slower review process than the rest of the group.
That's where operational analytics becomes management discipline. Reassign work, tighten ownership, and make sure high-risk applications aren't buried under lower-priority admin. Better reporting helps people focus. Better analytics helps managers decide where that focus should go.
Building Your Lettings Performance Dashboard
A lettings dashboard only works if the underlying data is consistent. If one negotiator updates a spreadsheet, another keeps notes in email, and a third logs progress in a property system only some of the time, you don't have one reporting view. You have competing versions of the truth.
That problem isn't unique to lettings. The UK Government Digital Service built its Performance Platform because disconnected data sources made it difficult to compare metrics consistently across departments and services (GDS performance platform context). Agencies face the same issue on a smaller scale when different team members calculate progress in different ways.

What a good dashboard includes
A useful dashboard isn't crowded. It shows the measures that help a branch act today.
Start with these:
- Live pipeline view showing every in-progress case by stage
- Exceptions list for stalled or overdue applications
- Outcome summary showing pass, conditional and refer decisions
- Compliance tracker for identity, right to rent and screening status
- Workload view by negotiator, branch or team
If you can't scan the dashboard and decide what your staff should do next, it's too complicated.
Why one source of truth matters
The biggest gain comes from standard definitions. Everyone should mean the same thing when they say a case is waiting, complete, delayed or under review. Once those definitions are built into one system, contradictory reporting drops sharply.
That's also why bolt-on spreadsheets age badly. They depend on discipline, and discipline tends to weaken when the branch gets busy. Integrated systems are better because they create the reporting as part of the workflow rather than as an extra task after the fact.
For agencies reviewing the wider operational stack, property rental management software often plays the same role across maintenance, rent collection and compliance. The principle is identical. Pull activity into one environment so the reporting reflects the work as it happens.
A dashboard should answer three questions fast. What needs attention now, what is slowing us down, and who owns the next action?
How to build it without overcomplicating things
Keep the first version lean. Don't try to design the perfect executive report before the branch has a usable operational one.
A practical order is:
- Choose the few metrics your team acts on weekly
- Define each status and outcome clearly
- Make updates part of the workflow, not a separate admin task
- Review exceptions daily and trend lines weekly
- Drop any metric that never changes a decision
That's usually enough to move an agency from anecdotal management to performance management.
From Insight to Action Real Examples from the Field
The best test of reporting and analytics is simple. Did the team change anything because of what they saw?
Below are the kinds of patterns that matter in real lettings operations. They aren't abstract dashboard exercises. They're practical situations where cleaner visibility changes what staff do next.

Example one: manual references are slowing the branch
A branch notices the same thing every week. Cases look active, but progress depends on whoever has time to call employers and previous landlords. Updates are inconsistent, and negotiators spend part of the day finding out what happened rather than moving the file on.
That's still common. The brief notes that 78% of UK letting agents still rely on manual phone calls for references, which explains why so many teams struggle to create a reliable live picture of progress. In a branch like this, the fix isn't another report. The fix is to remove the manual bottleneck that the reporting has exposed.
Example two: compliance checks are being treated as separate admin
Another team keeps referencing updates in one place and compliance activity somewhere else. The result is awkward handoffs. A tenancy may look commercially ready while important checks still depend on manual confirmation.
That creates risk, especially as compliance expectations tighten. The brief also states that penalties for failing sanctions screening are up 30%, which makes fragmented checking a dangerous habit rather than just an inefficient one. Once a branch combines progression reporting with compliance status, managers can see which cases are commercially close but operationally incomplete.
Good analytics doesn't just speed up the yes. It also stops the team progressing a case that shouldn't move yet.
Example three: managers are reacting too late
Some agencies only review performance after a complaint, a lost tenancy or an end-of-month shortfall. By then, staff can explain what happened, but they can't recover the missed opportunity.
The better pattern is earlier intervention:
- Review stalled cases daily so nobody waits too long for a chase
- Escalate missing compliance items before move-in dates get close
- Separate branch workload visibly so one overcapacity negotiator doesn't hold up completions
- Look for repeated causes rather than treating each delayed file as a one-off
These examples don't require a data team. They require managers who are willing to turn signals into rules, and staff who aren't forced to build the picture manually every time.
Getting Started with Analytics in Your Agency
Most agencies don't need a grand transformation plan. They need a cleaner starting point.
Begin with one workflow that already creates friction. Referencing is usually the obvious place because it touches speed, revenue, applicant experience and compliance at the same time. Pick the few operational measures that matter most to your branch, track them consistently, and make sure someone reviews exceptions every day rather than only at month end.
Keep it practical. Don't chase vanity metrics. Focus on the questions that affect placements: which cases are stalled, why they are stalled, what needs chasing next, and where compliance is incomplete. Once your team can answer those four questions quickly, reporting and analytics stop being a theory exercise and start becoming a commercial advantage.
If you're comparing systems before changing process, it's worth reviewing how other agencies assess letting agent software in the UK. The right setup should reduce manual follow-up, improve visibility and make decisions easier under pressure.
The agencies that get ahead aren't always the largest. They're usually the ones that can see problems sooner and act before a deal slips away.
If you want a simple way to put this into practice, try passref on your next few references. You'll get a live view of applicant progress, automated chasing, clear Pass, Conditional or Refer outcomes, and a faster route from offer agreed to tenancy secured without the usual spreadsheet guessing.