AI for Advertising Agencies: Media Plans and Weekly Budget Checks

An advertising agency can use AI to turn a checked client brief into a draft media plan with objectives, audiences, channel roles, test budget and measurement rules. Each week, export actual spend, calculate pace against the authorised schedule, then ask AI to explain exceptions. A media buyer verifies the data and obtains human sign-off before changing spend.

Keep arithmetic outside the language model where possible. A spreadsheet can calculate budget remaining and projected finish consistently; AI is useful for drafting the rationale and surfacing missing assumptions. The client-approved budget, platform settings and finance record may differ. The team must identify which figure governs the plan before a weekly check can mean anything.

Follow me on Instagram@sagnikteaches

Google Ads describes an average daily budget, a daily spending limit and a monthly limit for most campaigns, and also documents a separate campaign total budget option. Those are platform controls, not necessarily the client's agency-wide authorisation. A client may cap total spend across several platforms or include production fees in a single number. Do not treat a platform's budget field as proof of what the client agreed.

Connect on LinkedInSagnik Bhattacharya

Give the planning prompt an approved source pack

Start with the client's commercial objective, offer, deadline, approved media ceiling, exclusions, existing performance and conversion definition. Add what cannot be changed: brand claims, restricted audiences, creative availability and who approves changes. Mark every number with its period and source. If historical performance is incomplete, say so; AI should not manufacture a likely cost per result to make the channel mix look convincing.

Subscribe on YouTube@sagnikteaches

Use a plan sheet with columns for channel, role, audience hypothesis, creative, budget, dates, success measure, tracking owner and approval state. AI can suggest entries, but the planner checks feasibility. A channel may be attractive in the abstract yet unsuitable if the client has no landing page or cannot respond to enquiries promptly. The task is to make a decision-ready draft, not to produce a long list of platforms.

Take a sports club with $12,000 of authorised media spend over six weeks to recruit members. It has a working enquiry form, two short videos and no conversion history for a new paid channel. The planner sets aside $1,200 for a small test, $7,200 for the established search activity and $3,600 for social retargeting and creative tests. The split is for illustration only; the client's evidence sets the real one. A useful AI draft explains what evidence would justify moving money after week two.

Ask the model for alternatives with different risks, not a single supposedly optimal split. One version may prioritise known demand; another may buy learning in a new audience. Require it to label unsupported assumptions and identify what must be checked before launch. The detailed channel-mix planning tutorial covers allocation choices; this workflow concentrates on carrying the approved plan into weekly budget control.

Using only the approved brief below, draft a six-week media plan.
Show each channel's role, proposed allocation, evidence used,
tracking requirement and the decision needed before launch.
Do not invent cost-per-result benchmarks. Label unsupported
assumptions and leave unknown figures blank. Total proposed
media spend must equal $12,000. Do not include agency fees.

In an illustrative run, the returned plan might allocate $7,200, $3,600 and $1,200 correctly but say “search will deliver 240 enquiries at $30 each”. The brief contains no basis for that forecast. The planner deletes the 240-enquiry claim, labels the expected response unknown and defines a two-week measurement gate. The arithmetic was sound; the performance promise was not. This is exactly the sort of difference a reviewer should catch.

Freeze the authorised version before campaigns go live

Give the approved plan a version identifier, authorisation date and approver. Store the approved spend by channel, campaign and week. Record whether the amounts are gross media spend, fees included, or a ceiling rather than a target. If the client later changes the allocation, keep the old version and a short change reason. A weekly checker must compare actuals with the plan that was in force during the period, not with a newly edited spreadsheet.

Before launch, confirm that tracking measures the agreed outcome. An ad platform's “conversion” might be a form submission while the client cares about booked tours or paid membership. Use the agreed measure for evaluation and the platform measure for delivery diagnostics. If the distinction is not written in the plan, AI may call a platform event a sale in the first report. Conversion tracking before AI-managed ads explains the measurement checks in more detail.

Period mismatches are the classic launch error. The sports club's approved sheet has a $3,600 social allocation but the buyer enters a $3,600 monthly budget on a campaign meant to run six weeks. The weekly check may show spending “on pace” against the wrong period if it reads only the platform setting. A pre-launch reconciliation compares the approved total and dates with the live budget fields, and the buyer corrects the mismatch before delivery starts.

Define who can authorise a reallocation. A buyer may be allowed to move a small amount between creative variants while moving funds between channels requires the client. Write that rule down rather than having AI infer it from past emails. The review gate should include the plan version, proposed change, reason, projected effect and required approver. No AI output is itself an authorisation.

Calculate weekly pace from a complete spend export

On the same day each week, export spend with campaign ID, channel, date, currency and status. Check the report's time zone and last complete day. Join each campaign to the approved plan by a stable identifier, not by a name that a buyer might edit. Flag missing, duplicate and unmatched campaigns before calculating pace. A blank actual may mean no spend or a broken export; those should be different statuses.

