Client onboarding checklist: the first 14 days

Good client onboarding means that within 14 days of the signature, the client knows who they work with, how to reach you, what happens next and when, and you have everything you need to start: access, contacts, approvals and billing details. Send a welcome email on day one, hold a kickoff by the end of the first week, collect logins safely, agree on communication rules in writing, and deliver one small, visible win before day 14. Do it the same way for every client, and the rest of the project gets noticeably easier.

#Why the first 14 days matter

Right after signing, a client is at their most engaged and their most anxious. They have just committed budget and they want proof it was the right call. If they hear nothing for a week, they fill the silence with doubt. If they get a clear plan, a named contact and early progress, they relax and start trusting your process.

The first two weeks are also when most avoidable problems are planted. A missing billing contact becomes a late invoice in month two. An unclear approver becomes a stalled design round. Admin access sent in a chat message becomes a security issue nobody owns. A checklist turns all of this into routine.

#The onboarding checklist

Work through these items in order. Each one has a clear owner on your side and a clear output.

1. Send the welcome email

Send it within one working day of the signature. It confirms the start, introduces the main contact, lists what you need from the client and proposes kickoff times. A template is below.

2. Run the kickoff meeting

The kickoff is where both teams meet, confirm goals and agree on how the project will run. Book 60 minutes, send the agenda in advance and record decisions in writing the same day. A full agenda is further down.

3. Collect access and logins safely

You will usually need access to hosting, domains, analytics, the CMS, ad accounts or social profiles. Ask for exactly what the scope requires and nothing more. Where the platform supports it, ask the client to invite your team as users rather than sharing their own password. When a shared login is unavoidable, have it entered into a secure vault, not pasted into email, chat or a shared document.

4. Confirm roles and contacts

Write down who does what on both sides. On the client side you need at least: a day-to-day contact, the person who approves deliverables, the person who pays invoices, and an escalation contact. On your side: the project lead, the main specialists, and who covers when the lead is away. Most delays later in a project come from not knowing who has the final say.

5. Agree on communication rules and response times

Decide where conversations happen, how quickly each side replies, and what counts as urgent. For example: project messages in one place, replies within one working day, urgent issues by phone, and a weekly status update every Friday. Put these rules in writing so nobody has to guess, and so requests sent to a designer's personal phone have a polite place to be redirected.

6. Share the project plan and milestones

Within the first week, the client should see the plan: milestones, rough dates, and what you need from them before each one. List the client's own dependencies (content, feedback, brand files) next to the dates. A plan they can check at any time cuts down on "where are we?" emails.

7. Set up the approvals process

Agree on how a deliverable is approved: who approves, in which format, how many revision rounds are included, and how long the client has to respond before the timeline moves. An approval should be a recorded action, not a thumbs up buried in a thread. This also protects you from scope creep later, which we cover in our guide to stopping scope creep.

8. Confirm the billing contact and payment details

Ask who receives invoices, whether you need a purchase order number or vendor registration, and how the client prefers to pay. Send your payment details to the billing contact directly. Sorting this out in week one is far easier than discovering it when the first invoice is already overdue. The payment terms themselves belong in the signed agreement; see agency agreement clauses.

9. Deliver a first quick win

Pick something small and visible that you can finish before day 14: a technical audit, a moodboard, a fixed bug on the current site, a set of tracking events, a content inventory. It shows momentum, gives the client something to share internally, and lets you test the approval process on low-stakes work.

#The 14-day plan at a glance

Adjust the days to your project size, but keep the order.

#Welcome email template

Subject: Welcome aboard: next steps for your new website

Hi Alex,

Thank you for choosing us. We're looking forward to working with you and the team.

I'm Jamie, and I'll be your project lead. I'll be your main point of contact from here to launch, and you can reach me at this email or on 555 0100 during working hours.

Here is what happens next:

