7 How to follow a plenary yourself, and what this record cannot tell you

7.1 The five files, in the order to open them

Every 3GPP plenary leaves the same five things in one folder, and they are public ^[1]. Opening them in this order saves an hour.

F1. The agenda — SP-260361, version 2 for this meeting. It carries the deadlines, the 23 agenda items, the hour-by-hour time plan and the meeting's own rules on how to request a document number ^[2], SP-260361

F2. The document list — TdocsByAgenda. Every document under the agenda item it belongs to, with its type, its source and its result. This is the fastest way to see what a meeting did ^[3]

F3. The draft report — the secretary's narrative, agenda item by agenda item, then annexes listing every document, every attendee, every liaison statement and every approved change request

F4. The documents themselves — one zip file per document number, in the folder's Docs/ directory

F5. The welcome pack — what the chair tells a first-time delegate about where all of the above lives ^[4]

7.2 Three habits

H1. A document number is not a decision. SP-260417 and SP-260696 are the same work item. The first was revised and only the second was approved. Read the status word, not the title SP-260417, SP-260696 — the words themselves are in The document types and the status words, and what each really decides.

H2. A change-request pack is many changes in one number. SP-260379 alone carries 23 separate change requests SP-260379. Counting packs and counting changes give very different pictures of the same meeting.

H3. A pack can be split. SP-260387 came out "partially approved": some of the changes inside it went through and some did not SP-260387. "The pack was approved" is a claim you have to check, not assume.

7.3 What this record cannot tell you

This is the part that matters most, and it is the part a summary usually drops.

L1. The meeting report is a draft. The file is SP-112 draft report version 0.0.5, and its cover reads "Status: Draft - for comment". Nothing in it is final, confirmed or ratified, and the right form of words is "the draft report of the meeting records that…" ^[5]

L2. The chair's final notes are not here. The agenda says they are published after the meeting closes; nothing in this data says what they contain

L3. The report does not narrate every document. Of the 346 documents ^[6], 284 get a paragraph of their own ^[7]; for the other 62 the only evidence is a row in an annex table

L4. The draft contradicts itself in at least one place. Under agenda item 1.5 the narrative reads "The report of meeting SA#111 was approved." while the status line under the same document reads "Not concluded." Report both or neither, and never pick the one that reads better ^[8]

L5. The draft has not been proof-read. The chair's surname appears as both "Jaine" and "Jain" in the same report ^[9]

L6. No vote counts, no attendance per company, no reasons. One objection is named in the whole report ^[10] and nothing is said about anybody else's position. A decision here may never be called unanimous, widely supported or controversial

L7. Approved means approved by TSG SA, not published. Each of the 26 specifications and reports approved here ^[11] still has to be produced and put on the server, and this data does not say when

L8. The machine-written summary is not evidence. A language model wrote a summary of this meeting ^[12], along with 224 summaries of individual documents ^[13]. They are worth citing as summaries and never as the source of a claim about what was decided

L9. Two counts of the same thing can differ and both be right. 689 change requests by one method, 673 by another ^[14]. Say which

7.4 One meeting is one meeting

Everything in this course is read out of the paperwork of SA#112 3GPP TSG SA#112. It is a description of what one plenary did, not of how 3GPP always works, and the difference matters every time somebody quotes it.

The safest sentence you can build from this material has three parts: what the document number is, what word the record puts next to it, and that the record is a draft.

Two more habits keep that sentence honest. Say which count you are quoting when two exist, and name the sender only when the record names it — 62 different sources submitted something to this meeting ^[15], and the document list is where each one is written down.

7.5 Where to go next

• The meeting folder itself — the agenda, the report and one zip file per document, exactly as 3GPP publishes them ^[1]

• The document list, for any question of the form "what happened to SP-2606…?" ^[3]

• The sources page of this course, which lists every entry cited here with the file or database row each one was read from

• The in-depth course of this track, which walks the same meeting agenda item by agenda item rather than theme by theme

This course has no specification behind it, so it has no clause map, no glossary, no version history and no list of related documents. It can name a specification and point at it, and that is all TS 23.501.