A checklist tells you what to do. A working template tells you who will do it, when, and what is blocking the next step. This download is an Excel workbook with two sheets: a seven-column task sheet with 11 onboarding tasks, and the same sheet filled in for a fictional project. Replace the sample entries with your own details, or copy the columns into your project tool.

This page is the companion to our client onboarding checklist. The checklist explains the process; this template gives your team a record to run it. The client onboarding questionnaire collects the information the tasks depend on, and the client kickoff agenda covers the meeting that unlocks delivery work.

What is in the download

The file is client-onboarding-checklist.xlsx, version 1.1. It opens in Excel, Google Sheets, LibreOffice Calc or Numbers without conversion.

Sheet Columns What it contains
Checklist Phase, Task, Owner, Target date, Status, Dependency, Completion evidence 11 pre-written tasks across six phases: agreement, planning, brief, access, kickoff and delivery. Owner, date, dependency and evidence are blank for you to complete; every status starts at Not started.
Illustrative example The same seven columns One fictional project filled in, including a Blocked access task and the evidence entries that let a reader see why it is blocked.

Both sheets are visible in the workbook, so you can compare a blank row with a completed one. The example is fictional and exists only to show how dependencies and completion evidence read.

Who this template suits

It is built for a small agency running one to three onboarding projects at a time with a named owner per project. It also works for a solo operator who wants a record that survives a busy week.

It is not a full project-management system. If several people update the same engagement daily, a task board with notifications will suit you better; keep this workbook as the onboarding record. If the client requires evidence of access reviews or retention, check your agreement and your own policies before choosing where the completed file lives.

Set up the project record

Create one record per client engagement, not one generic row per company. The same client may have a website project and a reporting project with different owners and dates.

Project field Example entry What to enter
Project ID ACME-WEB-01 Stable internal identifier
Client Acme Bakery (fictional example) Business name
Service Five-page website Signed scope, in short form
Agreement date 2026-11-03 Actual signing date
Agency owner Jordan One person accountable for follow-through
Client contact Sam Person providing information
Final approver Taylor Person authorized to approve work
Kickoff target 2026-11-10 Proposed date, subject to inputs
First deliverable Homepage wireframe Specific reviewable output
First review target 2026-11-17 Confirm after dependencies are understood

This project record is not a sheet in the workbook. Add it as a third sheet if you need the engagement details in the same file, or keep it in your project tool and use the workbook only for tasks. Keep the signed agreement in the appropriate private system. This table is a coordination record, not a replacement for the contract.

Copy the task tracker

The workbook uses seven columns. The table below adds Task ID and Updated because spreadsheets get sorted: a stable ID survives a re-sort, and the updated date shows which row someone touched last. Copy the headers and rows, then edit the owners and dates.

Task ID Stage Task Owner Due date Status Blocked by Completion evidence Updated
ON-01 Handoff Confirm signed scope Jordan Nov 3 Done — Agreement confirmed Nov 3
ON-02 Welcome Send next steps and secure upload link Jordan Nov 4 Done ON-01 Welcome email sent Nov 4
ON-03 Intake Answer required business questions Sam Nov 6 Waiting on client ON-02 — Nov 4
ON-04 Assets Supply logo and approved photos Sam Nov 6 Waiting on client ON-02 — Nov 4
ON-05 Access Invite agency to site analytics Sam Nov 7 Not started ON-02 — Nov 4
ON-06 Verify Confirm files open and access works Jordan Nov 9 Blocked ON-04, ON-05 — Nov 4
ON-07 Kickoff Confirm scope, approver, and next date Jordan Nov 10 Not started ON-03, ON-06 Decision note Nov 4
ON-08 Delivery Share first wireframe for review Designer Nov 17 Not started ON-07 Review link and version Nov 4

Example only: Acme Bakery, the people, dates, and statuses above are fictional. They illustrate how dependencies work; they are not a client result.

