Consulting client onboarding checklist: what to collect before kickoff

A consulting client onboarding checklist is the list of everything a firm needs from a new client before billable work can start: the agreements to sign, the questions to answer, the files to send, the people to name, and the access to grant, each with an owner on the client side and a date. A usable one is built once per engagement type, copied for each new client, and tracked item by item until kickoff. The welcome email and the project plan are separate things. The checklist is the gate between “we won the work” and “we can do the work.”

Most of what ranks for this query is a template inside a project-management tool. It lists six steps, tells the firm to send a welcome pack and a questionnaire, and at the contract step it tells the firm to go and pick an e-signature app. That is a checklist for the firm’s side of the week. The client’s side, where three documents arrive from three different senders and the finance contact has never heard of the project, is where onboarding stalls, and it is what this page covers.

What goes on a consulting client onboarding checklist?

Whether the firm calls it a consulting client intake checklist or an onboarding checklist, it has five groups, in the order they happen: agreements the client signs, questions the client answers, files the client sends, access the client grants, and the things the firm sends the other way.

Agreements come first because nothing else can be asked for until they are in place. A mutual non-disclosure agreement, if the proposal itself needed confidential information, or if the questionnaire will. The master service agreement, which carries the terms every project with this client will run under. The statement of work for the first project, which names the scope, the fee, the dates, and the deliverables. And the client’s own paperwork running the other way: a supplier registration form, their security questionnaire, and a request for the firm’s W-9 so their accounts payable team can set the firm up as a vendor.

Questions the client answers are the intake questionnaire. Who sponsors the work and who runs it day to day. Who approves invoices, and whether a purchase order number has to appear on each one. The problem in the client’s own words, what a good outcome looks like, and what has already been tried. The dates that cannot move: the board meeting, the budget cycle, the quarter close, the blackout weeks. How the client prefers to hear from the team.

Files the client sends are what most people mean by consulting client onboarding documents, and this is the group that varies most between firms:

• For strategy work, three years of financial statements, the last few board decks, the org chart, any market research the client has bought, and the reports of the last consultant through the door
• For operations work, process documentation, volume and throughput data by month, headcount by function, and the list of systems each team touches
• For technology work, architecture diagrams, the vendor and license inventory, the current contract with each vendor, and incident and outage logs
• For financial advisory, the trial balance, management accounts, bank statements, and budget against actual for the current year

Access the client grants is the group that gets forgotten until day one of the engagement. A folder in the client’s shared drive or data room, read access to whichever systems are in scope, a client email address or building badge if the team works on site, invitations to the standing meetings the work depends on, and a channel in the client’s chat tool if they run one.

The firm sends its own set back. A welcome pack that names the team, says how to reach each person, and describes the first two weeks. The firm’s Form W-9 and its banking details, because the client’s finance team will ask for both before the first invoice can be paid. The deposit or first milestone invoice. The calendar invitation for kickoff, with an agenda attached.

Written out in full, the master list runs past thirty items. No client should ever see all thirty. A strategy engagement at a company that has already signed the MSA needs the SOW, the questionnaire, seven files, and two kinds of access. That is the copy the client gets, and it fits on one screen of a phone.

What order should the agreements be signed in?

NDA, then MSA, then SOW. Each one is the condition for the next, and each one should go out the moment the previous one comes back.

The NDA goes first because it governs the information in everything that follows. The Legal Information Institute’s definition is the one to send a client who asks why: it is the contract that says what each side may do with what the other side discloses. Most firms make it mutual, because the client will see the firm’s methods and the firm will see the client’s numbers. If the proposal already needed confidential information, this one was signed weeks ago and the checklist just records that fact.

The MSA is the slow one. It sets payment terms, liability, intellectual property, termination, and dispute handling for every future project, and on the client side it is the document that goes to legal or procurement. Three to ten business days is normal at a mid-size company, longer if the client insists on their own paper. Send it before the SOW, not with it, and draft the SOW while legal is reading the MSA. The SOW then arrives as a two-page document that points at terms the client has already agreed, and it is signed in a day.

The SOW is where the scope lives. Deliverables, dates, fee, the assumptions the fee depends on, and the name of the person on each side who accepts a deliverable. It should never be signed before the MSA, because a SOW without a master agreement behind it has to carry every term itself and becomes the slow document.

All three can be signed electronically. The federal ESIGN Act says a contract may not be denied effect only because it is in electronic form, and the same rule applies to the NDA, the MSA, and the SOW. What matters to the firm is the record: who signed, when, from where, and what the document looked like at that moment.

This is the step where the ranking templates say to go and pick a signing app, and the cost of that choice lands on the client rather than the firm. The NDA arrives from the signing tool’s address. The questionnaire arrives from the project tool’s address. The file request arrives from the shared drive’s address. The welcome pack arrives from the partner’s own inbox. Four senders, four threads, and a sponsor who forwards the wrong one to the wrong colleague. A client who experiences onboarding as one link that shows each next step as the previous one finishes signs faster, because they are never looking for the email.

