Easily manage cricket tournament matches and points tables using PHP and MySQL. This project is inspired by the Indian Premier League (IPL) scorecard system and aims to closely replicate its league-style format. It uses predefined teams, venues, and scheduling to showcase MySQL proficiency, especially in handling dynamic, CRUD-intensive data operations.

Admins can input critical match details such as participating teams, toss outcomes, venue, and Net Run Rate (NRR), allowing the system to generate an accurate and dynamic points table.

Additionally, the system maintains match histories for each team, offering comprehensive insights into team performance throughout the tournament.

• Only Super Admin is authenticated to register new admins.
• User authentication ensures secure access to the system.

• Admin users have special access rights, including:
  • Creating new matches
  • Deleting existing matches if necessary

• Allows users to reset their forgotten passwords using PHPMailer.
• Users receive an email with a unique reset link (valid for 15 minutes).
• Dynamic email content greets users by their registered name.

• Strike Rate Calculator – Calculates a batsman's strike rate based on runs scored and balls faced.
• Duckworth Lewis Calculator – The DLS Calculator is a work-in-progress and may not provide accurate results due to the lack of sufficient real-world data and scenarios. (under development).
• Reduced Overs Match Support – Admin can mark a match as "Reduced" and specify total overs per side (minimum 5, maximum 19 for T20Is as per ICC) due to weather or interruptions. System adapts ball inputs and logic accordingly.

• Developed with ~2500 lines of PHP backend code
• 50+ Git commits
• Technologies used: PHP, MySQL, HTML, CSS, JavaScript

a) Ranks teams primarily based on Points, the by Number of Wins and finally by Net Run Rate (NRR). b) Further tie-breakers like Head-to-Head results are not currently implemented. c) Calculates NRR based on: overs and balls played, wickets lost, runs scored and conceded, with special handling for teams that are all out or affected by reduced overs.
d) Updates scorecard including matches played, toss and decisions, venues, wins, losses, tied matches, points, and NRR.

• Abandoned Matches

  • If a match is abandoned (e.g., due to rain), both teams are awarded 1 point each, ensuring the match is treated as "No Result."
  • Two sub-scenarios are handled:
    • Abandoned Before Toss: Match abandoned without a toss. Example: Match 58 (RCB vs KKR)
    • Abandoned After Toss: Toss has occurred, but no play was possible.
      Examples: Match 44 (KKR vs PBKS), Match 55 (SRH vs DC)
  • Validation:
    ➔ Toss-related fields (i.e., Toss Won By and Decision) are disabled when Toss Status is set to "Match Abandoned Without Toss", ensuring the UI aligns with real-world logic and avoids unnecessary or misleading inputs. ➔ All score input fields are disabled when a match is marked as abandoned, preventing accidental data entry.

• Tied Matches

  • When both teams have equal scores at the end of their innings, a Super Over is triggered to determine the winner.
  • Example:
    ➔ Match No. 32 (DC vs RR) followed this scenario and was resolved via Super Over.
  • Validation:
    ➔ When scores are tied, an additional hidden field (Super Over Winner selection) becomes visible and must be selected before submission.

• Reduced Overs For Both Teams

  • Matches affected by weather or other interruptions are recorded with a reduced number of overs for both teams and recalculated accordingly.
  • Example:
    ➔ Match No. 34 (RCB vs PBKS) was played under reduced overs conditions for both teams.
  • Validation:
    ➔ Users are allowed to enter overs between 5 and 19 only.
    ➔ Values below 5 or above 19 overs are not permitted, as per ICC standards that a minimum of a 5-overs match must be completed by both teams to get a valid result.

