A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 6

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 7

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 8

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 9

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 10

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: 8192

Message: Return type of CI_Session_null_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice

Filename: drivers/Session_null_driver.php

Line Number: 11

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 284

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 291

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 306

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 316

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 317

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 318

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 319

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: ini_set(): Session ini settings cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 377

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent

Filename: Session/Session.php

Line Number: 110

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

A PHP Error was encountered

Severity: Warning

Message: session_start(): Session cannot be started after headers have already been sent

Filename: Session/Session.php

Line Number: 143

Backtrace:

File: /home/ipsit/public_html/application/controllers/Articles.php
Line: 31
Function: __construct

File: /home/ipsit/public_html/index.php
Line: 315
Function: require_once

NRIPage | Articles | BCCI Central Contracts 2025: Shreyas Iyer Likely to Return, Retainership System Explained | Get Indian Desi Latest Sports News & Updates in USA. Stay Ahead in Sports & Gaming Action - NRI Page
Edit

BCCI Central Contracts 2025: Shreyas Iyer Likely to Return, Retainership System Explained

BCCI Central Contracts 2025: Shreyas Iyer Likely to Return, Retainership System Explained

The Board of Control for Cricket in India (BCCI) is preparing to announce its annual central contracts for the senior men’s cricket team in April, with significant changes expected across various categories. Among the most talked-about developments is the anticipated return of Shreyas Iyer to the list after a notable absence last year due to multiple controversies. Iyer, who captains Punjab Kings in the IPL, had been dropped from the BCCI's central contracts in the 2023-24 cycle. However, his outstanding performances in both domestic and international circuits, particularly in the Champions Trophy 2025, have likely secured his re-entry. Iyer was instrumental in India's back-to-back ICC 50-over title win, anchoring crucial innings throughout the tournament.
 

The BCCI central contracts, known officially as the annual retainerships, are a structured system that classifies and rewards players based on their contribution to Indian cricket. The system is broken down into four categories — A+, A, B, and C — with varying levels of financial compensation and benefits provided to players. The last update featured 30 players, reflecting the depth of India’s current cricketing talent.
 

Understanding the BCCI Central Retainership Structure

The BCCI’s central contract system serves not only as a reward mechanism but also as a tool to ensure elite-level care for players representing India. Players who are centrally contracted gain access to exclusive facilities and support systems provided by the board. These include free recovery and rehabilitation services at the National Cricket Academy in Bengaluru, world-class training infrastructure at the Centre of Excellence, as well as full travel reimbursements and logistical support during international and domestic engagements.
 

In terms of financial benefits, the retainerships are tiered as follows:

  • Grade A+: ₹7 crore per annum

  • Grade A: ₹5 crore per annum

  • Grade B: ₹3 crore per annum

  • Grade C: ₹1 crore per annum

Additionally, players receive match fees based on the format they play:

  • Test Matches: ₹15 lakh per match

  • One Day Internationals (ODIs): ₹6 lakh per match

  • Twenty20 Internationals (T20Is): ₹3 lakh per match


To qualify for a central contract, a player must meet at least one of the following eligibility criteria within the evaluation period: participation in 3 Test matches, 8 ODIs, or 10 T20 Internationals. Meeting any of these thresholds makes a player eligible for inclusion in the list.
 

Current BCCI Contract Holders and Expected Changes

In the 2023-24 retainership cycle, the Grade A+ category featured four key players: Rohit Sharma, Virat Kohli, Jasprit Bumrah, and Ravindra Jadeja — all of whom are likely to be retained at the top tier due to their continued impact in all formats of the game.

The Grade A tier included prominent names such as R Ashwin, Mohammad Shami, Mohammad Siraj, KL Rahul, Shubman Gill, and Hardik Pandya. All of these players have maintained consistent performance levels and are expected to stay in their respective slots unless unforeseen developments prompt adjustments.
 

Grade B featured players like Suryakumar Yadav, Rishabh Pant, Kuldeep Yadav, Axar Patel, and Yashasvi Jaiswal. With Pant’s return to cricket following his injury and Jaiswal’s continued success at the top order, this tier may see re-evaluations based on current form.
 

The Grade C list was the most expansive, consisting of emerging talents and fringe players such as Rinku Singh, Tilak Varma, Ruturaj Gaikwad, Shardul Thakur, Shivam Dube, Ravi Bishnoi, Jitesh Sharma, and Washington Sundar, among others. Youngsters like Sarfaraz Khan, Dhruv Jurel, and Rajat Patidar were included, pointing to the selectors' intent to prepare a strong bench.
 

Now, with Shreyas Iyer’s return to form and his vital role in India’s successful international campaign, there’s growing expectation that he will be re-inducted — likely into Grade B or higher. His recent leadership in domestic leagues and his performance under pressure during global tournaments position him as a valuable asset across formats. The retainership update will also be closely watched for possible exclusions, particularly in the lower tiers, as the selectors aim to streamline the squad and focus on performance metrics. With increased competition and a steady stream of young talent entering the fray, the BCCI is expected to maintain a balance between experience and youth.
 

Apart from individual performances, factors like injury management, fitness levels, and player discipline are also believed to play a role in contract decisions. The BCCI has previously dropped players not just for form but also for disciplinary reasons or fitness concerns. As the official announcement nears, Indian cricket fans and experts are keenly awaiting the updated list, especially to see how it reflects the team's evolution over the past year. For players like Iyer, this is more than just a contract—it’s a recognition of resilience, consistency, and form. The BCCI’s annual retainership system remains a benchmark in cricket administration, rewarding merit while nurturing long-term talent. With India continuing to dominate world cricket and prepare for a packed international calendar, this year's central contracts will serve as a key indicator of the team’s strategy going forward.

What is your response?

joyful Joyful 0%
cool Cool 0%
thrilled Thrilled 0%
upset Upset 0%
unhappy Unhappy 0%
AD
AD