Skip to content
Live music on stage: a band under the lights
The GigXchange Index · Methodology

How the figures are built

From an observed fee to a percentile you can quote in a negotiation — the full pipeline in plain English: every source and its weight, the rules that keep junk out, what n really counts, and the honest limits of the data. Free to cite under CC BY 4.0.

Open methodology — free to cite under CC BY 4.0

Last updated: 3 September 2026

What the Index measures

UK live music only. Every figure is what the performer takes home, in pounds — tickets, door splits, gear hire and travel never enter the dataset.

§ 1

Coverage and definitions

A published cell is the meeting point of three axes: where (a canonical city, one of twelve UK regions, or the national baseline), what kind of gig (seven types, weddings to theatre/pit), and how many musicians (solo, duo, 3–4 piece, 5+). Each cell carries four percentiles — p25/p50/p75/p90 — never an average.

§ 2

How to read a rate cell

Averages lie in a market where a Mayfair gala and a Tuesday pub slot share a spreadsheet. So every figure here is four: p25 the budget end, p50 the typical fee (half pay less, half more), p75 a strong booking, p90 the premium tier. Find your quote on that curve and you know where you stand.

Where the data comes from

Money that provably changed hands says more than a listings-page price — so every source class is capped at a maximum share of any published figure.

§ 3

The source classes and their quotas

Every observation lands tagged with source, gig type, band size, venue type and location, through a single ingest funnel with documented provenance. Each source class then owns at most a fixed share of any published cell — the caps below sum to 1.00. A class that grows by collection cadence rather than by market activity therefore cannot buy influence with volume: scanning more rate cards sharpens the rate-card estimate within its ceiling. A class reaches its cap only as it accumulates evidence (credibility n ÷ (n + 50)), so a handful of rows cannot spend a large quota on noise.

Honest limit: a quota binds only while another class has evidence to absorb the remainder. Where a cell is served by one source, that source carries the figure whatever its cap. Classes with no observations yet — currently confirmed bookings and venue gig budgets — hold quota that cannot be claimed.

SourceMax shareWhy it counts this much
Anonymous public submission0.20A gig someone actually played, self-reported
Verified rate import0.18Externally sourced rate schedule, checked on import
Confirmed GigXchange booking0.15A cleared transaction — the strongest signal per row
Artist profile asking rate0.13Stated rates from real acts on the platform
MU / Equity recommended rate0.10The union floor — authoritative, not market-clearing
Industry published rate card0.10Asking price, commission stripped at ingest
Venue gig budget0.09The buyer’s pre-negotiation spend plan
Web-extracted rate0.05Public-page extractions, human-reviewed
Ticket-derived club estimate0.00Room-economics model — shadow mode, excluded from published cells
What each source may decide Bar = maximum share of any published figure. Number = observations behind it.
  • Public submission 0.20 36
  • Verified submission 0.18 39
  • Confirmed booking 0.15 none yet
  • Artist profile rate 0.13 536
  • MU / Equity minimum 0.10 143
  • Industry rate card 0.10 3,496
  • Venue gig budget 0.09 none yet
  • Web-extracted rate 0.05 173
  • Ticket-derived (shadow) 0.00 none yet

Caps sum to 1.00. Confirmed bookings and venue budgets hold quota no one can claim yet — that unclaimed share passes to whoever does have evidence.

Why the biggest source is not the loudest Industry rate cards, against the 4,423 observations in the August 2026 source mix
Share of all observations 79%
Most it may decide 10%

Re-scanning rate cards every Monday sharpens the rate-card estimate. It cannot enlarge the rate-card vote. The source mix is counted at the issue’s window close; the issue’s headline pool of 4,431 adds the observations approved between that close and the refresh it was built from.

§ 4

What is flowing now — and what is wired, awaiting volume

Flowing routinely: weekly re-scans of published UK industry rate cards (Mondays), the monthly artist-profile panel of stated rates (snapshots on the 28th), and fees reported by gig-workers through the public submission form (reviewed, then synced daily). Musicians’ Union and Equity published minimums refresh annually.

