Free public template · version 1

Client onboarding checklist template

Turn a signed engagement into a controlled first milestone with clear owners, minimum access, documented decisions, and visible outstanding inputs.

  • 5 sections
  • 13 tasks
  • JSON, Markdown, and CSV
  • Internal editorial review
Download
Use in SealTask

The public downloads are plaintext. After import, readable project content is encrypted on your device, while operational metadata remains visible to the service. Reuse is governed by the Public Template license. Already use SealTask? Open this template in SealTask.

Complete template · v1

Client onboarding

Sections
5
Tasks
13
Schedule anchor
Kickoff date

Coordinate the path from signed scope through kickoff and the first useful client milestone.

Kickoff date: The agreed client kickoff date; preparation is scheduled before it and activation work follows it.

01

Plan

Confirm the engagement boundary, outcome, and accountable people.

  1. Confirm the signed scope and source-of-record link

    Verify that the approved scope is accessible in the contract repository and record only a neutral reference here.

    High priority 7 days before kickoff date
    • Approved scope is available to the delivery owner
    • Neutral source-of-record reference is recorded
  2. Define a neutral client code and first success outcome

    Choose a recognizable internal label and write one observable outcome that demonstrates useful early progress.

    High priority 6 days before kickoff date
    • Neutral client code is agreed
    • First useful outcome is measurable
  3. Identify the decision maker and day-to-day owner

    Confirm who can make scope decisions and who will coordinate normal inputs, questions, and scheduling.

    Medium priority 6 days before kickoff date
    • Decision maker is confirmed
    • Day-to-day client owner is confirmed
02

Set up

Prepare the minimum channels, access, and operating agreements.

  1. Create the approved communication and project channels

    Set up only the channels needed for delivery and state where urgent, routine, and authoritative messages belong.

    Medium priority 5 days before kickoff date
    • Primary delivery channel is ready
    • Channel purpose and response expectations are stated
  2. Request the minimum necessary access

    List only access required for the first milestone, with an approving owner and an expiry or review date.

    High priority 5 days before kickoff date
    • Every request has an approving owner
    • Temporary access has an expiry or review date
    • Credentials will be exchanged through an approved secrets manager
  3. Confirm communication cadence and escalation path

    Agree on normal update timing, response expectations, and the named path for blockers or urgent decisions.

    Medium priority 4 days before kickoff date
    • Routine update cadence is scheduled
    • Escalation route and response expectation are clear
03

Kickoff

Align participants, decisions, actions, and unresolved questions.

  1. Prepare and circulate the kickoff agenda

    Send a short agenda focused on outcomes, roles, known constraints, immediate decisions, and next actions.

    Medium priority 2 days before kickoff date
    • Agenda and required pre-reading are sent
    • Decisions needed during kickoff are named
  2. Run the client kickoff

    Use the agenda to confirm the desired outcome, working boundary, responsibilities, constraints, and first milestone.

    High priority On kickoff date
    • Outcome, scope, and non-goals are confirmed
    • Owners and decision rights are confirmed
    • Known risks and missing inputs are surfaced
  3. Publish kickoff decisions and actions

    Write a concise recap with each decision, action owner, due date, and unresolved question while context is fresh.

    High priority 1 day after kickoff date
    • Decisions and open questions are recorded
    • Every action has an owner and due date
04

First value

Close missing inputs and deliver the first useful client outcome.

  1. Schedule the first discovery or working session

    Book the next focused session with the people and source material needed to produce the first useful result.

    Medium priority 2 days after kickoff date
    • Required participants can attend
    • Required source inputs are listed in their systems of record
  2. Close or escalate outstanding client inputs

    Track each missing input by owner and impact, then escalate only the items that block the first milestone.

    Medium priority 4 days after kickoff date
    • Blocking and non-blocking inputs are separated
    • Owners have a clear request and due date
  3. Deliver the first useful milestone

    Complete the smallest agreed client-visible outcome and place the authoritative deliverable in its approved repository.

    High priority 7 days after kickoff date
    • Deliverable meets the agreed acceptance signal
    • Client owner knows where to review it
  4. Confirm the next milestone, owners, and risks

    Close onboarding by agreeing on the next outcome, current risks, decision points, owners, and working cadence.

    Medium priority 8 days after kickoff date
    • Next milestone and acceptance signal are clear
    • Current risks and decision owners are visible
05

Done

Completed onboarding work moves here after its outcome is verified.

Completion stage — move finished work here.

Who this template is for.

  • Consultants, agencies, and service teams starting a new client engagement.
  • Project owners who need a repeatable handoff from signed scope to useful delivery.
  • Small teams that want operational follow-up without copying sensitive source documents into every tool.

When to use it.

  • After the commercial scope is approved and before the first client kickoff.
  • Whenever several people must coordinate access, inputs, decisions, and an early milestone.
  • When onboarding is currently rebuilt from memory or scattered across email threads.

How to put it to work.

  1. Choose the kickoff anchor

    Set the planning anchor to the agreed kickoff date. Relative due dates will place preparation before the call and follow-up work after it.

  2. Name owners after import

    Import first, then assign each operational task inside the encrypted workspace. Confirm authoritative owners in the contract or account system separately.

  3. Work toward first value

    Treat the first useful milestone as the end of onboarding. Move completed coordination into Done while keeping contracts and source deliverables in their proper systems.

Customize before you commit.

  • Replace the generic first milestone with the smallest client-visible outcome promised in the engagement.
  • Remove access requests that are not necessary, and give every retained request an owner and expiry date.
  • Add industry-specific review tasks only after the appropriate legal, security, or compliance owner approves them.
  • Keep client codes neutral if task titles may reveal more context than your team intends to expose.

Keep the system boundary clear.

Use SealTask for operational coordination and status. Keep each authoritative record in the specialist system that governs it, and link by neutral reference when needed.

Coordinate in SealTask

  • Operational task titles, checklists, owners, priorities, and milestone follow-up.
  • Concise decisions and next actions that the delivery team needs to execute.
  • Neutral reminders that an input or approval is still outstanding.

Keep in the system of record

  • Signed contracts, statements of work, change orders, and billing records.
  • Passwords, API secrets, recovery codes, and privileged access material.
  • Authoritative client files, regulated data, and final deliverables.

Common mistakes to avoid.

Requesting every possible permission

Broad access increases delay and risk. Ask only for what the first milestone needs, identify the approver, and record when temporary access should expire.

Treating kickoff as the finish line

A good meeting does not complete onboarding. Capture decisions, close missing inputs, and deliver a small useful result before declaring the client activated.

Duplicating authoritative documents

Copying contracts, credentials, or source datasets into task descriptions creates conflicting records. Track the action here and preserve the source elsewhere.

Questions about this template.

What should a client onboarding checklist include?

It should cover confirmed scope, accountable contacts, minimum required access, communication and escalation rules, kickoff decisions, outstanding inputs, and a clearly defined first milestone.

When is client onboarding complete?

For most service work, onboarding is complete when required access and inputs are available, decisions are recorded, the working cadence is clear, and the client has received the first agreed useful outcome.

Should contracts and credentials go in this template?

No. Track that a contract was signed or access was granted, but keep signed documents in the contract repository and credentials in an approved password or secrets manager.

Can I change the dates and stages?

Yes. Choose your actual kickoff date during import, adjust relative due dates, rename intermediate stages, and remove any task that does not apply to the engagement.