What do completion totals fail to show?
A dashboard can report that every monthly close was delivered while concealing how often the owner rescued the process. Staff may have waited for a decision, missing permission, undocumented client preference, or technical answer. The operations hub recommends looking beyond the final status to the interventions required to achieve it.
A workflow exception is a task or decision that cannot proceed through its normal authorized process and requires a documented alternative response, escalation, or unresolved dependency.Some exceptions are appropriate. A novel technical question may require consultation, and an unusual client event may change the work. The goal is not to eliminate judgment. It is to distinguish planned professional judgment from repeated interruptions that depend on one person’s memory, access, or informal relationships.
What should be recorded when work stalls?
Record the task, service category, date, normal process, specific obstacle, responsible person, escalation, and resolution. Identify the evidence location and any effect on timing or additional work. An entry saying owner handled it is incomplete; the successor needs to know what decision or action was required.
Use neutral language. A late record may reflect a client delay, an unclear request, or an unrealistic schedule. A rework event may reflect preparation error or new information. Document the observable facts before assigning causes. A log that staff view as a blame register may discourage the accurate reporting needed for diligence.
Which categories reveal transfer dependence?
Separate missing information, unclear scope, technical review, system access, client approval, staffing, and scheduling. Add categories appropriate to the actual practice instead of forcing every event into a generic software list. Identify whether the owner was needed because of qualification, authority, knowledge, relationship, or simply habit.
| Category | Observed obstacle | Question to test |
|---|---|---|
| Knowledge | Only the owner recalls the treatment | Can the rationale be documented and reviewed? |
| Authority | Staff cannot approve the change | Who should hold the decision right? |
| Technical capacity | Review waits for one qualified person | Is competent backup available? |
| Access | A permission or recovery step stalls | Can authorized continuity be tested? |
| Client expectations | Informal promises override the scope | What was actually agreed? |
Do not classify every owner intervention as removable. Some responsibilities properly belong to a qualified principal or final reviewer. The transaction question is whether the post-closing firm has an appropriate person to perform them. A different role assignment may solve dependence without pretending that the underlying professional responsibility disappears.
How should the observation period be chosen?
Include representative work cycles and peak periods where practical. A quiet summer month cannot establish that a tax-season process works without the seller. A monthly accounting service may require several closes to reveal recurring problems. State the period and any unusual conditions, rather than presenting the sample as universal proof.
Compare the log with workflow records, staff interviews, and the owner’s calendar. Missing time entries can conceal brief but frequent decisions. Reconcile differences and preserve uncertainty where records are incomplete. Do not convert rough recollections into precise hours or a definitive earnings adjustment without adequate support.
What does an illustrative exception register show?
Suppose a fictional firm observes 30 interruptions in a month: 12 missing-input issues, eight scope questions, six technical review questions, and four access problems. The counts are invented to illustrate classification. A total of 30 does not tell the buyer whether the firm is worse than another practice with a different service mix or reporting method.
If the owner resolved all eight scope questions and all four access problems, investigate those dependencies separately. Written terms may clarify the first category, while named permissions and recovery arrangements may address the second. Technical questions may still require qualified review. Record the proposed remedy, responsible person, and test outcome rather than declaring all interruptions eliminated.
How does scope affect recurring exceptions?
The professional liability program’s engagement letter guidance discusses scope, responsibilities, deliverables, timing, and fees. Unclear service terms can help explain repeated requests for owner approval. The scope change guide connects those requests to the actual agreement and an appropriate approval process.
Review the gap between written terms and delivered work. If staff regularly perform extra work because the owner promised it informally, documenting a new procedure does not erase the client expectation. Address the relationship and contract issues through the appropriate communication and advisor review before relying on a different service boundary in a sale model.
Which technical exceptions should remain escalated?
Professional judgment should be assigned to people with the required competence and authority. The AICPA Code of Professional Conduct addresses responsibilities for members within its scope, including competence and confidentiality. Do not improve a completion metric by encouraging staff to make decisions beyond their appropriate responsibilities.
Use the reviewer capacity guide to distinguish routine review from technical consultation and any formal engagement quality review. Identify who handles each role after the sale and whether that person is available at the necessary deadlines. A fast escalation path needs qualified capacity, not merely a shorter approval chain.
How should access and data exceptions be handled?
Treat repeated access failures as continuity and security questions. IRS Publication 4557 discusses safeguards for taxpayer data, including appropriate access limits, authentication, training, and incident response considerations. A deadline problem is not a reason to share credentials indiscriminately or bypass approved protections.
Record the business issue without placing passwords or sensitive client contents in the log. Use an approved evidence location and limited permissions. When an event may be a security incident, follow the relevant response procedure instead of treating it as an ordinary workflow inconvenience. Distinguish recovery from simply restarting the task.
How can a remedy be tested?
Choose a representative future assignment and observe whether the new responsible person completes the required step with appropriate review. Record remaining questions, time, and any seller intervention. The cross-training guide emphasizes observed performance and escalation, which are stronger evidence than a training attendance list alone.
If the event does not recur during the observation period, state that limitation. Absence of a test opportunity is not proof of successful remediation. Some low-frequency but consequential issues may require a controlled scenario or separate continuity exercise reviewed by the responsible professional. Explain what the exercise established and what it could not establish.
What evidence should a buyer receive?
Provide a summary of categories, observation period, owner interventions, unresolved items, and tested remedies through a controlled diligence process. Connect each conclusion to supporting records. Avoid exposing unnecessary personnel or client information in an early presentation. The buyer should understand both the operating pattern and the limits of the sample.
Preserve the open register for handover with named responsibilities. Assign an owner and due date to unresolved remedies so that follow-up survives the handover. A useful log turns vague claims about an owner-run firm into specific questions about knowledge, authority, resources, and timing. It does not guarantee a higher value or a smooth transition. It helps the parties decide which dependencies can be reduced and which must be planned for explicitly.
A few common questions
What else should you know?
Is every workflow exception evidence of a weak practice?
No. Complex professional work can involve legitimate unusual events and judgment. The useful questions are whether the issue is recognized, handled by an appropriate person, documented, and prevented from becoming a recurring avoidable interruption. Compare similar services and circumstances before treating a high exception count as a general measure of poor performance.
Should exception logs identify clients in a buyer presentation?
Use appropriately anonymized summaries at the relevant stage and control access to detailed records. Client identity and file contents may be confidential or subject to additional restrictions. A buyer can begin assessing categories, workload, and owner dependence without receiving unrestricted client records. Review the disclosure process with qualified advisors before sharing sensitive evidence.
Can a written procedure eliminate an owner dependency?
It can explain the intended response, but the firm still needs a competent person with appropriate authority and available time to execute it. Test the procedure on representative work and record the results. A dependency is not necessarily removed because instructions exist or because staff attended a training session about them.
How many cycles should be observed before drawing a conclusion?
Choose cycles that represent the relevant work and its seasonal concentration rather than using a universal count. A monthly service and annual tax season expose different patterns. Explain the observation period and limitations, including unusual conditions. A short favorable sample should not be presented as proof that the process will work through every deadline.
Which sources support this guide?
Primary rules and guidance support the factual statements in this article. The worked examples and decision frameworks are original educational analysis.
- AICPA Code of Professional Conduct — American Institute of CPAs
- Publication 4557: Safeguarding Taxpayer Data — Internal Revenue Service
- Frequently Asked Engagement Letter Questions for Accounting Firms of All Sizes — AICPA Professional Liability Insurance Program