Wired in, awaiting volume: confirmed GigXchange bookings — the 1.00-weight reference signal — are plumbed in but have yet to arrive in volume, so the Index still leans on asking prices and listings more than settled fees. Venue gig budgets, web-extracted editorial rates and ticket-derived club estimates have each contributed rows but are not yet routine inflows. This split is reported honestly in every issue — it is the single biggest thing that will sharpen the Index.

Counting rules

Two rules decide what a number means before it ever reaches a percentile: everything is normalised to artist take-home, and nothing is allowed to count twice.

§ 5

Fee basis and the commission haircut

Every observation carries a fee_basis field. Gross-of-commission sources — industry rate cards and agent-rostered artist profiles — are converted to artist take-home before percentile computation using a 20% default agency commission haircut (net = gross ÷ 1.20); agent-brokered bookings use the booking’s recorded commission. Already-net sources (MU/Equity rates, venue budgets, verified submissions) pass through unchanged. Every published figure is therefore artist take-home — client-facing gross prices typically run ~20% higher.

§ 6

Re-sighting, deduplication — and what n really counts

A listing that survives week after week is information — the price is stable — but it must never count twice. When a weekly scan meets a listing it already knows, it bumps that observation’s sighting counter instead of inserting a copy.

Reading note: the n shown against a cell counts weighted samples, not unique gigs — an observation counts at every geographic level it informs and once per re-sighting, so cell-level n runs far higher than the pool of unique observations. The distinct pool size is published in every issue (4,431 approved observations in the August 2026 issue).

The quality firewall

Every observation faces the same gates whatever its source, and every rejection is logged with a reason — the audit trail is part of the product.

§ 7

Five gates, plus one for ticketed clubs

Has the basics — no amount, no source, no gig type: no entry. From a known source — only the vetted source list may write to the Index, through a single ingest funnel. Is an artist fee — the database layer itself refuses ticket money, gear hire, licensing and door splits. Passes the plausibility check — each gig type carries per-musician-per-hour bounds, so a £40 wedding quartet and a £20,000 pub solo both bounce automatically. Not a duplicate — every observation is fingerprinted; a re-scanned listing bumps a sighting counter, never becomes a second row.

Ticketed club fees face a sixth test: a four-archetype room-economics model grounded in Music Venue Trust occupancy data — ticket price × capacity × realistic occupancy × the act’s share of the door.

§ 8

Anonymous submissions

Anyone who has played or booked a UK gig can report the fee at gigxchange.app/rates — no account needed. Submissions are rate-limited, sanity-checked and human-reviewed before they touch a cell. As a class they hold the largest quota in the model — a cap of 0.20, the maximum share of any published cell they may own — on the reasoning that a fee someone was actually paid beats a fee someone advertised. There is no post-event verification step: nothing in the Index promotes a submission to a different class once it has landed.

When a figure publishes

A figure only publishes when there is enough behind it — and when there isn't, the calculator tells you exactly which level answered instead.

§ 9

Cell thresholds and geographic fallback

Publication happens at three levels: city (major UK metros, with satellite towns folded into their hub — Hove reads as Brighton, Oldbury as Birmingham), region (the twelve official UK regions), and the UK baseline. Every cell in the grid prints. Nothing is held back. What a cell has to earn is not its place in print but its label.

The rule, in one line. A city cell is measured when it holds at least three observations collected in that city — three separate gigs there, not three sightings of one rate. A city cell that holds fewer still publishes, computed from exactly the same evidence, but it is labelled imputed: its figure leans on the pooled market rows rather than on local collection, and it says so in the API, in the open dataset and on this site. Region and UK cells are measured by definition — they are roll-ups of everything applicable to them, which is what a national baseline is.

Why the distinction exists. Since 12 August a city cell has been computed from its own observations plus every observation in the pool that carries no location at all — market rate cards, union minimums, published rate schedules — on the reasoning that a national price list is a price charged in that city too. That is right for the arithmetic and it stays. But it also means the raw count of rows behind a city cell can be large while the locally-collected count is zero, so the count alone cannot tell you whether you are reading a measurement or an estimate. The local floor is what tells you. Every city cell publishes both counts — local_sample_size and blanket_sample_size — in the open dataset (the is_imputed flag itself is on the live tables and the calculator; in the CSV, measured means local_sample_size of three or more), so you can always see which kind of cell you are reading and reconstruct the judgement yourself. Region and UK rows leave both columns empty: the split only means something where a pooled layer is being laid over local evidence. When you look up somewhere with no cell of its own, the live calculator walks the chain — city, then region, then the national figure with a regional adjustment — and tells you which level answered.

