Reading a ticket pacing curve

Most teams look at one number for a show: how many tickets have gone. It is the least informative number available, because it cannot tell you whether 340 sold is good news or a problem without knowing the capacity, the on-sale date and the shape of what happened in between.

The curve tells you all three. In Backline every show carries its own pacing curve, its capacity and its current sell-through together, so the shape is something you read in a few seconds rather than something you rebuild in a spreadsheet the night before a promoter call.

The three phases

Phase one, the on-sale spike. The first 48 to 72 hours, driven by people who already knew and were waiting: mailing list, followers, fans of the support act, the local promoter's list. This is the clearest read available on your committed audience in that market, because nobody in this phase needed persuading.

A weak on-sale means one of two things, and it matters which. Either the audience there is smaller than you thought, or they did not know. Check whether the announcement actually reached them: email sent, socials posted, local press placed, link working.

Phase two, the flat middle. Weeks of near-nothing. This is normal, it is what live ticket buying looks like, and it causes more unnecessary panic than anything else in the business. People do not decide about a Tuesday in November while it is still September.

Phase three, the late run. The final two weeks, often the final five days, and frequently a third or more of total sales. A show sitting at 55 percent with ten days to go is usually going to be fine.

Where the useful signal is

Since the middle is flat by nature, "sales are slow" is not information. Two things are.

A stall. No movement at all for several consecutive days at a point in the curve where there should still be a trickle. That is different from slow: slow is a shallow slope, a stall is a flat line. A stall four or more weeks out is the moment to act, because there is still time for local press, a support announcement, a targeted push or a radio drop to work.

A shape that does not match the market. If you are playing three cities and two have the same profile while the third is flat from the start, that third city is telling you something specific about your reach there rather than about ticket buying in general.

Sell-through is the comparable unit

Tickets sold is not comparable across shows. Sell-through, tickets divided by capacity, is.

• 340 in a 400 capacity room is 85 percent, an excellent story, and a candidate for a bigger room next time.
• 340 in a 2,000 capacity room is 17 percent, and needs a decision about production, papering or scaling the room.

This is why capacity belongs on every show record rather than in somebody's head. Backline holds capacity per show, calculates sell-through against it, and rolls up the dates that share a tour name into a combined sell-through for the whole run, so a routing conversation starts from one comparable figure instead of a list of raw totals.

Pollstar's 2025 year-end analysis put the top 100 tours at 8.9 billion dollars from 67 million tickets, with a per-show average of about 2.5 million dollars and 19,000 tickets. Those are stadium economics rather than yours, and the useful part for a smaller run is the same discipline: measure against capacity, not against last time.

Getting the data into one place

Three routes, in descending order of convenience.

An automatic box-office feed. Where a ticketing partner is connected, Backline brings in daily sold and gross figures for every event on its own, with capacity and venue detail attached. This is the version that actually gets used, because it never depends on somebody remembering.

A box-office export. A weekly or daily file of cumulative totals per date, uploaded against the show it belongs to and charted immediately.

Manual entry. One number typed into the show each week. That is enough for stall detection, which is most of the value in the whole exercise.

Whichever route you use, the figures stay aggregate. A pacing curve needs a date, a running total and optionally gross revenue. It never needs a buyer's name, email address or postcode, and any tool asking for those is creating a data protection liability in exchange for nothing analytical. Backline takes ticket data as aggregate measurement only, and that is the promise: you get the pacing curve without becoming the custodian of somebody else's fan records.

With every curve in one place, a whole run becomes a single question rather than six browser tabs, and Ask Backline AI answers it from the project's own show and ticket data.

A weekly routine

Per show, once a week, four questions:

1. Has it moved in the last seven days? If not, and the show is more than two weeks out, that is this week's job.
2. What is the sell-through, and how does it compare to the same point in the curve for a comparable show?
3. Is the pattern consistent with the other dates on the run, or is this one different?
4. If it needs help, is there time for the thing you are proposing to work? Local press needs a fortnight. A social push works in days. Discounting is the last option and it teaches your audience to wait.

Across a run that takes about five minutes in Backline, because every show carries its own curve and its current sell-through on the same screen. It is the difference between finding a problem while it is still solvable and finding it in the final week.