School of Specs Inside one plenary: TSG SA#112In depth

What a plenary is · chapter 3 of 12 · 8 minutes

3 How to read a plenary agenda

The 23 top-level items of SA#112, what belongs under each, why most of them were empty, and where the weight of the meeting actually sat.

3.1 The agenda is the index to everything

The first thing the plenary did was approve its own agenda: "The agenda was reviewed and approved." [1] Everything after that hangs off it.

That matters for a reader more than it sounds. Every document of the meeting carries an agenda item number, the document list is sorted by it, and the secretary's report walks the items in order. Learn the agenda and you can find anything.

The agenda document itself is SP-260361, version 2 [2] SP-260361. Besides the items it carries the deadlines, the day-by-day time plan and the meeting's own rules on how to request a document number, so it is also the file that tells a first-time delegate how to take part.

3.2 The 23 items

There are 23 top-level items [3], and the document counts below add up to exactly 346 — the same total the meeting handled.

Item What it is called Docs
AI 1 Opening of the Meeting 2 [4]
AI 2 Liaisons Statements 22 [5]
AI 3 Items for early consideration 25 [6]
AI 4 Reporting from SA Working Groups, other TSGs, and Others 31 [7]
AI 5 Release Planning 3 [8]
AI 6 Work Item Descriptions, Study Item Descriptions, Specifications 80 [9]
AI 7 Specifications 31 [10]
AI 8 Study on 3GPP AI/ML Consistency Alignment 0 [11]
AI 9 Study on Modernization of Specification Format and Procedures for 6G 11 [12]
AI 10 Rel-10 and pre Rel-10 CRs 0 [13]
AI 11 Rel-11 CRs 0 [14]
AI 12 Rel-12 CRs 0 [15]
AI 13 Rel-13 CRs 0 [16]
AI 14 Rel-14 CRs 0 [17]
AI 15 Rel-15 CRs 1 [18]
AI 16 Rel-16 CRs 0 [19]
AI 17 Rel-17 CRs 7 [20]
AI 18 Rel-18 CRs 17 [21]
AI 19 Rel-19 CRs 40 [22]
AI 20 Rel-20 CRs 63 [23]
AI 21 Project Management & TSG SA owned specifications 13 [24]
AI 22 Any Other Business 0 [25]
AI 23 Close of Meeting 0 [26]

The names in the middle column are the agenda's own wording, shortened for items 8 and 9.

3.3 Four shapes of item

Once you have seen that table twice, the agenda stops being a list of twenty-three things and becomes four kinds of thing.

  • Running the meeting. Items 1, 21, 22 and 23. Opening, project management and TSG SA's own specifications, any other business, close.

  • Taking things in. Items 2, 3 and 4: letters from outside, whatever the chair agreed to hear early, and the reports from the working groups and the other TSGs. Between them they were one of the busiest parts of the meeting.

  • Deciding what gets written. Items 5, 6 and 7 — the release calendar, the work and study item descriptions, and the finished specifications. Item 6 alone was the biggest item of the meeting.

  • Change requests, one bin per release. Items 10 to 20, each holding corrections to one release and nothing else.

Items 8 and 9 are the exception to the pattern: a single named study gets its own top-level item for as long as it is contentious. Item 8, on AI/ML consistency alignment, drew nothing at all this time; item 9, on modernising the specification format for 6G, drew 11 documents and an argument, which chapter The new work — what the plenary let start tells.

3.4 How a document reaches an item

The agenda document is also the meeting's rulebook for getting on it. It carries the deadlines and the rules for requesting a document number, which is the step that turns a draft on somebody's laptop into a row of the meeting's document list.

Once a document has a number it has an agenda item, and that item is where it will be handled unless the chair moves it. Nothing at a plenary is discussed off the agenda.

The exception is the escape hatch, item 3, and it is used heavily: 25 documents came through early consideration at SA#112, which the table above puts among the busiest items of the week.

