Pilot rehearsal · synthetic data only

Prove the data path before a club shares real fan data.

This rehearsal exercises the same ticket-grain logic used by the pilot, but only with the repository’s synthetic Brighton dataset. It proves the workflow, not a London City commercial outcome.

01 · INPUTTicket-grain records

Fixture, campaign, consent, paid value and scan state.

→
02 · MATCHRepeat cohort

Pseudonymous matching is used only to calculate the cohort.

→
03 · AGGREGATEDecision evidence

Only counts, rates and economics are needed by the product layer.

→
04 · INTERPRETDescriptive result

Attribution is visible; incrementality remains unproven.

What the rehearsal produces

The same decision ingredients the live pilot will need.

Addressable repeat cohort0

Consented opener buyers who have not purchased Brighton.

Campaign-attributed tickets10

Descriptive attribution from the synthetic current-fixture records.

Repeat purchase rate—

Observed in the rehearsal cohort; not an incremental-lift estimate.

Gross ticket revenue£156

Synthetic realised ticket value.

Scan rate83.3%

Based on records with a decided scan state.

Raw supporter rows stored0

The production bridge persists aggregate evidence only.

Interpretation

What this proves, and what it does not.

PROVESData contract and aggregation path

The workflow can turn ticket-grain input into repeat, attribution, revenue and attendance-quality evidence.

PROVESPrivacy boundary

The product can work with aggregate club evidence without storing supporter-level records in the repository.

DOES NOT PROVEIncremental commercial impact

A real pilot still needs authorised club data and a pre-agreed counterfactual if the club wants a causal lift claim.

Next step

Replace the synthetic input, not the product workflow.

A pilot club supplies an authorised export outside the repository. The same aggregation contract then feeds Opportunity, Impact and Results with measured evidence.

Pilot Rehearsal | AVELA