1. Kickoff meeting. Could you pick a 60-minute slot from the options below? I'll send an agenda two days before.
2. Project space. You'll receive a separate invitation to our client portal, where you can follow the plan, approve work and message the team.
3. Access. I've attached a short list of the accounts we'll need. Please don't send passwords by email; the list explains the safest way to share each one.
4. Billing. Who should receive invoices? If you use purchase orders or need us registered as a vendor, let me know and we'll handle it this week.

If you have questions before the kickoff, just reply here.

Best, Jamie

#Kickoff meeting agenda template

Send this agenda two days before the meeting, along with any questions the client should think about in advance.

1. Introductions (5 minutes). Who is in the room and what each person does on the project.
2. Goals and success (10 minutes). Why the project exists, what success looks like in six months, and how it will be measured.
3. Scope recap (10 minutes). What is included, what is not, and how change requests work.
4. Plan and milestones (10 minutes). Key dates, client dependencies, and known risks such as holidays or launches.
5. Roles and approvals (5 minutes). Who approves each deliverable, revision rounds included, and response windows.
6. Communication rules (5 minutes). Where messages go, response times, what counts as urgent, and the weekly update.
7. Access and billing (5 minutes). Open access items and the billing contact.
8. Next steps (10 minutes). Actions with owners and dates, plus the first quick win.

End by reading the action list aloud, then send it in writing the same day.

#Common onboarding mistakes

These come up again and again, and each one is easy to prevent.

• Going quiet after the signature. Even two days of silence can make a client wonder whether they chose well. Send the welcome email on day one, even if the kickoff is a week away.
• Collecting passwords in email or chat. Credentials end up in inboxes, screenshots and old threads for years. Use invitations where possible and a secure vault where not.
• Asking for more access than the scope needs. Full admin rights for a small task create risk for both sides. Ask for the minimum, and plan when to remove it.
• No named approver. Feedback from five people with no final decision maker stalls every round. Name one approver at kickoff.
• A kickoff without written notes. If decisions live only in memory, both sides will remember them differently. Send notes the same day.
• Leaving billing until the first invoice. Finding out about purchase orders after the due date delays payment by weeks.
• Different onboarding for every client. Improvising each time means things get missed. Keep one checklist and improve it after every project.

#Questions agencies ask

How long should client onboarding take?

For most agency projects, two weeks is enough to complete onboarding and start regular delivery. Small projects can compress it into a few days, while larger ones with many stakeholders may need longer. What matters is that every item on the checklist is finished before the main work depends on it.

Who should run onboarding, sales or the project lead?

The project lead should own it, with a short, written handover from whoever sold the work. The client needs to build a relationship with the person they will work with every week. Salespeople can join the kickoff to confirm what was promised, then step back.

What is the safest way to get logins from a client?

First, ask the client to invite your team as users on each platform, so nobody shares a personal password and access can be removed later. When a shared login is unavoidable, have it stored in an encrypted vault with limited access, never in email or chat. Keep a record of who can see it and remove it when the project ends.

What if the client is slow to send access or content?

List every client dependency next to its date in the project plan, so the impact of a delay is visible. Send one friendly reminder, then a second that states which milestone will move if the item doesn't arrive. Make the date change in writing so the timeline stays honest.

Do retainer clients need the same onboarding?

Yes, with a few changes. Retainer onboarding puts more weight on communication rules, response times, how requests are submitted and how hours are reported. The welcome email, kickoff, access, roles and billing steps stay the same.

#How Bitrack helps

Bitrack gives each client a client portal under your brand, where they sign in with a code sent to their email (no password) to follow progress and milestones, approve deliverables, sign agreements, raise tickets, ask for meetings and see invoices, while internal notes stay private to your team. Logins clients give you go into a credentials vault where they are encrypted, shared only when an Owner allows it, and every reveal is recorded. Projects hold your milestones, tasks and per-project messages, agreements are signed in the same place, and the calendar syncs with Google or Outlook so kickoffs land in everyone's diary. Bitrack is free to start; see how it works or read our client portal guide next.

Onboard every client the same way, and the first two weeks will start working for you.