METHODCIRCUIT — CLIENT ONBOARDING CHECKLIST
Version: 2026-09-12
Guide: https://methodcircuit.com/guides/client-onboarding-checklist/

HOW TO USE
Copy this file for each engagement. Replace the blanks with your agreed
requirements. Use Ready / Blocked / Not required. For every blocked task,
record an owner, next action, and due date. Do not put passwords, API keys,
recovery codes, or other secrets in this checklist.

ENGAGEMENT
Client:
Engagement/project ID:
Service:
Agency owner:
Client contact:
Authorized client approver:
Delivery lead:
Agreed start date:
First milestone:
Definition of ready for delivery:

TASK RECORD — copy the following block under any step that needs detail
Status:
Owner:
Evidence or source link:
Next action:
Due date:
Reason if not required:

01 — COMMERCIAL HANDOFF
[ ] Link the current agreement and scope.
[ ] Confirm deliverables and exclusions.
[ ] Record agreed start dependencies and payment prerequisites.
[ ] Identify who handles scope changes.
[ ] Delivery lead confirms understanding of scope.

02 — PEOPLE AND DECISIONS
[ ] Name agency owner and client contact.
[ ] Name authorized approver.
[ ] Agree primary communication channel.
[ ] Record review turnaround and decision location.

03 — BRIEF AND ASSETS
[ ] Confirm audience, offer, objective, and constraints.
[ ] Link approved source material and brand assets.
[ ] Separate required assets from optional references.
[ ] Assign each missing item an owner and due date.

04 — ACCESS
[ ] List systems required for this service.
[ ] Request role-based invitations where available.
[ ] Verify the correct teammate can access the correct workspace/asset.
[ ] Record intended permissions and access-removal owner.

05 — DELIVERY WORKSPACE
[ ] Check whether this engagement already has a project.
[ ] Create or update the correct project template.
[ ] Link the approved brief and current assets.
[ ] Assign first tasks, owners, and review dates.

06 — KICKOFF AND ACCEPTANCE
[ ] Confirm goal, boundaries, dependencies, and first milestone.
[ ] Record decisions and unresolved blockers.
[ ] Delivery lead accepts handoff or states the blocking condition.

HANDOFF DECISION
Ready / Blocked:
Accepted by:
Date:
First delivery action:
Open blockers and owners:

OPTIONAL AUTOMATION TRIAL
Trigger:
Required inputs:
Draft action:
Human approval point:
Unique engagement identifier used for duplicate checks:
Failure alert recipient:
Manual recovery steps:
Trial result — complete input:
Trial result — missing field:
Trial result — repeated trigger:
Trial result — connection failure:

MEASURE AFTER USE
Manual administrative time:
Review and correction time:
Maintenance time:
Follow-ups for missing inputs:
Handoff corrections:
Change to make next time:

USAGE
You may copy and adapt this template for your own agency and client work.
Do not resell the unmodified file as a standalone product.
Adapt this planning template to your service and agreement. Test any
automation in your chosen software before using it for client work.
Questions or corrections: support@methodcircuit.com