# Fan Passport — Post-World Cup Expansion Principles

## 1. Expansion vision

After FIFA World Cup 2026, Fan Passport should evolve from a single-tournament experience into a reusable football fan passport platform.

Future products:

- **Premier League Passport**
- **Champions League Passport**
- Domestic cup passports
- International tournament passports
- Club-specific fan passports
- A broader football fan rewards ecosystem

The core idea remains the same: fans collect their journey, prove their knowledge, unlock achievements, and preserve memories across competitions.

## 2. What should remain reusable

The following systems should be designed as competition-agnostic configuration wherever possible:

| System | Reusable concept |
| --- | --- |
| Passport profile | User identity, favorite teams/clubs, titles, archive |
| Fixture engine | Matches, rounds, stages, deadlines, results |
| Prediction engine | Result, scoreline, advancement, champion/winner picks |
| Achievement engine | Badges, criteria, progress, rewards |
| Collection engine | Teams/clubs, stadiums, matches, stickers, moments |
| Quiz engine | Daily trivia, themed questions, streaks |
| Leaderboard engine | Global, friends, private, stage/window boards |
| Challenge engine | Daily, weekly, team, competition, collection challenges |
| Sharing engine | Badge, prediction, recap, collection cards |
| Memory archive | Saved personal and generated moments |
| Notification engine | Deadlines, matches, streaks, recaps |
| Admin/content tooling | Configurable competitions, content, scoring, correction |

A “competition” should be a configurable object, not a hard-coded World Cup assumption.

## 3. Competition model principles

### 3.1 Competition configuration

Each passport should define:

- Competition name
- Season/tournament year
- Teams/clubs
- Stages/rounds
- Fixture calendar
- Scoring rules
- Collection categories
- Badge set
- Quiz calendar
- Leaderboard windows
- Recap format
- Rights/licensing display rules

### 3.2 Avoid hard-coded structures

World Cup-specific assumptions that should not be hard-coded:

- Exactly 48 teams
- Exactly 12 groups
- Group-stage advancement format
- Tournament length
- National teams only
- Neutral venues only
- One champion only before knockout bracket
- Single host country or stadium model

Instead, support flexible structures:

- Leagues with 20 clubs and 38 matchweeks
- Swiss-format competitions
- Two-legged knockout ties
- Domestic cup rounds
- Playoffs
- International breaks
- Multi-season archives

## 4. Premier League Passport

### 4.1 Product positioning

> “Collect your season. Follow your club every matchweek, predict the table, unlock rivalries and stadiums, and build your Premier League fan legacy.”

### 4.2 Target behaviors

- Return every matchweek
- Follow favorite club
- Predict results and table movement
- Collect stadium visits/follows
- Complete club sets
- Answer weekly trivia
- Compete in private leagues
- Preserve season memories

### 4.3 Adapted core loop

1. Open before matchweek
2. Predict fixtures
3. Answer weekly/daily trivia
4. Check in to favorite club match
5. Collect stadium/club/matchweek stamps
6. See leaderboard movement
7. Unlock matchweek badges
8. Return for next matchweek

### 4.4 Premier League-specific collections

| Collection | Description |
| --- | --- |
| Club collection | All 20 clubs |
| Stadium collection | 20 home grounds |
| Matchweek stamps | 38 matchweeks |
| Rivalry moments | Derby/rivalry fixtures |
| Table milestones | Top-four race, relegation battle, title race moments |
| Club journey | Favorite club’s season path |
| Player award moments | If rights/data allow, goal scorers or player milestones |
| Sticker album | Club badges/abstract kits/stadium art if licensed or generic alternatives |

### 4.5 Premier League prediction mechanics

Prediction types:

- Match result
- Exact scoreline
- Matchweek accumulator-style completion without gambling framing
- Table position predictions
- Top four prediction
- Relegation prediction
- Champion prediction
- Golden Boot-style prediction if rights/data allow
- Derby winner
- Managerial milestone prompts only if editorially appropriate

Scoring should include:

- Matchweek leaderboards
- Monthly leaderboards
- Season leaderboard
- Favorite-club fan leaderboard
- Comeback boards for each month

### 4.6 Premier League badges

Examples:

| Badge | Criteria |
| --- | --- |
| Opening Weekend | Participate in Matchweek 1 |
| Club Loyalist | Check in to every favorite club league match in a month |
| Derby Day | Predict or check in to a derby fixture |
| Boxing Day Regular | Participate in holiday matchweek |
| Top Four Prophet | Correctly predict top four before deadline |
| Survival Specialist | Correctly predict relegation-zone outcome before deadline |
| Stadium Hopper | Collect 10 stadiums |
| Full Season Passport | Complete season passport |
| Champion Caller | Correctly predict league champion before season or early lock |

### 4.7 Premier League retention design

Unlike the World Cup, the Premier League is long. Retention must avoid burnout.

Principles:

- Use matchweek loops, not mandatory daily loops all season.
- Daily trivia can exist but should not be the only path to completion.
- Monthly resets keep competition alive.
- Club-specific goals maintain emotional attachment.
- International breaks should include catch-up collections, quizzes, and historical challenges.
- End-of-month recaps preserve progress.

## 5. Champions League Passport

### 5.1 Product positioning

> “Trace Europe’s biggest nights. Collect clubs, stadiums, matchdays, knockout drama, and your road to the final.”

### 5.2 Competition-specific structure

Modern Champions League formats may include league phases, seeded draws, knockout playoffs, two-legged ties, and final. The passport must support format changes through configuration.

### 5.3 Target behaviors

- Return on European matchdays
- Predict high-profile fixtures
- Follow favorite club across Europe
- Collect stadiums and countries
- Complete matchday sets
- Predict knockout progression
- Compete in private leagues
- Share dramatic European nights

### 5.4 Champions League-specific collections

| Collection | Description |
| --- | --- |
| Club collection | Participating clubs |
| Country collection | Nations represented by clubs |
| Stadium collection | Home grounds and final venue |
| Matchday collection | League-phase or group-stage matchdays |
| Knockout tie collection | Two-legged tie stamps |
| Final road | Favorite club’s route |
| European nights | Special moments: comeback, penalties, extra time |
| Sticker album | Clubs, stadiums, moments, abstract player-role cards if licensed |

### 5.5 Champions League prediction mechanics

Prediction types:

- Match result
- Exact scoreline
- Tie winner
- Aggregate score band
- Extra time/penalties for knockout ties
- Qualifying clubs from league phase
- Final winner
- Top scorer-style prediction if licensed/data supported

Tie scoring must distinguish:

- First-leg match result
- Second-leg match result
- Aggregate winner
- Penalty outcome where applicable

### 5.6 Champions League badges

Examples:

| Badge | Criteria |
| --- | --- |
| European Night | Participate in first Champions League matchday |
| Away Days Collector | Collect stadiums in 5 countries |
| Knockout Specialist | Correctly predict 5 knockout tie winners |
| Comeback Witness | Check in to a tie where aggregate comeback occurs, if event data supports |
| Final Venue Stamp | Collect final stadium |
| Road to the Final | Follow finalist club through every knockout tie |
| European Champion Caller | Correctly predict winner before knockout stage |
| Full Champions League Passport | Complete season/tournament passport |

### 5.7 Champions League retention design

- Emphasize matchday spikes rather than daily obligations.
- Use “European week” challenges.
- Preserve drama around draws and knockout brackets.
- Use country/stadium collections to create travel fantasy.
- Reset leaderboards by phase: league phase, playoffs, round of 16, quarter-finals, semi-finals, final.

## 6. Long-term football fan rewards ecosystem

### 6.1 Ecosystem concept

Over time, Fan Passport can become a persistent fan identity across competitions.

A user could have:

- World Cup 2026 Passport
- Premier League 2026/27 Passport
- Champions League 2026/27 Passport
- Club-specific passport
- Lifetime football profile

### 6.2 Cross-competition identity

The user’s global profile can show:

- Lifetime XP
- Competition passports completed
- Favorite clubs/nations
- Rarest badges
- Prediction accuracy across competitions
- Stadiums collected
- Trivia mastery
- Shareable fan title

### 6.3 Cross-passport achievements

Examples:

| Achievement | Criteria |
| --- | --- |
| Global Traveller | Collect stadiums from 3 competitions |
| Year-Round Fan | Participate in World Cup and club season passports |
| Prediction Veteran | Submit 500 predictions across competitions |
| Trivia Archivist | Answer 365 football trivia questions |
| Club and Country | Complete favorite national team and club journeys |
| Final Collector | Collect final match stamps from multiple competitions |

### 6.4 Rewards principles

If real-world rewards are introduced:

- Rewards must not create pay-to-win prediction advantages.
- Prize eligibility must have clear terms, age/location rules, and anti-fraud controls.
- Sponsor challenges should be optional and clearly marked.
- Commercial rewards should enhance collection, identity, or access, not compromise fair play.
- User data usage must be transparent.

Potential reward types:

- Digital cosmetics
- Partner discounts
- Ticket ballot entries where legally compliant
- Merchandise discounts
- Supporter club perks
- Sponsor challenge collectibles
- Premium recap exports
- Charity-linked community challenges