For a flat schedule, expected spend to date equals approved budget multiplied by elapsed days divided by planned days. The pace gap is actual spend minus expected spend. Projected finish at the current average daily rate equals actual spend plus that rate times remaining days. These calculations are diagnostic, not a recommendation to change settings. Use a planned weekly curve instead when spend is intentionally front-loaded, phased around a launch or held for a creative test.

Worked illustration: the $12,000 sports-club campaign runs 42 days. At the end of day 14, a flat plan expects $4,000. The export shows $4,700, so the gap is $700 above flat pace, or 17.5% of the expected amount. Average actual daily spend is about $335.71. If that rate continued for 28 more days, projected total would be about $14,100, $2,100 above the authorised ceiling. The buyer checks the phased plan before treating that projection as a problem.

Assume the approved schedule deliberately allocated $5,000 to the first 14 days for an opening push. Against that schedule, $4,700 is $300 under, not $700 over. The same spend export produces opposite labels depending on the authorised curve. The agency should store the weekly schedule with the plan and show both comparisons if a client finds flat pace useful. The decision is based on the approved schedule and expected outcomes, not whichever graph looks neater.

Use a simple threshold to focus the review, perhaps a deviation above 10% of the expected spend or a projected finish above the client ceiling. This is an illustrative policy threshold, not a platform rule. Also trigger a check when a campaign has spend but no matching plan row, or when the export is stale. AI may draft a sentence explaining the flag, but the spreadsheet should compute it and preserve the inputs.

Turn an alert into a buyer question, not a budget edit

For each flag, provide the buyer with a compact exception card: campaign ID, plan version, authorised period and budget, spend through date, expected spend, gap, projected finish, data freshness, suspected reason and approval required. Ask AI to write two or three investigative questions from that card. It should not propose a specific new budget unless the agency has independently modelled the options and the person authorised to act has reviewed them.

A well-formed alert reads: “Campaign S-14 spent $800 in week two against $500 planned; the export is complete to Sunday. Was the extra $300 planned for the event weekend? If not, should the buyer check delivery settings and request a client decision?” That is useful because it points to the reason. An alert saying “overspend detected; reduce by 37.5%” mistakes a numerical gap for an operational instruction.

Another example concerns a campaign that spent only $90 against a $600 weekly allocation. AI may call it efficient because cost per click is low. The buyer sees that the campaign has almost no impressions because the approved creative was rejected or the audience is too narrow. Under-spend can mean a missed opportunity, a tracking issue or a deliberate pause. The exception card needs status and delivery context, not just spend.

For most Google Ads campaigns using average daily budgets, the platform says a day's billable spend can reach twice the average daily budget and describes a monthly spending limit based on 30.4 times that daily budget. A one-day spike is therefore not automatically evidence of a broken budget. The buyer compares the period's spend and billing rules with the client's actual ceiling. A campaign total budget works differently. It is available for Search, Performance Max, Shopping, Demand Gen and YouTube campaigns; Google adjusts daily spend to use the total across the campaign's dates, daily spending limits do not apply, and its help page says you will never be charged more than the total. Under either control, a heavy day in mid-campaign can be expected behaviour, so the weekly check should judge the period rather than the day. Verify current platform documentation before changing settings.

Make weekly sign-off short enough to happen

Hold a 15-minute buyer review at a fixed point in the week. Start with data quality flags, then campaign pacing, then performance against the agreed outcome. Record one of four decisions for each exception: no change, investigate, prepare change for approval, or stop pending clarification. Keep the reason and approver alongside the decision. The AI draft can turn the review notes into a client update, but a buyer checks that it does not imply an unapproved adjustment.

A sample review note: “No change to search budget. Spend is $420 under the approved week-three curve because the landing page was unavailable for two days. The buyer will confirm page stability before suggesting a catch-up allocation.” A weak AI rewrite might remove the outage and say “we are strategically pacing spend”. The reviewer restores the operational fact, because it matters to the client's understanding of results.

If the client approves a change, the buyer edits the live platform setting, captures the before and after values and updates the plan version. Re-run the weekly projection against the remaining period. A new budget in the ad interface without a revised planning record leaves next week's AI analysis comparing against an obsolete number. The agency automation sequence shows where a pacing alert can fit among other hand-offs without handing spend control to the automation.

Reconcile the plan with invoices and platform definitions

A weekly export is a delivery view, while a client's invoice may include credits, adjustments or charges that settle later. Keep a separate reconciliation between platform spend, billable amount and the client's agreed cap. The agency should decide which figure its pacing alert uses and state it. A forecast based on delivered cost can be useful operationally, but it is not automatically the final amount due. Ask the finance owner how credits and fees are shown in the client account before presenting a “remaining budget” number.

Another common mismatch is tax or fee treatment, which differs by account and contract. The plan should say whether a $12,000 ceiling is media only or includes the agency's management fee and any other charges. Do not let AI infer this from the phrase “total budget”. If the client authorised $12,000 all-in and $2,000 is reserved for the agency fee, the media ceiling is $10,000. A pacing sheet using $12,000 as spendable media would overstate available funds by $2,000. The numbers are illustrative; the contract is the source.

