What Managers Should Track During a Campaign

Track decisions, dependencies, and evidence

Source scope: Events in Google Analytics; Marketing and sales. Platform-, provider-, and territory-specific statements below are scoped to these 2026-07-11 checks and the complete bibliography; the assigned reviewer must recheck them before publication.

A manager's campaign tracker should explain the current state and next decision, not become a second analytics warehouse. Start with the objective, artist entity, campaign scope, dates and time zones, owner/approver matrix, budget boundary, critical dependencies, and definition of done.

Create workstreams for assets/rights, distribution, profile/EPK, content, press, live, fan activity, commerce, finance, and follow-up. Every item needs an owner, state, dependency, evidence/source, next action, and review date. Use a single source for facts instead of copying them between decks.

Maintain three views

Decision log: what was decided, by whom, when, with which evidence and implications.

Operating board: blocked, ready, awaiting approval, scheduled, verified, or closed work. “Done” should mean the public or provider state was checked where relevant.

Outcome note: selected metrics, data definitions, limitations, observed results, and the next decision. Keep system definitions separate and avoid causal claims from correlation.

At each meeting, review blocks first, then approvals, upcoming public/spend actions, incident coverage, and decisions. Do not spend the meeting narrating every completed task. Record changes to release date, budget, artist facts, rights, ticket terms, or provider rules and trace affected work.

Protect scope and data

Keep artist records entity-scoped and access role-based. Store credentials in approved systems, not the tracker. Limit fan-level data, financial details, contracts, and unreleased assets. Define retention and archive rules.

Pricing, commissions, fees, BANDS, rewards, and provider timing should be referenced by current catalog/claim/source keys, not copied literals. Legal, tax, rights, accounting, and contract questions are escalation items.

Close the campaign by reconciling provider and budget records, outstanding rewards/support, asset and link state, partner promises, and review ownership. Archive a concise retrospective that the next plan can use.

How Bandruption can help

Bandruption can supply current entity-scoped state for supported profile, event, commerce, fan, and agent workflows. The manager's tracker remains the cross-workstream decision record. Review Music Pro operations after agreeing on states, owners, and data boundaries.