Advisor Perspectives

How Long Should Client Review Prep Take? Review Exceptions, Not Packets

Most firms build the same review packet for every household, so quiet clients cost as much as complicated ones. Here is a simpler rule: spend prep time where something changed.

AdvisorPilot

Ask an advisor how long review prep should take and the honest answer is usually "longer than it does." Ask how long it actually takes and you hear about the Sunday before review season, the associate who built forty packets in a week, and the binder that went home with the client and never got opened.

Here is our short answer. For a household where nothing has changed, prep should be measured in minutes: confirm the data is current, look for anything unusual, and note what the client asked about last time. The hours belong to the households where something did change. Most firms do the opposite. They build the same full packet for every client, so the quiet households cost as much as the complicated ones, and the complicated ones get whatever time is left over.

How long should client review prep take?

There is no rule, but there is a useful baseline. In its advisor time-use study, Kitces Research found the average lead advisor spent 8.8 hours per week meeting with current clients, plus another 5.3 hours per week of preparation for the meetings. Do the division and that is roughly 36 minutes of prep for every hour in front of a client, before counting the 6.6 hours a week of supporting analysis the same study reported.

Thirty six minutes is an average, and averages hide the real problem. A retired couple with two accounts and no changes since spring does not need 36 minutes. A business owner who just sold the company needs far more than that. When every household gets the same packet, the average turns into a floor for the simple cases and a ceiling for the hard ones.

So a better target than a number of minutes is a rule: spend prep time in proportion to what changed.

What is an exception-based review?

An exception-based review starts from the assumption that most of what is in a client file is fine, then goes looking for the parts that are not. Instead of assembling everything and reading all of it, the team runs a short, consistent check on every household and only builds a full narrative where the check turns something up.

The exceptions are the things a person actually needs to look at. A few that come up again and again in our conversations with advisors:

• A statement that is missing, or newer than the data you are about to present
• An account that changed registration, beneficiary, or ownership
• A large deposit, withdrawal, or transfer since the last meeting
• Allocation that has drifted meaningfully from the household's model
• A life event the client mentioned: a retirement date, a sale, a death, a new grandchild
• An open item from the last meeting that nobody closed

If a household clears the check, the review still happens. The client still gets a real conversation. What changes is that nobody spends an evening formatting twelve pages to confirm that nothing happened.

Where do the minutes go before the client sits down?

Most of the time in a packet is not analysis. It is assembly. Someone pulls statements, rekeys or imports positions, runs performance, drops charts into a template, and checks that the totals match. Only then does anyone ask what the client needs to hear.

That order is the trap. By the time the assembly is done, the person doing it is tired, the meeting is tomorrow, and the one account with a real question looks just like the eleven without one. The work that matters, noticing, gets squeezed into the last half hour.

Flip the order and the same team can spend its attention differently. Collect what you need early. Run the check. Then build materials only where the check says there is a story. In AdvisorPilot, that looks like sending the client a statement upload link tied to their household well before the meeting, bringing in holdings with spreadsheet import where a custodian export already exists, and running performance reporting against the data you just confirmed. The narrative comes last, and only for the households that need one.

What belongs in the check, and what still needs a person?

The check is the boring part, and that is the point. It should be the same every time, short enough that nobody is tempted to skip it, and written down so a new associate can run it on day one. Is every account accounted for? Are the statements current? Does anything differ from the last meeting? Is there an open task?

What the check cannot do is decide what a change means. A withdrawal could be a new roof or the first sign of a parent who needs care. Drift could be something to correct or something the client asked for. That is judgment, and it stays with the advisor. Exception-based review is not a way to automate advice. It is a way to make sure the advisor's judgment lands on the households that need it, instead of being spread thin across a stack of packets.

This is also the line between a quality gate and a shortcut. A gate catches problems before they reach the client. A shortcut skips the check and hopes. If your firm moves to exceptions, the check itself has to become more disciplined, not less.

How do you run the week before the meeting without a night before scramble?

Work backward from the meeting date. The details will vary by firm, but a rhythm many teams can live with looks something like this:

1. About a week out: send the statement request and confirm the meeting.
2. A few days out: run the check on whatever has arrived and chase what has not.
3. Two days out: build materials for the exceptions. For a quiet household, a one page summary and the agenda may be enough.
4. The day before: the advisor reads the exceptions, not the whole file.

The calendar is what makes this hold. AdvisorPilot syncs with Google and Outlook calendars, so the date you count back from is the one actually booked, and the integrated CRM keeps open items from the last review attached to the client instead of living in someone's notebook. When the meeting moves, the clock moves with it.

What should the file show after the meeting?

An exception-based process has to leave a clear trail, because "we checked and nothing changed" is only worth something if you can show the check happened. The file should record what was reviewed, what was flagged, what the advisor decided, and what the client was told.

That record matters for supervision, and it matters for the next review. If the last meeting's notes and open items are easy to find, next quarter's check starts from something real. AdvisorPilot includes WORM compliance archiving, which helps keep that record intact once it is written. Your CCO decides what your firm has to retain.

Why does this matter for capacity?

Kitces' newer productivity research found the typical Senior Advisor spends just 17% of their time in client meetings, and concluded that most advisors would benefit from increasing client face time from that median to 35% to 40% of their week, with team support being key to getting there. It also found that the single most important driver of productivity is the right team structure, not more software.

Exception-based review fits that finding. It does not replace the associate or the paraplanner. It gives them a clear job: run the check, surface the exceptions, and hand the advisor the households that need thinking. The quiet clients still get seen. The complicated ones finally get the time they deserve.

This article is for educational purposes for financial professionals. It is not investment, tax, legal, or compliance advice, and it does not recommend any specific strategy or product. Statistics are reported as published by each source; see the linked studies for methodology.