Ownership
Name the business owner, brand owner, approver, publisher and incident contact for every client brand.
Agency onboarding guide, reviewed 15 August 2026
A social media client onboarding checklist that prevents later chaos
Client onboarding should create an operating contract, not just a folder and a kickoff call. Before production starts, the agency and client need to agree who owns each brand decision, which claims are allowed, how accounts are connected, what requires approval, which formats can really publish and how delivery will be evidenced. This checklist turns those decisions into a testable first week.
Use the checklist with the client’s contracts, platform terms and internal policies. A completed setup does not prove that every account, permission or format is ready until a real controlled delivery has been observed.
Finish six onboarding decisions before volume
Finish six onboarding decisions before volume
Access
Use delegated roles and scoped consent. Record who can grant, renew and revoke each connection.
Evidence
Define what counts as approved, scheduled, published, measured and handed back at the end of the relationship.
Capture the commercial and brand boundary
Start with the service that was actually sold. List brands, markets, languages, channels, expected formats, monthly volume, response times, reporting cadence and work that remains outside scope. Separate strategic advice, production, community management, paid media and direct publishing so neither side assumes that one label includes everything.
Create one brand record with audience, offer, voice, visual rules, approved terminology, prohibited claims, current sources and escalation topics. Record who can change each field. A kickoff presentation is useful, but the durable version must travel with briefs and approvals so a new operator does not reconstruct the brand from memory.
Inventory accounts and ownership before connecting
For each destination, record the public account, provider identifier, legal owner, administrator, business portfolio, account type, recovery contact and intended operator. Confirm that the person granting access has authority for the client. A successful connection to the wrong personal profile is still the wrong connection.
Prefer named roles, delegated consent and least privilege. Document the scopes requested, token lifecycle, provider review requirements and revocation owner. Never put client passwords or access tokens in a brief, chat thread or shared spreadsheet. If a legacy exception exists, give it an owner, expiry date and migration path.
Agree the review and publication contract
Define which content needs blocking approval, who may approve, how long approval remains valid and which edits send an item back to review. Bind the decision to the exact caption, asset, account, destination, disclosures and scheduled time. A generic approval on a campaign idea cannot safely authorise every later variant.
Distinguish draft, ready for review, approved, scheduled, published, failed, unknown and manual action. Decide how overdue approvals and missed slots behave. Run one rejection, one media replacement and one disconnected account during onboarding. The team should see a clear block and next owner, not a silent fallback.
Prove one real delivery and one report
Choose one representative brand, one eligible account and one low-risk format. Validate the media, final copy, timezone, account identity and approval, then preserve the provider response or remote object. A configured adapter or connected logo is not enough to call the path production-ready.
Build the first report from the same content. Separate delivery evidence, distribution metrics and business actions. Record the measurement window, source, missing fields and attribution limit. This rehearsal exposes incompatible definitions before the first monthly report becomes a dispute.
Document change, incident and exit paths
Name the person who handles expired access, provider rejection, sensitive news, client silence and suspected compromise. Decide who can pause future items and who authorises a restart. Keep emergency contact details outside the account that may be unavailable during the incident.
Agree the exit process at the start. List content, media, approvals, reports and evidence that can be exported, what must be retained, who disconnects accounts and when tokens are revoked. A clean offboarding contract protects both parties and makes the onboarding decision more credible.
Onboarding workflow references
Onboarding workflow references
These Cascads guides define the operating boundaries used in the checklist. Adapt them to the client’s contracts and current provider controls.
- Social media management for small agenciesReviewed 15 August 2026
- Manage social accounts without shared passwordsReviewed 15 August 2026
- Social media approval workflowReviewed 15 August 2026
- Multi-brand social media reportingReviewed 15 August 2026
FAQ
Social media client onboarding FAQ
What should a social media client onboarding checklist include?
Include scope, brand context, owners, delegated access, approval rules, formats, calendars, delivery evidence, reporting definitions, incidents and offboarding.
Should an agency ask for the client’s social passwords?
Prefer provider roles and delegated consent. A shared password weakens attribution, revocation and security and should never be the default.
When is onboarding complete?
When the operating contract is agreed and one representative path has been tested from brief through approval, delivery evidence and reporting.
Who should own account revocation?
Name both the client authority and agency operator. The client should retain the ability to remove access when the engagement changes or ends.
Continue with a focused path
Continue with a focused path
Test with one brand and one real account
Validate the workflow, permissions and evidence before expanding the scope.
Create a Cascads workspace