A weekly data review that takes twenty minutes

Managers do not have a data problem, they have a time problem. The dashboard is open for four minutes between calls, and whichever number is largest wins the attention. That is how a rounding artefact ends up in a label email.

The fix is a fixed order and a hard time limit. Same sequence every week, in the same place, so you are comparing like with like and the biggest number does not get to set the agenda. It works best when everything the project runs is already in one view, which is what a Backline project is: streaming, audience, social, advertising, website, search, press, newsletter and live dates on one timeline, so twenty minutes goes on reading rather than on collecting.

Minutes 1 to 4: what changed

Set the window to seven days, and look only at movement, never at totals. Streams gained, follower change, listener change, tickets sold this week, links clicked.

You are looking for anything outside the normal range for this project. Not outside a benchmark for other artists, outside its own recent range. A project that gains 12,000 streams a week is not having a good week at 13,000.

If nothing is outside range, write "quiet week" and move on. Most weeks are quiet weeks, and recording that honestly is what makes an unusual week visible later.

Minutes 5 to 8: what needs attention

This is the step people skip, and it is faster than it sounds because most of it is done for you.

Backline monitors the health of every connection on a project and surfaces anything that needs you: an account whose access has lapsed, a source that has gone quiet. You are not auditing plumbing, you are checking whether there is a flag and clearing it. Anomaly and milestone alerts sit in the same place, so a surge or a threshold crossed since last Monday is waiting for you rather than hiding in a chart.

That leaves you one genuinely editorial question for these four minutes: did everything you expected to appear actually appear? A show you added, a campaign you launched, a release that went live, a press piece you were promised. Those are things only you know to look for, and they are what the four minutes are really for.

Minutes 9 to 13: what is stalling

The most valuable four minutes, and the least dramatic.

Ticket pacing per upcoming show: has anything stopped moving? A show four weeks out that has not sold in eight days needs a response now, not in the last fortnight when the only options left are discounting and worry.

Then the same question on the online side. A campaign that was working and has stopped. A market that was climbing and has plateaued. Search demand that has drifted down since the release.

Stalls do not announce themselves. They look like nothing happening, which is why a routine finds them and a dashboard glance does not.

Minutes 14 to 18: what needs a decision

Only now do you look at anything that requires judgement, and only for the things surfaced by the previous three steps.

For each one, the question is what changes as a result. There are three legitimate answers: do a specific thing this week, put it in the diary for a date, or nothing. "Keep an eye on it" is not an answer, it is a way of avoiding a decision, and it guarantees the same item appears next week.

If you want a second opinion at this point, ask for one. Ask Backline AI answers from the project's own connected data, so "which of my upcoming shows is pacing behind the others" is a question with an answer rather than a research task, and it will tell you when the data cannot support a conclusion instead of inventing one.

Minutes 19 and 20: write two sentences

Per project, every week. First sentence: what happened. Second sentence: what you decided.

Streams flat, tickets in Manchester stalled at 61 percent with five weeks to go, Berlin listeners up a third after the radio play. Added a Manchester local push for Thursday, asked the agent about a Berlin date in the autumn.

That takes ninety seconds and it compounds. Six months of those sentences answers questions no dashboard can: when did this market start moving, what did we try in March, how long did the last placement take to decay. It is also the raw material for a label update, and it means the monthly report is a summary rather than an archaeology project. Kept in the project's context notes in Backline, those sentences also feed the assistant, so the answers you get back know what you tried in March.

What to ignore until month end

Cumulative totals are the main one. They are the same number every week by definition, so looking at them weekly trains you to feel progress where there is none.

Anything with less than a fortnight of history is the second. New sources, new shows, new campaigns: there is no baseline yet, and a percentage against a two day baseline is noise wearing a suit.

And any single metric that moved alone. A real change leaves marks in several places. One number moving on its own is more often mechanical than meaningful, which is the argument in when a spike is not a hit.

Running several projects

Twenty minutes each is comfortable at three or four projects on a Monday morning. Past that, the routine has to be fed rather than performed.

Stagger them. Two projects Monday, two Tuesday, the rest Wednesday. The review works on a weekly cadence, not a weekly deadline.

Then let Backline do steps one and two for the whole roster. Alerts tell you which projects moved outside their own range and which need a connection cleared, and a scheduled report on the cadence you choose, with your own prompt and your own recipients, lands the summary in your inbox before you open anything. Eight projects becomes "read five short emails, then properly review the two that need me". That is what automation is genuinely good for here: not the analysis, the triage.