Cipla corrects remote e-voting end date to June 24 for AGM
Cipla Limited issued a corrigendum to correct the remote e-voting end date for its 90th AGM from July 24 to June 24, 2026. The e-voting period commences on June 21, 2026, at 9:00 a.m. IST and concludes on June 24, 2026, at 5:00 p.m. IST. All other details regarding the AGM and the Integrated Annual Report for FY 2025-26 remain unchanged.

*this image is generated using AI for illustrative purposes only.
Cipla Limited has issued a corrigendum to the notice of its 90th Annual General Meeting (AGM), correcting the end date for remote e-voting. The company clarified that the remote e-voting period will conclude on Wednesday, June 24, 2026, at 5:00 p.m. IST, rather than the previously stated July 24, 2026. The voting process is scheduled to commence on Sunday, June 21, 2026, at 9:00 a.m. IST.
The correction was filed under Regulation 30 of the SEBI (Listing Obligations and Disclosure Requirements) Regulations, 2015. All other details regarding the AGM and the Integrated Annual Report for FY 2025-26 remain unchanged. The company had previously announced a final dividend of ₹13 per equity share, subject to approval at the AGM.
Key Dates for AGM and E-Voting
| Event | Date |
|---|---|
| Remote E-Voting Start | Sunday, June 21, 2026 |
| Remote E-Voting End | Wednesday, June 24, 2026 |
| Record Date | Friday, June 5, 2026 |
| AGM Date | Thursday, June 25, 2026 |
Shareholders are advised to take note of the revised timeline to ensure their participation in the e-voting process.
Historical Stock Returns for Cipla
| 1 Day | 5 Days | 1 Month | 6 Months | 1 Year | 5 Years |
|---|---|---|---|---|---|
| -0.27% | -2.28% | -5.22% | -9.81% | -9.77% | +40.68% |
How might the shortened e-voting window impact shareholder participation rates compared to previous years?
What strategic initiatives outlined in the FY 2025-26 Integrated Annual Report are likely to be the main focus of the AGM?
Will the correction of the e-voting date prompt the company to review its internal disclosure controls to prevent similar errors?

































