Work Item Description

Description

A Work Item Description (WID) is a critical project management and governance document within the 3GPP standards development organization. It is not a technical specification for network equipment, but a meta-document that governs the creation of such specifications. Each WID is a structured template containing several key sections: a precise title, a list of participating companies (the rapporteurs and contributors), the technical objectives and detailed work tasks, the list of 3GPP Technical Specification (TS) and Technical Report (TR) documents to be impacted (e.g., created, revised, or deleted), a justification for the work explaining the market need, and a proposed time plan with milestones for completion. The WID is created following an agreed-upon template (e.g., in 3GPP TS 21.900) and is the output of a feasibility study or a directly proposed new work area.

The process of how a WID works is integral to 3GPP's consensus-based operation. A member company or a group of members first submits a proposal for new work, often as a Study Item Description (SID). After a study phase concludes with a TR, a corresponding WID is drafted to convert the study findings into normative specification work. This draft WID is presented, discussed, and revised within the relevant Technical Specification Group (TSG) or Working Group (WG). Formal approval of the WID, typically by a TSG plenary meeting, authorizes the associated Working Group to expend resources and begin the detailed technical work described. The WID acts as a reference throughout the development cycle; any significant deviation from its scope requires an updated WID to be approved.

Key components of the WID include the 'Work Item' itself, which is a high-level label (e.g., "NR sidelink enhancement"), and the detailed 'Deliverables'. The deliverables section is the most technical, listing every TS and TR to be produced, along with a brief description of the content to be added to each, such as "Add clause on new QoS parameter X to TS 23.501." The WID also specifies the release target (e.g., Release 18). Its role is to ensure that all participants and the broader industry have a clear, agreed, and stable understanding of what a particular release will contain, preventing scope creep and aligning development efforts across multiple working groups that may be contributing to the same feature. It is the contractual blueprint for standardization.

Purpose & Motivation

The WID exists to bring order, predictability, and accountability to the complex, multi-party process of developing global telecommunication standards. 3GPP involves hundreds of companies across the globe working on dozens of parallel features. Without a formal mechanism like the WID, work would be chaotic, with unclear objectives, duplicated efforts, and inconsistent deliverables. The WID solves the problem of coordinating large-scale technical projects in a voluntary consensus environment.

Historically, as 3GPP's work expanded from core GSM/UMTS to LTE, 5G, and beyond, the need for structured project management became paramount. The WID formalizes what was often an ad-hoc agreement. It addresses the limitation of informal proposals by requiring a justification based on market requirements, technical feasibility, and backward compatibility considerations. It forces proponents to think through the full impact of a feature—which specs need change, how long it will take, and what resources are required—before work begins. This protects the interests of all members, ensuring that the group's work program reflects collective priorities and that the output (the specifications) is complete, consistent, and delivered in a timely manner for a given release.

Key Features

• Defines the precise scope and objectives of a standardization feature or study
• Lists all 3GPP specification documents (TS/TR) to be created or modified as deliverables
• Includes a justification section linking the work to market needs and trends
• Provides a detailed time plan with key milestones (e.g., freeze dates for each stage)
• Identifies the responsible rapporteur(s) and supporting companies for the work item
• Serves as the formal gate for approving the start of normative work in a working group

Evolution Across Releases

Defining Specifications