The playbook
Agency Client Onboarding: Template and Field Guide
This agency client onboarding template turns a broad task into a record another person can use. It captures client, scope, input, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
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.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| client | Record the client associated with this client or workflow record. Use a stable reference so later updates can be matched. |
| scope | Record the scope associated with this client or workflow record. Keep the value specific enough for another owner to interpret. |
| input | Record the input associated with this client or workflow record. Keep the value specific enough for another owner to interpret. |
| owner | Record the owner associated with this client or workflow record. Keep the value specific enough for another owner to interpret. |
| first milestone | Record the first milestone associated with this client or workflow record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with client. Use the same reference throughout the record so notes are not attached to the wrong item. Then confirm scope decision owners and success definitions. This establishes the information required before the worksheet becomes a request for action.
Next, request access and information tied to immediate tasks. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as collecting dozens of assets without explaining their purpose, rather than a broad instruction to “improve performance.”
Finally, agree on approval timing and the first delivery milestone. Put sequence requests according to the first agreed deliverable in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Collecting dozens of assets without explaining their purpose |
| Action | Sequence requests according to the first agreed deliverable |
| First check | Confirm scope decision owners and success definitions |
| Follow-up check | Agree on approval timing and the first delivery milestone |
| Outcome to define | clients reaching the first delivery milestone |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If scope changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep clients reaching the first delivery milestone connected to the item so the team can later assess whether the action was useful.
Keep client identity and responsibilities explicit at every handoff. Reusable processes can save work, but goals, account access, and customer information remain specific to each client. Check the context before reusing a previous setup.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now