A signed proposal is not a signed SOW. Firms that start work on an accepted proposal alone, and sort the MSA out later, are the firms that end up in a scope argument in month two with nothing to point at.

How to write the client intake questionnaire for consultants

Ask for what only the client knows. Collect what the firm can find on its own. Those two rules remove half the questions from most questionnaires.

The client knows who approves invoices, which dates cannot move, what was tried last year, and what the sponsor is actually worried about. The firm can find the company’s revenue, its headcount, its public filings, and its org chart from its own website. A questionnaire that asks the client to type in things the firm could have looked up reads as laziness, and the client answers it in the same spirit.

Put the names first. Sponsor, day-to-day contact, invoice approver, and the person who owns the data the work needs. Every other item on the checklist gets assigned to one of those four people, so the questionnaire cannot be finished until they are named, and nothing else can be sent until the questionnaire is back.

One question per fact, in plain words. “Who signs off on the final deliverable?” comes back with a name. “Describe your governance and approval structure” comes back a week later with a paragraph that still does not contain a name.

Keep it under fifteen questions and branch by engagement type. The operations questionnaire asks about sites, shift patterns, and monthly volumes. The technology questionnaire asks about the systems in scope and the last outage. The strategy questionnaire asks about the board, the competitors the client watches, and the number the CEO is measured on. One master questionnaire with forty questions, most of them marked “if applicable,” is the version that comes back half-empty.

Ask for the file, not a description of the file. “Upload your current org chart” produces an org chart. “Describe your organizational structure” produces a paragraph that a consultant then has to turn into an org chart. Any question whose real answer is a document belongs in the files group, with an upload slot, rather than in the questionnaire.

Leave out the questions whose only purpose is to make the firm look thorough. “What are your company values?” and “Describe your culture” go unanswered, and nothing in week one depends on them. The kickoff meeting is the right place for those conversations.

The questionnaire is itself an item with a state. It goes out, it comes back partly done, someone at the firm reads it and finds that the invoice approver is blank and the sponsor wrote “TBD” for the data owner. Treat it the way a file is treated: arrived is not the same as usable, and the gaps go back to the client as named items rather than as “please complete the questionnaire.”

Who at the client owes what?

The single largest cause of a late kickoff in professional services client onboarding is that the checklist was sent to a company and not to a person.

A consulting engagement at any client past about fifty people has four or five owners on the client side. The sponsor, usually a vice president or a business owner, who signs the SOW and approves deliverables. Finance or accounts payable, who set the firm up as a vendor, issue the purchase order, and pay the deposit. Legal or procurement, who redline the MSA. IT, who grant system access and provision the email address. And the operator, a controller or an operations manager or a systems lead, who holds the data the work needs.

Send the sponsor the whole list and the sponsor becomes the bottleneck. They forward the MSA to legal on Tuesday, the access request to IT on Thursday, and forget the data request until the firm asks about it. Nothing on the list is the sponsor’s own job, so nothing on the list gets done on the sponsor’s own timetable.

The fix is one item, one owner, one message. Legal gets the MSA and only the MSA. Finance gets the W-9, the banking details, and the deposit invoice, and sends back the purchase order. IT gets the access request with the names and start dates of the team. The controller gets the file list for the financial data. The sponsor gets the SOW, the questionnaire, and a view of the whole list so they can see what is outstanding without owning any of it. The firm asks the sponsor for those four names in the first conversation after the proposal is accepted, before anything is sent.

The client’s own vendor onboarding runs in the opposite direction and needs its own owner at the firm. Someone has to fill in the supplier registration form, answer the security questionnaire, and send the W-9, and if that someone is the partner who sold the work, it happens in week three. Put it on the checklist as a firm-side item with a firm-side owner and a date.

Where the same client comes back for a second project, most of this is already done. The MSA is signed, the vendor record exists, the names are known. The checklist for a repeat engagement is the SOW, a shorter questionnaire, and the new files and access, which is why the template has to be built per engagement type and then trimmed per client rather than written fresh each time. The consulting firm solutions page shows what a per-engagement template looks like when it is split by who at the client owes each item.

How do you know on day four what is still missing?

Kickoff is in ten days, eleven items went out, and some of them came back. What does the engagement manager look at on Thursday morning to decide who to chase?

The answer is a state for each item, and there are four that matter. Requested, meaning the item went out and nothing has come back. Arrived, meaning something is in the slot. Usable, meaning someone at the firm opened it and confirmed it is the right thing. Accepted, meaning it has been filed and the work can proceed on it. A state per item is what turns a consulting client onboarding checklist from a document into a tracker.

