There is no caseload limit in the Code, and agents sometimes take that as an answer. It is not — it is a different kind of constraint.
Section 13 of the Code of Conduct requires an agent to act professionally, competently, diligently, ethically, honestly and with integrity. Section 33 requires acting in the client's legitimate interests, responding in a timely manner, and being aware of the times by which things must be done. Section 45 requires a responsible migration agent to take all reasonable steps to ensure the work specified in a service agreement is completed.
None of that sets a number. All of it sets a standard, and capacity is simply what meeting that standard costs. A caseload you cannot handle diligently is not a business problem that might later become a compliance problem. It is already the compliance problem.
Why matter counts mislead
"Forty matters each" is the usual measure and it is close to useless, because the variance within a caseload is larger than the variance between caseloads.
Four dimensions determine actual load, and none of them is visible in a count.
Stage. A matter awaiting a decision consumes almost nothing. The same matter in evidence-gathering consumes a great deal. A caseload of sixty where fifty are lodged is lighter than a caseload of twenty-five in preparation.
Complexity. A straightforward extension and a complex sponsored matter with character issues are not comparable units.
Deadline pressure. Two matters with hard dates next week dominate a week regardless of what else is open.
Client contact intensity. Some clients need three touches; others need thirty. Anxiety and language needs are real drivers of load, and section 37's duty to arrange an interpreter where a client requests one has a scheduling cost attached.
A practice measuring only headline numbers will be surprised repeatedly, because the number moves independently of the work.
A weighting that is good enough
Precision here is a trap; the aim is a number that moves when the work does. A simple scheme, applied consistently:
- Score each matter for stage: preparation is heavy, awaiting decision is light, post-decision is moderate.
- Score for complexity: standard, or complicated by character, health, relationship evidence, sponsorship compliance, or review.
- Add a loading for a hard deadline inside 30 days.
- Add a loading for high-contact clients, which the person doing the work can identify immediately.
Sum it per person. Now you have a figure that rises when a matter enters preparation and falls when it is lodged — which is the behaviour a matter count conspicuously lacks.
The absolute number does not matter. What matters is calibrating it once against a period everyone agrees was sustainable, and then treating that as the line.
Watch the trend, not the level
Load is lumpy, and a busy fortnight is not a capacity problem. The signals worth acting on are directional:
- Weighted load rising for three consecutive weeks
- The gap between request and response to clients lengthening
- File notes being written in batches rather than at the time — a direct signal, because section 55 requires contemporaneous records
- Pre-lodgement review being skipped or compressed
- Deadlines increasingly handled inside the final escalation window
Those are leading indicators. Refusals, complaints and missed dates are lagging ones, and by then you are managing consequences.
What to do at the line
Capacity is only useful if there is an agreed response. Four levers, in the order that costs least.
Stop taking work. Uncomfortable, and cheaper than the alternative. Section 19 prohibits giving immigration assistance the agent reasonably believes would be futile, and section 26 prohibits false or misleading statements about immigration opportunities or risks. Accepting a matter you cannot service to the standard, on the basis that things will ease, edges toward both.
Reallocate. Requires knowing who has capacity, which requires the measurement above.
Bring in help. Section 24 makes you responsible for the quality, accuracy and timeliness of work performed by another person assisting you — with the exception that it does not extend to work performed by another registered agent. Adding an unregistered assistant adds a supervision obligation, and OMARA's guidance on practice management duties sets out what discharging it looks like. Adding an RMA does not, but adds coordination.
Defer the deferrable. Some work genuinely can wait. The discipline is deciding which, deliberately, rather than letting the least urgent thing be whatever was least recently mentioned.
Our guide to growing from solo to a team covers the point at which the third lever becomes the right one.
The capacity question nobody asks
What happens if you are unavailable for a month?
This is a capacity question and a Code question at once. Section 45 requires reasonable steps to ensure the agreed work is completed. Sections 30 and 31 impose notification obligations on all current clients, the Department and review authorities if your registration is suspended or expected to lapse. Section 42(3)(b) requires service agreements to name each agent expected to give assistance, and OMARA's guidance says that where an agent has planned leave during a period a client will need assistance, the agents expected to cover should be listed in the agreement.
Which means continuity is not something to arrange when it becomes necessary. For planned absence, it belongs in the agreement at the outset.
A single-agent practice with sixty active matters has a concentration risk that no amount of efficiency addresses. Our guide to starting a migration agency covers structuring for it early.
The capacity check
Once a month, per person:
- What is the weighted load, and which way has it moved for three weeks?
- How many matters are in preparation as opposed to awaiting a decision?
- How many carry a hard deadline in the next 30 days?
- Is the gap between client contact and response growing?
- Are file notes being written at the time?
- If this person were unavailable for a month, who would pick it up, and is that in the agreements?
Where a system helps
Capacity planning fails for a mundane reason: the data exists but not in one place. Matters in one system, deadlines in a calendar, client contact in a mailbox, and the only person who knows how loaded someone is, is that person — who is the least reliable judge when overloaded.
What changes it is having stage, deadlines and activity as properties of the matter, so load is a query. Then the conversation stops being about how someone feels and starts being about a number both people can see.
LodgeHQ tracks matters by stage with deadlines and activity attached, so workload across a team is a view rather than a survey. Start a free trial and find out how your caseload distributes once stage is taken into account.
Verify before you rely on it
No source sets a caseload limit, and nothing here is a benchmark. The weightings are a starting structure to calibrate against your own practice, not figures to adopt.
This is general information for migration practices, not legal or business advice. If you are carrying a caseload you cannot service to the Code's standard, deal with that as a professional obligation and take advice about the matters most at risk.