Client Onboarding Checklist, Template, and Process Steps for New Clients

The client onboarding checklist

Copy this and adapt the specifics to your service. The phase order matters more than the individual items: each phase exists to unblock the next one.

PHASE 1. AGREEMENT (day 0)
Engagement letter or contract signed by both parties, with scope, fees, payment terms, client responsibilities, and how either side ends it. Do not start work on a verbal yes. · Deposit or first invoice sent, and payment method set up. · Internal record created: client file, matter or job code, billing profile.

PHASE 2. DOCUMENTS AND ACCESS (days 0 to 3)
Send the full document and access request as one list, not in pieces. · Legal and tax identifiers, entity documents, and any authorizations your work requires. · System access: accounting file, bank or payroll portal, ad accounts, CRM, shared drive, whatever the work actually touches. · Named contacts: who approves, who pays, who answers day-to-day questions.

PHASE 3. WELCOME PACKAGE (day 1 to 2)
A short welcome message from the person who will actually run the account. · A one-page overview of what happens over the next 30 days and what you need from them. · Your intake form. · Who to contact for what, and your normal response times.

PHASE 4. KICKOFF CALL (week 1)
Introductions on both sides with roles, not just names. · Confirm goals in the client's words. · Walk the timeline and the first deliverable. · Agree how you will communicate and how often. · Name the open items and who owns each.

PHASE 5. FIRST MILESTONES (weeks 1 to 2)
Write down what done looks like at 30, 60, and 90 days, and send it to the client. · Schedule the recurring meeting now, not later. · Set up the internal workflow, templates, and any automation the account needs.

PHASE 6. FIRST DELIVERABLE (weeks 2 to 4)
Ship something real and early, even if it is small. The first deliverable is what converts a signature into confidence. · Ask for feedback on it explicitly.

PHASE 7. THIRTY-DAY CHECK-IN
A short call: is this working, what is confusing, what did we get wrong. · Close out every open onboarding item or move it into normal service. · Note what slowed this onboarding down and fix it in the template before the next client.

One structural rule holds the whole thing together: every item above belongs to exactly one person, with a date. Shared checklists where "the team" owns an item are how onboarding stalls, because a document nobody is specifically waiting on is a document nobody chases.

The documents and access to collect before you start

This is phase 2, and it is where onboarding usually breaks. The failure pattern is always the same: you ask for three things, get two, start work anyway, hit the missing one a week later, and now you are chasing a client who has mentally moved on. Send one complete request instead, with a deadline and a reason attached to each item.

For a US accounting or bookkeeping firm, the standard collection is the engagement letter, the client's entity and identification details, access to the accounting file and the read-only bank feed, prior-year financials and returns, the payroll system if you are touching it, and the authorizations that let you deal with the IRS on the client's behalf. Two IRS forms do different jobs there and are routinely mixed up. Form 8821, Tax Information Authorization, lets a client authorize a person or firm, in the IRS's words, to "inspect and/or receive your confidential information verbally or in writing for the type of tax and the years or periods listed on the form." Form 2848, Power of Attorney and Declaration of Representative, goes further: "Use Form 2848 to authorize an individual to represent you before the IRS." Information access versus the authority to act. Collect the one the engagement actually needs, and collect it during onboarding rather than in the middle of a notice response.

Also handle the direction of paperwork that runs the other way. If your client will pay your firm as a vendor, they will ask for your Form W-9 so they have your correct name and taxpayer identification number on file for their information returns, so keep a current one ready to send rather than treating it as a surprise. For non-accounting firms the list changes but the principle does not: brand assets and ad account access for a marketing engagement, conflict check and matter details for a legal one, the systems and stakeholder list for a consulting one.

• Send one complete request, not a trickle of individual asks
• Attach a reason and a date to every item so it is clear why it blocks the work
• Collect authorizations during onboarding, not during the first emergency
• Confirm access actually works before the kickoff call, not during it
• Keep your own W-9 and insurance certificate ready to send back

A worked example: onboarding a new bookkeeping client

Here is the checklist applied to a real-shaped engagement, a monthly bookkeeping client at a 12-person services business, so the timing is concrete.

Day 0. Engagement letter signed electronically, scope stated as monthly close by the fifteenth business day, fees and the annual price review in writing. Job code created. First invoice sent with the payment method set up in the same message.

