GGB The GGB Index · Edition 2026
Methodology & anonymisation.
A benchmark is only worth what its collection discipline is worth. This page states the Index's rules exactly — what is collected, how anonymity is enforced in code, and why publication waits.
Methodology registercollection · anonymisation · publication
- What is collected
- Exactly seven governed fields: market (band list), concept (band list), monthly revenue band, food cost as a percentage of revenue, labour as a percentage of revenue, delivery-platform share of revenue (band), and outlet count (band). Free text is not accepted anywhere in the survey. The two percentages are the only raw numbers, because they are the benchmark itself; everything identity-adjacent is a band.
- How anonymity is enforced — not promised
- The collection endpoint refuses any submission carrying a name, email, phone, business or message field — refusal happens in code, before storage, so a client bug cannot smuggle identity into the dataset. Submissions carry no account, no cookie linkage and no session join. If you also reserve the report, that reservation is a second, separate request that carries your email and none of your figures. The two records share nothing linkable.
- What contributors receive
- The full published Index, free, before general release. The reservation list is used for exactly that delivery and lives under the same consent discipline as every GGB email lane.
- When it publishes
- Publication waits for a real sample: nothing is published below 25 contributions, and figures are reported only at cohort level (market × concept) where the cohort itself is large enough not to expose an individual operation. The public contribution counter follows the same floor — below it, the counter deliberately shows nothing.
- What is published
- Distributions and medians per cohort — never a row. The published report states its sample size, collection window and edition. Outlier rows that look like data-entry errors (outside plausible operating ranges) are excluded by the same bounds the survey form enforces at entry.
- Retention & removal
- Rows are retained to build year-on-year comparisons across editions. Because rows are anonymous, GGB cannot identify which row is yours after submission — which also means a specific row cannot be recalled on request. That trade-off is stated here, before you contribute, not discovered after.