# Fan Passport Growth, Live Operations, and Future Expansion Plan

This package delivers the operating plan for keeping Fan Passport active every day during the 2026 World Cup window and for evolving the product into Premier League Passport, Champions League Passport, and a broader football fan rewards ecosystem.

The plan is designed to work with the existing Fan Passport MVP, content model, challenge catalog, gamification engine, and frontend prototype delivered in prior milestones. It does not require new third-party dependencies. It provides the process, schedules, policies, analytics taxonomy, retention model, commercial strategy, and expansion roadmap needed for a competent team to operate the product in public.

## Deliverables in this package

| File | Purpose |
| --- | --- |
| `docs/growth-live-ops/live-ops-calendar.md` | Full live-ops calendar from pre-tournament build-up through post-final retention and season transition. |
| `data/live-ops/daily_challenge_schedule_2026.csv` | Day-by-day World Cup 2026 challenge, quiz, collection, prediction, reward, and sharing schedule. |
| `docs/growth-live-ops/content-refresh-process.md` | Editorial workflow, content states, QA gates, reactive content process, review ownership, and rollback procedure. |
| `docs/growth-live-ops/notifications-sharing-viral-loops.md` | Notification strategy, sharing formats, frequency rules, segmentation, viral loops, and campaign testing plan. |
| `data/live-ops/notification_playbook.csv` | CRM-ready notification trigger matrix with copy templates, segments, deep links, and success metrics. |
| `docs/growth-live-ops/sponsors-rewards-monetization.md` | Sponsor packages, reward concepts, redemption operations, monetization options, compliance guardrails, and measurement. |
| `data/live-ops/sponsor_reward_concepts.csv` | Structured sponsor and reward concepts mapped to fan value, sponsor value, controls, and analytics events. |
| `docs/growth-live-ops/moderation-trust-safety.md` | Community policy, leaderboard integrity, anti-fraud, moderation enforcement, appeals, and incident handling. |
| `docs/growth-live-ops/analytics-retention.md` | North-star metric, funnel, retention KPIs, dashboards, cohort logic, experiments, alerts, and privacy guidance. |
| `data/analytics/events.json` | Machine-readable analytics event taxonomy for product, growth, content, reward, and safety instrumentation. |
| `docs/growth-live-ops/live-ops-runbooks.md` | Daily operations, matchday, upset, outage, notification, fraud, reward, and final-day runbooks. |
| `docs/growth-live-ops/future-expansion-roadmap.md` | Modular roadmap for Premier League Passport, Champions League Passport, and the fan rewards ecosystem. |
| `examples/live-ops/opening-day-daily-brief.md` | Completed example of the daily brief operators should publish internally before a major live-ops day. |

## Operating thesis

Fan Passport should give supporters a small but emotionally meaningful reason to return every day:

1. **A daily ritual:** claim a stamp, answer trivia, make or review a prediction, and see what changed.
2. **Fixture-reactive content:** the passport feels alive because challenges respond to actual match outcomes, upsets, goals, stadiums, and knockout stakes.
3. **Collectible progress:** users build visible collections of teams, groups, stadiums, badges, stickers, and memories.
4. **Social comparison:** fans compare streaks, squads, countries supported, prediction accuracy, and rare achievements.
5. **Rewarded fandom:** sponsors and partners fund rewards that feel additive without making the game pay-to-win.
6. **Season continuity:** the account, collection history, identity, and reward status persist after the World Cup into club and continental competitions.

## Core daily loops

### 1. Daily Passport Loop

1. User opens Fan Passport.
2. User claims the daily stamp.
3. User answers the daily trivia question.
4. User completes one challenge or progresses a collection.
5. User sees a fresh badge, XP, leaderboard movement, or reward unlock.
6. User shares a card or invites a squad member.
7. User receives a next-day reason to return.

### 2. Matchday Loop

1. User follows one or more teams.
2. User receives a pre-match challenge or prediction prompt.
3. User checks in during the match window.
4. User collects match, team, stadium, or moment stickers.
5. Final whistle resolves predictions and achievements.
6. User shares the result card and sees squad leaderboard impact.

### 3. Collection Loop

1. User receives a daily sticker pack or content drop.
2. User fills groups, stadiums, team pages, and special moment pages.
3. Duplicate stickers become trade, gift, or squad-completion opportunities.
4. Completing a set unlocks badges, XP, cosmetic passport pages, or sponsor rewards.
5. Late-stage rest days become collection catch-up days.

### 4. Social Growth Loop

