Campaign Documentation Handover the Next Person Can Use

A good campaign documentation handover records the decisions, not the settings. The ad platform already stores most settings and a dated list of changes. What it does not store is why a campaign exists, what counted as success, what was tried and dropped, and what happens outside the platform: approvals, landing pages, tracking and who needs the report. Write those down in one short document per campaign, test it by asking someone else to read it cold, and the next person can repeat the campaign instead of rebuilding it from guesses.

This is for the in-house marketer who is leaving, going on leave, or simply realizing that everything important lives in their head. It is not a template to fill in for its own sake. A long document nobody reads is no better than none.

The limitation first: documentation cannot replace judgment

A handover document will not make the next person as good at your account as you are. It cannot capture the instinct you built from watching the same numbers for two years, and it will go out of date the week after you write it if nobody keeps it.

What it can do is narrower and still valuable: stop the next person from repeating tests you already ran, breaking tracking they did not know existed, or quietly changing what "a conversion" means. Aim for that. If you aim for a complete record of everything, you will write something too long to finish and too long to read.

What the platform already remembers

Before writing anything, know what you do not need to write. In Google Ads, change history does a lot of the work. Google's help page about change history (checked on 2026-09-27) says it "lists the changes made to your account, campaigns, and ad groups," including details such as when a campaign was paused, who added a keyword and the amounts of previous budgets. The same page sets a limit that matters for a handover: it covers "the past 2 years," and older data is not available.

So there is no value in writing out every bid change. There is real value in writing out:

  • Why a change was made, which change history does not record.
  • Anything older than two years that still shapes how the account is run.
  • Anything outside the ad platform, which change history never sees.

That split is the core of a useful document. It keeps the document short and points the reader at the right source for everything else.

The one-page campaign record

For each campaign that matters, write one page. If a campaign needs more than a page, it probably needs splitting, or the extra detail belongs in a separate test log.

Purpose and success

One or two sentences on what the campaign is for and what counts as success. "Generate demo requests from mid-size manufacturers in the US" is useful. "Brand awareness" is not, unless you also say how awareness was judged.

Include the target you were held to, where it came from, and who agreed it. The next person inherits that target and needs to know whether it was a considered number or a guess someone made in a planning meeting.

Structure and the reason for it

Note how the campaign is organized and, more importantly, why. If you split campaigns by region because the sales team reports by region, say so; otherwise the next person may consolidate them for tidiness and break the sales report. For context on the trade-offs, our guide to Google Ads account structure on a small budget covers why "few or many campaigns" has no single right answer.

Budget and who controls it

Record the budget, the period it covers, who approves changes, and any seasonal pattern you plan around. Note whether the budget is fixed by finance or flexible within limits, because that changes how much the next person can move it without asking.

Tracking and what a conversion means

This is the section most likely to save the next person a painful month. List each conversion action, whether it is primary or secondary, what triggers it, and any change to that definition with a date. If the conversion fires on a thank-you page, say which page; if it fires on a button click, say which button. Our piece on thank-you page versus button click conversion triggers explains why that detail changes the numbers.

Also note how the campaign's tracking links are tagged. If your team follows a shared UTM naming convention, link to it rather than restating it. If it does not, write down the pattern this campaign actually uses.

Outside the platform

Landing pages and who can edit them. Approval steps for ad copy, including anyone in legal or compliance who must sign off. Where leads go after conversion, and who in sales picks them up. Who receives the report, how often, and in what format. These live in email threads and memory, and they are the first things lost.

The test log: the part worth most

If you keep only one extra document, keep a test log. It is a simple table: date started, date ended, what changed, the conditions at the time, what you concluded, and whether you would try it again.

Field Why it matters
Dates Lets the reader match the test to change history and seasonality
What changed One change per row, so conclusions are attributable
Conditions Budget, bid strategy and conversion setup at the time
Conclusion Written as what you saw, not a verdict
Try again? Yes, no, or "only if conditions change," with the condition

Write conclusions with their conditions attached. "Broad match did not work" invites the next person to either ignore you or never try it again. "Broad match on the two service campaigns, for six weeks, on a manual bid strategy, while conversion tracking was still being fixed: search terms drifted and cost per lead rose, so we stopped" tells them exactly when the result might not hold.

Routines and where the bodies are buried

Two short lists round out the handover.

Routines. What you check daily, weekly and monthly, and roughly how long each takes. For example: search terms reviewed weekly, budget pacing checked every Monday, report sent on the first working day of the month. If reading the search terms report is part of the routine, point to a guide such as ours on how to read the Google Ads search terms report so the next person has a method, not just a task.

Known issues. Anything broken, half-fixed or fragile. The tag that sometimes double-fires. The landing page that the web team keeps changing. The stakeholder who expects a call before any budget change. These are uncomfortable to write down and are exactly what the next person most needs.

A campaign documentation handover checklist

Use this to check the document is complete enough, not to pad it:

  1. Each important campaign has a one-page record with purpose, success, structure, budget, tracking and outside-the-platform notes.
  2. Conversion actions are listed with their triggers and any definition changes, with dates.
  3. A test log exists, with conditions attached to each conclusion.
  4. Routines are listed with their frequency.
  5. Known issues are written down honestly.
  6. Access and billing are recorded: who has admin rights, who pays, and who to call.
  7. The document says where everything lives and when it was last updated.

Test it before you rely on it

The only real test of a handover document is whether someone who was not involved can use it. Ask a colleague to read it and answer three questions without asking you: what is this campaign for, how would you know it is working, and what should you not change without checking first. If they cannot answer, the document is not finished.

Do this while you are still around. A handover tested on your last day is not tested.

Keep it alive, or date it clearly

A document that drifts out of date becomes misleading. The lightest habit that works is adding a line to the test log and the campaign record whenever something meaningful changes, and putting a "last updated" date at the top. If you cannot commit to that, at least date the document so the next reader knows how far to trust it.

FAQ

What should a campaign documentation handover include?

For each important campaign: its purpose and success measure, structure and the reason for it, budget and who controls it, conversion tracking definitions, and anything that happens outside the ad platform. Add a test log, a list of routines and a list of known issues.

Do I need to document every change I made in Google Ads?

No. Google Ads change history already records changes to accounts, campaigns and ad groups for the past two years. Document why important changes were made, and anything older than two years or outside the platform.

How long should a handover document be?

Roughly one page per important campaign, plus a test log and short lists of routines and known issues. If it is too long for a colleague to read in one sitting, it will not be read.

When should I write campaign documentation?

Ideally as you go, with a line added whenever something meaningful changes. If you are writing it because you are leaving, start early enough that someone can test it with you still available to answer questions.

Who should review the handover document?

Someone who was not involved in running the campaign. If they can explain what it is for, how to tell if it is working and what not to change, the document does its job.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *