When agency management ends, the client should receive the agreed program records, usable access, authorized creator contacts, and a dated list of unfinished obligations. Each item needs an in-house owner and evidence that the owner can use it. An influencer agency handover is complete when the client can run the next scheduled task without borrowing the agency's login or guessing what it promised a creator.
The inventory below is an illustrative operating template. It is a recommended acceptance process, not a claim about what every agency contract requires.
Agree what transfers before exporting anything
Start with the agency agreement, statement of work, creator agreements, and data-processing terms. List the records and files the client is entitled to receive. Flag uncertain ownership, export restrictions, and work that needs a separate agreement.
For each item, choose one disposition:
- Transfer. The agreed item can move to the named client destination.
- Restricted transfer. Only approved fields, files, or recipients can receive it.
- Resolve first. Ownership, permission, or the permitted use remains unclear.
- Exclude. The item falls outside the agreed handover, with a recorded reason.
Do not export the agency's entire creator database to settle a client-specific request. Separate this client's records from other clients' work, internal agency materials, and unrelated personal correspondence. For shared workspaces, use the controls in keeping creator data separated across agency clients before creating an export.
Ask qualified counsel to review disputed rights, assignment terms, and privacy duties in the relevant jurisdictions. The checklist helps teams prepare that review; it does not decide those questions.
Build one inventory with acceptance evidence
Keep one row per asset, account, dataset, or open obligation. Record the current location, transfer authority, receiving owner, destination, due date, and status. Link to the evidence rather than writing "done" after an email attachment leaves the agency.
| Item | Client should receive, where agreed | Acceptance evidence |
|---|---|---|
| Program plan | Current objectives, budget approvals, campaign calendar, stop decisions | Client identifies the next approval and its deadline |
| Creator records | Campaign-specific contacts, representation details, agreed communication preferences, current status | Recipient opens an approved record and finds its next action |
| Agreements | Signed versions, amendments, deliverables, payment terms, rights restrictions | Each active creator links to the governing documents |
| Content | Agreed final files, approved versions, live URLs, source files if included | Client opens the files and distinguishes approved from rejected work |
| Access | Client-owned workspaces, platform roles, storage, reporting, relevant integrations | Named client user performs the required task with their own account |
| Money | Invoices, payment status, commission calculations, disputed amounts | Finance reconciles open amounts and knows who will pay |
| Reporting | Final export, source labels, date ranges, definitions, missing data | Client reproduces one reported total from the supplied records |
| Open work | Pending approvals, shipments, revisions, renewals, corrections | Each item has one accepting owner and a next deadline |
Choose an export cutoff and record its time zone. If creators can still publish or invoices can still arrive, agree how those changes enter the inventory after the cutoff. Otherwise, the final spreadsheet may already be stale when the client receives it.
Transfer access through the platform
Use named invitations and roles where the service supports them. Check the receiving user's accepted access before removing the agency. Avoid making the agency's personal email account, phone, or password the client's permanent recovery method.
Platform roles need a task-level check. YouTube's channel-permissions documentation allows delegated channel management without sharing Google Account credentials. An Editor cannot manage permissions; a Manager can manage them in YouTube Studio. The channel-permissions Owner role cannot transfer ownership to another user. Invited users also cannot access YouTube APIs through channel permissions.
Those distinctions matter during acceptance. A client who can view reports may still be unable to remove an agency user or maintain an integration. Inventory integrations separately and verify the relevant service's authorization process. A successful browser login does not prove an API connection will continue working.
Apply this process to brand-controlled accounts within the agreed scope. If a creator supplied a report, label it as supplied evidence. Do not turn the handover into a request for the creator's account password or assume the client receives ongoing private analytics access.
Transfer contacts with purpose and limits
Give the receiving team the contact route and relationship history it needs to continue authorized work. Include the last agreed action, who represents the creator, and any recorded contact restrictions. Review shipping addresses, payment details, and personal notes separately; restrict their recipients to the people who need them.
For EU/EEA GDPR work, establish the parties' roles before choosing a transfer process. The European Data Protection Board explains that controllers decide the purposes and means of processing, while processors act on controller instructions. Its guidance requires controller-processor contracts to address security, confidentiality, and return or deletion of personal data after services end, at the controller's choice.
An agency label alone does not settle its data-protection role. Have the responsible privacy adviser confirm the role, lawful handling, recipients, international-transfer requirements, and any required retention. Record the resulting instructions alongside the handover. Do not promise immediate deletion of every copy before those questions are resolved.
For relationship continuity, agree who tells active creators about the change and when. Modash's relationship-management guide discusses reference materials for new team members and a single relationship contact. Use that operational idea in a transition message identifying the new contact, effective date, and current commitment. Keep the person-level introductions in a creator-manager handover; this inventory covers the whole program.
Keep open obligations separate from delivered files
A downloaded video can still have an unresolved approval, unpaid invoice, or approaching rights expiry. Record each obligation separately, even when it concerns the same creator.
Consider this hypothetical handover:
| Open item | State at cutoff | Accepting owner | Next action |
|---|---|---|---|
| Creator A's invoice | Approved, unpaid | Client finance lead | Confirm payment date with the contracted payer |
| Creator B's video | Revision requested | In-house campaign lead | Send the consolidated feedback by the agreed deadline |
| Creator C's content license | Expires in 12 days | Client rights owner | Review renewal or schedule removal of affected uses |
| Monthly report | Awaiting a supplied creator report | Client analyst | Request it through the agreed contact route |
These are illustrative entries, not observed client cases. They show why "content folder received" cannot close the program transfer.
For licensed assets, include permitted uses, channels, term, territory, editing restrictions, and the document that supports each entry. Track platform advertising permissions separately from contractual content rights. Use tracking content rights before expiry to schedule the follow-up work.
Accept the handover, then remove residual access
Run acceptance with the in-house owners present. Check the following before signing off:
- The client has received every agreed inventory item or accepted a named exception.
- Client users can open the files and perform the required account tasks.
- Active creators have a named contact and clear next action.
- Finance has accepted the unpaid, disputed, and contingent amounts for follow-up.
- Reporting gaps and supplied-report limits remain visible.
- Every open obligation has an owner and due date.
- Agency access, integrations, and copies have a documented removal or retention instruction.
Record exceptions as "blocked" or "accepted with follow-up," with an owner and deadline. Keep final commercial settlement separate from the operational acceptance record so a file receipt does not obscure an unresolved payment.
After acceptance, remove agency access at the agreed time and record completion. Ask the responsible agency owner to confirm the agreed return, deletion, or restricted retention of remaining copies. Start by booking the acceptance session and sending its attendees the inventory, especially the rows that still need a decision.