1. User earns a visible badge, prediction streak, or rare unlock.
2. User generates a share card with an invite link.
3. New user joins through the card, selects a team, and completes onboarding.
4. Referrer and referred user earn a cooperative reward after the new user completes a meaningful passport action.
5. Both are nudged into a squad or mini-league.

### 5. Reward Loop

1. User completes fair, skill-or-engagement-based challenges.
2. Reward eligibility is checked server-side.
3. User receives a digital collectible, coupon, sweepstake entry, or experience unlock.
4. Redemption is fulfilled with clear terms and support handling.
5. Sponsor value is measured through event attribution without selling raw personal data.

## Operating model

Fan Passport should be run as a live digital event, not as a static app. The recommended live-ops cell is small but cross-functional:

| Role | Primary responsibilities |
| --- | --- |
| Live Ops Lead | Owns calendar, daily decisions, go/no-go calls, incident coordination, and stakeholder updates. |
| Content Lead | Owns editorial voice, daily themes, quiz quality, collection drops, and post-match memory cards. |
| Football Data Editor | Verifies fixtures, teams, stadiums, scores, standings, trivia facts, and challenge eligibility. |
| Growth/CRM Manager | Owns notifications, segmentation, deep links, referral loops, share copy, and experiment plan. |
| Community and Moderation Lead | Owns reports, enforcement, leaderboards, abuse trends, appeals, and safety escalations. |
| Partnerships Manager | Owns sponsor inventory, reward budgets, campaign approvals, terms, and fulfilment readiness. |
| Analytics Lead | Owns event QA, dashboards, retention readouts, cohort analysis, and experiment decisions. |
| Support Lead | Owns fan-facing help macros, reward support, account issues, and public incident messaging. |
| Engineering On-call | Owns content publishing support, feed outages, notification kill switches, fraud controls, and rollback. |
| Legal/Compliance Reviewer | Reviews sweepstakes, sponsor claims, IP usage, privacy, age restrictions, and regulated categories. |

For a lean launch, one person can cover multiple non-conflicting responsibilities, but the accountabilities above should remain explicit.

## Live cadence

| Cadence | Meeting or output | Purpose |
| --- | --- | --- |
| Weekly pre-tournament | Calendar lock meeting | Approve next four weeks of campaigns, rewards, experiments, and dependencies. |
| Daily during tournament | Morning live-ops standup | Review fixtures, risks, overnight metrics, content readiness, notification plan, and moderation alerts. |
| Matchday during tournament | Fixture readiness check | Confirm challenge activation, prediction locks, data feed health, sponsor placements, and support coverage. |
| After each match block | Results and content review | Resolve predictions, publish memory content, unlock badges, and check leaderboard anomalies. |
| Daily close | Performance note | Record DAU, meaningful passport days, challenge completion, share rate, issues, and next-day changes. |
| Weekly post-tournament | Retention bridge review | Move fans into Premier League, Champions League, or rewards ecosystem loops. |

## Launch and daily readiness gates

The product should not publish a live-ops day until all of these gates are true:

- The day exists in `data/live-ops/daily_challenge_schedule_2026.csv`.
- The current fixture feed has been reconciled with the schedule engine.
- Daily challenge, trivia, collection drop, prediction prompt, and reward logic are configured.
- Notification copy and segmentation are approved in `data/live-ops/notification_playbook.csv`.
- Sponsor placements and reward terms have legal approval where applicable.
- Moderation coverage and escalation contacts are active for the highest-risk match windows.
- Analytics events listed in `data/analytics/events.json` are firing for the primary path.
- Support has fan-facing wording for known risks, reward rules, and account recovery.
- Engineering can pause notifications, disable a challenge, freeze a leaderboard, and rollback content without an app release.

## Key product outcomes

The World Cup campaign should optimize for these outcomes:

1. **Daily active ritual:** users complete at least one meaningful passport action per active day.
2. **Tournament-long identity:** users feel their passport is a personal record of the tournament.
3. **Collection completion pressure:** users return because sets are incomplete and new drops keep arriving.
4. **Social proof and sharing:** achievements are visible and invite-worthy.
5. **Fair competition:** leaderboards are trusted because rules, fraud controls, and moderation are visible.
6. **Reward credibility:** sponsors improve the experience without undermining gameplay.
7. **Post-tournament bridge:** the World Cup passport becomes the first chapter in a longer football fandom account.

## Dependency and build hygiene note

This milestone introduces documentation, CSV schedules, example operating materials, and a JSON analytics taxonomy only. It does not add runtime code, package manifests, lockfiles, SDK integrations, or third-party API calls. If the existing application imports these CSV or JSON files later, maintainers should map them through the existing content ingestion and analytics tooling already present in the project.