For all requests to advance a specification to a new maturity level other than Note, the Working Group must obtain Director approval. This is repository for managing W3C spec transitions. It contains the transition requirements document, available from Organize a Technical Report Transition, and an issues tracker for managing transition requests. Tags are used to manage the transitions, keeping track of who has the “ball”.

Select one of the transition templates below:

• First Public Working Draft: FPWD transition
• First Public Working|Interest Note: FPNote transition
• Ordinary Working Draft: no Director's approval needed, just use Echidna.
• Ordinary Working|Interest Group Note: no Director's approval needed, just use Echidna.
• Candidate Recommendation: CR transition
• Updating a Candidate Recommendation with only editorial changes: no Director's approval needed.
• Updating a Candidate Recommendation with substantive changes: Updated CR transition
• Proposed Recommendation: PR transition

• Edited Recommendation: Edited REC transition

If you're not sure what transition template to use, check out our next step finder to see your choices.

• If you're not sure how to fill the template properly, see Organize a Technical Report Transition (2017 Process).
• If you need to convey Member-confidential information, start a thread on w3c-archive@w3.org and link it from your issue; lists.w3.org's access control will manage permissions. Use w3t-archive@w3.org instead for Team-confidential infos.
• Your WG code is your WG's preferred (unique) abbreviation: it is included in the title template to help you search for transition requests relevant to your WG and manage the official or unofficial pestering of whoever has the “ball”.
• Assign your editor(s) and staff contact(s) to the issues to facilitate automatic pestering.
• Don't forget to tag/untag “Awaiting ...” so that issues show up in the appropriate to-do queues.
• Issues get closed once publication is complete and relevant announcements are posted.