Content marketing campaigns almost never end where they began. The person who drafted the outreach list moves to another account, the editor who knew every contact goes on leave, or a freelancer finishes a contract halfway through a posting schedule. If you manage a publishing programme, you need a repeatable way to hand over a content campaign without losing the thread. This guide sets out the steps in order, so you can run them the same way each time.
Step 1: Decide what “handed over” means before you start
Write one sentence describing the finished state. For example: “The new owner can publish the next scheduled article, answer a question from a contact, and find every draft without asking me.” That sentence becomes your acceptance test. Without it, handovers end when the leaver runs out of time instead of when the receiver is ready.
Step 2: Take stock of every item in flight
List everything that is neither completely done nor completely untouched. In a content programme that usually means:
- drafts at various stages of editing;
- pitches sent and awaiting a reply;
- accounts created on external publishing platforms;
- scheduled posts and the dates they are due;
- promised follow-ups, such as a revised draft or an updated link.
Resist the urge to polish. A rough, honest inventory serves the receiver better than a tidy but partial one.
Step 3: Give every item a status and an owner
Beside each entry, add a status in plain words: finished, half done, not started, blocked. For half-done and blocked items, add one more line explaining why. If an article is stuck because a contact has not responded, say when you last wrote and what you said. The receiver should never have to guess whether silence means yes, no or not yet.
Step 4: Record where everything is kept
Re-discovery is the costly part of a careless exit, and most of it is hunting for files and logins. Make a short map: where drafts sit, where published links are tracked, where outreach correspondence is stored, and who holds access to each platform. Never paste passwords into the note itself; point to the place where the team keeps them.
If your programme involves publishing on community and article platforms, add platform-specific notes. A quick pointer to a how-to such as posting an article on a developer community site saves a new owner from relearning the account setup and formatting rules from scratch.
Step 5: Flag what to watch for
This is the section people skip, and it is the most useful one. Include anything that does not show up in a spreadsheet:
- A contact who prefers short messages, or who replies only on certain days.
- A platform whose guidelines changed and caught you out.
- A draft that reads well but contains a claim you could not source.
- A deadline that looks flexible but is not.
Keep each one to a sentence. The aim is to spare the next person your mistakes, not to impress them with detail.
Step 6: Name who to ask
For every area, list one person to contact and the practical way to reach them. If the leaver will remain available for a short period, say how long and for what kind of question. Setting a time limit is a kindness to both sides. The receiver knows how long the safety net lasts, and the leaver can plan their next role without an open-ended obligation.
Step 7: Walk through it together
Hold a short session, even fifteen minutes, where you present the note and the receiver asks questions. Ask them to summarise the plan back to you. If their summary differs from yours, that is a gap in the note, and it is much cheaper to fix it now. Where a meeting is impossible, a recorded walkthrough or a written exchange of questions achieves the same thing.
Step 8: Let the receiver take the first action
A handover is proven by use. Pick one small task, such as publishing a scheduled piece or replying to a pending pitch, and let the new owner do it while you are still reachable. Note any point where they had to ask, then add it to the document. The platform-specific guides your team already relies on, for example the one on setting up a newsletter account and publishing a first piece, can sit alongside the note as reference material so the receiver does not have to ask for basic mechanics.
A short worked example
Imagine a three-month programme to publish tutorial articles across several external platforms. The outgoing owner’s note might say that four articles are finished and live, two are in editing with comments waiting on the writer, and one pitch is stalled because the platform asked for a shorter version. It lists the shared folder holding drafts, the tracker where live links are logged, and the colleague who holds the platform logins. It warns that one platform rewrites headlines on publication, so tracked links should be checked after going live. It names the editor as the contact for style questions for the next fortnight.
That note is under two hundred words. A newcomer reading it can act on the same morning, without a single message to the person who has left.
Mistakes that undermine a handover
- Handing over only the happy path. If the note lists successes and omits stalled items, the receiver rediscovers the problems the hard way.
- Burying the key point. Put the most time-sensitive item first, not in the middle of a long document.
- Assuming shared context. Shorthand that was obvious to you, such as nicknames for contacts or internal campaign names, means nothing to a newcomer.
- Leaving it until the last day. Draft the note a week earlier and keep updating it. Last-day notes are always the thinnest.
Step 9: Close out your own side
Before you step away, remove yourself from places where you were the only contact, hand over any personal accounts that were used for work, and update shared tracking sheets so they show the new owner. This sounds administrative, but outdated ownership records cause confusion months later, when a contact writes to someone who no longer reads the inbox.
When the work is a short outside engagement
Content teams often bring in freelancers for a few weeks at a time, and technical projects behind a publishing operation, from site tooling to automation scripts, are frequently done the same way. For that kind of arrangement, a portal like DevOps FreeLancers exists to list DevOps freelancers by country. The nine steps above translate directly: ask for a closing note covering what was delivered, what is unfinished, where it lives and what needs care, and agree on it before the engagement ends rather than after.
A template you can copy
Keep it on one page and reuse it for every campaign:
- Goal of the campaign in one sentence.
- Finished: items complete and requiring no action.
- In progress: each item, its status, the reason it is paused, and the next step.
- Where things are: folders, trackers, correspondence, access holders.
- Watch out for: quirks, dates, claims needing checks.
- Who to ask: names, topics and the period of availability.
Run the nine steps once and the template will feel obvious. Run them every time and campaigns stop depending on whoever happens to remember the details. The next person picks up where you stopped, and the audience never notices that anyone changed hands.