Technology

Migration Practice KPIs: Caseload, Deadlines, Cash Flow and Client Service

Most practice dashboards measure growth. The measures worth having are the ones that go wrong before anything else does — and several of them come straight from the Code.

LodgeHQ

Compliance Team

•20 November 2026•7 min read

Two measures dominate most practice dashboards: how many enquiries converted, and how much was billed. Both are real numbers and both point the same way, which is the problem.

A dashboard that only rewards volume will, over a long enough period, reward accepting matters that should have been declined. The Code of Conduct is direct about that boundary: section 19 prohibits giving immigration assistance an agent reasonably believes would be futile, absent a specific written process, and section 13 requires acting competently and diligently — which a caseload beyond capacity makes impossible.

The measures worth having are the ones that go wrong before anything visible does. Several of them come straight from the Code, because the Code is largely a list of things that go wrong.

Risk measures: the ones that lead

These move first, and they are the reason to have a dashboard at all.

Deadlines inside the escalation window without recorded action. Section 33 requires an agent to be aware of the times by which things must be done and to have regard to the consequences of missing them. The number to watch is not how many deadlines exist but how many are close with nothing recorded against them. Zero is achievable; anything else is a queue.

Matters with no activity beyond a threshold. Silence is the earliest reliable signal of drift, and the retention clock runs from the last action on the file — so a matter nobody has touched is aging in a way nobody has noticed.

Aged document requests. A count of requests made and not fulfilled, by age. Section 40 prohibits acting in a way that causes unnecessary expense or delay, and a request made once and never followed up sits badly against it.

Matters with an undelivered material development. Section 39 requires prompt advice of material developments. A gap between something happening and the client being told is a service failure and a compliance one.

File notes written more than a day after the event. Section 55 requires records of oral communications to be contemporaneous, and batching is the visible symptom of a practice under load.

Service measures that are not satisfaction scores

Satisfaction surveys in migration measure outcome anxiety more than service. These measure the thing you control.

Time from client contact to first response. Section 33 requires responding in a timely manner. Track the distribution rather than the average — the average hides the client who waited nine days.

Time from a request for further information landing to the client being told. This is where a practice's responsiveness is genuinely tested.

Proportion of client contact recorded on the file. OMARA's guidance on practice management duties lists recording all client contact on the file among the arrangements a practice should have, and it is measurable if contact happens in the system.

Complaints, including ones that never reached a complaint. A client who says they were unhappy is data even when nothing formal follows.

Money measures that are compliance measures

Cash flow measures are usual. These are the ones that also carry obligations.

Client-and-purpose balances below zero, at any point in the period. Section 50(1)(f) prohibits paying out more for a purpose than was paid in for it. This is the single most valuable financial measure a migration practice can have and almost nobody computes it.

Credit balances on finished matters, aged. Refunds are due promptly and no later than 14 days after they become payable, so anything past that is already late.

Fee transfers without a statement of services. Section 50(1)(d)(i) does not permit paying yourself where section 313 of the Migration Act says you are not entitled, and entitlement depends on a statement of services having been given.

Charges without a preceding itemised invoice. Section 49 requires the invoice before the charge and a receipt after payment.

Each of those is a count that should be zero. A dashboard of numbers that should be zero is far more useful than one of numbers that should be large.

Capacity measures

Volume tells you about the business. Load tells you about the risk.

Weighted load per person, accounting for stage and complexity rather than a matter count — our guide to capacity planning sets out a workable weighting.

Proportion of matters in active preparation as opposed to awaiting a decision. This is what actually drives the week.

Concentration. How many matters depend on one agent, and what would happen if that person were unavailable for a month. Sections 30 and 31 turn that scenario into a notification obligation across every current client.

The measures to be careful with

Three that look reasonable and distort behaviour.

Approval rate. It sounds like quality. It is mostly a measure of which matters you accept, and optimising it means declining hard cases and cherry-picking easy ones — which is a business strategy, not a professional one, and it can quietly conflict with acting in a client's legitimate interests.

Matters closed per person. Rewards closing rather than finishing. Section 45 requires reasonable steps to ensure the work specified in the agreement is completed.

Revenue per matter, in isolation. Section 46 requires fees to be fair and reasonable and constrains when they may be varied. A measure that rewards the number going up, without any counterweight, is pushing against a provision.

If you use these, pair each with a counterweight and look at them together — approval rate beside matter complexity, closures beside reopened matters, revenue per matter beside variation counts.

A dashboard that fits on one screen

Six numbers, reviewed weekly:

  1. Deadlines inside the window with no recorded action
  2. Matters with no activity beyond the threshold
  3. Aged document requests, oldest first
  4. Financial exceptions — negative balances, aged credits, transfers without a statement
  5. Weighted load per person, with the three-week trend
  6. Response time distribution, not the average

Four of those should read zero. That is the point: a dashboard where most measures should be zero tells you immediately whether to keep reading.

Reviewing without turning them into targets

Two rules keep a dashboard useful.

Measures are for conversation, not for pay. As soon as a number determines someone's review, it starts being managed rather than reported, and the practice loses its early warning.

Look at the trend, not the level. A busy fortnight is not a problem. Three weeks of the same direction is. Our guide to the weekly matter review covers running the conversation these numbers should produce.

The dashboard test

  • Which of your current measures would rise if you accepted work you should decline?
  • Do you know how many matters have had no activity for a month?
  • Could you produce client-and-purpose balances for the last quarter?
  • Do you measure the time to tell a client something happened?
  • How many of your measures should read zero?
  • Does any number determine someone's performance review?

Where a system helps

Nearly every measure above is unavailable to a practice running on a shared drive and a mailbox, and that is the real reason most dashboards are conversion and revenue: those are the two numbers you can get from a spreadsheet.

The risk measures require the system to know when a matter was last touched, which requests are outstanding, which developments have been communicated, and what each client's money is for. Once those are properties of the matter, the dashboard is a query rather than a monthly assembly job — which is also what makes it survive the quarters when nobody has time to produce a report.

LodgeHQ tracks activity, deadlines, document requests and client money on the matter, so these are views rather than exports. Our guides to software for registered agents and AI tools cover the wider toolkit.

Verify before you rely on it

None of the measures here is a standard, and no source prescribes thresholds for a migration practice. Calibrate them against your own work, and treat the Code obligations they reference as the authority rather than the metric.

This is general information for migration practices, not legal or business advice. Where a measure surfaces a compliance exception — a negative client balance, a transfer without a statement of services — deal with it as a compliance matter and take advice rather than treating it as a reporting issue.

Tags:KPIsDashboardsPractice ManagementMetricsRisk Management