The playbook
Agency Client Onboarding: Checklist
Use this agency client onboarding checklist before a new release, a handoff, or a scheduled review. Its purpose is to verify the decisions that affect clients reaching the first delivery milestone. Check an actual client or workflow record; a box marked complete without evidence does not show that the customer journey works.
Put the task in context
Confirm the purchased scope, decision-maker, required access, factual business information, and first milestone. Request only the inputs needed for that stage. Keep a visible list of missing dependencies so the team does not promise dates based on unavailable materials.
Before you use the checklist
Name the exact item being checked and its purpose. Gather client, scope, input, owner, first milestone. If one of those details is unknown, mark it as unknown and assign a way to resolve it. An invented value makes the checklist look complete while weakening every later decision.
Working checklist
| Check | Evidence to keep | Responsible role |
|---|---|---|
| Confirm scope decision owners and success definitions | A dated observation showing how client was verified | account lead |
| Request access and information tied to immediate tasks | A dated observation showing how scope was verified | delivery owner |
| Agree on approval timing and the first delivery milestone | A dated observation showing how input was verified | business owner |
Check the failure path
- Look specifically for this failure: collecting dozens of assets without explaining their purpose.
- Sequence requests according to the first agreed deliverable. Record the actual correction, not just the intention to make it.
- Repeat the affected task after the correction and check first milestone.
- Make sure the next owner can find the decision and supporting evidence.
Use three outcomes for each check
Mark an item as complete only when the expected behavior or information has been observed. Mark it as incomplete when a required condition is absent. Use not applicable when the condition genuinely does not belong to the chosen scope, and write a short reason. These states keep a review useful without forcing every process into an identical mold.
For example, if the check is “Confirm scope decision owners and success definitions,” a meeting about the subject is not the evidence itself. Retain the relevant client and scope, the decision made from them, and the result of checking that decision. The record should allow someone who missed the meeting to understand what changed.
Decide what must be resolved first
An incomplete item that prevents collect the context and access needed to start client work responsibly deserves attention before a cosmetic improvement. Assign an owner and a next action to that issue. Keep optional refinements visible, but do not let them obscure a failure in the core process.
Close the review
Recheck corrected items and note anything still uncertain. The checklist is finished when the next owner understands what was verified and what remains open. Follow clients reaching the first delivery milestone using a consistent definition so later reviews can connect execution quality with useful results.
Follow one customer journey across the involved teams and systems. A correct step can still create a poor experience when its output is not usable by the next team. Verify the transitions as carefully as the individual tasks.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now