Backline

Reporting to a label without losing the argument

The manager who brings context wins the conversation, and the one who brings a screenshot loses it. How to structure a monthly update that holds up when somebody disagrees with it.

Danny Angove

Co-founder, Backline · 5 July 2026 · 3 min read

In short

  • You will be reporting into a room that has other numbers. Agree the definitions before there is a disagreement, not during one.
  • Lead with the argument, not the data. One paragraph saying what happened and what you want, then the evidence.
  • Volunteer the bad number. The credibility from raising it yourself is worth more than the awkwardness it avoids.
  • State what you cannot see. An update that quietly omits a disconnected source implies things about the project that are not true.
  • Keep an archive of your own monthly updates. Six months of them is the most persuasive document in any negotiation.

A monthly update to a label is not a data exercise, it is a negotiation with numbers in it. The manager who arrives with context and a recommendation gets a decision. The one who arrives with a screenshot gets questions.

Agree the definitions first

The most common way one of these goes wrong has nothing to do with the campaign. You say streams were up 9 percent, somebody else has a number showing 4 percent, and the next twenty minutes are about arithmetic rather than the project.

Both numbers are usually right. One is a trailing 28 days and the other a calendar month. One includes a platform the other excludes. One is corrected for reporting lag and the other is not.

Fix it once, in writing, before it matters. Which window, which platforms, which source, corrected or not. It is a two paragraph document, and it converts a recurring argument into a footnote.

Five definitions to agree before you need them

Illustrative
The questionWhy it causes an argument
WindowTrailing 28 days or calendar monthThe two differ by enough to reverse a direction
PlatformsWhich services are in the streams figureOne party including video changes the total materially
SourcePlatform dashboards or a third-party feedThird-party feeds lag and round
Lag correctionCorrected for reporting lag or notA couple of days shifts a release week
Audience metricMonthly listeners, followers, or bothThey move in opposite directions after a placement
Agreeing these in writing takes ten minutes once. Not agreeing them costs twenty minutes of every subsequent meeting.

Structure that survives disagreement

One paragraph up front: what happened and what you want. Not a summary of metrics. An argument. "The project grew through the month and the growth is concentrated in one market we have not been supporting. I want to move the remaining Q3 budget there."

Then the evidence, in the same order as the argument. Every number in the paragraph, in the order it was claimed.

Then the thing that did not work. Volunteered. This is the part that decides whether you get believed for the rest of the year.

Then what you cannot see. Which sources are not connected, and what that means for the report.

Then the ask, restated with a date. People forget the ask, so it appears twice.

Volunteer the bad number

If a campaign underperformed, say so first and with a figure attached. Two things follow.

You keep control of the interpretation. A number you raise comes with your explanation. The same number found by somebody else comes with theirs.

And you buy credibility for the good numbers. Anyone who has sat through enough of these updates knows which managers only bring good news, and discounts everything they say accordingly.

State what you cannot see

If a project has no advertising connection, the report says nothing in this report reflects paid activity because no ad account is connected. Silence on paid implies there was none.

This is the same discipline as an honest empty state in a dashboard, and it matters more here because the recipient is one step further from the data and cannot check.

Drafting the update from the data

Illustrative
You asked

Draft this month's label update for Aster Bloom. Lead with the argument, include the underperforming campaign, and say what you cannot see.

Data readget_streaming_statsget_audience_geographyget_ads_performanceget_smart_link_statsget_live_showsget_news

Backline AI

The project grew steadily and the growth is concentrated in a market we are not supporting. Recommendation: move the remaining quarter budget to the Netherlands and Ireland, decision needed by the 12th.

Evidence: 214,000 streams for the month, up 9 percent on a calendar month basis across Spotify, SoundCloud and YouTube. Monthly listeners 61,400, followers up 1,310, which is 21 new followers per thousand new listeners and the strongest that ratio has been in four months. Netherlands share of listeners moved from 11 to 19 percent, Ireland from 4 to 7 percent.

What did not work: the paid campaign in the two largest markets spent 1,850 pounds and produced 4,900 landing page arrivals at a 22 percent click-through, against a project average of 61 percent. Neither market shows listener movement outside its normal range. On the evidence, that spend did not land.

What I cannot see: no newsletter platform is connected, so nothing here reflects email performance. Two of the four upcoming shows have no ticket data connected.

Ask, restated: approval to move the remaining quarter budget to the Netherlands and Ireland, by the 12th.

Illustrative example using a fictional project. The underperforming campaign appears in the draft because the prompt asked for it, which is the point: a report generator will happily leave it out if nobody insists.

What to include, and what to leave out

Include: streams gained in the window with the window named, monthly listeners and followers with their movement, the conversion ratio between them, geography changes worth acting on, campaign spend against the outcomes you can measure, live pacing per show if there are shows, and press count.

Leave out: total streams all time, impressions, playlist reach as a headline, anything cumulative, and any metric you have not used in a previous report. A new metric appearing in a month when the usual ones look weak is transparent to everyone in the room.

Keep the archive

Every monthly update, filed, with the numbers as they were reported at the time.

Two uses. It stops the slow revision of history where everyone remembers the last campaign going better than it did. And when a contract conversation arrives, six months of consistent, honest updates including the bad months is the most persuasive document you can produce, because it demonstrates something no single report can: that your numbers are reliable when they are unflattering.

The one sentence version

Say what happened, say what you want, show the evidence in that order, raise the bad news yourself, and be explicit about what you could not see. The credibility compounds, and credibility is what actually moves a budget.

Common questions

What should a monthly report to a label contain?
One paragraph stating what happened and what you want, then the evidence in the same order, then whatever underperformed, then what you could not see because a source is not connected, then the ask restated with a date. Leave out cumulative totals, impressions and any metric you have not used in previous reports.
Why do a manager's numbers and a label's numbers disagree?
Usually because of definitions rather than errors: a trailing 28 day window against a calendar month, different platforms included, a third-party feed against a platform dashboard, or one figure corrected for reporting lag and the other not. Agreeing the definitions in writing once removes the argument permanently.
Should you include bad results in a label update?
Yes, and raise them first with a figure attached. A number you volunteer comes with your interpretation, while the same number found by somebody else comes with theirs, and consistently reporting the unflattering months is what makes the good ones believed.

Sources

  1. 1IFPI, 2026. Global Music Report 2026
  2. 2Spotify, 2026. Loud and Clear: takeaways

Danny Angove

Co-founder, Backline

Danny Angove is a co-founder of Backline. He works on the music business side of the platform: what managers, labels and independent artists actually need to see, and which numbers are worth arguing about.

Backline does this for the projects you run

Streaming, audience, social, advertising, website, search, ticketing and press data in one dashboard per project, with an AI assistant that answers questions about your own connected data. Invite-only.

What Backline does

Analytics foundations

The twelve numbers worth knowing about every project

A short list of music industry KPIs that survive contact with a real week, why each one earns its place, and the popular metrics that belong in a footnote instead.

Danny Angove · 3 min read

AI and automation

Scheduled reports without a data team

A recurring report written from a project's own connected data, sent to whoever needs it. What makes one worth reading, and the scheduling details that decide whether it arrives on time.

Danny Starr · 3 min read

Live and ticketing

Report on the tour, not on the show

Twelve separate show reports hide the pattern that matters. What tour-level roll-up shows that per-date reporting cannot, and the one field you have to fill in for it to work.

Danny Angove · 3 min read

Ask Backline AI
Ask Backline AI
Backline

Ask anything about your project: suggestions, strategy, next steps.

Select a project to start chatting

Enter to send · Shift+Enter for new line

Backline

Booting up your Backline session…