Edit these five things before the first client

  1. Replace the phases if your process differs. The workbook's six phases are a starting sequence, not a standard. If your agency runs a paid discovery stage before the agreement, add it.
  2. Name one owner per task. A row with no owner has no next action.
  3. Turn relative targets into dates once the kickoff is booked. The workbook's example uses targets such as Before kickoff, which works for planning but cannot show lateness.
  4. Delete tasks that do not apply. A shorter tracker that gets updated beats a complete one that does not.
  5. Decide where the completed file lives before you share it. One location, named access, and a rule for who may edit the status column.

Define statuses before the first project

Use a short list everyone understands: Not started, In progress, Waiting on client, Blocked, and Done. A task is Done only when its evidence column contains a link, decision, or other checkable result. A reminder sent is not the same as the requested asset received.

Waiting on client means the next action belongs to the client. Blocked means someone must resolve a dependency or make a decision. Name that person in Owner; a blocked task without an owner can sit untouched for days.

If you want a calculated lateness flag in Google Sheets, add a column named Attention after Updated. In row 2, use:

=IF(OR(E2="",F2="Done"),"",IF(E2<TODAY(),"Overdue","On track"))

This formula assumes Due date is column E and Status is column F. Use real spreadsheet date values, not text such as “next Friday.” If you add columns or rearrange the tracker, update the references. A date due today displays On track; change < to <= if your team wants it flagged at the start of the due date. Formulas and list separators can vary by locale.

How to run a five-minute daily check

Filter the tracker to tasks that are not Done. Look at overdue tasks, then at items blocking the kickoff or first delivery. For each one, decide the next action, who will take it, and when. Update the record while you are looking at it.

At the weekly client check-in, share a short summary rather than your entire internal tracker:

Completed: scope confirmed and welcome sent. Needed from you: logo and photos by Friday. Next: we will confirm the first wireframe review date when the files and analytics access work.

If inputs change the schedule, agree a revised date and record the reason. Do not quietly overwrite the original target; keep a short change note.

Separate intake from discovery

Use the task tracker to monitor whether answers arrived. Use our agency onboarding questionnaire to collect the strategic answers themselves. If a question has no bearing on the first deliverable, save it for a later conversation.

When should you automate this template?

Automate the repeatable parts first: create a project folder, assign standard tasks, and notify the owner that a form has arrived. Keep final approval of scope, dates, and sensitive access with a person. Document and test each handoff before relying on an automation. The Make onboarding workflow guide walks through a build for this stage, and the automation audit checklist lists the failure tests to run before a client project depends on it.

Use the template once, then improve it. After your next client, identify the task that caused the longest delay and rewrite that row with a clearer owner, deadline, or completion rule.

Questions about the onboarding template

Is this an Excel template or a project-management checklist?

It is an Excel workbook with two sheets: a seven-column task checklist and a filled fictional example. The columns copy cleanly into Notion, Airtable, Asana or Trello if you prefer, but the optional lateness formula described on this page exists only in a spreadsheet.

Should I use one row per client or one row per task?

One row per task, with a project ID identifying the client engagement. A single row per client cannot show which step is blocking, who owns it or what evidence closed it. The workbook follows the task-row model, and the project record above holds the engagement details.

What counts as completion evidence?

A link to the signed scope, the uploaded file, the recorded access confirmation, the decision note or the approval message. A date alone is not evidence. If the cell cannot point to something that exists outside the tracker, the task is not Done, even if someone has done the work.

Can I use this template without Excel?

Yes. The columns are plain text, so the sheet copies into Google Sheets, Numbers, Airtable or a task board. Only the optional lateness formula and locale-dependent separators are spreadsheet-specific. Keep one shared location and one owner for status updates whichever tool you use.

How should access and credentials be recorded?

Record that access was granted, who owns it and when it was confirmed, not the credential itself. Never paste passwords, API keys or one-time codes into a shared onboarding sheet. Store secrets in a password manager and note only the access owner in the tracker.

Related guides and next step

Next step: open the workbook, replace the six phases with your own if they differ, and fill the owner column for the next client engagement today. A tracker with owners is the difference between a checklist and a process.

Our templates are editorial practice, not a certified standard. The fictional example is not a client result, and the workbook is not a substitute for your contract, privacy policy or legal advice.