The Release 21 timeline is the clearest case. Its subject is release planning and its home is item 5, but the decision was taken in the joint session and recorded under early treatment SP-260595. If you go looking for the big decisions of a plenary under the item whose title matches, you will miss them.

3.5 Why most of the items were empty

The draft report of the meeting says "There were no contributions to this agenda item." forty times [27]. That count includes sub-items as well as top-level ones.

At the top level, three items drew nothing — item 8, any other business and the close — and six of the eleven change-request bins were empty: Rel-10 and older, Rel-11, Rel-12, Rel-13, Rel-14 and Rel-16. The table above carries the count behind each one.

This is not waste. The agenda is written to fit any plenary, so a bin for Rel-12 corrections exists whether or not anybody has a Rel-12 correction. An empty item is a question that was asked and answered "nothing this time".

Release planning is the one empty-looking item that is not what it seems. It drew three documents, yet the Release 21 timeline was settled at this meeting — in the joint session with TSG RAN, reached through early consideration rather than through item 5 [28]. Chapter Release planning — the timeline, the checkpoint and the names follows that.

3.6 Where the weight sat

Three items carry the bulk of the paper: item 6 with 80 documents, item 20 with 63 and item 19 with 40.

Read plainly, that is a meeting spending half its paper on two things: what may be written next, and corrections to the two releases currently being written.

The next tier is the reporting and the early items — item 4 with 31, item 7 with 31, item 3 with 25 and item 2 with 22. Housekeeping, item 21, took 13.

3.7 Sub-items, and what an item number is not

Every top-level item breaks into sub-items, and the report's narrative works at that level. The previous meeting's report was handled under item 1.5, where the narrative reads "The report of meeting SA#111 was approved." [30] The joint-session business sits under 3.4, and the working group reporting that postponed the terms of reference under 4.1 [31].

Two habits follow from that.

  • Cite the sub-item, not the item. "Agenda item 3" covers 25 documents at this meeting. "Agenda item 3.4" points at a paragraph.

  • Do not read meaning into the number itself. For items 10 to 20 the item number happens to match the release number, and nowhere else does an item number mean anything at all.

3.8 What the agenda will not tell you

It is an index, and an index has limits.

  • It does not say what happened. The item tells you where a document was handled, never with what result. That is the status column, and chapter The kinds of document, and the ten words that decide them is about it.

  • It does not rank anything. Item 21 carried 13 documents, including the principle the plenary noted about changing frozen releases [32] — a sentence with more consequence than most of the 80 documents under item 6.

  • It does not follow a subject. The satellite work at this meeting appears under work items, under specifications and under change requests, and no agenda item collects it.

  • It does not survive being read alone. Three documents under release planning looks like a meeting that ignored the subject, and chapter Release planning — the timeline, the checkpoint and the names shows that it did the opposite.

3.9 Where this leads

The agenda tells you where a document was handled. It does not tell you what kind of document it was or what happened to it. That is the next chapter: The kinds of document, and the ten words that decide them.

