Signing an outsourcing agreement is the easy part. The first month afterwards decides whether the partnership feels like a relief or like a second job. Most outsourcing arrangements that go wrong don't fail because the partner lacked skill; they fail because the handover was rushed, access was granted piecemeal, and nobody wrote down the dozens of small rules that the previous team carried in their heads.
In short: a good transition runs in four stages over roughly a month: access and documentation first, then a shadow period where the new team watches your live work, then a reverse-shadow period where they do the work while you check it, and finally a formal go-live with agreed reporting and escalation. Skipping the shadow stages is the single most common reason early campaigns go out with avoidable mistakes.
1Before Day One: Access, Inventory and Ground Rules
Start by listing every platform the outsourced team will touch: your ad server, each DSP or SSP seat, verification and measurement tools, creative storage, ticketing, and the chat channel where requests arrive. For each one, decide the permission level up front. Trafficking roles rarely need billing or user-management rights, and giving named, individual logins rather than shared credentials keeps an audit trail of who changed what. This is also the moment to agree how access is removed when someone rotates off the account.
Alongside access, agree the ground rules in writing: who is allowed to submit requests, what a complete request looks like, the turnaround expected for each request type, and which actions always need your sign-off before going live. If those rules aren't written down yet, the onboarding is the right time to write them, because the new team will ask every question your previous process quietly skipped.
2Week 1: Document the Unwritten Rules
Every ad operations setup has conventions that exist only in someone's memory: naming formats for orders and line items, which advertisers need a manual creative check, why a particular key-value exists, which reports go to which client and when. The first week should turn as much of that as possible into a shared runbook. A practical approach is to walk through a handful of recent campaigns end to end and note every decision that was made along the way, rather than trying to write a manual from scratch.
The runbook should cover at least these areas:
| Runbook area | What to cover |
|---|---|
| Naming conventions | Orders, line items, creatives and placements, with examples |
| Request intake | The brief template, required assets and where they arrive |
| QA standards | What gets checked before launch and who signs it off. Our ad trafficking QA checklist is a reasonable starting point |
| Reporting | Which reports, for whom, how often and in what format |
| Escalation | Who to contact for a delivery problem, a creative rejection or a billing question, and how fast |
3Week 2: The Shadow Period
During the shadow period your current team keeps doing the work while the incoming team watches and asks questions. It feels slow, but it is the cheapest way to surface the exceptions that never make it into documentation. Encourage the new team to log every question they ask; that list becomes the runbook's missing chapters.
If you have no in-house team left to shadow, because the reason you are outsourcing is that someone left, replace the shadow period with a structured audit of the live setup instead. The outsourced team reviews every active campaign, flags anything they don't understand, and you answer those questions before they take ownership. Partners who offer technical advisory work will usually run this audit as a defined piece of work.
4Week 3: Reverse Shadow
In the reverse-shadow stage the outsourced team does the work and your team reviews it before anything goes live. Start with lower-risk tasks such as creative swaps, flight extensions and routine reporting, then move to new campaign builds once the error rate on simpler work is consistently low. Keep a simple log of corrections. If the same correction appears twice, it belongs in the runbook.
This is also the week to test the escalation path deliberately. Raise a mock urgent issue outside normal hours, if the agreement covers out-of-hours support, and see how long the response actually takes. It is far better to discover a gap in coverage during onboarding than during a live campaign.
5Week 4: Go-Live and the First Review
Go-live means the outsourced team owns execution and your team moves from checking every task to spot-checking. Agree in advance what "owning" means: which tasks no longer need approval, and which still do. Most teams keep sign-off on new advertiser launches and budget changes for a while longer, and that is a sensible default.
Schedule a formal review at the end of the first month. Look at turnaround times against what was agreed, the number and type of corrections, and anything that fell between the two teams. Update the runbook and the service levels based on what you find. The terms you agree here are worth formalizing; our guide to ad ops outsourcing SLAs covers what belongs in that agreement.
6Common Onboarding Mistakes to Avoid
- Handing over during peak season. If you can, start the transition before a busy quarter rather than in the middle of it.
- Shared logins. They make it impossible to tell who changed a setting and hard to remove access cleanly later.
- Skipping the shadow stages to save two weeks, then spending longer fixing preventable launch errors.
- No single owner on your side. The outsourced team needs one person who can answer questions and make decisions quickly.
- Treating the runbook as finished. It should be updated every time an exception is found.
If you are planning a handover and want a team that runs this process as standard, see how our outsourced ad operations engagements are set up, or talk to us about your current stack.
