A new client can be fully signed and still not be ready for the first close. The challenge is deciding when work moves from setup into delivery, especially when a few open items remain. A broad onboarding checklist tells the firm what to collect. A first-close readiness gate answers a different question: can the assigned team start this period, and what specifically is still blocking it?

This guide focuses on that handoff decision. It does not replace your engagement acceptance, client identity checks, jurisdiction-specific requirements, or document list. Adapt the gate to your firm’s approved process and the service you agreed to provide.

Define “ready for first close” before the work arrives

Write a short start rule for each recurring service. For example: “The first bookkeeping period is ready when the service scope and period are confirmed, the delivery owner accepts the handoff, essential access is in place, and each remaining dependency has an owner and next date.” Keep this rule concrete enough that two team members would make the same call.

The rule should separate an item that prevents all work from an item that only blocks one step. Missing bank access may stop reconciliation while another agreed setup task can continue. A question about a nonessential coding choice may be recorded for review without pausing the whole engagement. The client and firm should not be left guessing which situation applies.

Seven checks for the handoff

1. Confirm the work being handed over

Record which service, entity, and first period are moving to delivery. Include the agreed cadence and the person who can approve a change. Avoid reopening the entire sales conversation; capture only the decisions the delivery team needs to start the work that was sold.

2. Ask a delivery owner to accept the handoff

Name one person accountable for the first close and make sure they have accepted the assignment. A relationship owner can stay responsible for the client relationship, while a preparer or manager owns the delivery. If those roles are the same, say so. Unassigned work is not ready merely because it appears in a system.

3. Separate blockers from follow-up items

For every open item, record whether it blocks all work, one task, or no current task. Add a brief reason. This is more useful than a single “onboarding incomplete” label because the team can see what may proceed and what must wait.

4. Give every dependency an owner and a next date

A client-side dependency needs a named contact and a due date. A firm-side dependency needs a responsible teammate and a target date. If a vendor, previous accountant, or another party is involved, name who will follow up. Avoid vague statuses such as “waiting” with no next action.

5. Map the first period’s sequence

List only the steps that must happen in this first cycle, in order. Mark the steps that depend on a client answer or a review. This reveals whether the proposed due date is achievable and where the work will pause if a dependency slips. Build the recurring template after the first period and handoff sequence are understood.

6. Set a pause and escalation rule

Agree what happens when a critical item misses its date: who contacts the client, when the manager is alerted, and whether the delivery date needs to change. Tell the client what is affected in plain terms. Do not let a blocked engagement look active simply because nobody changed its status.

7. Review the first close and improve the gate

After delivery, compare the planned handoff with what actually blocked the work. Which item arrived late? Was the owner clear? Did the team wait for information it did not need yet? Change the service template only when the same lesson is likely to apply to future clients. Keep client-specific exceptions in that client’s record.

Why the owner and capacity check matter

A handoff is not complete if nobody has room to take the work. Check the assigned person’s workload and the due date before confirming the start. AICPA’s 2026 CPA Firm Top Issues Survey identified managing staff workload and capacity among firms’ current issues; technology and AI change management ranked as a leading anticipated issue across firm sizes. The survey had 629 respondents and ran online from April 20 to May 22, 2026. It represents U.S. firms, not a Canadian capacity benchmark, but it supports treating ownership and workload as part of the process rather than an afterthought. AICPA & CIMA, June 23, 2026.

Make exceptions visible without restarting onboarding

When a first-close dependency is late, update the item, not the whole relationship. State what can continue, what is paused, who is taking the next action, and when the client will hear from the firm again. If the delay affects scope, fees, or the promised completion date, route that decision to the person authorized to agree to the change.

This approach is useful whether the firm collects answers through a meeting, a form, or a portal. Practitioners discussing new-client questionnaires in July 2026 described using forms in different ways: some send them to clients, while others treat them as a call guide. That is anecdotal discussion rather than a representative survey, but it illustrates why the handoff needs a clear owner and follow-up method regardless of the intake format. r/Bookkeeping discussion, July 2026.

Where practice software can help

A workflow tool should make the owner, next step, due date, and blocker visible together. Awditify’s in-app client onboarding guide describes templates for repeatable steps, client and firm tasks, owners, due dates, next-step visibility, late-step views, and client portal steps. Its public firm page also describes engagement and task templates, recurring schedules, document requests, and deadline visibility. These features can support the handoff; assess the actual plan and team workflow before choosing software. Awditify for Firms · Firm pricing.

Frequently asked questions

When is a new accounting client ready for the first close?

Use the start rule for the service. At minimum, the scope and first period should be clear, an accountable delivery owner should accept the work, and any remaining dependency should have a status, owner, and next date.

Should a firm pause all work when a client is late with one item?

Not automatically. Identify which task depends on the item and whether other agreed work can continue. Explain any delay that affects the client’s deliverable or due date.

Who should own an onboarding blocker?

Every blocker needs one person responsible for the next action. The client may need to provide the item, while a firm employee owns follow-up and communicates how the delay affects the work.

Turn a signed engagement into owned work

A first-close readiness gate makes the transition from accepted client to active delivery explicit. It gives the team a shared definition of “ready,” makes work that can continue visible, and gives every blocker a next action.

If your handoffs depend on people reconstructing status from email, see how Awditify for Firms connects onboarding, client requests, engagements, recurring work, and deadlines. See Awditify for Firms · Book a demo