Monitor marketing pace against the monthly plan
Refresh channel-level actuals and run-rate estimates, then surface material gaps in a daily team notification.
How this works
Refresh channel-level actuals and run-rate estimates, then surface material gaps in a daily team notification. Pacing alerts should tell an owner whether a plan is becoming hard to reach and which assumptions drive that conclusion. A straight-line forecast from a partial day or an unusual weekend can create false urgency and unnecessary budget changes.
Refresh channel actuals, calculate run rates with explicit calendar and maturity rules, and compare them with the monthly plan. Use AI to explain material gaps and formulate investigation questions. The alert is a decision aid, not an automatic budget instruction.
Before you start
Approved plan
Obtain channel targets and metric definitions for the month.
Reporting calendar
Define business days, time zone, and completed-day cutoff.
Alert policy
Agree materiality, owner routing, and repeat-notification behavior.
Prepare the inputs
- actuals
- Required
Daily channel data
Mark incomplete days and missing values.
- plan
- Required
Monthly targets
Include volume and unit-cost definitions.
- calendar
- Required
Working-day schedule
Account for holidays or known campaign pauses.
- forecast_method
- Required
Run-rate rule
State the lookback and any weighting.
- owners
- Required
Channel responsibility
Provide a fallback for unassigned alerts.
Implementation, step by step
Validate daily inputs
- Load only completed reporting intervals under the agreed cutoff.
- Reconcile channel totals and flag missing feeds before forecasting.
Checkpoint: A trustworthy actuals snapshot.
Calculate pace
- Compute elapsed eligible days, achieved volume, and unit costs deterministically.
- Keep missing outcomes distinct from zero and explain denominator changes.
Checkpoint: Current pace measures.
Estimate month-end outcomes
- Apply the documented run-rate method to remaining eligible days.
- Show the assumption and sensitivity to an unusual recent period.
Checkpoint: A forecast with visible limitations.
Compare with plan
- Evaluate volume and efficiency gaps against the approved materiality rule.
- Distinguish a target miss from a data-quality alert.
Checkpoint: A prioritized exception list.
Draft owner-specific alerts
- State the plan, actual, projection, relevant period, and suggested diagnostic question.
- Avoid prescribing spend changes without a reviewed budget decision.
Checkpoint: A concise notification draft.
Track follow-up
- Record the owner's action or explanation and suppress unchanged repeat noise according to policy.
- Reconcile later actuals with prior forecasts to refine the method.
Checkpoint: A pacing review history.
Decisions along the way
A channel's data is missing
Send a data-quality notice rather than a zero-performance alert.
The month includes a planned pause
Exclude those days according to the approved calendar.
A one-off event drives the run rate
Show an alternate scenario instead of presenting one precise forecast.
What you will produce
marketing-pacing.csv
CSVSupports daily investigation.
Include: channel · plan · actual · eligible_days · projection · gap · data_status
pacing-alerts.md
MarkdownGives owners concise actionable context.
Include: owner · issue · evidence · question · followup_status
Check the result
- Recalculate elapsed-day and remaining-day counts.
- Verify unit costs use the intended outcome definition.
- Check alert routing and duplicate suppression.
- Compare forecast assumptions with known campaign schedules.
When something goes wrong
Timezone shifts move spend between days
Rebuild the period consistently before alerting.
A late conversion import changes history
Refresh affected actuals and note the revision.
Alerts repeat without new information
Apply the agreed suppression rule while retaining the open issue.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Check lead pacing on day 10 of a 20-business-day month.
Inputs
Synthetic example. Synthetic plan is 200 leads; completed-day actuals are 80. One recent day is incomplete and excluded.
Expected result
Synthetic expected result. Using the agreed completed-day rate of 8, project 160 and flag a 40-lead gap. Do not include the incomplete day as zero.
Run a small pilot
Start small
A few channels over a full reporting cycle.
Record the baseline
Record manual forecast time and false or redundant alerts.
Agree success criteria
Agree forecast usefulness and data-quality tolerance with channel owners.
Stop or revise
Stop automated alerts when reporting completeness cannot be established.
Keep the scope clear
- An alert does not authorize changing budgets or targets.
- Projections are conditional estimates, not promised outcomes.
Check before using
Run rates are rough estimates. Check seasonality, conversion delays, and tracking failures before treating a change as a performance problem.
Business activities
- Run advertising and acquisition tests
- Review business performance
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Channel plans and metric definitions · Daily spend and funnel results · Alert thresholds
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow