# Live Operations, Analytics, Fair Play, and Expansion Playbook

## 1. Purpose

Fan Passport is not a static product. It must be operated daily during a global live tournament and then transitioned into a long-term football passport ecosystem. This playbook defines how to run the product, measure it, protect fairness, and expand it after FIFA World Cup 2026.

## 2. Live-Operations Principles

1. **Every day has a reason to return.**
2. **Matchdays prioritize prediction deadlines and result settlement.**
3. **Rest days prioritize trivia, collections, recaps, and upcoming brackets.**
4. **Content must be accurate before it is clever.**
5. **Scoring trust is more important than surprise.**
6. **The final week should create memories, not just rankings.**
7. **Post-tournament archive must feel like a reward, not a shutdown.**

## 3. Tournament Operating Calendar

### 3.1 T-120 to T-60 Days: Foundation

Objectives:

- Confirm product rules.
- Build content plan.
- Prepare data model and admin workflows.
- Establish rights strategy.
- Draft badge, challenge, and quiz banks.

Live-ops work:

- Define daily reset timezone.
- Confirm match data source and fallback process.
- Prepare initial team/stadium content.
- Build first 200–300 trivia questions.
- Create badge and challenge calendar.
- Write scoring rules and help copy.
- Draft notification categories and opt-in language.

Success criteria:

- Fixture ingestion process tested with sample data.
- Admins can create quiz, challenge, badge, and collection items.
- Scoring rules are approved and frozen for MVP launch.
- Rights register exists for every visual asset category.

### 3.2 T-60 to T-30 Days: Beta Preparation

Objectives:

- Validate activation and first-session experience.
- Seed pre-tournament gameplay.
- Recruit early users.

Live-ops work:

- Launch countdown missions.
- Publish “Passport Prepared” challenge.
- Open champion prediction if qualified teams and rules are ready.
- Create starter pack item pools.
- Test share cards.
- Test friend invite flows.
- Run internal settlement simulations.

Success criteria:

- New users complete onboarding and first action.
- Daily trivia can publish without engineering intervention.
- Prediction lock and settlement are verified in simulation.
- Support team can answer scoring questions.

### 3.3 T-30 to Opening Match: Countdown Campaign

Daily content themes:

- Team spotlights.
- Stadium spotlights.
- World Cup history trivia.
- “Choose your team” prompts.
- Champion prediction reminders.
- Starter collection missions.
- Invite friends before kickoff.

Key challenges:

| Challenge | Window | Criteria |
| --- | --- | --- |
| Passport Prepared | T-30 to opening match | Complete onboarding, favorite team, privacy setup |
| Early Believer | T-30 to opening match | Submit champion prediction |
| Stadium Scout | T-21 to opening match | Collect three stadium items |
| Trivia Warm-Up | T-14 to opening match | Complete five daily quizzes |
| Bring Your XI | T-14 to opening match | Invite friends to private leaderboard |

Operational focus:

- Monitor onboarding funnel.
- Check champion prediction participation.
- Confirm opening match prediction market.
- Load group-stage daily missions.
- Prepare incident response for opening day.

### 3.4 Opening Match Day

Priority order:

1. Site/app availability.
2. Prediction lock correctness.
3. Daily stamp reliability.
4. Result settlement after match.
5. Share-card performance.
6. Leaderboard updates.

Live-ops checklist:

- Confirm kickoff time.
- Confirm prediction lock time.
- Schedule prediction reminders.
- Publish opening trivia.
- Publish Opening Match Stamp.
- Staff admin monitoring before lock.
- Verify result before settlement.
- Watch support and social channels for scoring confusion.

Opening-day moments:

- Passport Issued share.
- Opening Match Stamp.
- First Call badge.
- First exact scoreline highlight.
- Opening quiz perfect score.

### 3.5 Group Stage Operations

Group stage is dense and habit-forming.

Daily operating rhythm:

| Time Relative to First Match | Operator Actions |
| --- | --- |
| Previous evening | Verify next-day fixtures, publish trivia, schedule missions |
| Morning | Check Today screen content, notification queue, data freshness |
| 2–3 hours before kickoff | Monitor prediction submissions, send reminders |
| Lock time | Verify prediction markets locked |
| During matches | Monitor traffic, avoid major non-critical releases |
| After final whistle | Verify result, settle predictions, publish result moments |
| End of day | Review leaderboard anomalies, support issues, content metrics |

Group-stage content types:

- Predict today’s matches.
- Stamp multiple matches.
- Complete group-specific challenges.
- Collect teams from each group.
- Stadium of the day.
- Daily trivia tied to current matches.
- “Upset watch” for eligible giant killings.

Group-stage risks:

| Risk | Mitigation |
| --- | --- |
| Too many matches overwhelm users | Home prioritizes favorite team and soon-locking predictions |
| Prediction reminders become spam | Send only for followed teams, pending predictions, or opted-in all matches |
| Result settlement errors compound | Verify match-by-match and use idempotent settlement |
| Users miss days and churn | Streak freeze, catch-up collection missions, rest-day recaps |

### 3.6 Round of 16 Operations

Focus:

- Reframe product after group-stage churn.
- Promote bracket and knockout predictions.
- Help users whose teams are eliminated.

Content:

- “Knockout Ready” challenge.
- Adopt-a-team prompt.
- Round-of-16 prediction queue.
- Giant killing eligible match highlights.
- Knockout bracket explainer.
- Best group-stage moments recap.

Metrics to watch:

- Retention among users whose favorite team was eliminated.
- Bracket prediction submission.
- Prediction participation per knockout match.
- Share rate for group-stage recap.

### 3.7 Quarterfinal and Semifinal Operations

Focus:

- Fewer matches, higher emotional stakes.
- Deeper match pages and shareable prediction moments.

Content:

- “Bold Weekend” challenge.
- Head-to-head trivia.
- Exact-score spotlight.
- Stadium story content.
- Prediction Pro leaderboard updates.
- Friend leaderboard nudges.

Operational concerns:

- Avoid ambiguous giant killing eligibility.
- Prepare support copy for extra time and penalties.
- Make settlement basis clear for knockout matches.
- Ensure leaderboard tie-breakers are documented.

### 3.8 Final Week and Final Match

Focus:

- Maximize emotional payoff.
- Preserve final memories.
- Generate recap and future-passport intent.

Content:

- Final prediction.
- Final venue stamp.
- Champion badge.
- Final trivia.
- “My World Cup Journey” recap preview.
- Final leaderboard provisional notice.
- Post-final waitlist for next passport.

Final match checklist:

- Confirm final prediction market.
- Confirm lock time and notification schedule.
- Freeze non-critical deploys.
- Staff support around kickoff and post-match settlement.
- Verify final score and champion data.
- Settle predictions.
- Award champion/bracket badges.
- Generate provisional recaps.
- Begin leaderboard correction window.

### 3.9 Post-Final T+1 to T+30

Focus:

- Archive.
- Recap sharing.
- Fair-play finalization.
- Transition to next passport.

Timeline:

| Window | Actions |
| --- | --- |
| T+1 day | Publish provisional recap, thank-you message, correction window notice |
| T+3 days | Complete abuse review and scoring corrections where possible |
| T+4 days | Archive final leaderboard |
| T+7 days | Send final recap campaign |
| T+14 days | Open next passport waitlist or preview |
| T+30 days | Move World Cup passport to stable archive mode |

## 4. Content Operations

### 4.1 Content Roles

| Role | Responsibilities |
| --- | --- |
| Product Operator | Owns daily schedule, challenge calendar, scoring configuration |
| Football Content Editor | Writes/reviews trivia, team/stadium facts, match context |
| Rights Reviewer | Confirms asset and mark usage status |
| Community/Support Lead | Handles user questions, disputes, moderation reports |
| Data Operator | Verifies fixtures, kickoff times, results, standings |
| Analytics Lead | Monitors KPIs and anomaly dashboards |
| Engineering On-Call | Handles incidents, settlement failures, performance issues |

### 4.2 Trivia Workflow

1. Draft question.
2. Add answer choices.
3. Add explanation.
4. Add source/review note.
5. Assign category and difficulty.
6. Check for ambiguity.
7. Check for localization concerns.
8. Mark reviewed.
9. Schedule to daily quiz.
10. Monitor performance.
11. Retire or invalidate if necessary.

Question acceptance checklist:

- One unambiguously correct answer.
- Incorrect answers plausible but not misleading.
- Explanation teaches.
- Time-sensitive facts include date context.
- No unsupported claims.
- No disrespectful framing.
- Rights-safe if mentioning protected media or imagery.

### 4.3 Badge and Challenge Workflow

1. Define objective.
2. Confirm it supports a product loop.
3. Define measurable criteria.
4. Confirm reward values.
5. Confirm availability window.
6. Confirm whether criteria are visible or secret.
7. Configure rule version.
8. Test with sample users.
9. Publish.
10. Monitor completion rate.

Challenge quality checklist:

- Criteria are understandable.
- User can see how to progress.
- Reward matches effort.
- Challenge is possible within window.
- Expiration behavior is clear.
- It does not require paid spend.
- It does not require impossible physical attendance.

### 4.4 Collection Content Workflow

1. Define album categories.
2. Define item list.
3. Assign rarity.
4. Confirm asset rights.
5. Write item description.
6. Link item to team/match/stadium/challenge if applicable.
7. Add item to pack pools.
8. Test duplicate and crafting behavior.
9. Monitor completion rates.

Collection quality checklist:

- Starter experience is duplicate-free.
- Missing items have clear acquisition paths.
- Rare items are exciting but not blockers for broad engagement.
- Crafting gives agency.
- Official assets have rights status.
- Neutral fallback art exists.

### 4.5 Notification Workflow

1. Define trigger and audience.
2. Confirm category and opt-out handling.
3. Write short copy.
4. Include local time/team where relevant.
5. Check quiet hours.
6. Test deep link.
7. Schedule.
8. Monitor open and opt-out rates.

Notification copy guidelines:

- Be useful, not noisy.
- Use urgency only for real deadlines.
- Celebrate user achievements.
- Avoid guilt-heavy streak language.
- Never imply betting or financial stakes.

Example copy:

| Trigger | Copy |
| --- | --- |
| Prediction deadline | “Kickoff is close. Lock your [Team A] v [Team B] prediction before it closes.” |
| Daily trivia | “Today’s World Cup trivia is live. Keep your passport streak going.” |
| Exact score | “You called it exactly. Your prediction points are ready.” |
| Giant killing | “Shock predicted. Your bold call paid off.” |
| Final recap | “Your World Cup passport recap is ready.” |

## 5. Analytics Framework

### 5.1 North Star Metric

**Daily Passport Actions per Active User**

Included actions:

- Daily stamp.
- Prediction submitted.
- Prediction result viewed.
- Quiz completed.
- Pack opened.
- Collection set progressed.
- Badge/challenge progressed.
- Leaderboard viewed.
- Share card generated.

This metric captures daily habit breadth better than simple sessions.

### 5.2 Core Dashboards

#### Executive Dashboard

- DAU/WAU.
- New passports created.
- Activation rate.
- D1/D7 retention.
- Daily Passport Actions per Active User.
- Total predictions submitted.
- Quiz completion rate.
- Collection pack opens.
- Share cards generated.
- Leaderboard views.

#### Matchday Dashboard

- Users active today.
- Predictions by match.
- Prediction submission rate before lock.
- Lock-time errors.
- Match stamps.
- Settlement status.
- Post-settlement return rate.
- Prediction share cards.

#### Trivia Dashboard

- Quiz starts.
- Quiz completions.
- Correct answer rate by question.
- Perfect quiz rate.
- Question difficulty performance.
- Streak continuation.
- Invalidated question count.

#### Collection Dashboard

- Packs earned.
- Packs opened.
- Unique items collected.
- Duplicate rate.
- Craft Token generation/spend.
- Set completion rate.
- Items blocking completion.
- Pack source performance.

#### Leaderboard/Fairness Dashboard

- Score distribution.
- Top score event sources.
- Anomaly flags.
- Hidden accounts.
- Score corrections.
- Support disputes.
- Finalization status.

#### Expansion Dashboard

- Recap views.
- Recap shares.
- Archive revisits.
- Next passport waitlist joins.
- Push/email opt-in retained after final.
- Returning user activation for new passport.

### 5.3 Funnel Metrics

#### Onboarding Funnel

1. Welcome viewed.
2. Passport created.
3. Favorite team selected.
4. Privacy preference set.
5. Starter Pack opened.
6. First daily stamp.
7. First prediction or quiz.
8. First badge unlock.

#### Prediction Funnel

1. Match prediction card viewed.
2. Prediction form opened.
3. Prediction saved.
4. Prediction locked.
5. Result settled.
6. Settlement viewed.
7. Share generated.

#### Quiz Funnel

1. Quiz card viewed.
2. Quiz started.
3. Question 1 answered.
4. Quiz completed.
5. Results viewed.
6. Explanation expanded.
7. Share generated or streak continued.

#### Collection Funnel

1. Pack earned.
2. Pack opening started.
3. Pack reveal completed.
4. Album viewed.
5. Missing item viewed.
6. Crafting used.
7. Set completed.

### 5.4 Event Taxonomy

Product analytics events should include:

| Event | Key Properties |
| --- | --- |
| passport_created | account_type, locale, source |
| onboarding_step_completed | step_name |
| favorite_team_selected | team_id |
| privacy_setting_changed | setting_name, value |
| daily_stamp_claimed | date, tournament_phase, streak_count |
| match_viewed | match_id, phase, team_ids |
| prediction_submitted | match_id, phase, before_lock_seconds, fields_completed |
| prediction_locked | match_id |
| prediction_settled_viewed | match_id, points_awarded, exact_score, giant_killing |
| giant_killing_declared | match_id, eligibility_rule |
| quiz_started | quiz_date, locale |
| quiz_completed | quiz_date, correct_count, perfect |
| quiz_question_answered | question_id, correct, difficulty |
| pack_earned | pack_type, source |
| pack_opened | pack_type, item_count, duplicate_count |
| collectible_acquired | item_id, rarity, new_or_duplicate, source |
| item_crafted | item_id, rarity, cost |
| badge_unlocked | badge_id, category, tier |
| challenge_completed | challenge_id, challenge_type |
| leaderboard_viewed | leaderboard_type, filter |
| share_card_generated | moment_type, source_id |
| share_completed | channel_type, moment_type |
| notification_sent | category, trigger |
| notification_opened | category, trigger |
| recap_viewed | recap_state |
| next_passport_interest | competition_type |

### 5.5 Segmentation

Important segments:

- New vs returning.
- Guest vs registered.
- Favorite team still active vs eliminated.
- Casual users: 1–2 actions/day.
- Competitors: high prediction participation.
- Collectors: high album views/pack opens.
- Trivia users: high quiz completion.
- Social users: share/invite activity.
- Region/country where legally and ethically appropriate.
- Matchday vs rest day active users.

### 5.6 Health Thresholds

Suggested watch thresholds:

| Metric | Concern Signal |
| --- | --- |
| Prediction submission errors | Spike within 30 minutes before lock |
| Quiz completion rate | Drops below 60% of starts |
| Pack open failure rate | Any sustained failure above normal error budget |
| Duplicate rate | High duplicates before 50% album completion |
| Support disputes | Spike after settlement |
| Notification opt-out | Sharp increase after campaign |
| Favorite elimination retention | Large drop among eliminated team fans |
| Leaderboard anomaly flags | Concentrated in top ranks |

## 6. Experimentation Plan

Experiments should not alter competitive fairness mid-stream unless carefully isolated.

### 6.1 Safe Experiment Areas

- Onboarding copy.
- Home module ordering outside prediction deadline urgency.
- Share-card design.
- Notification timing within user preferences.
- Rest-day mission framing.
- Collection album hints.
- Quiz intro copy.

### 6.2 Risky Experiment Areas

Avoid or heavily control tests on:

- Prediction scoring.
- Quiz scoring.
- Leaderboard tie-breakers.
- Pack odds after users have started collecting.
- Badge criteria for active badges.
- Privacy defaults.
- Prediction lock times.

### 6.3 Example Experiments

| Hypothesis | Variant | Success Metric |
| --- | --- | --- |
| A shorter onboarding increases activation | Skip country/region until later | First action completion |
| Prediction urgency card improves submissions | Deadline countdown on Home | Predictions per open match |
| Explanations improve quiz retention | Expanded explanation by default | Next-day quiz return |
| Collection hints reduce frustration | Show best next pack source | Album revisit and pack earning |
| Recap preview increases final return | Show progress-to-recap card | Final week retention |

## 7. Fair Play and Trust Operations

### 7.1 Score Event Audit

Every score-affecting action should be auditable:

- Source action.
- User.
- Timestamp.
- Rule version.
- Award amount.
- Admin actor if manual.
- Correction reference if changed.

### 7.2 Prediction Integrity

Controls:

- Server-side lock enforcement.
- Trusted match status.
- Submission timestamp.
- Rejection after lock.
- Idempotent settlement.
- Correction workflow.
- Clear help content.

Common support explanations:

- “Scoreline predictions are settled on regulation plus stoppage time unless stated otherwise.”
- “Knockout advancement is scored separately from 90-minute result.”
- “Your prediction was submitted after lock and could not be accepted.”
- “This match was voided; no users received result points.”

### 7.3 Quiz Integrity

Controls:

- One scored attempt per daily quiz.
- Question randomization only if it does not create unfair difficulty variance.
- Retired questions for practice.
- Invalid question correction.
- Unusual perfect-score pattern detection.

Correction options for invalid question:

| Scenario | Recommended Correction |
| --- | --- |
| Correct answer wrong in system | Award credit to users who chose actual correct answer; optionally credit all |
| Ambiguous question | Credit all users for that question |
| Question published with spoiler/error | Remove from scoring and normalize points |
| Localization mistranslation | Correct affected locale attempts only |

### 7.4 Collection Integrity

Controls:

- Pack award idempotency.
- Pack reveal cannot double-award.
- Duplicate conversion logged.
- Crafting irreversible and logged.
- Pack rule version recorded.
- Paid mechanics, if future, excluded from leaderboard advantage.

### 7.5 Leaderboard Moderation

Flag criteria:

- Impossible score totals.
- Duplicate scoring events.
- Excessive events from same source.
- Suspicious account clusters.
- Admin-granted points without reason.
- Prediction submissions at or after lock.
- Quiz attempts exceeding limit.

Review process:

1. Flag generated.
2. Account hidden from public leaderboard if severe.
3. Operator reviews score events.
4. Invalid events reversed or account restored.
5. Audit log records action.
6. User notified if material and appropriate.
7. Aggregate metrics updated.

### 7.6 Correction Window

After final:

- 72-hour provisional window.
- Resolve data errors.
- Resolve top leaderboard abuse flags.
- Publish final archive.
- Preserve correction audit internally.
- Avoid open-ended rank instability.

## 8. Support and Help Operations

### 8.1 Help Topics Required at Launch

- How to earn Passport Points.
- Difference between XP and Passport Points.
- Prediction lock rules.
- Scoreline and knockout settlement.
- Giant killing eligibility.
- Daily quiz attempt rules.
- Collection packs and duplicates.
- Badge progress.
- Leaderboard privacy.
- Score corrections.
- Account upgrade.
- Data deletion/export.
- Rights/asset explanation if neutral visuals are used.

### 8.2 Support Macros

#### Prediction Locked

“Predictions lock before kickoff using the official match time in Fan Passport. Once locked, picks cannot be changed so every fan competes under the same rule.”

#### Score Correction

“We corrected the result or rule application for this match. Your passport now shows the updated points and the adjustment in your prediction history.”

#### Quiz Question Issue

“We reviewed today’s question and found an issue. A correction has been applied to affected quiz attempts, and your score now reflects the updated decision.”

#### Collection Duplicate

“Duplicates become Craft Tokens. You can use them toward eligible missing items, helping you complete your album over time.”

#### Private Leaderboard

“Private users can play normally but are hidden from public leaderboards. You can change this in Privacy Settings.”

## 9. Post-World Cup Product Transition

### 9.1 Transition Goals

After the World Cup, Fan Passport should:

- Preserve the World Cup journey.
- Celebrate completion and final rank.
- Convert tournament users into long-term football fans.
- Launch or preview next competition passports.
- Reuse systems without making future products feel generic.

### 9.2 Passport Hub

The Passport Hub is the long-term container for multiple competition passports.

Hub functions:

- Show active passport.
- Show archived passports.
- Show upcoming passports.
- Display global fan identity.
- Display cross-passport cosmetics and legacy badges.
- Let users manage privacy across passports.
- Let users opt into new season notifications.

Passport types:

| Passport | State |
| --- | --- |
| World Cup 2026 | Archived after final |
| Premier League Passport | Seasonal active/passive depending on launch |
| Champions League Passport | Seasonal active/passive depending on launch |
| Future World Cup | Future tournament |
| Club/International Special Events | Future scope |

### 9.3 Data Continuity

Carry forward:

- Account.
- Display name/avatar.
- Privacy settings.
- Global XP/cosmetics if implemented.
- Legacy badges.
- Share-card identity.
- Friend graph/invite relationships where appropriate.
- Notification preferences.

Reset per passport:

- Competition Passport Points.
- Competition-specific leaderboards.
- Season-specific predictions.
- Season-specific quizzes.
- Season-specific collections.
- Season-specific badges and challenges.

Archive per passport:

- Stamps.
- Predictions.
- Quiz history.
- Collections.
- Badges.
- Leaderboard final rank.
- Recaps.

### 9.4 Cross-Passport Fairness

- A legendary World Cup user should have prestige in profile but not start Premier League leaderboard ahead.
- Paid or legacy cosmetics must not affect competition scoring.
- Cross-passport rewards should be cosmetic, commemorative, or access-oriented, not competitive score boosts.

## 10. Premier League Passport Expansion

### 10.1 Product Positioning

Premier League Passport turns a club season into a week-by-week fan journey. It should emphasize club loyalty, matchweeks, stadiums, derbies, form swings, and season-long achievements.

### 10.2 Key Differences from World Cup

| World Cup Passport | Premier League Passport |
| --- | --- |
| Short, intense tournament | Long seasonal rhythm |
| National teams | Clubs |
| Groups/knockouts | League table and cups/derbies |
| Daily tournament habit | Matchweek habit plus midweek content |
| Tournament recap | Season recap |
| Giant killings by rank/seed | Upsets by table position/form |
| Stadium collection finite | Grounds, away days, club histories |

### 10.3 Premier League Core Loop

1. Monday–Thursday:
   - Recap previous matchweek.
   - Trivia and club history.
   - Collection progress.
   - Matchweek predictions open.
2. Friday:
   - Prediction reminders.
   - Matchweek challenge.
3. Weekend:
   - Match stamps.
   - Live matchday activity.
   - Result settlement.
4. Sunday/Monday:
   - Leaderboard movement.
   - Team-of-the-week style badges if rights allow neutral alternative.
   - Weekly recap.

### 10.4 Premier League Collections

Categories:

- Clubs.
- Stadiums.
- Matchweeks.
- Derbies.
- Historic moments.
- Season milestones.
- Away-day stamps.
- Table position milestones.

Examples:

| Collection Set | Criteria |
| --- | --- |
| All Clubs | Collect all club items |
| Grounds Tour | Collect all stadiums |
| Derby Days | Stamp/predict named derby matches |
| Matchweek Complete | Predict/stamp every match in one matchweek |
| Loyal Season | Stamp/predict every match for favorite club |
| Top Six Tracker | Complete collections for selected high-profile clubs where rights-safe |

### 10.5 Premier League Badges

Examples:

| Badge | Criteria |
| --- | --- |
| Season Ticket Digital | Start Premier League Passport |
| Matchweek Regular | Complete actions in five matchweeks |
| Derby Day Witness | Stamp a derby match |
| Away Grounds Collector | Collect ten stadiums |
| Boxing Day Passport | Complete Boxing Day challenge |
| Run-In Ready | Active during final five matchweeks |
| Final Table Prophet | Correctly predict champion or top-four style outcome if offered |
| Loyal Club Journey | Complete favorite club season path |

### 10.6 Premier League Prediction Mechanics

Prediction types:

- Match outcome.
- Exact score.
- Table movement pick.
- Derby pick.
- Upset pick based on table gap/form.
- Season predictions:
  - Champion.
  - Top four/five depending qualification rules.
  - Relegation zone.
  - Golden boot/player awards only if rights and content strategy support it.

Rules:

- Weekly leaderboard resets can coexist with season leaderboard.
- Late joiners need matchweek leaderboards.
- Avoid official fantasy scoring unless a licensed integration exists.

### 10.7 Premier League Daily Return

Because the season is long, avoid requiring daily activity forever.

Recommended cadence:

- Daily trivia optional.
- Matchweek streak primary.
- Club journey weekly progress.
- Special holiday fixtures.
- Transfer-window quizzes and collections.
- Monthly badges.

### 10.8 Premier League Live-Ops Calendar

- Preseason: choose club, season predictions, starter pack.
- Matchweeks 1–5: onboarding and habit-building.
- Derbies/holiday periods: special challenges.
- January: transfer-window trivia and midseason recap.
- Run-in: table prediction challenges.
- Final day: season recap and archived final table passport.

## 11. Champions League Passport Expansion

### 11.1 Product Positioning

Champions League Passport turns European nights into a continental journey. It should emphasize elite match nights, travel, stadiums, league phase/group structure depending format, knockout drama, anthemic rituals, and underdog stories.

### 11.2 Key Differences from World Cup

| World Cup Passport | Champions League Passport |
| --- | --- |
| National team tournament | Club continental competition |
| One summer event | Season-long midweek event |
| Groups/knockouts | League phase plus knockouts depending format |
| Daily habit | Matchnight habit |
| Host stadium set | European stadium/travel map |
| Nation loyalty | Club loyalty plus neutral glamour matches |

### 11.3 Champions League Core Loop

