“The campaign sold more tickets” leaves too much unanswered. How many more? Compared with which shows, over what dates, and what else changed? A case study should answer those questions before asking readers to judge the work. For a venue, promoter, independent label, studio or festival team, that means linking a specific decision to a measurable change while being frank about what the evidence cannot prove.
The most useful stories are often modest. A clearer presale email might cut routine questions without changing attendance. A revised show listing might help visitors find accessibility information without producing a visible sales spike. Both matter, provided the case study explains whose problem was solved, how the team measured the change and what happened next.
Start with a decision, not a compliment
Choose a project that shows how a decision was made. Praise from an artist or client can give the story a human voice, but it cannot establish a business result. Look for a defined starting problem, a meaningful change and records that allow a fair before-and-after comparison.
Say a small venue revises its ticketing information after staff notice repeated questions about door times. The story is not simply that the new page looked better. Did guests find the information? Did related messages to staff change, and did that change coincide with the revision? If the venue also changed its box-office hours, include that too.
Before interviewing anyone, write a one-sentence premise: “The team changed X to address Y, then tracked Z.” If X amounts to “improved its digital presence,” name the actions that can be checked. If Z is only “positive feedback,” find a more concrete outcome or present the piece as a process story rather than a results case study.
Get permission before gathering the story
Music projects rarely fit a neat client-and-agency account. An artist may approve a quote but not the release of ticket revenue. A promoter may hold attendance figures but need the venue’s permission to publish them. An email platform may show campaign performance alongside subscriber information that must stay private.
Agree early on who can authorize the account, which figures can be shared, whether images and quotes may be used, and who will check factual claims. Ask if numbers need to appear as percentages or ranges. Set a review deadline that allows the partner to correct errors without turning the case study into an advertisement.
Consent extends to context. A photograph of a packed room does not show that a campaign sold out a show; it might be from another performance. Use visuals from the documented project only when their origin and usage rights are clear.
Build a baseline that can bear comparison
A result needs a starting point. That might be previous comparable shows, an earlier newsletter series, a defined period before a website change or a target agreed before the work began. “Last month” may be convenient, but it can mislead if the event calendar, artist draw or season was markedly different.
Record the baseline alongside the project’s scope:
- Period: the dates covered and when the change went live.
- Population: which events, customers, subscribers or enquiries were counted.
- Definition: what counts as a sale, attendance, booking or qualified enquiry.
- Comparison: why the earlier period or group is reasonably similar.
- Other changes: pricing, lineup, capacity, advertising spend or distribution that could affect the outcome.
Ticket sales and attendance are not interchangeable. A sold ticket may go unused; a guest-list entry may count toward attendance without bringing in ticket revenue. If the project aimed to improve advance sales, report advance sales rather than the total number of people in the room. If capacity changed, raw ticket counts may conceal a shift in sell-through rate.