The gap between arrived and usable is where consulting onboarding hides its delays. The “financial statements” turn out to be a forty-page general ledger export with no income statement in it. The org chart is dated 2023. The read-only system access works, but expires in seven days because IT provisioned a contractor account by default. The data room link opens a login page for an account the firm does not have. Each of those reads as done on a tracker that only knows “arrived,” and each of them is discovered on day one of the engagement by the consultant who needed it.

So the usable check happens the day the item lands, by the person who will use it. A file that arrives on day three and is found wrong on day three costs one message. The same file found wrong on kickoff day costs the first week of the engagement.

Reminders go to the owner and name the item. “Your onboarding is incomplete” sent to the sponsor gets nothing. “Still need read access to the ERP for Priya and Marcus, starting the 29th” sent to the IT contact gets a reply the same day. Every reminder should be generated from the items still in the requested state, addressed to whoever owns each one, so that nobody is chased for something they already sent. A controller who uploaded the trial balance on Monday and is chased for it on Wednesday stops reading the firm’s messages.

Cadence is anchored to the kickoff date, not to when the request went out. A reasonable pattern for a two-week onboarding sends a reminder on day four, another on day eight, and a phone call from the engagement manager on day ten for anything still open. Email carries the list, a text carries the reminder, and the comparison of SMS and email for document requests covers when each one works.

Put a cutoff in the welcome pack. “Kickoff on the 29th depends on the MSA, the ERP access, and the last three years of financials being in by the 24th. If any of those is late, kickoff moves.” A date with a consequence, said upfront, does more than any number of polite nudges, and it makes the sponsor an ally in chasing their own colleagues. The alternative is a kickoff meeting that goes ahead with nothing to work on, followed by a week of billable time the firm cannot invoice.

Source Global Research reported in 2024 that 35% of consulting firms name client onboarding as their top operational challenge, and the hidden cost of chasing clients for documents works through what follow-up on unclear requests costs in staff hours for a firm of a given size.

What does the two weeks before kickoff look like?

A working timeline for a new client, counted from the day the proposal is accepted, assuming the NDA was signed during the sales process.

Day zero. The sponsor gets a call, not an email, and the firm asks for four names: invoice approver, legal contact, IT contact, and data owner. The welcome pack goes out the same afternoon with the kickoff date and the cutoff date in it. The MSA goes to legal. The questionnaire goes to the sponsor. The firm’s W-9, banking details, and deposit invoice go to finance, with a request for the purchase order.

Days one to three. Legal reads the MSA. The sponsor works through the questionnaire. Finance sets the firm up as a vendor. The firm drafts the SOW from the proposal and holds it. On day three the engagement manager reads whatever has come back from the questionnaire and sends the data owner the kickoff document request list, and sends IT the access request with team names and start dates.

Days four to eight. The MSA comes back signed, usually on day four or five, and the SOW goes out within the hour. Files arrive from the data owner and each one is checked the day it lands. Access is provisioned and someone at the firm logs in to prove it works. The day-four reminder goes to whoever still owes something. The sponsor signs the SOW.

Days eight to ten. The day-eight reminder goes out. On day ten the engagement manager phones the owner of anything still in the requested state. The cutoff is the same day or the next. If a blocking item is still missing, kickoff is moved now, while the calendar can absorb it, and the sponsor hears why.

Days eleven to fourteen. The team reads the files, prepares the kickoff, and starts the engagement with everything in hand.

When the client’s procurement process takes six weeks instead of one, the timeline splits rather than stalls. The MSA runs on procurement’s calendar, and the questionnaire, the files, and the access run on the firm’s calendar. Some firms will start discovery under a signed NDA and a signed SOW on the client’s own terms while the MSA is negotiated, and some will not start anything until the MSA is back. Either is a firm’s own policy to set. What no firm should do is let the slow document hold up the fast ones.

The same shape applies to the engagement letter workflow that accounting firms run in December, where a batch of letters goes out and the firm chases only the unsigned ones. The consulting version has fewer clients and more documents per client, but the mechanics of send, track, and chase-by-name are the same.

Where zendoc fits in client onboarding

zendoc turns the checklist into a workflow template per engagement type, spins up one instance per client, and sends each person on the client side a single link by SMS or email that opens their own items on a phone with no password and no signup form. The NDA, MSA, and SOW are signed inside that same link with built-in e-signature and a tamper-evident audit trail, as ordered steps in one workflow, and the questionnaire and file requests sit beside them. Every upload is read on arrival by AI that classifies the file and flags a wrong document type, an incomplete file, or an unreadable scan as a suggestion for staff to review, and reminders go out automatically to whoever still owes an item. The signed PDFs and the collected files download for filing wherever the firm keeps its engagement records, and the pricing page lists current rates.