Back to resourcesGuides for Advisors

How to run a structured client review — a practical framework

A clear review structure for identifying Priority Issues, discussing the relevant context, and recording decisions, owners and review dates.

5 min read

Most client reviews are run from memory. A partner opens the file, scans the numbers they always scan, raises whatever stands out, and moves on. It works — until it doesn't. Something gets missed, a client asks why a decision was made and there's no record, or a new team member runs the same review and reaches a different conclusion. The fix isn't working harder. It's running every review to the same structure.

Here's a framework that holds up across a portfolio.

Start from the priorities, not the whole ledger

The instinct is to review everything. Don't. Open with the issues that actually need attention this period — ranked by severity — and work down from there. A full scan has its place, but it belongs after you've dealt with what's material, not before. Leading with the critical items means the most important conversation happens while you and the client are freshest, not in the last five minutes.

For each item, work the same four questions

Consistency comes from asking the same things in the same order, every time:

  • What surfaced, and why? Read the plain-language explanation and the actual figure behind it. "Cash runway is two months" is a starting point; the reason is the review.
  • How does it compare to the threshold? A number in isolation means little. A number against the level you'd expect for this business is a signal.
  • Is it connected to anything else? A single metric rarely tells the whole story. An elevated payroll ratio reads very differently when cash is also tight. Look at the combination.
  • Is this already known and intentional? Sometimes the issue is a deliberate decision — a planned equipment purchase, a seasonal hire. That's still worth recording, just with different context.

Every item gets a decision

This is the discipline most reviews lack. An issue that's been seen but not decided is an issue that will be seen again next period — and eventually missed. Give each one an outcome: accept it (reviewed, no action needed), assign it (someone owns the next step), defer it (revisit on a set date), or resolve it. "We looked at it" is not an outcome. "Accepted, planned capex, revisit after next receipts clear" is.

Attach an owner and a date

An action without an owner is a wish. Name who's responsible — the client's finance manager, the accountant, yourself — clearly enough that the next step can't get lost. Where the item needs following up, set a review date. This is what turns a review from a conversation into a commitment.

Record the context, briefly

A good note is short, specific, and useful months later. "Deferred until final month-end data available" or "Assigned to finance manager to chase the two largest overdue accounts by Friday" will make sense to anyone who reads the file — including you, next quarter. Vague notes ("looks fine") are worse than none, because they imply a review happened without capturing what it found.

Keep the trail, and share what matters

The decisions, owners, dates and notes should accumulate into a record you can stand behind — to the client, a board, or a regulator. When you share back with the client, keep it practical: what needs attention, why it matters, who owns it, and when it'll be looked at again. Save the technical calculations for the working file.

The cadence is the other half

A structure only compounds if it runs on a rhythm. Active clients with changing conditions may warrant a light monthly or in-month check; steadier businesses align to quarterly reviews. The point isn't frequency for its own sake — it's that the same structure runs each time, so nothing depends on who happened to open the file.

Run reviews this way and two things change. They get faster, because you're not reinventing the approach each time. And they get defensible, because every decision has a reason, an owner and a date attached — the difference between advice you gave and advice you can show you gave.

Orbiant turns this kind of structured review into a repeatable workflow — surfacing priority issues, recording decisions, and keeping a defensible trail across every client.

See how it works for advisors