1. Before matchweek:
   - Predict matchnight results.
   - Complete club/stadium trivia.
   - Choose spotlight match.
2. Matchnight:
   - Stamp matches.
   - Follow favorite club.
   - Predict late drama or upset if offered.
3. After matchnight:
   - Settlement.
   - Collection packs.
   - Leaderboard updates.
4. Knockouts:
   - Bracket predictions.
   - Two-leg aggregate mechanics.
   - Final venue journey.

### 11.4 Champions League Collections

Categories:

- Clubs.
- Stadiums.
- Countries/cities.
- Matchnights.
- Knockout ties.
- Final venue.
- Historic European nights.
- Upset moments.

Examples:

| Collection Set | Criteria |
| --- | --- |
| League Phase Explorer | Stamp/predict across all matchweeks |
| European Grounds | Collect stadiums/cities |
| Favorite Club Europe Run | Follow every favorite club match |
| Knockout Nights | Stamp each knockout round |
| Final Night | Stamp final and complete final quiz |
| Giant Slayers | Collect upset moment items |

### 11.5 Champions League Badges

Examples:

| Badge | Criteria |
| --- | --- |
| European Passport Issued | Start Champions League Passport |
| Tuesday Night Regular | Complete Tuesday matchnight actions |
| Wednesday Night Regular | Complete Wednesday matchnight actions |
| Away Day Dreamer | Collect stadiums from five countries |
| Knockout Anthem | Predict/stamp every Round of 16 tie |
| Aggregate Expert | Correctly predict a two-leg tie winner |
| Final Night Witness | Stamp the final |
| European Champion Caller | Correctly predict champion before knockout phase |

### 11.6 Champions League Prediction Mechanics

Additional mechanics:

- Two-leg tie winner.
- Aggregate score prediction as optional advanced mechanic.
- Extra time/penalty advancement.
- League phase table position bands.
- Upset prediction based on coefficient/table position/form.

Rules:

- Be explicit whether match score means single leg only.
- For two-leg ties, separate “match result” and “tie advances.”
- Prediction lock remains before kickoff for each leg.
- Tie prediction locks before first leg unless product offers second-leg-specific predictions.

### 11.7 Champions League Daily Return

Recommended cadence:

- Matchnight-first, not daily-pressure-first.
- Daily trivia on matchweeks.
- Rest-week content:
  - Club history.
  - Stadium collection.
  - Knockout bracket prep.
  - Classic moments quiz.
- Streaks should be matchweek or matchnight based to avoid fatigue.

## 12. Reusable Passport Platform Principles

### 12.1 Competition Template

Each passport should define:

- Competition ID.
- Season/tournament dates.
- Participants.
- Phases.
- Fixtures.
- Venues.
- Prediction types.
- Collection categories.
- Badge taxonomy.
- Challenge calendar.
- Leaderboard types.
- Archive rules.

### 12.2 Shared Systems

Reuse:

- Account.
- Profile.
- Privacy.
- XP framework.
- Passport Points concept.
- Prediction engine.
- Quiz engine.
- Collection engine.
- Badge/challenge engine.
- Leaderboards.
- Share cards.
- Admin tools.
- Analytics events.
- Archive/recap system.

Customize:

- Scoring weights.
- Badge criteria.
- Collection sets.
- Calendar cadence.
- Prediction types.
- Visual theme.
- Live-ops schedule.
- Terminology by competition.

### 12.3 Passport Lifecycle

Each passport goes through:

1. Draft.
2. Preview.
3. Active pre-event.
4. Active live.
5. Provisional final.
6. Archived.
7. Legacy/display.

### 12.4 Global Fan Identity

Global profile can show:

- Active passport.
- Archived passport covers.
- Legacy badges.
- Favorite clubs/teams.
- Global XP or reputation.
- Shareable football journey.

Global profile should not:

- Merge competition leaderboards unfairly.
- Expose private passport details.
- Require users to participate in every competition.
- Make missed seasons feel like permanent failure.

## 13. Expansion Roadmap

### Phase 1 — World Cup Archive and Waitlist

Timing: Immediately post-final.

Features:

- Final recap.
- Archived passport.
- Final leaderboard.
- Share final journey.
- Waitlist or preview for next passport.

### Phase 2 — Passport Hub

Timing: Post-tournament product update.

Features:

- Multiple passport navigation.
- Global profile.
- Archived World Cup access.
- Next competition preview.
- Notification opt-in.

### Phase 3 — Premier League Pilot

Timing: Next feasible domestic season window.

