An Operations Runbook for a Growing Ad Program: Daily, Weekly and Monthly Routines

Editorial team Spend Ledger

Why a growing ad program needs a runbook

As advertising activity grows, routine decisions can become harder to track. More campaigns, payment arrangements, account levels and people with access create more opportunities for missed notices, unclear ownership or conflicting changes. A runbook makes the work repeatable: it records what the team checks, who is responsible, what to do when something looks wrong and where to escalate a question.

The runbook is not a substitute for platform policies, account terms or approval processes. It should direct the team to the relevant official help, policy and support channels when a platform notice or restriction needs attention. If delivery stops, a balance changes unexpectedly or verification is requested, the response is to understand and address the cause through those channels—not to route activity around a check or restriction.

Keep the document focused on operational decisions. A useful runbook can explain how the team monitors delivery and balances, reviews performance, reconciles records, manages access and documents changes. It should also make clear who owns each routine and who can act if that person is unavailable. The aim is dependable handling, not a promise that campaigns will perform or accounts will remain available.

Set the scope and assign ownership

Begin by listing the advertising accounts and business-level structures covered by the runbook. Describe how the team understands the relationship between business access, ad accounts, campaigns and payment arrangements. Use the platform’s own terminology where it matters, and avoid informal labels that could make ownership ambiguous.

For each routine, name a role rather than relying on an individual’s memory. A delivery owner can review campaign status; a finance owner can check balances and reconcile charges; an account administrator can review permissions; and a program lead can approve material changes. In a small team, one person may hold several roles, but the responsibilities should still be separated in the document. That makes handoffs easier and helps the team notice when a decision needs a second review.

Record who is allowed to make routine adjustments and what requires approval. For example, the runbook can distinguish a correction to a documented setup from a change to targeting, budget allocation, payment details or account ownership. It need not invent a universal approval threshold. The team can define its own approval rules and revise them as its governance needs change.

If accounts are prepared internally or provided through an agency arrangement, document the actual operating relationship. Record who controls access, who pays, who handles support requests and who is responsible for keeping business and billing details current. An account is a work tool, not a way to avoid platform requirements. Any arrangement should be clear in writing and consistent with the applicable platform terms.

Daily checks: delivery, balances and notices

The daily routine should catch issues that need attention before they become harder to diagnose. The delivery owner checks whether active campaigns are serving as expected, whether a campaign or account shows a warning, and whether recent changes correspond to the current plan. The check is not simply a glance at spend. It should include status, pacing, unexpected pauses and any material difference between the intended setup and what the platform displays.

The finance owner reviews payment and balance information available in the account. The purpose is to notice failed or pending payments, unexpected charges, a balance that needs attention, or a mismatch with the team’s records. The runbook should say where the team records a discrepancy and who follows up. Current balance rules, payment methods and other platform-specific values should be checked on the platform’s own help and policy pages rather than copied into a document that may become outdated.

A designated owner also checks account notices and messages. Record the notice’s subject, affected account or campaign, the action requested and the person responsible for follow-up. If the notice involves verification, policy compliance, billing or an appeal, use the official process and keep the relevant correspondence in the team’s approved records. Do not guess at what a notice means or make changes intended to conceal the situation.

Close the daily check with a brief status entry: no action needed, action assigned, or escalation underway. Include enough context for another team member to understand what happened, without copying sensitive information into an unnecessarily broad record. If delivery or access is disrupted, pause discretionary changes until the cause and next step are clear.

Weekly review: results, changes and learning

The weekly review looks across the program rather than treating each campaign as an isolated task. The performance owner compares results with the campaign’s stated objective and the assumptions used to plan it. Depending on the objective, the team may review conversions, cost per action, spend, return, or another relevant measure. Explain how each measure is defined so that the team does not compare unlike outcomes.

The review should connect performance to changes made during the period. Note what changed, why it changed, who approved it and what outcome the team intended to observe. This creates a useful record when results move, while avoiding unsupported claims about cause. A change and a result occurring together do not by themselves prove that one caused the other.

Use the review to decide whether to continue the current approach, investigate a concern, or plan a controlled adjustment. Before increasing spend, check that the business can support the associated payment and that the team understands the risks of the proposed change. Avoid treating a weak result as a reason to move activity into another account to escape a platform limit, review or policy check. Investigate the underlying issue and follow the applicable rules.

