In this Article
- What a Client Audit Means in an Advisory Firm
- Set the Audit Scope Before You Ask a Question
- Build the Client Household Inventory
- Calculate Meeting Capacity From the Household Base
- Run the Survey Administration Workflow
- Use the Online Dashboard as a Decision Tool
- Convert Feedback Into Practice Decisions
- Quality Control and the Repeat Cycle
- References
Most advisory teams already run something they call an audit. Sometimes it is a compliance review, sometimes a satisfaction poll, sometimes a CRM cleanup dressed up in survey language. This guide treats the Client Audit as a specific instrument tied to a specific output: better capacity planning. If your feedback exercise does not eventually change a meeting cadence or a workload split, it belongs in a different category.
What a Client Audit Means in an Advisory Firm
A Client Audit is a proprietary client survey and feedback system used to evaluate how well a financial planning firm is serving its client households, and where operational changes may be required. That is the definition I work from, and it deliberately excludes testimonial gathering, sales persuasion, and promotional satisfaction claims. The audit is a process-design tool, not marketing copy.
The core unit of analysis is the Client Household — an individual or couple living in the same house. Fix that definition and do not switch between individual clients and households inside the same audit file. A couple is one service-demand unit, not two.
One boundary worth stating plainly: according to available data, the Practice Audit survey referenced here dates to 2001 and was last revised on November 21, 2001, with Advisor Impact identified as the survey administrator in that historical model. Treat it as a methodology reference point rather than a current benchmark, and adapt the mechanics to how your firm actually serves clients today.
Set the Audit Scope Before You Ask a Question
Scope control comes before survey design for one reason. Vague feedback cannot be translated into staffing, service-tier, or meeting-capacity decisions. If you do not lock the population and the rules first, you get comments you cannot act on.
Record these scope variables in a control sheet before administration:
- Active client households only
- Advisor or team ownership per household
- Service tier, if your firm uses one
- Expected review-meeting cadence
- Communication standard
- Excluded fielding periods and excluded service periods
Decide the file cutoff too. A practical choice is the CRM export date used to build the population file; households added after that date wait until the next cycle. Write inclusion and exclusion rules down so a later audit can reproduce the same population logic.
RRSP season deserves a specific call. For firms with Canadian seasonal demand, treat it as a capacity exclusion when you evaluate proactive meeting availability, because it is a predictable high-demand period rather than normal service time. Firms without that calendar pressure still have their own recurring blackout windows — identify yours and exclude them the same way.
Build the Client Household Inventory
Build the audit file from the household base, not from a raw contact list. A CRM export drags in spouses as separate records, adult children, estate contacts, dormant relationships, and professional referral sources. Survey all of them and you overstate demand against capacity.
This is the failure case I see most often. A firm surveys every CRM contact, counts spouses twice, includes prospects and dormant households, then concludes advisor capacity is worse than reality. The population file broke the math before a single response came back.
Inventory sequence
- Export households from the CRM
- Remove duplicate records
- Assign the primary advisor
- Tag relationship status
- Confirm communication permission
- Mark outreach eligibility
Control these fields on every record: household name, primary contact, advisor, planning relationship, communication permission, service tier, last meeting date, and next expected review date. Separate active households from prospects, dormant relationships, former clients, estate-only contacts, and referral sources unless you have set up separate reporting groups for them.
Use a household-level identifier, not a person-level one. Reconcile the list against CRM records before fielding, and assign any unresolved duplicate household to one primary service team first. One couple should never register as two service-demand units.
Calculate Meeting Capacity From the Household Base
Capacity Analysis is the calculation of meetings required to service a client base. The discipline here is to build that calculation from the service promise you already made to clients, rather than importing a generic advisor productivity ratio that describes a firm you are not.
Work from these inputs: household count, promised proactive meetings by service tier, expected meeting length, preparation time, follow-up time, advisor availability, and blackout periods such as RRSP season. Count eligible households, apply your own promised cadence, estimate the required proactive meetings, remove blackout time from available capacity, then compare demand against advisor availability.
Do not fold RRSP season into normal proactive review capacity when you already know it is dominated by seasonal contribution and planning work. That is borrowed time, not service time.
Capacity findings should shape the questions you ask. If meeting demand runs tight against availability, weight the survey toward access, responsiveness, meeting cadence, clarity of follow-up, and perceived value — the exact places where a stretched calendar shows up in client experience. Joe Martin of Golub Group, LLC is a named historical practitioner associated with this framework, and based on reported figures, the Golub Group partnership ran across eight years; useful as context, not as proof that any single ratio transfers to your practice.
Run the Survey Administration Workflow
Administration is a controlled fielding process, not an informal email request. Roles stay separate: the advisory firm owns the client relationship and every decision that follows, while Advisor Impact administers the survey process and reporting workflow in the historical Client Audit model.
Workflow order
- Finalize the household file
- Confirm the question set
- Prepare client communications
- Administer the survey through Advisor Impact
- Monitor the completion window
- Close fielding
- Prepare results for dashboard review
Hold these variables steady while the survey is live: timing, eligibility, contact accuracy, survey version, reminder cadence, confidentiality language, and household-level tracking. A defined fielding window — something like 10 to 15 business days — helps operational planning. Do not turn that window into an expected response rate; it is a schedule, not a forecast.
Preserve the exact survey version for the cycle, including question wording and the response scale, before any interpretation begins. And resist the urge to fabricate response rates, satisfaction scores, or benchmark rankings that the data does not give you. If the number is not in front of you, make the point qualitatively.
Use the Online Dashboard as a Decision Tool
The Online Dashboard is the reporting tool for survey results. Read it as a management instrument, not a presentation deck. Start with participation context: confirm the fielding population, the completion window, household group labels, advisor assignments, and any excluded records. Interpretation without that context is guessing.
From there, move to patterns. Look for recurring friction, unmet expectations, relationship risks, service strengths, and comments that reveal confusion about the firm's service promise. Segment by household group, service tier, or advisor only if those variables were controlled in the household file beforehand. Do not invent tiers or advisor groups during interpretation to make a chart look tidier.
Caution: Dashboard patterns should guide management questions, not replace advisor judgment. When a single response signals relationship risk or a misunderstood service expectation, that calls for direct follow-up, not a chart.
Charles F. Steege of SFG Wealth Planning Services, Inc. and Jayme O'Donnell of Evergreen Advisors appear as historical examples connected to the methodology. Their experience is illustrative, not a template that every firm will reproduce.
Convert Feedback Into Practice Decisions
Findings become decisions when each issue gets an owner and an operating lever. Classify the finding, assign ownership, link it to capacity or service design, choose an action, and set a dated review. That sequence is the whole point of the audit.
Decision categories
- Client communication changes
- Meeting cadence adjustments
- Service-tier redesign
- Advisor workload balancing
- Referral-process refinement
- Follow-up conversations
Prioritize in order: address high-risk service gaps first, then improve repeatable client-experience systems, then reinforce positive feedback that reflects intentional service design. There is a trap in that last step. Leadership sometimes celebrates warm dashboard comments without comparing the household service promise to available meeting capacity, which leaves an unsustainable cadence quietly in place. Praise is not capacity.
Give every decision an owner, a target action, an affected household group, an expected operational change, and a review date. Keep the language honest — findings may reveal a gap, can inform a cadence change, or may help balance workload. None of them guarantee growth, retention, or referrals.
Main Point: A Client Audit is only useful when feedback changes operating behavior. The moment it becomes a static report, the exercise has failed regardless of how good the charts look.
Quality Control and the Repeat Cycle
Build the quality-control file at the end of this audit, not at the start of the next one. Later teams will not remember which households were excluded or which survey version ran.
Store these together: survey version, household definition, fielding dates, excluded periods, advisor or team assignments, dashboard export date, decision log, and follow-up commitments. Include the historical source boundary again — as commonly cited, the referenced Practice Audit survey is from 2001, last revised November 21, 2001 — so nobody mistakes it for a current standard. The dashboard export date matters most; it ties a decision log to the exact report leadership reviewed.
For a repeat cycle, retain assumptions and record changes. Separate true feedback shifts from changes caused by altered definitions, revised tiers, different fielding dates, or new communication language. Methodology drift makes year-over-year comparison unreliable, especially when household definitions or excluded seasonal periods move between cycles.
Responses
Leave a comment.