New Delhi: BRICS negotiators are close to finalising the wording of a joint statement ahead of the bloc’s upcoming leaders’ summit in New Delhi, with Sherpas expected to reach an agreement on the draft as early as tomorrow.
The negotiations have focused on resolving differences over sensitive geopolitical issues while ensuring that the final document reflects a consensus acceptable to all member countries.
A recent Sherpa meeting made significant progress, with discussions described as constructive and focused largely on refining language around a few remaining contentious issues. Negotiators are now working against a tight deadline to complete the draft before the arrival of the leaders.
Once the Sherpas agree on the text, the draft will be circulated among member countries for review and final approval. The joint statement is expected to emerge as one of the key outcomes of the summit, outlining the bloc’s shared position on major international developments and areas where members intend to strengthen cooperation.
BRICS Sherpas play a crucial role in preparing such declarations. Senior officials conduct detailed negotiations ahead of leaders’ meetings, working through politically sensitive language and attempting to bridge differences between member states.
The latest discussions have reportedly maintained a constructive atmosphere, with negotiators seeking language that represents genuine consensus rather than simply avoiding disagreements. A major challenge has been finding formulations that accommodate the differing priorities and international positions of BRICS members.
The effort assumes added significance as the expanded grouping brings together countries with diverse geopolitical interests. Reaching agreement on a common document would underline the bloc’s ability to maintain cooperation despite differences among its members.
With leaders scheduled to begin arriving in India on Friday, diplomats are now racing to complete the statement with enough time for final consultations and approval.
Sorry, there was a YouTube error.






