The standard weekly review goes through the caseload in order. It starts alphabetically or by open date, moves at a reasonable pace, and runs out of time somewhere around two thirds of the way through.
The matters discussed are therefore selected by where the list happened to start. The matters at risk are distributed randomly through it. A meeting organised this way is a status update that occasionally catches something by accident.
Inverting it — discuss only exceptions, and let everything else be silent — makes the meeting a control. The question is then which exceptions, and the Code of Conduct supplies most of the list.
Six exceptions worth surfacing
Each of these maps to an obligation, which is why they are worth the meeting's time.
Deadlines inside the escalation window. 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 them not being done. This is the standing first item, and our guide to deadline management covers the machinery behind it.
Matters with no activity for a defined period. Choose a number — three weeks is common — and surface anything below it. Silence is the most reliable early signal of a matter drifting, and the retention clock runs from the last action on the file, so a matter nobody has touched is also a matter aging in a way nobody has noticed.
Evidence blocked for more than a set period. A document requested and not received is where matters quietly stall. Section 40 prohibits acting in a way that causes or is reasonably likely to cause unnecessary expense or delay, and a request that was made once in July and never followed up is exactly that.
Clients who have not heard from you. Section 39 requires you to advise a client in writing when anything is lodged, give them a copy, and promptly advise material developments. The exception here is not "we have not spoken to them" but "something happened and we have not told them".
Money exceptions. Balances on finished matters — refunds are due promptly and no later than 14 days after becoming payable — plus fee transfers pending a statement of services, and any client-and-purpose balance that has gone negative.
Matters where something changed. A relationship ending, a sponsor restructuring, a client disclosing something new. These trigger conflict analysis under section 34 and may change the advice entirely.
The dashboard is the agenda
If those six are the agenda, the dashboard is simply the query that produces them. Which has a useful implication: the meeting cannot be better than the data, so the effort belongs in making the exceptions computable rather than in preparing for the meeting.
A workable dashboard shows, per person:
- deadlines by consequence class, inside the escalation window
- matters with no activity beyond the threshold
- outstanding document requests, aged
- matters with a material development not yet communicated
- financial exceptions
- new matters opened this week, so intake is visible
Everything else is noise for this purpose. A dashboard showing all matters is a list, and a list is what you were trying to escape.
Preparation should be zero
If the meeting requires anyone to prepare a report, it will be skipped in the weeks it matters most — the busy ones.
The dashboard should be a live view, not a compiled document. That is a system requirement, and it is the single largest determinant of whether a weekly review survives past its second month.
Running it in twenty-five minutes
The meeting should be short enough that nobody resents it and frequent enough that nothing waits long.
- Deadlines (5 min). Every date inside the window. For each: is action recorded, and if not, when.
- Blocked and stalled (7 min). Aged document requests and inactive matters. The output for each is a decision, not a discussion — chase, escalate to a call, change approach, or close.
- Client communication (4 min). Material developments not yet communicated.
- Money (4 min). Refunds due, transfers pending, negative balances.
- Changes and risks (5 min). Anything that changed the shape of a matter, including conflicts.
Two rules keep it to time. No matter is discussed unless it appears as an exception — however interesting it is. And anything needing more than two minutes leaves the meeting as a scheduled conversation between the people involved.
Follow-up is where these meetings die
The pattern is familiar. Decisions are made, nobody records them, and next week starts by re-deriving what was decided.
Three things fix it, and all are cheap:
- Every decision produces a dated action with an owner, recorded on the matter rather than in the meeting notes. If it lives only in the minutes, it is not on the file, and the file is what matters under section 56.
- Last week's actions are the first thing checked, before the new exceptions. This is the accountability mechanism; without it the meeting is advisory.
- A decision to do nothing is recorded as a decision. "Leave until the client returns from overseas" is a legitimate outcome and belongs on the file, because in three months the alternative reading is that the matter was forgotten.
Where a decision is communicated to a client orally, section 55 requires a contemporaneous written record of that conversation, so the file note is not optional housekeeping.
Who should be there
Small enough that everyone speaks. In a practice of three, that is everyone. Beyond about eight, split by team and hold a shorter principals' review on the aggregate.
The supervising agent should attend, and not only for oversight. Section 24 makes an agent responsible for the quality, accuracy and timeliness of work performed by others assisting them, and OMARA's guidance on practice management duties lists maintaining records of internal discussions with staff about client applications among the supervisory arrangements a practice should have. A weekly review with recorded outcomes is that record, produced as a by-product.
The meeting test
- Would a matter that has had no activity for a month appear on your dashboard?
- Can you see aged document requests without asking anyone?
- Does the meeting start with last week's actions?
- Do decisions land on the matter, or in the minutes?
- Has the meeting been skipped in either of the last two busy weeks?
- Could someone else run it from the dashboard alone?
Where a system helps
The reason most weekly reviews degrade into status meetings is that exceptions are not computable. Without a system that knows when a matter was last touched, which requests are outstanding and which developments have been communicated, the only available agenda is the full list.
Once those are properties of the matter, the dashboard writes itself, preparation drops to zero, and the meeting becomes twenty-five minutes about the six things that actually need attention. Our guides to ImmiAccount workflow and client onboarding cover the upstream habits that make the data reliable.
LodgeHQ surfaces deadlines, stalled matters, outstanding requests and financial exceptions as live views. Start a free trial and see what your current caseload looks like filtered to exceptions only.
Verify before you rely on it
The thresholds here — three weeks of inactivity, a seven-day escalation window — are starting points to calibrate against your own work, not standards drawn from any source.
This is general information for migration practices, not legal advice. Where a review surfaces a matter that has gone wrong, deal with it as a matter rather than a meeting item, and get advice where a deadline or an obligation has been missed.