Turn the scope into an operating record
Social media client onboarding establishes how the agency will access accounts, produce work, obtain decisions and report results. A kickoff meeting is useful, but its notes need to become an operating record with named owners and verified conditions. Begin with the contracted service scope and identify what it requires from the client. Publishing, community responses, listening and reporting each have different access and decision needs.
Social media management platforms belong in onboarding tests because access, approval behavior and available data can differ between client accounts.
List the included brands, markets, languages, accounts and service periods. Define exclusions explicitly where they affect expectations. If paid media reporting is excluded, a combined paid-and-organic executive chart needs a separate decision. If community management is included only during agreed hours, record the urgent escalation route. A useful onboarding record makes these boundaries visible before they become a delivery disagreement.
Verify identity and permissions
Ask the account owner to grant access through the supported native process. Confirm the account identity, relevant role and intended agency recipient. The YouTube Help: channel permissions [1] provides a platform-specific example of channel permissions. Use the current documentation for the actual network and account type; do not assume that one platform's role names or supported tasks apply everywhere.
Record access status as invited, accepted, verified or blocked. An invitation email does not prove that the person can retrieve analytics or manage the intended account. Run a harmless authorized check for the required task. Inspect the account identifier and relevant permission rather than relying only on the visible brand name. Keep credential recovery and administrator ownership with the appropriate client process.
Distinguish native account access from an agency tool connection. A connection can exist while specific scopes, history or tasks remain unavailable. Document the connected account, authorizing owner, verification date and unresolved limitations. If historical data is absent, determine the available window and establish an honest baseline. Do not populate a new client space with another client's data to make onboarding appear finished.
Agree on content and response decisions
Collect current brand guidance, approved offer information, claims evidence and asset permissions. Identify who verifies facts and who approves publication. These may be different people. A marketing contact can approve wording while a product owner verifies implementation details. Record each decision route with a substitute and escalation rule so production does not depend entirely on one person's availability.
For community work, define the categories the agency can handle and the cases it must transfer. Record the secure route for private customer details. Explain what the agency can acknowledge publicly without promising an unverified outcome. A response template should identify the source policy and situations where it does not apply. Previous comments are useful examples, but they should not silently become the authority for a current promise.
Choose a version rule for approvals. Material changes to copy, media, offer terms, destination or publication timing should trigger the review required by the client's process. Record approval against the asset and intended use. A broad statement that "the campaign is approved" can leave individual posts and later changes ambiguous when the team is ready to publish.
Worked example: an onboarding gap becomes visible
This hypothetical example concerns an invented regional service brand. The agency is engaged to publish approved content and produce a monthly report. The client sends an account invitation and an old report template. The agency marks the invitation as accepted, then tests the authorized reporting task. It can view current analytics but cannot establish the requested prior-quarter history through the connected tool.
The agency does not label the missing quarter zero activity. It records the gap, asks the client for an approved native export if available and agrees on the first comparable reporting window. The old template also uses "engagement" without defining its denominator. The agency and client choose a specific interaction measure and retain the old report separately because the two versions are not directly comparable.
Before production begins, the client names an approver and a backup. A sample draft is reviewed, revised and approved through the agreed version process. A sample report is checked for account identity, window, source links and visible limitations. The onboarding is accepted for the verified scope, with the historical data question remaining open. The invented example shows a bounded launch decision, not a claim that every onboarding requirement has automatically passed.
Use an onboarding acceptance checklist
- Confirm the brands, accounts, markets and tasks included in the service.
- Verify the required access using harmless authorized tasks.
- Identify administrator ownership and connection recovery routes.
- Collect current factual sources, brand rules and asset permissions.
- Name approvers, substitutes and urgent response owners.
- Agree on reporting definitions, date windows and delivery recipients.
- Inspect a sample draft, response handoff and report before recurring delivery.
Give every unresolved item an owner and consequence. A missing brand image may delay one draft; missing publication authority may prevent the entire release workflow. Separate essential launch conditions from improvements that can follow safely. The acceptance record should describe the scope actually ready to operate instead of using one green status for a mixture of verified and blocked tasks.
Establish reporting and data handling limits
Record metric definitions, timezones, paid-and-organic scope, source refresh conditions and the date of the baseline. The Google Analytics: data freshness [2] explains that Analytics processing and freshness vary. Where website outcomes are included, agree on the reporting cut-off and check the actual source conditions. A schedule that delivers too early can repeatedly produce incomplete numbers while appearing punctual.
Decide who may receive reports and what fields they need. The NIST Privacy Framework [3] provides a voluntary reference for privacy-risk management. Keep sensitive customer records within the approved process and prefer aggregate reporting for broad recipients. Onboarding should also establish how retained records, exports and shared links will be handled if the relationship changes, rather than leaving that discussion until offboarding pressure arrives.
Frequently asked questions
Is a signed contract enough to start publishing?
It establishes the commercial relationship, but operational readiness also needs the appropriate account access, current assets, authorized approvers and a verified release process. Check the requirements that affect the specific service instead of treating the signature as proof of every technical permission.
What should happen when historical data is unavailable?
Record the available period and the reason for the gap where known. Explore permitted native exports or other approved sources, then agree on a comparable baseline. Keep unavailable periods visible and avoid filling them with estimates presented as observations.
How can onboarding avoid becoming a long questionnaire?
Organize requests around the tasks the agency will perform. Ask for the minimum information needed to verify access, decisions and reporting. A tested sample workflow often reveals gaps more clearly than a large form whose answers have never been checked.
References and source scope
- YouTube Help: channel permissions
YouTube delegated channel roles and documented limits, including API access; native permission behavior is source-specific.
Source link checked 2026-10-03 - Google Analytics: data freshness
Google Analytics processing intervals, report changes and data freshness limits; source-specific cut-off considerations.
Source link checked 2026-10-03 - NIST Privacy Framework
NIST voluntary privacy-risk framework; informs handling considerations, not a compliance certification or disclosure authorization.
Source link checked 2026-10-03