Agency Reporting Checklist: What a Creator Needs to Understand

A useful agency report lets a creator trace each number to a definition, source, period and owner. It separates observed account data from interpretation, shows changes in definitions or context, reconciles important totals, records exceptions and ends with a named next action. If a creator cannot explain what a metric counts or reproduce the calculation from available records, the report is not yet decision-ready.

Require a Metric dictionary before a dashboard

A metric dictionary is the source of meaning. For every reported value, state what is counted, what is excluded, the period, source, extraction method, owner and limitation. A familiar label such as revenue, subscriber, retention or conversion can still hide different definitions. Copy the source label where possible and explain any transformation.

Calculated metrics need numerator and denominator definitions. Preserve raw counts beside a rate. State how pending, unavailable, reversed or adjusted items are treated. Never remove inconvenient rows to improve a result. If the account surface does not expose a reliable field, mark it unavailable instead of reconstructing it from conversation or assumption.

Give each metric a decision job. A creator may need to know whether the planned content was delivered, whether an offer changed, whether a messaging queue is covered or whether an invoice reconciles. A large collection of numbers without a question can create activity while leaving the creator unable to act.

Version the dictionary. When a source, calculation or label changes, record the effective period and avoid presenting the new series as directly comparable with the old one unless the data is restated on the same basis.

Use Weekly questions for operating visibility

A weekly report should show the state of current work: what was planned, completed, delayed, blocked and changed. Compare the report with the approved calendar, queue or service scope. A missed item needs an owner and next action; it should not disappear inside a narrative about a stronger metric elsewhere.

• What changed in creator-controlled operations this week, and which source supports it?
• Which planned content, messaging, promotion or reporting outputs were completed, delayed or blocked?
• Which account observations are comparable with the prior period, and which changed definition or context?
• What creator approval, asset or decision is currently blocking the team?
• What is the single next action, owner and review date?

Separate facts, interpretations and decisions. “Twelve planned posts were published and two were blocked awaiting creator approval” is an observation tied to a calendar. “The audience preferred format A” is an interpretation requiring evidence and context. “Test format A again next week with the same offer” is a decision. Put each in its own field.

The weekly view should make creator dependencies visible without turning them into blame. If approvals or assets are late, show the requested item, requested time, current owner and effect. That gives the creator a solvable handoff.

Use Monthly questions for reconciliation and change control

A monthly report closes a period. Reconcile important monetary or volume totals to the current source records and explain adjustments. If the agency invoice uses a revenue base, the reported base, period and source should match the fee calculation or show a clear reconciliation. Do not force a match by relabelling a metric.

• Do period totals reconcile to the underlying statements or exports?
• Did any metric definition, source, fee base, offer, account state or reporting process change?
• Which weekly exceptions remained open, repeated or changed owner?
• Which strategy decision was made, what evidence informed it and when will it be reviewed?
• What must be corrected in the report before the month is treated as closed?

Summarise context changes: posting plan, price or offer, traffic source, content supply, team coverage, account issue or data availability. When several variables changed, avoid attributing movement to one intervention. Use the month to establish a new baseline if comparison is no longer credible.

Close the month with corrections and open items. A corrected report should retain the original version, reason, approval owner and effect on previous decisions. Silent replacement makes future reconciliation harder.

Keep an Exception log beside the report

The Exception log captures anything that makes a number incomplete, late, non-comparable or disputed. Give each exception an ID, affected metric, period, observed problem, evidence, owner, due date and resolution state. Examples include missing export rows, changed offer labels, delayed adjustment, duplicated event, unavailable source or definition change.

Do not delete the reported value automatically. Mark it Provisional, Excluded from comparison, Corrected or Unavailable. The creator should see the limitation at the point where the number appears, not only in a hidden operations sheet.

Review repeated exceptions as process defects. If source access regularly fails, fix the access ownership. If labels change without versioning, fix the dictionary process. If approvals arrive after the reporting cutoff, align the operating calendar. Avoid treating every exception as an analyst mistake when the system produces it.

Trace a reported number back to evidence

Select one material number and reproduce it. Open the named source or approved snapshot, confirm the period and filters, copy raw rows or counts into a working sheet, apply the dictionary formula and compare the result with the report. Record the difference. This is a reconciliation check, not an accusation.

If the result differs, check snapshot timing, adjustments, currency, filters, duplicates, missing rows and definition versions. Ask the metric owner to explain the exact difference. Preserve both values until the issue is resolved. Do not pick the result that better supports a preferred story.

Rotate checks across financial, content, messaging, promotion and service-delivery metrics. The creator does not need to rebuild every report line each week, but the system should be capable of being traced. A provider that supplies a beautiful chart but no source, period or owner has supplied presentation rather than accountable reporting.

Agree on the reconciliation method during agency onboarding, not after the first disputed result. Include source access, snapshot timing, dictionary location and correction channel.

Turn each report into one Decision record

End the report with a decision statement: issue observed, evidence used, assumptions, chosen action, owner, start date and review point. “Improve content” is not a decision. “Move the delayed series to next week, assign the missing edit to the named owner and review planned-versus-published completion at Friday's snapshot” is operational.

Keep the decision proportional to the evidence. A single period can justify fixing a clear process failure. It rarely establishes why subscribers or revenue changed. When the evidence is uncertain, choose a reversible test or request more data rather than manufacturing confidence.

Carry open decisions into the next report and close them explicitly. Record whether the action was completed and what was observed, then decide to continue, change, stop or collect another comparable period. Do not retroactively rewrite the original expectation.

Ask these reporting questions during discovery as well. The creator discovery call guide helps test whether a provider can explain definitions, source access and owner accountability before work begins.

Worked example: a changed publishing total

A fictional weekly report states that eighteen items were published. The dictionary defines an item as one approved feed or message asset published during the stated account-time-zone week. The creator's calendar shows sixteen completed items, one rescheduled item and one story asset that the dictionary excludes.

Reconciliation finds that the report used an earlier dictionary version that included story assets and counted the rescheduled item by its planned date. The analyst opens an exception, marks the total provisional and issues a corrected value of sixteen with the method change. The report does not claim that sixteen is good or bad; it compares delivery with the approved plan and assigns the two delayed items.

The next report uses the current dictionary and retains the correction note. This example demonstrates traceability and change control. It does not invent an engagement, sales or creator performance outcome.

Audit the reporting process, not only the finished report

Once per review cycle, choose one financial line, one publishing line and one service-delivery line and trace each from the report back to its source. Record whether the source is available to the creator, which snapshot was used, which dictionary version applied and who can correct an error. Rotate the sample so the same convenient metrics are not checked every time.

Review timeliness separately from accuracy. A correct report delivered after the decisions it was meant to support has a process problem; a fast report with unresolved source differences has an evidence problem. Name the expected delivery point, correction window and escalation owner. When a deadline changes, keep the original expectation and record the reason rather than silently moving the date.

Check whether open exceptions survive into the next period. Every unresolved item should retain its ID, owner, status and next action. If an issue disappears from the dashboard without a resolution note, the reporting process has lost state. Repeated exceptions may justify a workflow change, but they do not by themselves explain changes in subscribers, revenue or content performance.

End the audit with a process result such as Traceable, Traceable with corrections, Source access missing or Definition unresolved. That result describes the reliability of the reporting workflow. It is not a score for the creator or agency and should not be converted into a performance claim.