Daily Pacing Alerts: How We Catch Budget Problems Before They Become Client Problems

The $50 Problem Nobody Catches

A $50/day overspend on Tuesday is a rounding error. By Friday, it's $250. By month end, it's $1,500 your client didn't approve. Most agencies catch this in their weekly review — five days too late. We catch it at 10 AM the next morning.

This isn't a monitoring philosophy. It's a system we built because we got tired of the conversation every agency has eventually: "How did we overspend by 20% this month?" The answer is always the same — a campaign started over-delivering on day 3, nobody noticed until the weekly check on day 8, and by then half the monthly budget was gone.

We decided that conversation should never happen again. So we built what we call the Morning Pacing Protocol — an automated system that runs at 10 AM Singapore time, every day, across every client, and tells our team exactly where the money went yesterday and where it's heading this month.

The Pacing Ratio Formula

The math behind pacing is almost embarrassingly simple. That's also why it's powerful — there's nothing to miscalculate, nothing to interpret, nothing to argue about.

Pacing Ratio = MTD Actual Spend / MTD Expected Spend

Where expected spend = (monthly budget / days in month) x days elapsed.

A client with a $10,000 monthly budget on day 15 of a 30-day month should have spent $5,000. If they've spent $6,500, their pacing ratio is 130%. Simple math. But nobody does it daily across 20 clients manually, because "simple" multiplied by 20 clients, each with 3-8 active campaigns, becomes 100+ calculations before your first coffee.

The system does all of them in under 30 seconds.

The 10 AM Morning Run

Every morning at 10 AM SGT, the system executes a sequence we call the Daily Pacing Sweep:

Step 1: Pull. BigQuery queries pull month-to-date spend for every active client across Google Ads and Meta. One query per platform, not one per client — aggregated for speed.

Step 2: Calculate. For each client, compute the pacing ratio against their approved monthly budget. Also calculate yesterday's single-day spend as a percentage of daily target — this catches sudden spikes before they compound.

Step 3: Classify. Every client gets a RAG status based on calibrated thresholds. Not arbitrary color codes — these are engineered to the intervention window.

Step 4: Post. A formatted alert drops into ClickUp Chat — four columns, every client, one glance. The account manager sees their entire portfolio in a table they can scan in 10 seconds.

RAG Thresholds: Why These Numbers

We didn't pick these thresholds from a textbook. We calibrated them over three months of daily data across our Singapore and Indonesia portfolio.

Green: 90-110%. Normal variance. Platform delivery fluctuates daily. A campaign pacing at 105% on day 10 will probably normalize by day 20. No action needed.

Amber: 80-90% or 110-120%. Worth watching. At 115% pacing by mid-month, you're on track to overspend by 15% — that's $1,500 on a $10K budget. Not a crisis yet, but it will be if you wait five more days. The AM checks which campaigns are driving it.

Red: Below 80% or above 120%. Intervene today. At 125% pacing, something structural changed — a bid strategy shifted, a budget cap was hit and redistributed, a campaign launched with the wrong daily budget. Every day of delay costs real money.

The critical insight: these thresholds are calibrated to the point where intervention still prevents material damage. Red at day 5 means you have 25 days to correct. Red at day 25 means the damage is done. The system catches it at day 5.

Campaign-Level Drill-Down

A client-level Red is the alarm. The campaign-level drill-down is the diagnosis.

When a client flags Red, the system doesn't just say "Atlas Copco is pacing at 134%." It identifies which campaigns are responsible: "Campaign 'Brand Search EN' consumed 45% of monthly budget in 15 days. Campaign 'Competitor Terms' is pacing at 180% due to a bid strategy change on March 8."

That gives the account manager an instant, specific action item. Not "go check Atlas Copco" — which leads to 20 minutes of tab-switching across Google Ads and spreadsheets — but "go adjust the daily budget on Competitor Terms, which is the source of the overspend."

This is the difference between an alert system and a diagnostic system. Alerts tell you something is wrong. Diagnostics tell you what to do about it.

Why Daily Beats Weekly — The Compound Effect

The argument for weekly reviews sounds reasonable: "We check budgets every Monday. That's frequent enough." It isn't. Here's why.

A campaign starts over-delivering on Wednesday. It's spending 140% of daily target. Your weekly review is on Monday — five days away. In those five days, the overspend compounds:

Wednesday: +$20 over. Thursday: +$40 cumulative. Friday: +$60. Saturday: +$80. Sunday: +$100. You catch it Monday at +$100. On a $5,000 monthly budget, that's 2% of the total budget gone before you even knew.

Now imagine three clients doing this simultaneously. Or a campaign that starts over-delivering by 200% on day 2 of the month. By day 8, you've burned a quarter of the monthly budget.

Daily pacing catches the Wednesday anomaly on Thursday morning. Total exposure: $20. That's the difference — not better math, just faster math.

Routing to Where the Team Already Works

We made a deliberate decision about where these alerts go. Not email — nobody reads automated emails. Not a dashboard — dashboards require someone to remember to check them. Not Slack — we don't use Slack for task management.

The alerts post directly to ClickUp Chat, the same tool where our team manages tasks, communicates about clients, and tracks deliverables. The pacing alert is a message in the channel they already have open. There's no context switch, no additional login, no "I'll check it later."

This is an underrated design choice. The best monitoring system in the world fails if it requires a behavior change. Our team was already in ClickUp. So we put the alerts in ClickUp.

What We Learned Running This for Six Months

The system has been live since late 2025, running across our APAC client portfolio. A few things we didn't expect:

Under-pacing is as dangerous as over-pacing. A client pacing at 75% by mid-month will under-deliver by 25%. That's $2,500 of unspent budget on a $10K account — and a client asking "why aren't we spending what we agreed?" Under-pacing often means a campaign got paused accidentally, a payment method expired, or a disapproved ad killed delivery. The morning alert catches all of these.

The "yesterday" column prevents false alarms. A client pacing at 112% MTD but 95% yesterday is self-correcting. A client pacing at 112% MTD and 135% yesterday is accelerating. The combination of cumulative and daily signals reduces unnecessary escalations by roughly 40%.

Weekends matter. Spend patterns differ on weekends. Some industries spike (e-commerce), some dip (B2B). The system runs seven days a week including Singapore public holidays. The Saturday morning alert has caught problems that would have compounded through a two-day weekend before Monday's review.

Daily pacing alerts aren't sophisticated. They're just honest — the simplest possible math, applied automatically, every single day, before the team has a chance to forget.