An influencer campaign pacing dashboard should flag overdue publications, blocked approvals, budget commitments and missing evidence. Compare each with the schedule agreed before launch. Keep outcome reporting separate: an unfinished analytics report cannot tell you whether a creator has missed a deadline, and a late post cannot tell you how many sales the campaign will eventually produce.
Build the first version around five signals and a list of named actions. The thresholds below are hypothetical operating choices, not platform rules or industry benchmarks.
Start with the dates and records you control
Use one row per agreed publication, with a stable ID. Store its creator, format, approval deadline, publication deadline, actual publication time, verified URL and owner. Keep draft delivery and final approval as separate milestones. A submitted draft does not satisfy a publication deadline.
Save the original schedule. When someone approves a date change, record the new date, reason and approver without erasing the original. Otherwise, moving deadlines can make an unchanged backlog appear healthy. For the underlying row structure, use deliverable tracking that preserves revisions.
Keep two linked records alongside those publication rows:
- A cost ledger with approved obligations, amounts paid, unpaid balances and proposed additions. Use one reporting currency and a consistent treatment of taxes and fees.
- An evidence register with the publication ID, required report or proof, reporting window, evidence due date, last successful collection time and missing-data reason.
Choose a campaign timezone and show an explicit cutoff on every dashboard refresh. A post due tomorrow must not enter today's overdue count.
Specify five warning signals
Place these five summaries above an exception list. Every summary should open the rows behind its number. Use written states such as "Review" and "Blocked" alongside any color.
| Signal | Calculation or test | Hypothetical trigger | First action |
|---|---|---|---|
| Publication pace | Verified publications from the due cohort / publications due by cutoff | Review below 90%; urgent below 80% | Inspect the missing publication IDs |
| Approval risk | Unapproved items scheduled to publish within the next 48 hours | Review any item waiting over 24 hours after submission | Name the reviewer and unblock the decision |
| Budget exposure | Paid amounts + unpaid approved obligations + proposed additions | Block new approval if exposure exceeds budget | Remove, reduce or fund the proposed addition |
| Evidence completeness | Complete evidence packages / packages due by cutoff | Review below 95%; urgent below 80% | Chase the missing package or repair collection |
| Data freshness | Time since the last successful collection, compared with that source's agreed cadence | Review when a scheduled collection is missed | Check the source and collection job |
When nothing is due, show "Not due" rather than 0% or 100%. An empty denominator says nothing about execution quality.
For publication pace, count only the publications whose deadlines have arrived. Publishing two future items early must not cancel out two overdue items. Show the overdue count and oldest overdue age beside the percentage. One launch-critical post may need immediate attention even when the overall percentage looks acceptable.
For evidence completeness, define a complete package before launch. It might require a verified publication URL and an agreed creator report covering a specified window. If either part is missing, the package remains incomplete. Report the missing parts separately so a manager can distinguish a missing URL from a report that has not arrived.
These are operational definitions for this dashboard. They do not define platform reach, views or engagement. If you add those metrics later, preserve each platform's definition and access requirements in the data dictionary.
Work through a hypothetical review
Suppose a campaign has 20 agreed publications and a $20,000 budget. At the chosen cutoff, eight publications are due. Six of those eight have verified live URLs; the other two are overdue. Three further publications are due within 48 hours. Two of those three have waited more than 24 hours for approval.
Five evidence packages are due, and four are complete. The sixth live publication has a later evidence deadline, so its package is excluded from this calculation.
The cost ledger shows $8,000 paid and $6,000 of unpaid approved obligations. A manager has also requested $7,000 of additional work that nobody has approved.
| Dashboard result | Reproducible calculation | Decision |
|---|---|---|
| Publication pace: urgent | 6 / 8 × 100 = 75% | Contact the owners of the two overdue publications |
| Approval risk: review | Two qualifying items | Ask the assigned reviewers for decisions |
| Evidence completeness: review | 4 / 5 × 100 = 80% | Request the one incomplete package |
| Approved commitments | $8,000 + $6,000 = $14,000, or 70% of budget | Keep this separate from cash paid |
| Proposed exposure: blocked | $14,000 + $7,000 = $21,000, or 105% of budget | Resolve the $1,000 excess before approval |
At exactly 80%, evidence completeness is in review under the example rules; it becomes urgent below 80%. Write these boundary conditions into the dashboard specification.
Do not add paid invoices to the full value of the same obligations. Here, the $6,000 is the remaining unpaid balance, so the addition avoids double counting. Proposed exposure is a request scenario, not booked spend or a prediction of final cost. A complete campaign cost ledger helps define which costs belong in that total.
Keep reporting delays out of performance alarms
Data can be absent because it is still processing. Google's GA4 freshness documentation says processing can take 24 to 48 hours, during which reports may change. It also describes temporary gaps in event-scoped traffic-source dimensions during intraday processing. Attribution credit for key events can change for up to 12 days.
Store both the collection timestamp and the latest reporting period available. A successful refresh can return data that still excludes recent activity. Set source-specific expectations rather than applying the example 24-hour approval threshold to analytics.
Use separate missing-data reasons such as:
- Report not yet due.
- Source still processing.
- Creator report overdue.
- Access unavailable.
- Collection failed.
Never turn those states into zero sales. Follow missing-data reporting rules when an outcome panel lacks enough evidence to interpret.
If you include Shopify orders, label the report and attribution model. Shopify's marketing report documentation explains that attribution models allocate credit differently. Its Any click model can allocate more credit across channels than the number of orders received. The documented reports also include canceled, pending and unpaid orders. An attributed order count therefore needs its report definition before anyone treats it as completed purchases or cash received.
Make each warning produce an action
Modash's tracking and forecasting article proposes using ambassador counts, conversions, recruitment and departures to build forecasts. It also asks teams to record changes in markets and products. That is a separate planning task. The dashboard specified here makes no sales forecast and tests no causal claim.
For every warning, record the affected ID, evidence, owner, next action, action deadline and next review time. Route approval delays to the reviewer, overdue creator reports to the relationship owner, collection failures to the data owner and budget decisions to the budget owner.
Refresh execution records before the campaign team's agreed review time. Resolve a warning when evidence meets its rule, or record an approved exception with an expiry date. Keep a missed original deadline visible after rescheduling.
Start by entering this week's publication deadlines, outstanding approved costs and evidence due dates. Run the five rules once. Assign an owner and a deadline to each exception before adding another dashboard metric.