Keep the weekly record concise. A summary can state the main observation, the decision, the owner and the next review point. Detailed analysis can live in the team’s normal reporting records, while the runbook explains where those records belong and what must be retained. The goal is a clear decision trail, not a second reporting system.

Monthly routine: reconciliation and access review

The monthly routine brings advertising records and financial records together. The finance owner compares platform billing information with the team’s internal records, including payments, credits or adjustments shown by the platform. Investigate differences rather than forcing figures to match. Record what remains unresolved, who is following up and which official support channel applies. Current billing terms and platform-specific processes should be confirmed in official help and policy pages.

The review should also check how spend is allocated across the program and whether the accounting records reflect the relevant business, campaign and account structure. Where an agency or another service provider is involved, confirm that responsibilities, billing arrangements and access expectations still match the written agreement. If the arrangement has changed, update the records and resolve any ambiguity before relying on the old description.

An access review checks whether each person still needs the permissions they hold and whether those permissions match their responsibilities. Remove access that is no longer required through the platform’s normal controls, and follow the platform’s security and identity requirements. Do not share credentials informally or keep access in place merely because removing it may require coordination. Record the review and any follow-up without exposing passwords or sensitive verification material.

The monthly routine can also check whether the runbook reflects current account ownership, payment responsibilities and escalation contacts. This is especially useful after team changes, a change in agency arrangements, or a reorganisation of business-level access.

Escalation, exceptions and handoffs

A runbook should explain what happens when a routine check finds something outside the team’s authority. The person who spots the issue records the relevant account or campaign, the visible status, the time it was noticed and any action already taken. They then notify the designated owner and avoid making additional changes that could complicate diagnosis.

For platform decisions, restrictions, verification requests and policy questions, the designated owner should use the platform’s official support or appeal channels. The runbook can point to the location of those channels without reproducing policy interpretations that may become stale. Keep copies of relevant notices and responses in an access-controlled place, and assign one person to coordinate the case so that the platform receives consistent information.

Define a handoff for absences and urgent issues. A deputy should know where to find current status, what decisions they may make and which matters must wait for the primary owner or an authorised approver. If a problem affects billing, compliance or business access, the runbook should direct staff to the appropriate internal decision-maker rather than encouraging improvised workarounds.

Exceptions should be documented as exceptions, not quietly converted into normal practice. If the same issue recurs, review whether the routine, training or account structure needs correction. Do not add procedures that circumvent platform rules, limits, verification or checks.

Keep the document short, findable and safe

Store the runbook in the team’s approved, access-controlled documentation space. It should be easy for authorised staff to find but not broadly exposed. Avoid putting passwords, payment credentials, identity documents or other sensitive material in the runbook. Instead, explain which approved process or secure record contains the necessary information, and who may access it.

Use plain language and a consistent format for each routine: owner, purpose, checks, record to update and escalation route. A short checklist is often easier to follow than a long explanation of every possible scenario. Put detailed platform-specific instructions in a separate reference only when they are necessary, and identify them as material that must be checked against current official guidance.

Keep the runbook separate from campaign strategy. It should not become a catalogue of every test, result or temporary adjustment. Link the routine to the appropriate reporting and finance records, and state what information must be entered there. This reduces duplication and makes it easier to update the operational document without rewriting historical analysis.

Use a clear revision record that shows what changed, who approved the change and why. Do not retain obsolete instructions as if they still apply. If an old process is useful for context, mark it clearly as superseded and keep it outside the active checklist.

When to revise and how to maintain it

Review the runbook when the way the team works changes: a new account structure is introduced, responsibilities move, billing arrangements change, access is reorganised, or a recurring issue exposes a gap. Also revise it when official platform guidance changes in a way that affects the team’s routine. The team should not rely on a fixed calendar alone; an operational change may require an update before the next scheduled review.

Ask the people who perform the checks to identify unclear instructions, unnecessary steps and missing escalation paths. The owner of the runbook should resolve those comments, obtain any required approval and communicate the updated process to affected staff. A revision is not complete if the new version exists but the team continues to use an old copy.

A practical runbook is specific enough to guide action but restrained enough to stay current. Daily checks protect visibility over delivery, balances and notices; weekly reviews connect results to decisions; monthly reconciliation and access review strengthen financial and operational control. Clear ownership, honest records and official escalation routes help a growing program remain understandable without treating account structure as a route around platform rules.