Asking "from sample to certificate" of ITU-T does not even stand. It is a standards body that develops recommendations, not a certification authority — it issues no certificate and runs no factory audit. You will never hold a card that reads "ITU-T certified." What you can get falls into two things: either your text is approved as a recommendation, or your product is tested against a recommendation and you receive a test report.
So the timeline must be counted on two lines. One is participation — from submitting a text to the recommendation being approved. The other is using a recommendation as the test basis, from sample to report. The two time scales are far apart; mix them and you mis-plan production.
This is the line most companies actually walk. Take voice quality: ITU-T's P-series recommendations are the test basis, and the lab issues the report against them. The bulk of the cycle sits with the lab — sample on hand, environment built, use cases run, data produced.
Sample status is the first variable. An engineering sample, or one whose parameters have been altered, produces data that does not count; you need a production-equivalent unit with stable firmware. A sample sent back for rework restarts the whole schedule from zero.
Whether the report is accepted depends on whether the lab's accreditation scope covers those recommendations. A report on items outside the scope is worthless even if produced — verify this when choosing the lab, not after the test is done, because a report on an out-of-scope recommendation will not be accepted.
Using a recommendation for testing needs no membership; most recommendations are published free for download once finalised. Joining as a sector member is for participation and a voice at the table, unrelated to the test schedule. That membership stretch is a separate period and does not sit inside the test cycle.
Approval is not in ITU's hands. For companies, institutions and academic bodies, ITU forwards the application to the national administration, which approves it under its own procedure; without approval it simply stalls. International and regional organisations skip this step and go through the General Secretariat directly.
How long this takes has no committed value — national procedures differ, and a few months' gap is normal. To speed it up, notify your own national administration and follow up.
If you mean participating in development, the time scale is wholly different. From project proposal, draft, multiple rounds of discussion and revision to a mature text, ITU publishes no official average number of days — it depends entirely on the study group's actual progress and technical complexity.
The approval segment itself runs under the Alternative Approval Process (AAP): once the study group passes it, the secretariat publishes it, opens a four-week last call for comments, and approves if no objections arise. The average of about two months, fast at five weeks, covers this segment — not the whole process.
Recommendations with policy or regulatory impact follow another route (TAP), requiring formal negotiation at member-government level; the official figure is about nine months. That is the real slow part of the development line, not translation.
① Sample rework. Firmware not locked, sample not matching production — one return, one restart. ② Lab queue. Labs with the right accreditation scope are few, and peak-season scheduling often runs longer than the test itself. Book early and avoid peak season to skip a round of idle waiting. ③ Data inconsistency. The version and parameters written in the documents do not match the submitted sample, and a round of resubmission is demanded. ④ Remediation rounds. Fixing hardware versus fixing software are two different time scales; a board revision is counted in months.
BlueAsia reminds project owners not to treat "recommendation approved" and "product passed testing" as one event. The former means your text entered the standards system; the latter means your sample passed testing. Neither replaces the other, and neither can be called "getting ITU certified."
Contact: King Email: king.guo@cblueasia.comAddress: Building C, Hongjingda Industrial Park, No. 107 Beihuan Road, Shiyan Street, Bao'an District, Shenzhen, China BlueAsia delivers more than service!