Choose a metric that matches the problem
Reach, impressions and page views describe exposure, but on their own they say little about business value. For a campaign intended to fill a weekday room, paid tickets, ticket revenue, sell-through or the cost of acquiring a buyer may be more telling. For a studio seeking better enquiries, the number of contact forms matters less than how many matched its services and became bookings.
Some outcomes need both numbers and accounts from people affected. To assess a revised accessibility section, a team might look at clarification emails, guest feedback and checks that the published details remained accurate. One falling message count does not prove the site became more accessible: people might simply have stopped asking. Say what was checked and what remains unknown.
Show the work between the problem and the number
“We optimized the campaign” hides the part another team could learn from. Describe the decisions without exposing confidential details: which audience received which message, how event information was reorganized, when a presale opened or what the team stopped doing.
A clear account covers four points:
- Situation: the organization, its constraints and the specific problem.
- Action: what changed, when and who did the work.
- Evidence: results reported with defined measures and a fair comparison.
- Limits: plausible alternative explanations and gaps in the data.
Keep the organizational background brief but relevant. A touring artist’s first show in a city differs from a venue’s recurring club night. Audience, lead time and ticket inventory all affect what a result means; a long biography rarely explains a change in bookings.
Make the sequence visible
Put the change and the measurement period on a simple timeline. If an email redesign launched halfway through a ticket campaign, do not credit the redesigned emails with the full campaign’s sales. State how many tickets had sold before the change. Apply the same caution if an artist announced a support act, earned press coverage or added a second date during the measurement window.
Timing also helps teams working with limited resources. Did staff rewrite the information before tickets went on sale, or after repeated enquiries? Did they test the campaign on one show before using it more widely? Those details affect whether another team can put the lesson to use.
Calculate results without overstating them
Give percentages a denominator and a clear unit. A move from 20 to 30 qualified enquiries is 10 additional enquiries, a 50% increase over the starting figure. Neither number says whether those enquiries led to paid work. When the baseline is small, the absolute change matters especially.
Take the same care with revenue. Gross ticket revenue is not profit: fees, refunds, artist guarantees, staffing and promotional costs can all change the financial picture. If costs cannot be disclosed, label sales or gross revenue accurately rather than implying a return on investment. If a team does report return on investment, specify which costs and returns it counted.
Attribution is harder than arithmetic. An uptick after a new event page goes live does not prove the page caused it. A case with imperfect evidence can still be useful if its wording fits the records: “After the page changed, support enquiries about door times fell during the measured period” may be justified. “The page eliminated confusion” calls for much stronger evidence.
Be specific about limitations. Say if the comparison covers two similar-capacity events or if paid social spending rose at the same time. Tracking links can show visits or purchases associated with those links, but not every influence on a buyer’s decision.
Use voices and visuals as evidence, not decoration
A quote belongs when it explains a decision or captures a change the numbers miss. “The new briefing gave door staff one agreed answer about entry times” tells readers more than “We loved working together.” Attribute claims to people in a position to make them, and confirm their wording and role before publication.
Charts make comparisons easier to check when labels include dates, units and group sizes. Screenshots can show a revised booking form or event-information layout; remove personal data, and do not present expired instructions as current. A caption should distinguish an example of the work from evidence of its outcome.

Handle confidential and uneven evidence honestly
A partner may agree to share an outcome but not exact financial figures. A verified range or percentage can work if the comparison is clear. “Revenue rose by between 10% and 15% across the stated shows” says more than “revenue grew significantly.” Do not calculate a precise percentage from rounded numbers.
Sometimes the records support only a narrow claim. A venue may know that fewer guests emailed about entry requirements but lack reliable attendance data for the earlier period. Report the change in emails and explain how they were categorized. If record-keeping was inconsistent, say so; a graph cannot fix a shifting definition.
Unsuccessful work can be worth publishing, especially for independent teams deciding how to spend scarce time. A newsletter may get more opens without bringing in bookings. Explain what was tested, what happened and what the team changed next. That is more useful than assembling a success story from whichever metrics rose.
Edit the draft against its source material
Before publication, check every figure against the original report, spreadsheet or ticketing export—not another draft. Verify dates, event counts, currency, units and whether figures include tax or fees. Have a second person recalculate percentages. Make sure the headline claims no more than the body supports, and do not treat a quote about a better experience as proof of higher revenue.
A short evidence check catches common problems:
- Can readers identify the baseline and measurement period?
- Does each result measure the problem raised at the start?
- Are relevant changes in price, capacity, lineup or spend disclosed?
- Do causal claims have support, or should they describe an association?
- Has the organization approved the use of its data, quotes and identifiable images?
Keep an internal record of the data version and calculations behind published figures. If a ticket report is later corrected for refunds, the team can update the case study without reconstructing its original number from memory. Beneath a results chart, a small source note such as “paid tickets, excluding refunds, for the stated sales window” can spare readers a great deal of guesswork.