The Climate Practice Wiki for UN Work

The review clock

Six windows, every one of them counted back from the technical expert review week. Everything the four carousels promised, with the Project instructions in full.

4 min read5 sectionsSources opened 2026-10-23. Both documents are linked at the end of the page.
Save this page.Every prompt below copies in one click. Dates are the editions quoted.Jump to the first prompt

1. The six windows

Decision 18/CMA.1, annex, paragraph 162 sets the procedure for in-country, centralized and desk reviews. Every window in it is measured from the technical expert review week. None of them is measured from the day you submit.

When What happens Whose job Paragraph
14 weeks before Review week dates agreed para. 162(a)
10 weeks before Review team composed para. 162(b)
4 weeks before Preliminary questions arrive para. 162(c)
The review week Draft areas of improvement para. 162(d)
2 months after Draft review report for comment para. 162(e)
1 month after that Your comments due para. 162(f)

The words matter as much as the counts.

  • 162(a) The secretariat shall "agree with the Party the dates of the technical expert review week at least 14 weeks prior to the technical expert review week". You are in that conversation. If you are not ready for it, you agree to dates anyway.
  • 162(b) The secretariat "shall compose a technical expert review team at least 10 weeks prior to the technical expert review week".
  • 162(c) The team "should communicate any preliminary questions to the Party at least four weeks prior". Your answer is due "within two weeks of the request", and developing country Parties that need flexibility "are instead encouraged to provide the information within three weeks of the request".
  • 162(e) The draft review report comes to you "within two months of the technical expert review week".
  • 162(f) You are "given up to one month from its receipt to provide comments", with three months available to Parties that need flexibility.
  • 162(h) The whole report is to be complete "no later than 12 months from the start" of the review.

2. The same question, with and without the source

I asked for this clock with no source open, then with the stored decision text in front of me. The run is recorded.

Claudeno tools open

Working backwards from the technical expert review week, what deadlines do the secretariat, the review team and the Party each have to meet?

Review week dates agreedfar enough aheadat least 14 weeks priorpara. 162(a)
Preliminary questionsahead of the sessionat least four weeks priorpara. 162(c)
Draft review reportroughly three monthswithin two monthspara. 162(e)

Asked with no tools open, 2026-10-23. The shape is right and not one window has a number.

The run itself says to treat its day counts as orders of magnitude. That is the honest part. The part that costs you is the shape that is almost right, because a shape that is almost right does not get checked.

3. Why counting from December goes wrong

The deadline and the clock are two different things.

31 December 2026 is when the report is due. Paragraph 162 starts running at the review week, which is scheduled after you submit. A desk that counts from December sees one date. A desk that counts from the review week sees six.

The cycle is not pending. FCCC/PA/CMA/2026/10, paragraph 5, says "the first BTR2 was submitted on 8 August 2026, before the deadline of 31 December 2026". The same paragraph says a total of 136 Parties had submitted BTR1s as at 31 August 2026, and that 88 of them had submitted by the 31 December 2024 deadline.

4. Project instructions

Paste this into a Claude Project, not into a chat. It answers in one order and it quotes the paragraph it used.

Paste into Claude
I run transparency reporting for one Party. Work backwards
from the review week, never forward from the submission date.

For every task I give you, answer in this order.
1 Window    which para. 162 window it falls in
2 Owner     secretariat, review team or us
3 Trigger   what has to exist before the window opens
4 Provision the MPG paragraph, quoted

Rules.
Quote the MPGs from the file I paste. Never from memory.
No paragraph number? Write NOT IN THE MPGS.
Deadlines change each cycle. Ask me for the cycle dates.
Last line: what I have to confirm with the secretariat.

The Project cannot know your cycle dates. It asks for them. That is deliberate, because the dates move every cycle and the rules do not.

5. What this page does not do

It does not tell you whether your evidence is good enough. It sorts the clock, not the content. It also does not cover the simplified review of a national inventory report in a year when no biennial transparency report is due. That is paragraph 161, and it is a different page.

Sources