## 7. Product architecture principles for expansion

### 7.1 Configurable passports

A passport instance should be defined by configuration:

```text
Passport
├── Competition metadata
├── Participants
├── Fixtures/stages
├── Collections
├── Badges
├── Challenges
├── Prediction rules
├── Quiz schedule
├── Leaderboard rules
├── Share templates
└── Archive/recap template
```

This lets the platform launch new competitions without rebuilding all mechanics.

### 7.2 Stable event model

Most game mechanics can be powered by events such as:

- UserRegistered
- FavoriteTeamSelected
- PredictionSubmitted
- PredictionLocked
- MatchResultFinalized
- PredictionScored
- QuizAnswered
- BadgeUnlocked
- CollectionItemAcquired
- ChallengeCompleted
- MatchCheckedIn
- MemorySaved
- ShareCreated
- LeagueJoined

Achievement and collection rules should consume these events consistently.

### 7.3 Separation of participation and competition

Maintain the separation across all passports:

- Participation rewards: XP, badges, collections, memories
- Skill competition: prediction points, quiz points
- Social competition: private leagues, friend rankings
- Completion competition: passport percentage

This allows more fans to feel rewarded even when they are not top predictors.

### 7.4 Archive-first thinking

Each passport should become an archive after the competition ends.

Archive should preserve:

- Final stats
- Collections
- Badges
- Predictions
- Memories
- Leaderboard finishes
- Share cards
- Recap

Live-only data should be transformed into memory surfaces rather than disappearing.

## 8. Content strategy for expansion

### 8.1 Repeatable content calendars

World Cup:

- Daily trivia
- Matchday predictions
- Stage challenges
- Final recap

Premier League:

- Matchweek trivia
- Monthly challenges
- Club-specific stories
- Holiday fixtures
- Derby weeks
- End-of-season recap

Champions League:

- European week trivia
- Draw reactions
- Matchday predictions
- Knockout tie challenges
- Final week recap

### 8.2 Localization

Long-term football audiences are global. Expansion should prepare for:

- Multiple languages
- Local kickoff time formatting
- Localized trivia
- Region-specific notification timing
- Culturally sensitive rivalry language
- Market-specific rights and sponsor rules

### 8.3 Rights flexibility

If official rights are not available for a competition, the product should still function using:

- Text names where legally allowed
- Country flags where permitted
- Abstract team color themes without protected marks
- Generic stadium illustrations
- User-generated preference labels
- Non-infringing football iconography

If official rights are secured, the same IA and game systems can display richer assets.

## 9. Expansion roadmap

### 9.1 Phase A — World Cup MVP

- Launch core passport
- Validate daily trivia, prediction, collection, badge, and sharing loops
- Learn which mechanics retain users
- Build final recap/archive

### 9.2 Phase B — Post-World Cup archive and waitlist

- Deliver recap
- Archive passport
- Launch Premier League/Champions League waitlists
- Survey users on preferred next competition
- Offer early supporter badges for next passport

### 9.3 Phase C — First club-season passport

Recommended next product: Premier League Passport or Champions League Passport depending licensing/content feasibility.

Launch with:

- Existing account/profile
- Reused prediction engine
- Reused badge/achievement engine
- Matchweek or matchday loop
- Club/stadium collections
- Private leagues
- Season archive

### 9.4 Phase D — Multi-passport ecosystem

- Unified profile
- Lifetime achievements
- Cross-competition collections
- Reward partner framework
- Public profile pages
- Yearly fan recap

## 10. Expansion decision criteria

Before launching a new passport, evaluate:

| Criterion | Question |
| --- | --- |
| Audience pull | Do users want this competition? |
| Calendar fit | Does it have a natural recurring loop? |
| Data reliability | Can fixtures/results be maintained accurately? |
| Rights feasibility | Can names/assets be used safely? |
| Content supply | Can quizzes/challenges be produced consistently? |
| Social relevance | Will friends compete around it? |
| Collection richness | Are there teams, stadiums, moments, and stages to collect? |
| Commercial potential | Are partners interested without compromising fairness? |

## 11. Non-negotiable expansion principles

1. A passport must always produce lasting memory value.
2. New competitions should reuse existing engines before adding bespoke mechanics.
3. Prediction fairness must remain transparent.
4. No user should lose their World Cup passport when the product evolves.
5. Club-season loops should respect user attention and avoid daily burnout.
6. Competition-specific flavor should come through badges, collections, trivia, and recap design.
7. Rights and licensing constraints must be handled before public asset usage.
8. Social features must remain safe and moderation-aware.
9. Monetization must not compromise competition integrity.
10. Fan Passport should become the trusted home for football journeys across time.