Client Onboarding Checklist
Use when: tracking whether a client's onboarding is complete, or checking one item independently. One list covers every client: contract through 30 days after go-live.
Item list (canon): client-onboarding-checklist.csv. There is one row per item and no comment rows, so people and agents parse it the same way.
Per-client tracking: the SC Client Onboarding Tracker workbook in G:\Shared drives\Client_Delivery\system\, beside the SC Client Dashboard. The workbook records status. This repo owns the item wording.
Item columns
| Column | Meaning |
|---|---|
item_id | Stable key, area prefix + number (DOM-06). Never renumber or reuse; retire an item by deleting the row and noting it in the changelog |
area | Account & access · Domain & email · Messaging & compliance · CRM configuration · Automations · Website & funnels · Tracking & listings · Training & go-live |
item | The finished outcome, stated so it is either true or false |
applies_when | all, or one service flag: website, wordpress, sms-us, whatsapp, payments, gbp, social |
depends_on | Client if the item cannot finish without a client input, else SC |
client_input | What the client must supply. Blank when depends_on is SC |
verify_how | How someone who did not do the work confirms the item |
evidence | What to link when marking the item Verified |
agent_checkable | yes: an agent can confirm it through the platform API, DNS or a page fetch. partial: an agent can check part of it. no: needs a person, or a login an agent does not hold |
sop_ref | The procedure that does the work. Task codes (M4, I4, S3) refer to the Client Onboarding Procedure SOP |
Tracker workbook
One tab, Checklist: one row per item, one column per client, each client cell holding a status from a dropdown. Four summary rows sit above the header row: % verified, waiting on client, open with SC, and done but not yet verified. They count only cells that are not N/A. A README tab repeats the rules below.
N/A cells are pre-set from each client's services (the applies_when flags), seeded from the client profiles. Change any that are wrong.
Status values
| Status | Meaning |
|---|---|
| Not started | No work yet |
| In progress | Symphony Core is working on it |
| Waiting on client | Blocked on a client input. Say what is needed in a cell note |
| Done | Work finished; nobody has checked it independently |
| Verified | Confirmed using verify_how by someone other than the person who did the work |
| N/A | Does not apply to this client |
The verification rule. A Verified cell carries a cell note naming who verified it, the date and a link to the evidence. A Verified cell without a note does not count. An agent may verify agent_checkable items and signs the note as claude-agent.
Reading the summary rows. Waiting on client counts client blockers. Open with SC counts Not started and In progress, which is Symphony Core's open work. Telling the two apart is the point of the tracker.
Adding or changing items
- Edit the CSV in this repo by pull request. Keep
iteman outcome, not a task step. - Insert a matching row in the workbook and set each client cell to Not started or N/A.
- A new client gets a column when it is registered in the client document kit manifest: set N/A where an item does not apply and copy the summary formulas across.
Related
- Client Implementation Lifecycle SOP: stages and exit criteria
- L2 Validation Checklist: the post-fanout check, whose outcomes appear here as ACC-02 to ACC-05
- Client Input Checklist (Master): the client-facing list behind the
Clientitems - Client Document Kit: the SC Client Dashboard and profile validation
Changelog
| Version | Date | Change |
|---|---|---|
| 1.0 | 2026-10-12 | Created. Consolidates the implementation checklist template and the four verification CSVs into 71 outcome items with verification method, evidence and client dependency |