The floor only ever rises. Three is deliberately low while the Index is young: a cell published with its evidence attached and honestly labelled is more useful than no cell at all, and every figure carries its n so a reader can weigh it. The floor is a value in the database rather than a promise in prose, and the database refuses any attempt to lower it — so no figure can ever be re-labelled measured by relaxing the bar, and raising it costs no coverage at all: the same cells print, more of them carry the honest label. At present more than half of all measured cells rest on fewer than ten observations, so single-city figures are indicative; the national baselines carry the weight. § 11 covers the other kind of estimate — a cell a city has no observations for at all — and how it is flagged.

§ 10

Regional adjustments

The adjustment layer blends ONS regional household income and family-spending data with public industry price benchmarks, tuned per gig type: corporate fees track regional wealth closely, wedding spend barely does, and pub fees hardly flex at all because venue economics set the ceiling everywhere. Adjustments only ever fill gaps — wherever real observations exist, they win outright.

§ 11

Derived cells, and how they are marked

Coverage is uneven: a city may have plenty of wedding observations and none at all for a four-piece in a pub. Rather than leave a hole that makes cities incomparable, the Index fills that gap with a derived cell — and marks it as derived everywhere it appears, in the API, the dataset and on the page. The value is the national figure for that same gig type and band size, scaled by how that city prices against the national baseline on the cells it does have. We use the city’s own observed pay level rather than its neighbours’, because geography is not what sets gig fees — Brighton’s nearest large market is London, and borrowing London’s rates would simply make Brighton look dearer than it is.

Every city carries the same grid. An index is only an index if you can look up any town and find the same data points, so the grid is every gig type and band size the UK baseline can anchor — 23 cells, identical in all thirteen cities (seven gig types across four band sizes, minus the six combinations the UK baseline cannot anchor, plus an any-size wedding cell). It is not narrowed to whatever a city happens to have collected; that would make towns incomparable, which is the fault derived cells exist to fix.

Two rules keep it honest, and they are deliberately the ones that stop nonsense rather than the ones that limit coverage. A city needs three measured cells of its own before we will estimate how it prices at all — below that it gets no derived cells. And a measured cell more than three times, or less than a third of, its national counterpart is treated as unusable and replaced by the derived figure, with the original retained in the record. Those thresholds, and the local floor in § 9, only ever ratchet upward as coverage grows; the database refuses to loosen them to make a figure publishable.

Derived cells are never evidence. They are never counted in a sample size, never used to calculate another cell, and never written back into the observation record — the raw data stays purely observed. They are rebuilt from scratch on every refresh, so the moment observations arrive for that city and gig type, the derived figure disappears and the measured one takes its place.

Two kinds of estimate, one flag. A city cell is flagged is_imputed either because the city had no observations at all for that gig type and band — the derived cell described above, method ratio — or because it holds fewer than three locally-collected rows and therefore leans on the pooled market rows, method blanket_pool (§ 9). Both print; both are labelled; the method column tells you which you are reading. Anyone wanting measured figures only can filter the CSV on local_sample_size of three or more (the flag itself is exposed on the live tables and the calculator), so the judgement can be reconstructed from the raw dataset rather than taken on trust.

The grid, in one city Newcastle — the same 23 cells every city carries. Solid = measured here. Outlined = derived.
Gig typeSoloDuo3–45+Any size
Pub / bar£250£334£320£812·
Wedding£347£565£1065£1600£1227
Private party£310£446£913£600·
Corporate£385£446£812£1329·
Club£250£468£600··
Festival··£669£1560·
Theatre£175····

Five cells clear the local floor and read as measured; the other eighteen publish too, labelled. Every other city answers the same twenty-three questions — that is what makes the league a like-for-like comparison rather than a comparison of who has collected most.