• Second Innings Reduced Matches (DLS Method)

  • In some weather-affected matches, only the second innings is shortened. The DLS (Duckworth-Lewis-Stern) method is applied to set a revised target.
  • The team batting second must chase this revised target within the reduced overs.
    • Example: ➔ In Match 56 (MI vs GT), only the second innings was reduced, and the DLS method was used for par score calculation.
  • Validation: ➔ The user must enter the revised overs and revised target when this condition is selected. ➔ Input fields for revised values are enabled only in this scenario. ➔ If scores are tied at the revised target, the Super Over option must still be selected.

• Overs played = overs played + (balls played / 6)
• For = number of runs scored / number of overs played
• Against = number of runs conceded / number of overs bowled
• Net Run Rate = For - Against

a) Zero Runs: If a team scores 0 runs, overs are set to the reduced total overs (or 20 overs) and balls to 0.
b) All Wickets Lost: If all 10 wickets fall, overs are set to the reduced total overs (or 20 overs) and balls to 0.
c) Inning 1 Specific: If the first batting team doesn’t complete the reduced overs (or 20 overs) and doesn’t lose all wickets, overs are set to the reduced total overs (or 20 overs) and balls to 0.
d) Inning 2 Specific (Lost Without All Out): If the second batting team scores fewer than the first team without losing all wickets, overs are set to the reduced total overs (or 20 overs) and balls to 0.
e) Inning 2 Specific (Won Without Facing Legal Delivery): If the second team wins without facing a legal delivery (e.g., due to extras like wides or no-balls), overs are considered 0 and balls as 1 to avoid a division by zero error. This rare edge case is especially critical if it occurs in the very first match of the tournament, where no previous data exists to compute average NRR. f) General Case: All other scenarios use the actual overs and balls faced/bowled, based on either the full or reduced overs, to calculate NRR.

⚠️ Note: Editing existing match data is currently disabled. To make any changes, the existing match needs to be deleted and re-added with the correct details.

This project simulates the IPL 2025 season using real match data, with predefined teams, venues, and a schedule.

All 70 group stage matches have now been completed and recorded in the system.

Live updates are reflected on the deployed project here, with match data and points table updated in real-time.

The README is now updated with a final screenshot of the complete points table and summary of key statistics from the season.

All calculations, including team rankings, Net Run Rate (NRR) up to 3 decimal places, and tie-breaking logic (based on points, wins, and NRR), have been thoroughly implemented and validated.

The points table generated by this system matches the official IPL 2025 standings exactly, ensuring complete accuracy and consistency.

All CRUD operations and match updates are functioning seamlessly, with real-time reflections on the live deployment.

• Qualification Predictor (Q): Automatically mark teams as qualified based on current points, remaining matches, and whether other teams can mathematically catch up. This feature would simulate all remaining scenarios to confirm top-four teams.
• Improved DLS Calculator: Enhance the Duckworth-Lewis-Stern (DLS) calculator by incorporating official tables and historical match data to offer more accurate par scores.
• Mobile Responsiveness & UI Polish: Refine front-end experience, particularly for smaller devices.
• Post-League Phase Extension: Extend the system beyond league-stage matches to include Qualifier 1, Eliminator, Qualifier 2, and the Final, capturing the full tournament journey.
• Recent Match Form Indicator: Display each team’s last five match results (e.g., W, L, NR) in the points table to reflect recent form and momentum.
• Match Score Summary in Points Table: Show concise match summaries (e.g., KKR 131/10 vs RCB 49/10) alongside existing toss and venue details in the points table for better context.

This project is primarily focused on functionality and database handling. It does not emphasize full mobile responsiveness.

The web application is hosted at: https://scorecard.siddheshmestri.in

For comparison with the real-time IPL standings, refer to the official IPL Points Table.

You can learn more about me and my other projects on my portfolio website.

Home Page : Reference - Official IPL Points Table (for design and rules inspiration): Team Match History (Modal View) : Register Page : Login Page : Admin Dashboard-1 : Admin Dashboard-2 : Add New Match : Update Match Details : Forgot Password Page : Reset Password Page : Strike Rate Calculator : DLS Par Score Calculator :