Features:

- Club selection.
- Matchweek predictions.
- Club/stadium collections.
- Matchweek badges.
- Weekly leaderboards.
- Season recap.

### Phase 4 — Champions League Pilot

Timing: Next Champions League season phase.

Features:

- Club selection.
- Matchnight predictions.
- League phase/knockout journeys.
- European stadium collections.
- Two-leg tie predictions.
- Final night recap.

### Phase 5 — Football Rewards Ecosystem

Timing: After core passports prove retention.

Potential features:

- Sponsor challenges.
- Partner rewards.
- Club/community groups.
- Limited safe trading.
- Real-world attendance verification with consent.
- Merchandise discounts.
- Ticketing partnerships.
- Loyalty integrations.

Guardrails:

- No pay-to-win.
- Clear reward terms.
- Privacy-first partner integrations.
- Age-appropriate experiences.
- Transparent sponsored content labeling.

## 14. Monetization and Rewards Principles

The milestone does not require monetization design, but future commercial layers should follow these rules:

Allowed future options:

- Cosmetic passport covers.
- Sponsored non-competitive challenges.
- Partner discounts.
- Premium recap designs.
- Physical merchandise tied to completed memories.
- Optional subscription for advanced stats if not competitive advantage.

Avoid:

- Selling Passport Points.
- Selling correct-answer hints for scored quizzes.
- Selling prediction boosts.
- Selling exclusive leaderboard-advantage collectibles.
- Gambling partnerships inside youth-accessible core flows.
- Obscured loot-box economics.

If paid packs are introduced:

- Publish odds where required.
- Keep collection completion possible through earnable paths.
- Separate paid cosmetics from competitive scoring.
- Comply with jurisdictional rules.

## 15. Operational Incident Playbooks

### 15.1 Prediction Lock Failure

Symptoms:

- Users submit after lock.
- Lock time wrong.
- UI/API mismatch.

Response:

1. Freeze affected prediction market if necessary.
2. Identify submissions after intended lock.
3. Decide whether to void late submissions or entire market based on fairness.
4. Communicate clearly to affected users.
5. Correct score events.
6. Update audit log.
7. Add monitoring to prevent recurrence.

### 15.2 Incorrect Match Result

Symptoms:

- Wrong score entered.
- Wrong advancement winner.
- Settlement ran on bad data.

Response:

1. Mark result under review.
2. Pause further settlement if possible.
3. Correct result.
4. Rerun settlement idempotently.
5. Generate adjustment events.
6. Notify affected users if material.
7. Record admin reason.

### 15.3 Quiz Error

Symptoms:

- Wrong correct answer.
- Ambiguous question.
- Translation issue.
- Duplicate question problem.

Response:

1. Retire or invalidate question.
2. Decide correction approach.
3. Recalculate affected attempts.
4. Update quiz results page.
5. Notify users if material.
6. Add editorial note to prevent recurrence.

### 15.4 Pack Award Failure

Symptoms:

- Pack not awarded after completed action.
- Pack opens but items missing.
- Duplicate rewards.

Response:

1. Check reward event logs.
2. Reconcile user inventory.
3. Restore missing pack/items.
4. Reverse duplicate awards only if necessary and explain.
5. Patch idempotency issue.

### 15.5 Leaderboard Abuse

Symptoms:

- Impossible top score.
- Bot-like account cluster.
- User reports cheating.

Response:

1. Hide severe suspect entries pending review.
2. Inspect score events and account signals.
3. Recalculate or restore.
4. Apply ban if necessary.
5. Communicate final leaderboard correction if public ranks change.

## 16. Final Competent-Handoff Summary

A team moving from this milestone into design or implementation should treat the following as locked for MVP unless explicitly changed by a later decision record:

- Fan Passport’s primary loop is daily stamp, prediction, quiz, collection, badge progress, leaderboard comparison, and sharing.
- XP and Passport Points are separate systems.
- Prediction lock defaults to 5 minutes before kickoff and must be enforced server-side in implementation.
- One daily quiz attempt is scored.
- Collections are earnable and duplicates convert into Craft Tokens.
- Badges use categories and tiers with visible progress for most achievements.
- Leaderboards are privacy-aware and use deterministic tie-breakers.
- Share cards are privacy-safe previews.
- Admin tools are required for fixtures, results, trivia, challenges, badges, collections, settlement, and moderation.
- The World Cup passport becomes an archive and the platform expands through Passport Hub into Premier League and Champions League passports.