Before contacting a creator, the new manager needs the agreed commitments, the latest conversation, any unresolved issue, and the next action with its owner and deadline. They also need to know who can approve changes. Put that information on one handover page, linked to the supporting records. Leave unrelated personal history out.
An influencer manager handover should let the incoming owner continue the conversation without asking the creator to reconstruct it. The procedure below is an operational recommendation. The privacy, copyright and disclosure guidance cited applies in the jurisdictions named.
Build the page from evidence
Start with the signed agreement, approved brief, latest amendments, current message thread and payment status. Read the most recent exchange even if a 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. Separate three states:
- Agreed. The record shows what the parties accepted.
- Requested. Someone proposed a change, but acceptance is missing.
- Unclear. Records conflict, or the person who made the promise lacked confirmed authority.
Do not silently turn a request into an obligation. If an email appears to change a signed term, flag it for the person authorized to resolve contract questions. The handover summary should point to that conflict rather than decide its legal effect.
Modash's relationship guide recommends onboarding documents and describes teams giving 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 will answer messages already in progress.
One-page relationship handover template
Copy this table into your team's approved workspace. It is an illustrative template, not a real creator record. Keep entries short and link to controlled records rather than pasting entire conversations.
| Field | What the incoming owner needs |
|---|---|
| Identity and contact route | Creator name and profile; business contact; agent's role; agreed channel; relevant time zone |
| Ownership | Outgoing owner; incoming owner; effective transfer time; backup; person authorized to approve changes |
| Current agreement | Agreement and amendment links; agreed deliverables; due dates; payment milestones; any unresolved interpretation |
| Brand commitments | Feedback due; product shipment or replacement promised; approved exceptions; person responsible for each |
| Live work | Current asset version; approval state; last feedback; reviewer; next deadline |
| Current conversation | Latest relevant thread link and date; what the creator asked; who owes the reply |
| Rights and disclosure | Licence record and expiry; allowed uses; unresolved permissions; current campaign disclosure instructions |
| Finance and logistics | Invoice or shipment status; responsible team; restricted record link when needed; no bank details |
| Working preferences | Creator-stated contact preference and availability relevant to this campaign, with source date |
| Next action | One concrete task; named owner; due date and time zone; blocker and escalation contact |
| Acceptance | Incoming owner confirms record access, identifies gaps, and accepts the next action; date of review |
For a payment record that needs separate handling, use the guide to keeping creator payment details out of campaign notes. The handover needs the payment status and finance contact, not a copy of the creator's banking information.
Keep useful context without transferring gossip
Ask one question of every relationship note: what work decision will this help the incoming manager make?
A creator's request to use email rather than phone helps route the next message. Speculation about why they dislike calls does not. A confirmed period of unavailability helps schedule work. The private family circumstances behind it usually add nothing to that task.
For organizations subject to 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 page is under review following the Data (Use and Access) Act.
That supports a practical editing rule: preserve the scheduling or communication consequence and question the need for the private explanation. Follow your organization's retention and legal-hold rules when handling the underlying records. Trimming the handover does not mean deleting evidence that must be retained.
Replace personality labels with dated events. "Difficult about revisions" gives the new manager little to act on. "Creator disputed a request outside the approved brief; scope decision pending with client lead" identifies the issue. If a relevant opinion must remain, label it as an opinion and include its author, date and basis, as the ICO guidance recommends.
Carry forward limits on use and approval
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. The new owner should check the actual agreement before offering reuse or extensions. Ask a qualified adviser about disputed or unclear rights; the template does not resolve them.
Record content-use rights separately from any platform advertising permission. A status such as "approved" is too vague to tell the next manager what action is allowed. For work approaching a licence deadline, use the rights-expiry record to identify which use needs attention.
Also preserve the campaign's disclosure instructions and review owner. For endorsements affecting U.S. consumers, FTC guidance covers material connections such as payment or free products. It advises placing an understandable disclosure with the endorsement and warns against assuming a platform tool is enough. A staffing change should not lose those instructions. Seek jurisdiction-specific advice where requirements are uncertain.
Test the handover against the next reply
The incoming manager should open the linked records using their own authorized account. Ask the administrator to arrange the required access and review the departing manager's access. Do not put passwords in the handover. If permissions are unclear, follow the creator-data access audit.
Then ask the incoming manager to explain what they would send next. The following example is hypothetical. Dates, people and events are invented to demonstrate the decision.
| Handover item | Hypothetical record |
|---|---|
| Latest creator message | Draft delivered on 5 October; creator asks whether the ending needs changes |
| Brand promise | Feedback due on 7 October, agreed in the existing email thread |
| Publishing date | 10 October under the current agreement |
| Open request | Client requested another ending; creator has not accepted the extra work |
| Next action | Incoming manager obtains the client's scope decision before sending feedback on 7 October |
The next message should acknowledge receipt and preserve the existing promise. It should not chase a draft already delivered or 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 involved where practical. If the outgoing manager is unavailable, tell the creator who now owns the work and ask only about gaps you could not resolve internally.
Before sending that first message, confirm that the incoming owner can name the promise they must keep next, find its evidence, and act by its deadline.
