Most small publisher ad ops teams are quietly running two jobs. One is the direct-sold job: pacing, delivery commitments, advertiser communication. The other is the programmatic job: yield, fill, deal health, discrepancy chasing. When volume on both sides grows faster than headcount, the team does not get twice as busy. It gets a different kind of failure mode. This is the practical diagnosis of that problem and the coverage model that keeps both jobs from leaking.

Engineering teams solved the always-on coverage problem decades ago: on-call rotations, a pager that only fires on real signal, runbooks that make any engineer effective at 3 AM, and postmortems that fix systems instead of blaming people. Publisher ad ops runs the same always-on risk - campaigns deliver seven days a week - with none of the machinery: everyone vaguely watching everything, detection by whoever happens to look. Here's the translation: how the on-call playbook maps to ad ops, and how a daily coordinator turns GAM coverage into a calm, one-person duty.

Every summer handover doc ever written: "Check pacing on the Q3 campaigns. Keep an eye on revenue. Watch the video fill. You know, the usual." The usual is a full-time job, and the person covering already has one. Here's the handover doc structure that actually works - five sections, each answering a question the covering person will genuinely face - plus the part most handover advice misses: the checking work you should automate instead of writing down.

Half the team is out. The campaigns don't know that, and the under-delivery definitely doesn't care. Summer is when publisher ad ops slips - not because anyone's careless, but because the person who usually catches the problem is on a beach. This guide covers the vacation-season coverage math, the three failure patterns that cost publishers real revenue every summer, and how to build coverage that doesn't depend on who happens to be in.