Executive Summary
- Starting work with incomplete information costs 30-50 percent more total time than waiting for completeness — due to context-switching, rework, and additional review cycles.
- Postponement is a deliberate, criteria-based decision with specific triggers, deadlines, and consequences — fundamentally different from procrastination, which is avoidance without a plan.
- The decision matrix evaluates four factors: percentage of work affected by missing information, days until deadline, complexity of the missing information, and client responsiveness history.
- Postponement requires aggressive proactive communication — the client must know exactly what is missing, when it is needed, and what happens if it is not provided by the deadline.
- The clean queue effect improves prioritization — when incomplete engagements are removed from the active queue, preparers work only on engagements that can be completed efficiently.
- First-pass completion rate is the correct productivity metric — measuring engagements completed correctly the first time, not engagements started.
The "Start Now, Fix Later" Fallacy
The default instinct in accounting firms during busy season is to start every engagement as soon as possible. The logic seems sound: start early, get ahead, and fix any gaps as information arrives. In practice, this approach creates more work than it eliminates.
When a preparer begins a return with missing information, they build the return around the gap. They make assumptions. They leave sections incomplete. They create placeholder entries. Then, when the missing information arrives — days or weeks later — they must re-enter the workflow, recall the context of an engagement they set aside, identify which assumptions were correct and which need revision, and rework the affected sections. This re-entry costs 20 to 30 minutes of context recovery alone, before any actual correction work begins.
The "start now" approach also pollutes the review process. A return with flagged incomplete sections requires the reviewer to distinguish between "this is done and ready for review" and "this is incomplete and will change." The reviewer wastes time evaluating work that will be modified, and must review those sections again after the modification — creating a double review cycle for sections that could have been reviewed once if the work had started complete.
The total cost of starting incomplete is consistently 30 to 50 percent more time than starting complete. An engagement that takes 4 hours to complete with full information takes 5.5 to 6 hours when started with significant gaps — spread across multiple work sessions with context-switching overhead between each.
The Postponement Decision Matrix
Postponement is not a blanket rule — it is a decision that depends on specific conditions. The matrix evaluates two primary factors:
Factor 1: Percentage of work affected. How much of the engagement depends on the missing information? If a return is missing one W-2 out of four income sources, the affected percentage is low — roughly 15-20 percent. If the return is missing the primary source of income, the affected percentage is high — potentially 60-80 percent. The threshold matters because it determines whether the preparer can productively work on the unaffected portions.
Factor 2: Time until deadline. How many working days remain before the filing deadline or the client's expected delivery date? More time means more room for the postponement strategy to work — missing information can be obtained without deadline pressure.
The matrix produces four outcomes:
Start and Flag (Low Impact, Few Days): When less than 10 percent of the return is affected and the deadline is imminent, start the work and flag the incomplete section. The preparer can complete 90 percent of the return and address the gap when information arrives with minimal rework.
Postpone and Pursue (Low-Moderate Impact, Many Days): When the affected percentage is moderate and there is time, postpone the engagement and aggressively pursue the missing information. Set a specific date by which the information must arrive. Begin work only when the engagement is 90 percent or more complete.
Always Postpone (High Impact, Many Days): When more than 30 percent of the work depends on missing information and the deadline is comfortably distant, always postpone. Starting under these conditions guarantees extensive rework that wastes more time than the delay.
File Extension (High Impact, Few Days): When significant information is missing and the deadline is imminent, file an extension rather than rushing a return built on incomplete data. A rushed incomplete return is the worst outcome — it combines deadline pressure, low quality, and guaranteed rework into a single engagement. The extension creates time to obtain complete information and produce a correct return on the first pass.
The Hidden Rework Cost of Incomplete Starts
The rework cost of starting incomplete compounds through three mechanisms:
Context-switching overhead: Every time a preparer sets down an incomplete engagement and picks it back up later, they lose 15 to 25 minutes recovering context — remembering where they left off, what assumptions they made, and what still needs to be done. For a single engagement, this might happen two to three times as missing information trickles in, consuming 30 to 75 minutes of pure overhead that produces zero output.
Assumption rework: When the preparer built sections based on assumptions, some of those assumptions will be wrong. The correction is not just updating a number — it is tracing the impact of the incorrect assumption through every section it affected. A wrong income estimate changes AGI, which changes phase-outs, which changes credits, which changes the tax liability. One wrong assumption can cascade through a dozen calculations.
Double review: Review time increases because the reviewer either reviews the incomplete version (wasting time on sections that will change) or waits for completion (adding to the review queue). In either case, the total review time exceeds what a single review of complete work would require.
Track the rework cost in your firm by comparing total engagement time (including all work sessions, context recovery, and corrections) between engagements that started complete versus those that started incomplete. The data will make the case for postponement more convincingly than any argument.
Case Pattern: The Firm That Started Saying "Not Yet"
A 10-person tax firm had always operated on the "start everything immediately" model. During their busiest month, preparers averaged 4.2 work sessions per engagement — meaning they picked up and set down each return an average of 4.2 times before completion. Context-switching overhead consumed approximately 680 hours across the team during the season.
The firm implemented the postponement strategy with a simple rule: no engagement enters the production queue until it passes the preaccounting completeness gate at 90 percent or above. Incomplete engagements were moved to a "waiting — information needed" status with automated client follow-up sequences requesting the missing items.
The results were immediate. Average work sessions per engagement dropped from 4.2 to 1.4 — most returns were completed in a single sitting. Total production hours per return decreased by 22 percent because context-switching overhead was nearly eliminated. First-pass review acceptance rates increased from 62 percent to 81 percent because returns were prepared with complete information from the start.
The firm also discovered that their extension rate did not increase significantly. Most clients, when told specifically what was missing and given a clear deadline, provided the information within the timeframe. Only about 8 percent of postponed engagements ultimately required extensions — and those 8 percent would have required rework and possible amendments anyway if they had been started incomplete.
The net effect: the firm processed more returns with less total labor, higher quality, and fewer extensions — simply by waiting to start until the engagement was ready.
Making Postponement Work in a Deadline Environment
The primary objection to postponement is deadline pressure: "We cannot afford to wait — the deadline is approaching." This objection is valid in specific circumstances (the Start and Flag quadrant) but usually overstated. Two practices make postponement effective even during peak deadline periods:
Practice 1: Aggressive Proactive Communication. The moment an engagement enters "waiting" status, the client receives a specific, urgent communication: "To complete your tax return by April 15, we need the following items by [date — typically 10 business days before the deadline]: [specific list]. If we do not receive these items by [date], we will file an extension on your behalf to ensure accuracy." This communication does three things: it tells the client exactly what is needed, creates a clear deadline, and establishes the consequence of non-response.
Practice 2: Rolling Prioritization. Instead of working on engagements in the order they arrived, work on engagements in the order they become complete. When a previously postponed engagement reaches completeness, it moves to the front of the production queue because its deadline is now the most pressing. This rolling model ensures that the firm's production capacity is always focused on the engagements that can be completed most efficiently.
Together, these practices ensure that postponement does not create deadline crises — it prevents them. The alternative — starting every engagement regardless of completeness — creates its own deadline crises when returns stall mid-production waiting for missing information, clogging the workflow with partially complete work that cannot be delivered.
Postponement and Prioritization: The Clean Queue Effect
One of the most powerful side effects of postponement is what it does to your active production queue. When incomplete engagements are removed from the queue and placed in a separate "waiting" status, the remaining queue contains only engagements that are ready for uninterrupted completion. This is the "clean queue" effect.
A clean queue transforms prioritization from a complex juggling act into a simple ordering decision. Instead of deciding between 40 engagements — some ready, some partially ready, some barely started — the preparer is choosing between 25 fully ready engagements. Every item in the queue can be completed in a single work session. Every item will pass preaccounting completeness. Every item can move through production to review without stalling.
The clean queue also eliminates the cognitive burden of tracking incomplete work. When a preparer has 6 engagements in various states of partial completion, they carry the mental overhead of remembering what is missing, what they were doing, and what needs attention. When they have a clean queue of complete engagements, each one is a fresh start with full information.
The productivity improvement from a clean queue typically exceeds the productivity cost of postponement. Firms consistently report that their effective throughput increases even though they are starting fewer engagements — because the ones they start get completed faster and with fewer interruptions.
Implementation: Workflow Status and Communication Protocols
Implementing postponement requires three operational changes:
Change 1: Add a "Waiting — Information Needed" workflow status. Your practice management system needs a distinct status for postponed engagements — separate from "in progress" and "not started." This status should track what information is missing, when it was requested, when the follow-up reminder is scheduled, and what the deadline is for receiving it.
Change 2: Automate the follow-up sequence. When an engagement enters "waiting" status, an automated sequence begins: initial request (day 0), first reminder (day 3), second reminder (day 7), escalation to phone call (day 10), extension notification (day 14 or as deadline dictates). The sequence should be specific — each communication lists the exact missing items, not a generic "please send your documents" message.
Change 3: Establish the completeness threshold. Define the minimum completeness percentage required for an engagement to enter the production queue. For most firms, 90 percent is the right threshold — it allows minor missing items to be obtained during production while preventing the major gaps that cause rework. Engagements below the threshold remain in "waiting" status regardless of deadline pressure.
The exception to the threshold is the Start and Flag quadrant: engagements where less than 10 percent is affected and the deadline is imminent. For these, the preparer starts work with explicit documentation of what is incomplete and why the decision was made to proceed. This exception should be rare — if more than 15 percent of engagements are proceeding below threshold, the preaccounting process needs improvement.
Track the results rigorously for the first season: compare average engagement time, first-pass acceptance rate, rework frequency, and extension rate between postponed and non-postponed engagements. The data will validate the strategy and identify any adjustments needed for the following season.