How do you document reviewer capacity before a practice sale?

Why is the reviewer often the hidden constraint?

A practice may have enough preparers but only one person who resolves difficult questions and approves completed work. If that person is the seller, a staff roster can overstate transferability. The operations hub starts with the actual work system: who makes the decisions, when review happens, and which responsibilities remain concentrated in the owner.

This definition combines skills and timing. A capable person who is unavailable during the deadline week does not solve that week’s shortage. An available person without the necessary competence or authority does not solve it either. Document both dimensions instead of treating every professional hour as interchangeable capacity.

Which kinds of review should be separated?

Identify preparation checks, supervisory review, technical consultation, final approval, and any formal engagement quality review. Use the names and requirements appropriate to the services actually provided. Bookkeeping, tax, advisory, and attest engagements can have different responsibilities; an internal workflow label does not determine the professional standard.

The AICPA and CIMA quality management guidance discusses implementation and monitoring for accounting and auditing practices subject to the relevant standards. It explains the move from the former quality control standard to quality management. Do not apply those requirements indiscriminately to every nonattest CAS activity or assume that a general article defines every engagement-specific duty.

Have the professional responsible for the firm’s standards map the actual requirements. Mark which roles require credentials, independence considerations, consultation, or other specific conditions. A buyer’s commercial staffing plan must fit that professional assessment. It should not replace a required role with a cheaper generic reviewer based solely on a spreadsheet.

What evidence belongs in a review register?

Use completed engagements to identify actual review stages, reviewer names, hours, delays, and rework. Include the service category, period, deadline, and reason for unusual review time. Preserve enough detail to distinguish a complex engagement from an inefficient handoff. Do not interpret every long review as poor performance without understanding the underlying facts.

If formal time records are incomplete, supplement them with dated workflow logs and documented estimates. Identify the estimates clearly and explain their limitations. A reconstruction can be useful, but it should not be presented as a complete contemporaneous time system. Avoid deriving precise margins from rough recollections without showing the uncertainty.

How should owner review time be captured?

Ask the owner to record technical decisions, client escalation, final approvals, and staff consultation over representative cycles. Short interruptions can accumulate into material work that never appears on a client timesheet. Capture the purpose and service category so a buyer can distinguish replaceable review tasks from ownership and business development responsibilities.

Compare that log with the team’s account. Staff may know that work pauses until the owner answers a recurring question. The workflow exception guide explains how those interruptions reveal dependence that routine task completion statistics can miss. Reconcile the records rather than assuming that either the owner or staff has a complete view alone.

Why should the calendar show weeks rather than just a year?

Map review demand to the actual production calendar. Include filing seasons, monthly closes, quarterly reporting, recurring board deadlines, planned leave, and overlapping client requests. Then map qualified availability to the same periods. Annual spare hours cannot be carried backward to a week when the review queue exceeds available resources.

Account for work arriving late. A reviewer may have a planned slot that disappears when client information arrives after the agreed date. Distinguish predictable concentration from avoidable delay and genuine unforeseen events. Each calls for a different response: staffing, improved information collection, revised scheduling, or an explicit escalation process.

What does an illustrative peak-week model show?

Consider a fictional week requiring 44 hours of routine review and 16 hours of technical consultation. The primary reviewer has 35 available hours after other responsibilities, and a qualified backup has 10. The assumed 60-hour demand exceeds the 45-hour supply by 15 hours. These figures illustrate the method; they are not a staffing benchmark.

Test whether the backup can perform the relevant work, whether consultation overlaps routine review, and whether deadlines can legitimately move. Do not solve the gap by counting the same person’s hours twice. A preparation plan might change scheduling, improve upstream work, or secure additional qualified support, but each option needs evidence and cost.

How should replacement cost be researched?

The BLS Occupational Employment and Wage Statistics data provide occupation and geographic wage estimates with stated vintages. Use them cautiously as a research reference. They do not establish the current compensation, benefits, recruiting cost, or immediate availability of a specific reviewer with the required technical background.

Seek current role-specific hiring evidence, lawful compensation information, and written proposals where appropriate. Include benefits, payroll taxes, onboarding, supervision, and scheduling limitations. Separate employee and contractor assumptions. If the model depends on a resource who has not agreed to participate, label that dependency instead of treating a hypothetical hire as secured capacity.

What does a useful backup test involve?

Assign the backup a defined set of work with the appropriate supervision. Record questions, review findings, time, and whether the final responsibility was completed by the intended person. Choose representative complexity rather than only the easiest engagements. A name on a continuity list is not evidence that the person can cover the actual role.

The cross-training guide uses observed assignments and escalation paths to assess readiness. Keep training separate from authority and qualification requirements. A competent staff member may still need a qualified final reviewer. Record what the test established and what remains dependent on the seller or another professional.

Which conduct and confidentiality issues matter?

The AICPA Code of Professional Conduct addresses professional competence and confidentiality for members within its scope. A staffing model cannot excuse work outside the firm’s competence or unrestricted sharing of client records. Review arrangements for outside support under the applicable professional, tax, contractual, and data protection requirements.

For diligence, begin with anonymized workload and role information where appropriate. Do not circulate sensitive personnel or client records simply to make a capacity table more convincing. Give authorized reviewers enough evidence to assess the assumptions through controlled access and the appropriate permissions.

What should the buyer receive at handover?

Provide the service-role map, recent review demand, peak calendar, documented owner tasks, tested backup coverage, and support for replacement costs. Include unresolved technical questions and open review work. The client file audit guide helps connect these responsibilities to the files and records the successor will actually receive.

The result is a capacity discussion that can be checked. A buyer can identify which work transfers, which resources must be added, and which assumptions affect the offer or transition. Documentation does not guarantee staff retention or professional compliance. It makes the remaining dependence visible while there is still time to address it.