Where the numbers in this chapter come from

  1. 'The agenda was reviewed and approved.' found character for character in SP-112_Draft_Report_v005.md, which is a draft and says so on its cover, read 2026-08-04
  2. SP-260361, the SA#112 agenda, version 2
  3. 23 top-level agenda items rows of the agenda table in SP-260361_SA112_Agenda_v2.md whose item number has no dot in it, read 2026-08-04
  4. Agenda item 1: Opening of the Meeting Tuesday, 09 June 2026, 1400 local time the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '1' for the count, read 2026-08-04
  5. Agenda item 2: Liaisons Statements the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '2' for the count, read 2026-08-04
  6. Agenda item 3: Items for early consideration (Please contact the SA Chair in advance) the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '3' for the count, read 2026-08-04
  7. Agenda item 4: Reporting from SA Working Groups, other TSGs, and Others the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '4' for the count, read 2026-08-04
  8. Agenda item 5: Release Planning the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '5' for the count, read 2026-08-04
  9. Agenda item 6: Work Item Descriptions, Study Item Descriptions, Specifications the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '6' for the count, read 2026-08-04
  10. Agenda item 7: Specifications the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '7' for the count, read 2026-08-04
  11. Agenda item 8: Study on 3GPP AI/ML Consistency Alignment (FS_AIML_CAL) the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '8' for the count, read 2026-08-04
  12. Agenda item 9: Study on Modernization of Specification Format and Procedures for 6G (FS_6GSpecs) the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '9' for the count, read 2026-08-04
  13. Agenda item 10: Rel-10 and pre Rel-10 CRs the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '10' for the count, read 2026-08-04
  14. Agenda item 11: Rel-11 CRs the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '11' for the count, read 2026-08-04
  15. Agenda item 12: Rel-12 CRs the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '12' for the count, read 2026-08-04
  16. Agenda item 13: Rel-13 CRs the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '13' for the count, read 2026-08-04
  17. Agenda item 14: Rel-14 CRs the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '14' for the count, read 2026-08-04
  18. Agenda item 15: Rel-15 CRs the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '15' for the count, read 2026-08-04
  19. Agenda item 16: Rel-16 CRs the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '16' for the count, read 2026-08-04
  20. Agenda item 17: Rel-17 CRs the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '17' for the count, read 2026-08-04
  21. Agenda item 18: Rel-18 CRs the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '18' for the count, read 2026-08-04
  22. Agenda item 19: Rel-19 CRs the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '19' for the count, read 2026-08-04
  23. Agenda item 20: Rel-20 CRs the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '20' for the count, read 2026-08-04
  24. Agenda item 21: Project Management & TSG SA owned specifications the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '21' for the count, read 2026-08-04
  25. Agenda item 22: Any Other Business the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '22' for the count, read 2026-08-04
  26. Agenda item 23: Close of Meeting Friday, 12 June 2026, 1730 local time (or earlier) the agenda table of SP-260361_SA112_Agenda_v2.md for the wording; rows of tdoc whose ainumber starts '23' for the count, read 2026-08-04
  27. 40 times the report says 'There were no contributions to this agenda item.' occurrences of the sentence 'There were no contributions to this agenda item.' in SP-112_Draft_Report_v005.md. It counts sub-items as well as top-level items, read 2026-08-04
  28. 'SP-260595 was presented in the Joint session and was agreed.' found character for character in SP-112_Draft_Report_v005.md, which is a draft and says so on its cover, read 2026-08-04
  29. 140 documents belong to Rel-20 sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112' and release='Rel-20';", read 2026-08-04
  30. 'The report of meeting SA#111 was approved.' found character for character in SP-112_Draft_Report_v005.md, which is a draft and says so on its cover, read 2026-08-04
  31. 'It was decided to ask SA WG4, SA WG5 and SA WG6 to also submit ToRs to the next TSG SA meeting and SA WG1, SA WG2 and SA WG3 may update or re-submit the same ToR proposals.' found character for character in SP-112_Draft_Report_v005.md, which is a draft and says so on its cover, read 2026-08-04
  32. 'Care should be taken to agree or endorse CRs against frozen releases in the working group level, especially given the existing commercial deployments.' found character for character in SP-112_Draft_Report_v005.md, which is a draft and says so on its cover, read 2026-08-04

Every source this course is built on

Check yourself

Answers appear when you pick one, with where they come from.

Q3.1 Which three agenda items carried most of the meeting's documents?

Q3.2 How many times does the draft report say "There were no contributions to this agenda item."?

Q3.3 Agenda item 20 handled 63 documents. How many documents of the meeting belong to Release 20?

Q3.4 What is agenda item 3 for?

Q3.5 Which agenda items are reserved for change requests to a single named release?

This chapter was built from a source register generated 2026-08-04. A fresher build of the register may hold different numbers.