A text adopted by consensus does not require every delegation to agree with it. It requires only that the chair finds no objection it is prepared to recognise as blocking. When a party objects but the chair gavels the decision through regardless, the party's disagreement does not disappear from the record: it is read into the record, on the floor, as a formal explanation of position. The mechanism lets a summit close with a text and still preserve, word for word, who refused to own it.

What is an explanation of position?

An explanation of position is a short statement a delegation asks to deliver, usually immediately after a decision is adopted, setting out why it does not accept the text or why its acceptance comes with reservations. It is entered into the official record of the session, typically annexed to or noted in the meeting report, so that the delegation's disagreement survives independently of the adopted outcome. The statement does not reopen the text and does not create a legal exception for that party; the decision stands as adopted for the body as a whole. What changes is the historical record: the archive shows not just what was agreed, but who objected, and in what terms.

How does a text get adopted over an open objection?

Consensus in a UN-style process has never meant unanimity in the strict sense. It means the chair finds no delegation formally blocking, and treats silence or qualified objection as insufficient to prevent adoption. The clearest illustration from the UNFCCC process came at the 2010 climate conference in Cancún, where Bolivia stated clearly that it did not accept the Cancún Agreements. The conference president, Mexico's foreign minister Patricia Espinosa, declared the decisions adopted, said Bolivia's position had been duly reflected in the records of the conference, and stressed that consensus does not mean unanimity or the right of one delegation to veto. The gavel fell with Bolivia's objection on record rather than withdrawn.

Why doesn't the objecting party just block it?

Blocking requires either a procedural rule that gives a single delegation a veto, or enough allied delegations to prevent the chair from finding consensus at all. The UNFCCC's parties have never adopted a voting rule: the first conference, in 1995, could not agree on one and deferred the question, so decisions are taken by consensus in practice. The absence of a vote is what makes "no delegation blocks" the working test. A party that stands alone in its objection, as Bolivia did in 2010, discovers that the absence of a voting mechanism cuts both ways: it also means there is no mechanism by which one delegation can stop the 193 others Espinosa said she could not disregard. The explanation of position is the compensating instrument. It cannot stop the gavel, but it can make the objection permanent.

What goes into the written record?

The explanation is read aloud for the room and then typically captured in the meeting's report of proceedings, sometimes verbatim, sometimes summarised with the full text annexed. Observers and secretariat staff who keep daily records, the kind the Bulletin side of this site tracks, note the statement alongside the adopted text. For a journalist or researcher reconstructing a decision years later, the explanation of position is often the only trace that the room was not unanimous. Reading a declaration twenty years on, as the companion piece on this site does for an adopted text, means reading past the final wording to whatever objections were filed against it at the time.

Does an explanation of position change anything legally?

No. The decision applies to the body as a whole once adopted, regardless of any single delegation's stated disagreement; an explanation of position is not a reservation in the treaty-law sense and does not exempt the objecting party from the decision's effect within the process. Its force is reputational and historical rather than legal: it tells future negotiators, civil society and historians that the adoption was contested, and by whom, in terms the objecting delegation chose for itself rather than terms a critic later assigned to it.

How should a reader use this when following a summit?

Treat the explanation of position as part of the decision, not an aside to it. A text adopted "by consensus" can mean anything from unanimous agreement to a single, loud, recorded dissent; the only way to tell the difference is to check whether anyone asked for the floor after the gavel. For organisers tracking a convention's history, the explanation of position is also a model worth borrowing outside the summit: a sign-on statement, discussed elsewhere on this site as an organising tool in its own right, works on the same principle of making a position permanent by putting it in writing where it can be found again.