Before accepting a ChatGPT campaign handover, the incoming operator should be able to answer one question: what needs my attention next, and why? A folder of creative files and a dashboard link may be useful, but neither necessarily contains the answer.
A good handover transfers operational judgment as well as information. It explains the current configuration, the evidence behind recent decisions and the boundaries of the new operator’s responsibility. This guide concerns continuity within an ongoing campaign. It does not describe a platform mechanism for transferring account ownership or an agency’s full client-offboarding process.
Start with tomorrow’s work
Put the next scheduled check at the top of the handover note. State when it happens, which source the operator should open, what they should inspect and who can decide if action is needed. “Monitor performance” is too broad to serve as the first instruction.
For example, an internal handover might say that the next review will compare completed reporting periods after a known data-refresh interval. Another might prioritize verifying a corrected destination. These are different tasks, and the distinction should come from the campaign’s actual situation rather than a standard list pasted into every handover.
Include deadlines outside the advertising interface. An offer can end while a campaign remains configured. A client can require approval before new copy is submitted. A product team can be planning a page change that affects the advertised destination. The incoming operator needs the relevant dependency and a contact, not the entire organization’s calendar.
Leave a map of the current state
Record the account and campaign identifiers, then show how the relevant ad groups and ads connect. Keep names for readability, but retain stable identifiers so a rename does not make the note ambiguous. Link to the controlled source record instead of scattering screenshots through unrelated messages.
Describe what is active, paused or awaiting a decision using an observation time. A handover note is a snapshot, not a live guarantee. The receiver should confirm the current state before making a consequential change, particularly if work continued after the note was prepared.
OpenAI’s campaign-management documentation distinguishes campaign, ad-group and ad state. A visible creative preview is therefore not enough to establish the full operating condition. The handover should point the receiver to the relevant status checks in the tools they actually use, without inventing controls that their interface does not expose.
Preserve the reason behind the unusual settings
Most configuration fields explain what is set, not why it was chosen. Highlight the exceptions that another operator might otherwise “clean up.” An intentionally narrow offer, a paused creative awaiting confirmation or a budget held while a reporting issue is investigated can look accidental without its decision context.
Use three separate labels in the note:
- Observed: something checked in the account or supporting evidence, with a time and source.
- Decided: an approved course of action, with the responsible decision-maker.
- Unresolved: a question that still needs evidence or approval before action.
This separation prevents a tentative explanation from becoming an inherited fact. “We suspect the destination affects enquiries” is different from “the destination caused the decline.” The incoming operator needs to know which statement is supported and which remains a hypothesis.
Link recent report snapshots where they explain a decision. Include the definitions of unusual metrics through the metric dictionary. A chart without its reporting period or outcome definition can mislead a competent new operator as easily as a novice.
Separate evidence from assumptions
- Observed
The checked destination opens the intended offer at the recorded time.
Checkpoint - Decided
The owner has agreed that the next comparison will use completed periods.
- Unresolved
The reason for the change in enquiry count remains to be investigated.
Reconsider
Transfer responsibilities explicitly
State what the receiver can change independently and what requires a further decision. Identify the person who approves changes to offers, spend plans or client-facing claims in this workflow. The handover itself should not silently expand that authority.
Keep credential handling separate from the operational note. Confirm that the receiving person has the appropriate access through the organization’s established process. Do not paste secrets into the handover document to make a demonstration convenient. A document may circulate more widely and live longer than the temporary access need. When reporting or conversion services depend on API access, use the credential handover procedure to verify each dependency before retiring previous access.
Record who remains responsible during the transition. If the outgoing operator continues making changes, agree how those changes reach the receiver. A clear handover time and one shared update location reduce the chance of two people acting on different versions of the same plan.
Ask for a demonstration, not just a signature
Have the receiver locate the correct campaign, explain the next scheduled check and identify one unresolved question. They should be able to find the evidence for the most recent significant change and describe the escalation route if the next check fails.
This can be a read-only walkthrough. There is no need to change a live campaign merely to prove that the handover happened. If the process includes a recovery scenario, use the existing rollback record to discuss what would be restored and which later changes must be preserved.
Capture any missing information as specific follow-up items with owners. Close the handover when the receiver can perform the agreed routine and the responsibility boundary is understood. A large document is not the completion criterion. A usable next action, supported by current evidence and clear authority, is. Consult OpenAI campaign management for the relevant platform operations when maintaining the team’s instructions.
Sources and scope
Transfer day-to-day responsibility for an active campaign through current state, upcoming decisions, unresolved questions and a practical receiver check.
Working methods and examples are editorial suggestions. Check current platform requirements and available features before implementation.