How much of each city is measured Cells holding at least three locally-collected observations, out of 23
  • London 12/23
  • Manchester 11/23
  • Bristol 9/23
  • Brighton 8/23
  • Cardiff 8/23
  • Birmingham 7/23
  • Leeds 7/23
  • Sheffield 7/23
  • Glasgow 6/23
  • Liverpool 6/23
  • Edinburgh 5/23
  • Newcastle 5/23
  • Nottingham 4/23

The remaining cells still publish — labelled, never withheld. This is the number to weigh a city figure by, and it is published beside every one of them. It only goes up.

§ 12

Refresh cadence

The cells rebuild nightly at 05:00 UTC. Industry rate cards re-scan on Mondays; the artist panel snapshots on the 28th; approved submissions flow daily. Every rebuild is archived rather than overwritten — that is what makes issue-on-issue comparisons possible. The full report ships monthly.

Honest limits

A record of what the UK market paid, asked or budgeted across the observation window — nothing more.

§ 13

What this is and isn’t

Not a recommended price. We publish where the market sits, not where you should sit in it — undercut or exceed any figure here with a clear conscience. Not an official benchmark. No industry body endorses or regulates these figures; independence is the point. Not financial advice. Evidence in, decision yours. Not the whole market. Most UK gig fees are agreed privately and surface nowhere — an index can only weigh what it can see.

Known gaps are reported in each issue: confirmed platform bookings have yet to arrive in volume, festival and theatre remain the thinnest gig types, and no genre-level cells publish yet — the tags exist on every observation, and publication waits on volume, not engineering. Corrections to our own data are documented in the open in the issue they land.

Most city figures are labelled estimates, not measurements. Where local collection is thin we still publish the cell rather than a hole, always flagged as such — § 9 sets the floor and § 11 explains the two kinds of estimate. A flagged figure is an estimate of what a city would pay given the wider market and how that city prices elsewhere; it is not a record of a gig anyone played there. Coverage is uneven and we publish it openly: London clears the local floor on 12 of its 23 cells, Manchester 11 and Nottingham 4 — every city figure carries that count, so you can see at a glance how much of it is measured.

See the method at work: the live percentiles are the GX Index itself; UK gig pay measured in pints is the same medians in a friendlier unit, and Gig Pay Anatomy takes a fee apart. For the sourced industry backdrop see the UK market statistics sheet; for the circuit itself, open mic statistics and gig calendar statistics. Each month’s full tables are in the report library.

Datasets, DOIs & downloads

The report, the live figures and the raw dataset are all published under Creative Commons Attribution 4.0 — use them, republish them, build on them commercially, with credit.

How to cite this Index

GigXchange Index, UK Live Music Booking Rates 2026. Available at: https://gigxchange.app/rates. Licensed under CC BY 4.0.

DOI 10.5281/zenodo.19663014 · CC BY 4.0

Issue 05

August 2026 — 4,431 observations, 13 cities

Read online · PDF · CSV

Issue 04

July 2026 — 4,290 observations, 13 cities

Read online · PDF · CSV · Zenodo DOI 10.5281/zenodo.21712429 · Hugging Face · Kaggle

Issue 03

June 2026 — 4,036 observations, 13 cities

Read online · PDF · CSV · Zenodo DOI 10.5281/zenodo.21197463 · Hugging Face · Kaggle

Issue 02

May 2026 — 3,847 observations, 13 cities

Read online · PDF · CSV · Zenodo DOI 10.5281/zenodo.20304563 · Hugging Face · Kaggle

Issue 01

April 2026 — 2,381 observations, 14 cities

Read online · PDF · CSV · Zenodo DOI 10.5281/zenodo.19663015 · Hugging Face · Kaggle

Licence

CC BY 4.0

Cite as “GigXchange Index, gigxchange.app/rates”. Machine-readable snapshot: /data/rates-snapshot.json. Live percentiles: the GX Index hub. All monthly issues: the reports library.

Naumaan
Founder & Builder

Real UK gig-fee data, not guesswork — built from actual bookings. Add yours and it gets sharper for everyone.

Did you know? The UK is one of the world’s largest music markets, behind only the US and Japan.
Email me directly →