Skip to content

Tipping overview

A tipping competition asks participants to predict the winner of each match in a round. Points are awarded for correct picks, and the leaderboard updates after results are confirmed.

  1. Fixtures are published: Fanzava imports the schedule from the sports data feed. Each fixture shows the two teams, venue, and scheduled start time.
  2. Participants submit tips: Before each fixture’s lock time, participants select their predicted winner. They can change picks any time before lock.
  3. Fixtures lock: Tips close at the scheduled start time of each match. Fanzava locks matches individually, so early-week games lock earlier than Saturday games.
  4. Results come in: Fanzava confirms results automatically from the data feed, usually within minutes of full time.
  5. Round is scored: Points are calculated and the leaderboard updates.

Fanzava supports live data feeds for:

Sport Competitions available
AFL AFL Men’s, AFLW
NRL NRL, State of Origin
EPL English Premier League
NFL NFL regular season and playoffs
NBA NBA regular season and playoffs
MLB MLB regular season
Cricket BBL, IPL, international
F1 Formula 1 season

Custom sports and manual fixture entry are also supported. See Custom sports and Manual fixture entry.

The default scoring is 1 point per correct tip. You can configure:

  • Weighted scoring: different games worth more points (e.g. finals worth 2×)
  • Joker tips: participants nominate one game per round as their joker, doubling its point value
  • Margin prediction: participants predict the winning margin, with bonus points for accuracy
  • Perfect round bonus: extra points for tipping every game correctly

See Scoring for full configuration options.

By default, fixtures lock individually at their scheduled start time. You can configure a hub-wide lock policy:

  • Individual lock: each fixture locks at its own start time (default)
  • Round lock: all fixtures lock when the first game of the round starts
  • Custom lock: set a specific time offset before each fixture

Was this page helpful?

Raise a ticket about this page

Comments