3GPP CR verification tool

3GPP CR verification tool (BETA version) - User guide

This page briefly explains the 3GPP CR verification tool’s main functionalities. The goal is to allow users to get familiarized with the tool.

The CR Verification Tool (BETA) is a web‑based application that allows users to verify Change Request (CR) documents from metadata aspects (cover sheet fields) and also against the 3GPP formal and drafting rules.

This BETA version:

• does not support CRs on multi-file specifications
• performs verification only
• does not write or update any data in the 3GPP Portal or any database
• displays verification results in the user interface
• allows download of verification reports

The tool's purpose is to support early detection of formal issues before CR discussion or submission.

The tool considers the latest version of the CR form and the latest version of the stylesheet template. Both templates are fetched from the official 3GPP FTP.

Last update: This page is under construction. It was last updated on March 17^th, 2026.

Known issues / bugs

This tool is under active development. The table below lists known issues with warnings/errors/blocking errors raised by the tool, and indicates the next steps.

Verification	Message	Comments	Mitigation / Next steps
Header Info Check	The working group in the document (...) is different from the database (...)	This warning is raised for a number of group naming conventions	Use 3GPP TSG RAN or 3GPP CT1 format. Ticket #19724 (in progress)
Correctness of style definitions	Differences in styles were discovered between the CR document and its document template. The definition of the following styles of the CR document are different from the template: LD.	This warning may be raised.	Disregard warning. Ticket #19621
Date Check	Date is too old: (...)	Verification rule being rewritten	Disregard if CR date is posterior to the end of the last plenary meeting. Ticket #20023 (in progress)
Correct use of list styles	The document contains paragraphs identified as being part of a list that are not formatted properly.	In some cases, the tool may misinterpret some characters (e.g. '-') as being the start of a new bullet. It may also misinterpret reference to other bullets (e.g. "b) see also bullet a)") as being the mark of a new bullet.	Analysis in progress. Ticket #20007
Latest attached template	The document is not based on the latest 3GPP template. The template needs to be attached.
Work items check	Some work items are invalid or do not belong to the correct release: DUMMY	The tool raises an error when the work item "DUMMY" is used	Disregard error. Correction in progress. Ticket #20169
Work Items check	Some work items are invalid or do not belong to the correct release	The tool raises an error for mirrors.	Disregard error. Correction in progress. Ticket #20015

This list will be updated regularly based on user feedback and internal testing.

Versioning / Changelog

• V1.0.1: Beta release (5 March 2026)

Accessing the tool

To access the 3GPP CR verification tool, one needs a 3GPP portal account and to be logged in. The tool will first be released as a Beta version. During the testing phase, only direct URL access will be allowed. The direct link to the 3GPP CR verification tool will be provided to the 3GPP community for user feedback collection and validation during March 2026.

Target Users

The tool is intended for:

• 3GPP Delegates (CR authors)
• MCC Technical Officers (TOs)
• Rapporteurs (verification and review)

Navigation and Entry Points

The Verification feature is organised into three UI states:

• Verification upload (before any CR is uploaded)
• Verification in progress
• Verification results

Each state is described below.

Verification Upload screen (Initial State)

Purpose

This screen is the starting point for CR verification. It is displayed before any CR document is uploaded.

Upload Area

A drag‑and‑drop area labelled: Drag and drop or add files here

Supported Inputs

• For CR verification: regular CR TDoc documents (in docx format), or ZIP files containing one CR TDoc document (in docx format)
• optional TDoc_List (Excel spreadsheet file) when verifying against meeting data (for the option 'Verify against a TDoc list')
• a CR pack (for the option 'Verify CR Pack') for MCC use

User Actions

Possible user actions are

• Select files for upload using 'Add File(s)' button, or via drag and drop. When used, the uploaded files appear in a list.
• Remove selected files individually before starting the verification.
• Optional verification options can be selected: 'Verify CR Pack' or 'Verify against a TDoc list'. If these options are selected, the upload maximum rules change.
• Click Start Verification to launch the verification job.

Verification Progress screen

Purpose

This screen is displayed while the uploaded files verification is ongoing.

The central panel is titled Verification Job and contains:

• a progress indicator bar
• a list of CR files being processed
• a status message indicating that verification is ongoing

Each CR is processed sequentially. No verification results are shown at this stage.

Verification Results screen

Purpose

This screen displays the final verification outcome once all CRs have been verified. Up to 10 CRs can be verified simultaneously.

Results summary

At the top of the screen:

• a summary message indicates the overall result (for example, blocking errors detected)
• the verification job identifier is displayed

Report Section

Below the summary, a tabular verification report is shown. The report includes the following columns:

• File Name – name of the verified CR document
• Check: category of verification check
• Status: result of the check[*]
• Message: description of the issue
• Details: additional contextual information (for example, affected clauses or annexes)

[*]Statuses can be:

• Passed: no issue detected (no line displayed)
• Warning: minor issue detected (line displayed)
• Error: issue requiring correction (line displayed)
• Blocking error: critical issue preventing CR implementation (line displayed)

Download verification results

A Download as Excel button is available on the result screen. This allows export of the verification report in XLSX format for offline review, sharing with other delegates, or meeting preparation.

BETA version details

Scope of verification

The tool verifies, among others:

• file format and naming conventions
• CR cover page structure and metadata consistency
• use of the correct CR template
• mandatory metadata fields
• correct use of Word Track Changes
• structural and drafting‑rule compliance in the CR body

The tool:

• does not modify CR documents
• does not correct detected issues
• does not update Portal metadata

Characteristics and limitations

This BETA version has the following characteristics and limitations:

• no data is written to any 3GPP Portal databases
• verification results are not persisted
• no conflict detection
• no CR implementation functionality
• attachments inside CRs are ignored

All verification results are for consultation purposes only. No portal data will be impacted by uploading and verifying a file via this tool.

Support and Feedback

As this is a BETA tool, feedback is encouraged via the established ETSI Product Owner, or MCC/Technical Officer.

---