Prepare a handover when the creator manager or agency changes

A creator handover happens in two common cases. One manager leaves and a colleague takes over their creators. Or an agency stops running the program and hands it back to the brand's in-house team. Both cases need the same result. The new owner can send the next message and run the next scheduled task without asking the creator to explain the history, and without borrowing anyone's login.

For one creator, that means one handover page with the agreed commitments, the latest conversation, any open issue, and the next action with its owner and deadline. For a whole program, it means an inventory of records, files, access and open obligations, each with an in-house owner and proof that the owner can use it. Both leave out unrelated personal history.

The procedure below is an operating recommendation. The templates are illustrative and hold no real creator or client records. The privacy, copyright, platform and disclosure guidance cited applies where each source says it does.

Agree what transfers before you copy anything

For a program handover, start with the agency agreement, the statement of work, the creator agreements and the data-processing terms. List the records and files the client is entitled to receive. Flag uncertain ownership, export limits, and work that needs a separate agreement.

Give each item one of four dispositions:

• A transfer item can move to the named client destination as agreed.
• A restricted transfer item can go only to approved fields, files or recipients.
• A resolve-first item has unclear ownership, permission or permitted use.
• An excluded item falls outside the agreed handover, and the inventory records why.

Do not export the agency's whole creator database to settle one client's request. Separate this client's records from other clients' work, internal agency material and unrelated personal correspondence. In a shared workspace, apply the controls in keeping creator data separated across agency clients before you build the export.

Ask qualified counsel to review disputed rights, assignment terms and privacy duties in the relevant jurisdictions. The checklists here help a team prepare that review. They do not decide those questions.

Build each creator page from evidence

For each creator, start with the signed agreement, the approved brief, the latest amendments, the current message thread and the payment status. Read the most recent exchange even if the campaign tracker looks complete. A creator may be waiting for the brand's answer while the tracker still says "awaiting content."

For each commitment, record its source and date. Sort it into one of three states:

• An agreed commitment is one the record shows both parties accepted.
• A requested commitment is a proposed change that nobody has accepted yet.
• An unclear commitment has conflicting records, or the person who made the promise had no confirmed authority.

Do not quietly turn a request into an obligation. If an email seems to change a signed term, flag it for the person authorized to resolve contract questions. The handover should point to that conflict and leave its legal effect to that person.

Modash's relationship guide recommends onboarding documents and describes teams that give each creator a single relationship contact. Apply that idea at the transfer point. Name when the new owner starts, who covers their absence, and who answers messages already in progress.

One-page relationship handover template

Copy this table into your team's approved workspace. Keep entries short and link to controlled records instead of pasting whole conversations.

The handover needs the payment status and the finance contact. It does not need a copy of the creator's banking information. If someone asks to change payment details during the transition, verify the change outside the incoming message before finance acts on it.

Program inventory for an agency handover

When a whole program moves, 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 instead of writing "done" after an email attachment leaves the agency.

Each active creator in the inventory still gets the one-page relationship record above. The inventory covers the program, and the page covers the person.

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. Without that rule, the final spreadsheet may be stale by the time the client receives it.

Pass on contacts and notes with a purpose

Ask one question of every relationship note: what work decision will this help the incoming manager make?

A creator's request to use email instead of phone helps route the next message. A guess about why they dislike calls does not. A confirmed period of unavailability helps schedule work. The private family reason behind it usually adds nothing to that task.

For organizations under UK GDPR, the ICO's data minimisation guidance says personal data must fit its purpose and stay limited to what is necessary. It also warns against keeping too little information to make a sound decision. The ICO notes the page is under review after the Data (Use and Access) Act.

That supports a working rule. Keep the scheduling or communication consequence, and question the need for the private explanation. Follow your organization's retention and legal-hold rules for the underlying records. Trimming the handover does not mean deleting evidence that must be kept.

Replace personality labels with dated events. "Difficult about revisions" gives the new manager nothing to act on. "Creator disputed a request outside the approved brief; scope decision pending with client lead" names the issue. If an opinion must stay, label it as an opinion with its author, date and basis, as the ICO guidance recommends.

Review shipping addresses, payment details and personal notes as a separate step, and limit them to the people who need them. Include the last agreed action, who represents the creator, and any recorded contact restrictions.

