Cricket Projections: How It Works¶

What Are Cricket Projections?¶

Cricket projections provide predictive insights for matches, including:

Win Probability - The likelihood of each team winning
Player Projections - Expected performance stats for batsmen and bowlers
Projected Lineups - Anticipated starting XI for each team

How Data Enters the System¶

Automated Data Imports¶

Projection data is received from analytics partners who analyze historical stats, form, and conditions. This data flows in automatically:

Pre-match: Initial projections and predicted lineups
During match: Win probability updates after each delivery

Manual Lineup Editing (Content Managers)¶

Content managers can create and edit projected lineups through the Foundry UI:

Navigate to the Fixture Page
Open the Lineup Editor panel
For each team:
Select players from the available squad (up to 11)
Assign batting order positions (1-11)
Designate the Captain (C)
Designate the Wicketkeeper (WK)
Click Save to store the projected lineup

Validation Rules: - Maximum 11 players per team - Each player can only appear once - Complete lineups (11 players) must have exactly 1 captain and 1 wicketkeeper - Partial lineups are allowed for work-in-progress saves

From Projected Lineup to Live Match¶

When a projected lineup is saved, the system automatically:

Stores the projection in the Projections system
Copies it to the Scoreboard as the "actual" lineup
Marks it as a "Projected Lineup" for reference

This means you only need to enter the lineup once - it flows through to both the projections display and the live scoreboard.

Live Match Behaviour¶

What Happens When the Game Starts¶

Before Match	During Match
Lineup can be edited	Lineup becomes locked*
Projections are predictions	Win probability updates live
Squad changes possible	Actual participants tracked

*Note: Automatic locking when a match goes live is a planned feature.

Live Updates¶

During a live match: - Win probability updates ball-by-ball based on match state - The scoreboard tracks actual batting/bowling performances - Player projections remain static as reference predictions

The Complete Data Flow¶

flowchart TD
    subgraph Input["Data Sources"]
        A["Analytics Data<br/>(Automated)"]
        B["Content Manager<br/>(Manual Entry)"]
    end

    subgraph Processing["Processing"]
        C["Import System"]
        D["Lineup Editor UI"]
        E["Projections System"]
    end

    subgraph Output["Output"]
        F["Match Insights<br/>Display"]
        G["Scoreboard<br/>(Lineups)"]
    end

    A --> C
    B --> D
    C --> E
    D --> E
    E --> F
    E --> G

What Users See¶

Match Insights Page: - Live win probability graph - Top batsmen with projected runs and milestone chances - Top bowlers with projected wickets - Player of the match prediction

Fixture Page: - Home and away team lineups - Batting order positions - Captain and wicketkeeper indicators

Key Points for Content Managers¶

Save early - Projected lineups can be partial while you gather information
One entry point - Edit in the Lineup Editor; it flows everywhere
Check before match - Ensure lineups are complete with captain and WK assigned
Projections are locked - Player projections come from analytics and cannot be manually edited