A client onboarding checklist template turns the messy stretch between a signed contract and live ads into a repeatable sequence. By the end of this guide you will have one that moves a new client from signature to launch without chasing logins, payments, or approvals. Before you start, gather three things: a list of the services you sell, a recent example of a client who onboarded badly (or well), and a place to store the template, such as a project tool, a spreadsheet, or your client dashboard.
Step 1: Map your current onboarding from signature to first campaign
Pull up your last two or three clients and write down every action that happened between "proposal accepted" and "ads go live." Include the messy parts: the email threads asking for the same login three times, the Page that turned out to be owned by a former employee, the first invoice that went out a week late. Use sent folders, chat history, and calendar entries rather than memory.
Next to each action, add two things:
- Owner: you, a team member, or the client.
- Rough time cost: both effort and elapsed time. Collecting ad account access might take you five minutes of effort but six days of waiting.
Once the list is annotated, patterns appear. In most agencies the stalls cluster around client-owned tasks: granting access, supplying assets, paying the first invoice, approving the first creative. That tells you where the checklist needs the most structure and the firmest deadlines.
A short example helps. Suppose a client signs on a Monday. You send the access request Tuesday, remind them Friday, receive partial access the following Wednesday, discover the pixel is missing, and launch eleven days after signing. Every one of those events becomes a row in your map, with its owner and delay.
Mistake to avoid: do not design the checklist from the ideal process in your head. A tidy list built from how onboarding should go produces a document nobody follows, because it ignores where things really break. Build from what happened, then fix it.
Step 2: Group tasks into phases with clear deadlines
Sort your mapped actions into four phases, in this order:
- Contract and payment: agreement, billing details, first invoice.
- Access and assets: platform permissions, brand materials, existing data.
- Strategy and setup: tracking, audiences, campaign structure, creative approval.
- Launch and handoff: final checks, go-live, first report scheduled.
Give each phase a target window counted from the start date, so the checklist works for any client regardless of calendar. As illustrations only, you might aim for payment items within 1 business day of signing, access and assets within 3 business days, setup within 5 more, and launch by day 10. Adjust these to your service mix. A single-platform lead generation account can move faster than an ecommerce client with a product feed to clean up.
Decide what is a blocker
For every task, make one call: is it a blocker (no launch until it is done) or a nice-to-have (useful, but launch can proceed)? A verified conversion event is a blocker. A set of customer testimonials probably is not. Label blockers explicitly, for example with a "BLOCKER" tag in the task name or a dedicated column. Done well, the checklist doubles as a launch gate: if any blocker is open, the campaign does not go live, and the client can see exactly why.
Step 3: Add the contract, billing, and payment tasks
This section covers the admin that, left vague, causes awkward conversations later. List each item as its own line with an owner and due date:
- Signed agreement received and filed.
- Scope and deliverables confirmed in writing (platforms, number of campaigns, creative volume, reporting).
- Billing contact named, which is often not the person you work with day to day.
- Payment method on file.
- First invoice sent.
- Ad spend responsibility recorded: does the client pay the platform directly with their own card, or do you bill spend through the agency?
That last item matters more than it looks. If the client pays Meta or Google directly, you need to confirm a valid payment method exists on the ad account before launch. If you front the spend and rebill, your cash flow is exposed, and your terms should say so plainly.
Write your payment rule into the checklist
Decide the rule you will actually enforce and add it as a blocker. A common one is "no ad spend before the first invoice is paid." Whatever you choose, state it in the contract and repeat it in the checklist so neither side is surprised. A rule that lives only in your head will be waived the first time a client pushes back.
Tip: set up recurring invoices or payment tracking during this phase, not after launch, so late payments surface in the first billing cycle rather than the third. If you use ClientPlug, its payment tracking keeps invoice status visible next to campaign data, which makes it easier to spot a client whose spend is running while their payment is overdue.
Step 4: Build the access and asset request section
Itemize exactly what you need, by platform, so the client gets one clear request instead of five emails. A typical list looks like this:
- Meta: partner access through Meta Business Manager to the ad account, the Facebook Page, and the pixel or dataset.
- Google Ads: a link request from your manager account to the client's account.
- Google Analytics and Tag Manager: user access at the level you need to view data and publish tags.
- Website or CMS: access only if tracking changes require it, or a named developer who can make them.
Menu names and permission levels in these platforms change often. As of 2026, verify the current steps in each platform's help documentation before you write client-facing instructions, and recheck them periodically. Link to the official guides inside your checklist rather than copying screenshots that age quickly.
Then add the asset requests: logos and brand guidelines, product feeds, existing creative, past performance reports, and customer testimonials. Past reports are especially valuable because they give you a baseline for Step 5.
Never ask for passwords. Request access through partner or admin sharing. It keeps the client in control, leaves an audit trail, and means you are not holding credentials that become a liability when someone leaves.
Add a fallback for clients without a clean setup
Some clients have no Business Manager, or they run their ad account from a personal profile. Include a branch in the checklist: if the client has no Business Manager, walk them through creating one and adding the Page and ad account; if the account sits under an individual's profile, have them add you as a partner or transfer ownership as the platform allows. A short, linked how-to for this case saves days of back and forth.
Step 5: Include tracking and measurement setup
Many agencies treat onboarding as paperwork and leave tracking to "later." That is how campaigns run for two weeks with no reliable conversion data. Make these items part of the checklist:
- Conversion events agreed with the client (a purchase, a form submission, a booked call) and documented.
- Pixel or tag installation verified on the live site.
- Conversion API configured for Meta.
- A test conversion confirmed in the platform before any spend starts.
Conversion API sends conversion events from the server to Meta, supplementing browser-based pixel data. Browser pixels can lose events to ad blockers and browser restrictions, so a server-side connection helps fill those gaps. Avoid promising clients a specific improvement in results from it; the effect varies by site and audience, and any figure you quote should come from a named source. If you want to shorten this task, ClientPlug can set up Conversion API in a few clicks.
Align on KPIs before you launch
Add a task to record three things in the client file: the primary goal (leads, ROAS, or cost per acquisition), a baseline drawn from past reports or the current account, and the reporting cadence. Without a baseline, you cannot show improvement, and without an agreed goal, every report becomes a debate about what success means. Mark the test conversion and the goal record as blockers.
Step 6: Script the kickoff call and communication rules
The kickoff call should follow a written agenda so it does not drift into a general chat. A workable one covers:
- Goals and the offer being promoted.
- Audience, and what the client has learned from past campaigns.
- Creative approval process: who approves, in what format, and how quickly.
- Budget and pacing, including how you will handle underspend or overspend.
- What happens in the first 30 days.
Then set communication expectations in writing and send them as a follow-up. Specify:
- The primary contact on each side.
- Response times you commit to, and what you expect in return.
- The channel: email, Slack, or a shared inbox. Pick one for day-to-day questions.
- Approval turnaround, and what happens if approvals are late.
The late-approval rule deserves care. For example, you might state that creative not approved within two business days moves the launch date by the same amount, or that you proceed with a pre-agreed default. Either works, as long as it is agreed before it is needed.
Finally, book the first report date and the first review call during the kickoff itself. Open-ended follow-ups tend to slip, while dates already on both calendars do not.
Step 7: Turn the checklist into a reusable template and test it
Choose where the template lives: a shared spreadsheet, a project board template, or a client record in a dashboard. Whatever you pick, each copy should carry the same fields: task, phase, owner, due date, status, and a "blocked by client" flag. That last flag lets you see at a glance which onboardings are stalled on your side and which are waiting on the client.
Resist the urge to create a separate template for every client. Build one base template, then add optional sections only where services truly differ: a Meta Ads add-on, a Google Ads add-on, an ecommerce feed section. Duplicate the base, attach the relevant add-ons, and you are done.
Pilot it on your next new client and keep notes as you go. Where did they get stuck? Which task did you have to explain twice? Which blocker turned out not to block anything? Revise the template based on those answers, then schedule a review every quarter and after any significant platform change, since access flows and tracking requirements shift.
Optionally, make reporting setup the final launch-gate item. If you use ClientPlug, you can configure automated white-label reports so the client receives results from the first week, which reinforces that onboarding led somewhere. Confirm the current report options in the product before you build this into your process.
Running the template on your next signed client
Your next new client is the real test. Run them through the template from the day the contract is signed, flag every task that stalls, and note who owned it. After the first campaign goes live, spend fifteen minutes updating deadlines, rewording unclear requests, and moving any task that keeps slipping into an earlier phase. Each pass should make the next onboarding shorter and calmer.
If you would like one place to keep client payments, campaign performance, tracking, and reports together, Learn more about our services.