Day 1. One request email: accountant-level access to the accounting file, read-only bank and card feeds, prior-year return and trial balance, payroll provider login or reports, the chart of accounts as it stands, and the name of whoever approves payments. Each line says why it is needed and asks for everything by day 5.

Day 2. Welcome package: a note from the bookkeeper who will run the account, a one-page timeline through the first close, the intake form, and the response-time commitment.

Day 5. Access confirmed and tested. Anything missing gets a named chase, not a general reminder.

Week 1. Kickoff call, thirty minutes: how the business actually makes money, what the owner wants to see monthly, which reports they read and which they ignore, who to ask about odd transactions, and what the cleanup will look like.

Weeks 1 to 2. Cleanup scope written down and priced separately if it is real work. Milestones stated plainly: catch-up complete by day 30, first clean monthly close by day 45, reporting pack agreed by day 60.

Week 4. First deliverable, even if the books are not fully caught up: a current cash position and a list of what the cleanup found. Something real, early.

Day 30. Check-in call. Confirm the reporting format, close the onboarding items, and write down the one thing that slowed this down for the next client.

The detail that makes this version work is that the cleanup gets scoped and priced before it starts. Unscoped historical cleanup is the most common way a bookkeeping engagement goes underwater in month one, and onboarding is the only moment where raising it feels normal rather than like a renegotiation.

The client onboarding form: what to actually ask

An intake form earns its place only if every answer changes something you will do. Long forms full of questions nobody reads are why clients stop filling them in. Keep it to the fields that route work, set expectations, or prevent a mistake.

The fields worth having: legal entity name and structure, billing contact and billing address, the day-to-day contact and the approver (which are often different people, and assuming they are the same causes most early friction), the systems you will need access to, the client's stated goal for the engagement in their own words, any hard deadlines already on their calendar, how they prefer to be contacted, and anything a predecessor firm left unfinished. That last question is the highest-value one on the form and almost nobody asks it.

Send the form as part of the welcome package rather than before the agreement is signed. Asking a prospect to complete an intake form during the sale is friction in the wrong place; asking a signed client to complete it as step one of a clear process is just organization.

Where client onboarding actually goes wrong

Almost every onboarding problem traces to one of four causes, and none of them is a missing template. The first is starting work before the agreement is signed, which turns every later scope conversation into an argument. The second is collecting documents in pieces, which stretches a two-day phase into three weeks. The third is an unowned item: a checklist where everything is technically visible to everyone and therefore chased by no one. The fourth is silence, where the client hears nothing for ten days after signing and starts wondering what they bought.

The fix for the last two is the same and it is unglamorous: someone has to notice that an item is late and send the follow-up. That is a tracking and nudging job, it repeats identically for every client, and in most small firms it lands on whoever has the least protected calendar. It is also the part that gets dropped first in a busy week, which is exactly why onboarding quality varies so much between a firm's first client of the quarter and its fifth.

The structural answer is to write the process down once, as a repeatable procedure with owners and dates, instead of relying on memory. If you do not already have one, the format in our standard operating procedure template is the right container for it, and the kickoff call runs better off a written outline from the meeting agenda template.

• Work started before signature: every scope conversation gets harder
• Documents requested in a trickle: a two-day phase becomes three weeks
• Items owned by "the team": nobody chases what nobody is waiting on
• Ten days of silence after signing: the client starts doubting the decision

Running onboarding without it eating the week

Look at what the checklist above actually consists of. A handful of judgment calls (scope, pricing, what the cleanup is worth) and a long tail of coordination: sending the same document request, confirming access arrived, booking the kickoff, writing up what was agreed, chasing the two items that did not come back, and reminding someone that the thirty-day check-in is due. The judgment is the work you are paid for. The coordination is the part that decides whether the client thinks you are organized, and it is pure repetition.

That coordination layer is what Officeagent runs. It drafts and sends the document request from your standard list, chases the items that have not come back without anyone remembering to, books the kickoff and the recurring review against real availability, turns what was agreed on the call into tracked items with an owner and a due date, and files the signed agreement and returned paperwork where the next person will find it. Every message it drafts and every document it files waits for a human approval before anything happens, which is the control you want on anything a client sees during their first month with you.

If your firm onboards more than a couple of clients a month, the compounding win is not any single automation. It is that the fifth client of the quarter gets the same onboarding as the first.