For the sports-club example, assume two platforms export cost through Sunday but one invoice posts an adjustment on Tuesday. The buyer's Monday pacing review uses the complete Sunday delivery export and labels it “provisional delivery spend”. The finance check later reconciles the adjustment and reports any difference. Mixing the Tuesday invoice into only one channel's Monday export would make the channel comparison inconsistent. A labelled lag is preferable to false precision.

Set a naming convention for client, campaign and plan version. A campaign renamed from “Autumn trial” to “Membership launch” should still join by stable platform ID. If a buyer duplicates a campaign, the new ID should appear as unmatched until assigned to the plan. This is a useful safety alert: spend in an unplanned campaign can escape a name-based report entirely. The weekly review should treat unmatched paid activity as a priority even when aggregate spend appears within the client ceiling.

Test the weekly checker against awkward weeks

Before relying on an automated alert, run a small set of controlled examples. Include a normal week, a deliberately front-loaded week, a paused campaign, a campaign created mid-period, a currency mismatch, a missing export row and a duplicated campaign. The expected answer is not always “over” or “under”. The checker should sometimes say “cannot assess until data is corrected”. Have the buyer write the expected label before running the AI explanation, then compare the two.

Take a paused campaign with $1,500 assigned to week four and $0 spent because the client held creative approval. A flat pacing alarm would claim the media buyer failed to deliver. The correct note is that spend was paused by client instruction, and the $1,500 remains unspent until the client decides whether to move or release it. The alert should carry the approval record and ask the account lead for a decision; it should not silently spread the amount over the remaining days.

In a second test, the export repeats one campaign's $620 spend row because the analyst downloaded overlapping date ranges. A naive sum reports $1,240 and warns of overspend. The data check spots duplicate campaign ID, date and amount, stops the projection and asks for a clean export. If AI is asked to explain the doubled figure first, it may produce a persuasive but false story about auction pressure. Validate the rows before asking for prose.

A third test uses different currencies in the two source files. Even if both columns display a dollar sign in a spreadsheet format, the underlying accounts may differ. The workflow should stop and identify the mismatch. The media buyer chooses an agreed conversion source and date if cross-currency reporting is required; the AI must not guess a current rate. The client's approval should specify which currency governs the ceiling.

Finally, test the release gate itself. Give the checker a genuine overspend projection and ask whether it can change the platform budget. It should create a review card, not an edit. The buyer confirms the data, proposes options and obtains the right authorisation. Log the final choice so next week's comparison uses the updated plan. A workflow that generates correct warnings but can bypass approval has failed its most important design requirement.

Check the workflow after four weeks. Count alerts that found a real issue, alerts caused by stale or mismatched data, missed budget problems and changes made without the right approval. If half the alerts are false, fix the data join or schedule before adding more AI prose. If a campaign is healthy but performance is poor, address creative, audience or tracking as a separate decision. A pacing check protects the agreed spend route; it does not prove the campaign is effective.

Media planning and pacing questions

Can AI decide the channel split?

AI can propose alternatives from the client brief and historical evidence, but the media planner should check reach, tracking, minimum viable test spend and client constraints. Treat the split as a proposal until the client authorises the plan and the channel specialist confirms the campaign setup.

Should a pacing alert change the budget automatically?

No. Use an alert to bring the source data, calculation and reason for review to the media buyer. A budget edit can change delivery and billing, so a named person should verify the period, planned spend curve and client authority before making it.

What if the spend export is delayed?

Label its last complete date and do not compare it with a newer plan as though the figures are current. Re-run the check when the export is complete. A stale-data alert is better than a confident overspend warning based on an incomplete day.

Further reads

• How Marketing Agencies Use AI to Automate Client Reporting — Turn checked outcomes into client reporting.
• How to Test Ad Variations With AI on a Small Budget — Design a creative test within the plan.
• How Meta and Google Use AI to Run Your Ads: A Plain-English Guide — Understand the platforms' own automated delivery.
• How Much Should You Spend on AI-Run Ads Before Judging Results? — Choose a sensible test window and spend.
• Timesheet Software for Agencies: Budgets, Billable Hours and AI — Separate agency delivery cost from media spend.
• PR Coverage Report: Build One for Each Client With AI — A coverage report structure, the clippings log columns, AI prompts for the summary, and a sample monthly report with the checks a person must do.
• Ads in AI Overviews: A Pre-Spend Checklist for Ad Agencies and Clients — How Google ads in AI Overviews are bought and reported, plus a client pre-spend checklist, eligibility checks and a sensible test budget.
• Using AI in Advertising: What a Small Agency Can Hand to a Tool — A task-by-task map of what a small ad agency can hand to AI, where each approval gate sits, and the jobs that stay human.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Google Ads Help, About average daily budgets, About overdelivery and your average daily budget, and About campaign total budgets, checked 4 November 2026. Agency calculations and campaign cases are illustrative.