School of Specs Inside one plenary: TSG SA#112Overview

How the paperwork is organised · chapter 3 of 7 · 5 minutes

3 Reading the agenda, and what the top-level items are for

The 23 items a plenary's agenda is built from, how many documents each one drew at SA#112, and why most of them drew nothing at all.

3.1 The agenda is the filing system

Every document at a plenary is filed under one agenda item, and the agenda is approved before anything else happens [1].

That makes the agenda more useful than it looks. It is not a plan for the conversation; it is the index of the meeting, and the number of documents under each item tells you where the work actually sat.

3GPP writes the items "AI 1", "AI 2" and so on, and so does this course. SA#112 had 23 of them [2], running in one order from the opening of the meeting to its close.

3.2 The 23 items, and what each drew

The third column is how many of the meeting's 346 documents were handled under that item.

Item What it is for Documents
AI 1 Opening of the meeting 2 [3]
AI 2 Liaison statements 22 [4]
AI 3 Items for early consideration 25 [5]
AI 4 Reporting from the SA working groups and other top-level groups 31 [6]
AI 5 Release planning 3 [7]
AI 6 Work item and study item descriptions 80 [8]
AI 7 Specifications 31 [9]
AI 8 Study on 3GPP AI/ML Consistency Alignment 0 [10]
AI 9 Study on modernising the specification format for 6G 11 [11]
AI 10 to AI 16 Change requests for Rel-10 through Rel-16 1 in total [12]
AI 17 Rel-17 change requests 7 [13]
AI 18 Rel-18 change requests 17 [14]
AI 19 Rel-19 change requests 40 [15]
AI 20 Rel-20 change requests 63 [16]
AI 21 Project management and TSG SA's own specifications 13 [17]
AI 22 Any other business 0 [18]
AI 23 Close of meeting 0 [19]

Those counts add up to the meeting's 346 documents [20], which is the point of the structure: nothing is handled outside it.

3.3 The shape of the agenda is the shape of the work

Three items carry most of the meeting between them — AI 6 with 80 documents, AI 20 with 63 and AI 19 with 40, as the table above records.

Read them together and they say something plain: this plenary was mostly about starting new work, and about changing the two releases currently being written.

  • AI 6, 80 documents. New work item and study item descriptions. This is where a piece of work is proposed and either gets a number or does not.

  • AI 20, 63 documents, and AI 19, 40. Change requests against Release 20 and Release 19 — the release being written and the one being finished off.

  • AI 4, 31 documents, and AI 7, 31. The working groups reporting on themselves, and the specifications brought for approval.

3.4 Most of the agenda is empty

The other half of the story is the items that drew nothing. In the draft report of this meeting the sentence "There were no contributions to this agenda item." appears 40 times [21].

Three examples make the pattern clear:

  • Release planning, AI 5, drew three documents. The item whose title sounds like the centre of a plenary was one of its quietest.

  • AI 8, the study on AI/ML consistency alignment, drew none at all.

  • The seven change-request items for Rel-10 through Rel-16 drew one document between them.

That is not neglect. Every release back to Rel-10 has its own numbered slot on this agenda, whether anybody files against it or not, and at this meeting almost none of those slots was used.

3.5 Underneath the 23

The 23 items are only the top level. Each is divided again, and the sub-items are where documents actually sit. The previous meeting's report, for instance, is handled under agenda item 1.5 rather than under AI 1 as a whole [22].

The arithmetic gives that away. The report says "There were no contributions to this agenda item." 40 times, and there are only 23 top-level items. Most of what that sentence is counting must therefore be sub-items.

It matters when you go looking for something. A number with a dot in it is a pointer inside one of the 23, and the document you want is filed under the sub-item, not under the round number.

3.6 What the agenda cannot tell you

The counts above come from the meeting's own document list and its draft report, and the report is exactly that — a draft, marked "Status: Draft - for comment" on its cover [23].

Two things the agenda will never give you, however carefully you read it:

  • It does not say what was decided. An agenda item with 80 documents under it might have approved all 80 or none. The decision is a separate word, and the next chapter is about those words.

  • It does not say how long anything took. The document list carries the agenda item, the type, the source and the result of each paper [24], and nothing about the clock.

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. 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
  3. 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
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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
  19. 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
  20. 346 documents at SA#112 sqlite3 /var/www/whatthespec.net/data/database/api/api.sqlite "select count(*) from tdoc where meeting='SP-112';", read 2026-08-04
  21. 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
  22. '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
  23. SP-112 draft meeting report, version 0.0.5
  24. TdocsByAgenda, the SA#112 document list

Every source this course is built on

Check yourself

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

Q3.1 How many top-level agenda items did SA#112 have?

Q3.2 Which agenda item drew the most documents?

Q3.3 How often does the draft report say "There were no contributions to this agenda item."?

Q3.4 How many documents did release planning, AI 5, draw?

Q3.5 What do agenda items 10 to 16 cover, and how busy were they?

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