When an agency hands a program back under EU or EEA GDPR, settle the parties' roles before choosing how to transfer the data. The European Data Protection Board explains that controllers decide the purposes and means of processing, and processors act on the controller's instructions. Its guidance requires controller-processor contracts to cover security, confidentiality, and the return or deletion of personal data after the service ends, at the controller's choice.

The word "agency" alone does not settle a data-protection role. Have the responsible privacy adviser confirm the role, lawful handling, recipients, international-transfer requirements and any required retention. Record those instructions with the handover. Do not promise to delete every copy at once before those questions are answered.

Move access through the platform

Use named invitations and roles where the service supports them. The incoming owner should open every linked record with their own authorized account. Check that the receiving user has accepted access before you remove the outgoing manager or the agency. Do not put passwords in the handover, and do not leave a departing person's email, phone or password as the permanent recovery method. If permissions are unclear, follow the creator-data access audit.

Check platform roles at the task level. YouTube's channel permissions help page lets people manage a channel without sharing Google Account credentials. An Editor cannot manage permissions, and a Manager can manage them in YouTube Studio. The Owner role in channel permissions cannot transfer ownership to another user. Invited users also cannot reach YouTube APIs through channel permissions.

Those limits show up during acceptance. A client who can view reports may still be unable to remove an agency user or keep an integration running. List integrations separately and check each service's authorization process. A working browser login does not prove an API connection will keep working.

Apply this to brand-controlled accounts within the agreed scope. If a creator supplied a report, label it as supplied evidence. Do not ask for the creator's account password, and do not assume the client gets ongoing private analytics access.

Carry forward rights, disclosure and open obligations

Include the rights record even when production is finished. In UK guidance, GOV.UK explains that a copyright licence can limit purpose, time and place. For each licensed asset, record the permitted uses, channels, term, territory, editing limits, and the document behind each entry. The new owner should check the actual agreement before offering reuse or an extension. Ask a qualified adviser about disputed or unclear rights, because the template does not resolve them.

Record content-use rights apart from any platform advertising permission. A status such as "approved" does not tell the next manager which action is allowed. For work near a licence deadline, use the rights-expiry record to find which use needs attention.

Keep the campaign's disclosure instructions and their review owner. For endorsements that reach U.S. consumers, FTC guidance covers material connections such as payment or free products. It advises placing a clear disclosure with the endorsement and warns against assuming a platform tool is enough. A staffing change should not lose those instructions. Get advice for the specific jurisdiction where the rules are uncertain.

A downloaded video can still have an open approval, an unpaid invoice or a licence close to expiry. Record each obligation on its own row, even when several concern the same creator. The table below is hypothetical and shows no real client.

Each of these rows stays open after the content folder arrives. A received folder cannot close the transfer on its own.

Test the handover against the next reply

Ask the incoming manager to say what they would send next. The example below is hypothetical. The dates, people and events are invented to show the decision.

The next message should confirm receipt and keep the existing promise. It should not chase a draft that already arrived, and it should not present the extra ending as agreed work.

An illustrative introduction for that case could read:

Hello Alex, I'm taking over as your campaign contact from Morgan. I have your draft and the current brief. Our feedback is due on 7 October. I'm checking the request for another ending with the client before we ask you to make changes. Please continue using this thread.

Send the introduction through the established business channel, with the outgoing manager copied where practical. If the outgoing manager is unavailable, tell the creator who now owns the work and ask only about gaps you could not close internally. For a program handover, agree who tells each active creator about the change and when, and name the new contact, the effective date and the current commitment in that message.

Accept the handover, then remove old access

Run acceptance with the incoming owners present. Check each point before you sign off:

• The incoming team has every agreed item, or has accepted a named exception.
• The incoming users can open the files and do the required account tasks with their own accounts.
• Every active creator has a named contact and a clear next action.
• Finance has accepted the unpaid, disputed and contingent amounts for follow-up.
• Reporting gaps and the limits of supplied reports stay visible.
• Every open obligation has an owner and a due date.
• Old access, integrations and copies each have a written removal or retention instruction.

Mark exceptions as "blocked" or "accepted with follow-up," with an owner and a deadline. Keep the final commercial settlement apart from the operational acceptance record, so a file receipt does not hide an unpaid amount.

After acceptance, remove the outgoing manager's or agency's access at the agreed time and record that it is done. For an agency, ask its responsible owner to confirm the agreed return, deletion or restricted retention of remaining copies.

Before the first message goes out, the incoming owner should be able to name the next promise they must keep, find its evidence, and act by its deadline.