Five members belonging to the Non-Aligned Movement will sit on the Security Council in 2022
11 October 2021
Of the countries serving terms on the Security Council in 2022, five will be full members of the Non-Aligned Movement (NAM): Gabon, Ghana, India, Kenya and the United Arab Emirates, representing a drop of one from the 2021 Council . . .
Five members belonging to the Non-Aligned Movement will sit on the Security Council in 2022
11 October 2021
Of the countries serving terms on the Security Council in 2022, five will be full members of the Non-Aligned Movement (NAM): Gabon, Ghana, India, Kenya and the United Arab Emirates, representing a drop of one from the 2021 Council . . .
Five members belonging to the Non-Aligned Movement will sit on the Security Council in 2022
11 October 2021
Of the countries serving terms on the Security Council in 2022, five will be full members of the Non-Aligned Movement (NAM): Gabon, Ghana, India, Kenya and the United Arab Emirates, representing a drop of one from the 2021 Council . . .
Five members belonging to the Non-Aligned Movement will sit on the Security Council in 2022
11 October 2021
Of the countries serving terms on the Security Council in 2022, five will be full members of the Non-Aligned Movement (NAM): Gabon, Ghana, India, Kenya and the United Arab Emirates, representing a drop of one from the 2021 Council . . .
Five members belonging to the Non-Aligned Movement will sit on the Security Council in 2022
11 October 2021
Of the countries serving terms on the Security Council in 2022, five will be full members of the Non-Aligned Movement (NAM): Gabon, Ghana, India, Kenya and the United Arab Emirates, representing a drop of one from the 2021 Council . . .
Vetoes, insufficient votes and competing draft resolutions accentuate divisions within the Council
2 April 2022
Since 2000, and especially since 2010, there has been a marked increase in divisive votes in the Security Council,
which reflects the fact that some Council members are now less willing to shield the Council's divisions from
public view. In part, this reflects the polarizing nature of some key items more recently before the Council . . .
Last Update: 7 March 2025

UPDATE WEBSITE OF
THE PROCEDURE OF THE UN SECURITY COUNCIL, 4TH EDITION
by Loraine Sievers and Sam Daws, Oxford University Press, Oxford, 2014
Posted on 16 August 2020
Chapter 6: VOTING
Section 3: Procedural matters and the 'double veto'
Eight points on ‘preliminary question’ or ‘double veto’ in context of Iran snapback mechanism
There is presently widespread discussion on social media about the so-called ‘double veto’ and how it might impact on an attempt by the United States to initiate the snapback mechanism set out in resolution 2231 (2015) to reimpose sanctions against Iran. Because this discussion has included some misunderstandings, SCProcedure has tweeted some clarifications, which are also set out here (in expanded form):
1) It needs to be kept clear, when talking about ‘procedure’, whether the reference is to regular Security Council procedure as established by the Provisional Rules of Procedure and practice, or procedure stemming from resolution 2231 (2015). They are two very different things.
2) The informal term ‘double veto’ is a partial misnomer and creates misunderstandings. The accurate term is ‘preliminary question’.
3) ‘Preliminary’ is not chronological but legalistic. It means that in order to correctly interpret the results of a vote on a draft proposal (that is, whether a negative vote by a permanent member constitutes a veto), the ‘preliminary question’ must be settled as to whether the proposal being voted upon concerns a procedural or substantive matter.
4) In all cases of voting on resolutions since 1959, there has been implicit agreement on the ‘preliminary question’ and therefore there has been no need to resolve it explicitly.
5) However, if in the Iran snapback context it does become necessary to establish whether or not a veto will apply to a specific draft resolution, then the ‘preliminary question’ must be explicitly dealt with. By practice, this can occur before or after the vote on a draft resolution. In some past cases, Council members have wished to resolve the ‘preliminary question’ at the outset so that, depending on the results, the determination might influence their vote on the draft resolution. In other cases, members have waited to raise the ‘preliminary question’ until after a vote, because it might turn out that no permanent member casts a negative vote, in which case explicitly resolving the ‘preliminary question’ will become unnecessary.
6) It is firmly established that the ‘preliminary question’, if put to a vote, is itself a substantive question and therefore the negative vote of permanent member will constitute a veto.
7) The only case when a ‘double veto’ occurs is when a permanent member vetoes a proposal to consider a draft resolution procedural – in which case it must be considered substantive – and then on that basis proceeds to veto the draft itself.
8) The ‘preliminary question’ or ‘double veto’ never applies to a vote pursuant to Rule 9 to adopt the agenda for a meeting (absent which the meeting cannot go forward). Adoption of the agenda has, from the outset of Security Council practice, been without exception acknowledged to be a purely procedural matter.
In specific applicability to the snapback issue, this means that if a Security Council member tables a draft resolution by which the Council would decide that the United States lacks standing to initiate the snapback mechanism and presents that draft as procedural (thus not subject to veto), the United States can a) challenge the contention that the draft is procedural, b) veto a vote that would say that it is procedural, and then c) veto the draft itself. But the snapback mechanism involves a lot more.
For further background on the 'preliminary question' or 'double veto', we are making available here pages 318 to 327 of our book (copyrighted).
See also on this website the related articles:
"Will the Iran Plan of Action “snapback” provision have a wider impact on the veto?"