--- decision-policy-v3.html	2012-09-24 21:58:43.000000000 -0700
+++ decision-policy-v3-mod.html	2012-09-24 22:19:45.000000000 -0700
@@ -73,6 +73,8 @@
 
 <li><a href="#cr-integration">12. Integration of Extensions during CR</a> - The Process by which the Working Group decides whether a specification that extends HTML be integrated into the core HTML spec.</li>
 
+<li><a href="#cr-remove-early">13. Removing some at-risk features early in CR</a> - The Process by which the Working Group may drop certain at-risk features early in CR..</li>
+
 </ul>
 
 
@@ -1144,9 +1146,49 @@
 
 </dl>
 
+</section>
+
+<section>
+<h2 id="cr-remove-early">13. Removing some at-risk features early in CR</h2>
+
+<p>Working Group members may request early removal of features that
+the WG has approved to be on the list of at-risk features for a
+specification in (or soon to be in) Candidate Recommendation.</p>
+
+<dl>
+
+<dt>1. Marking as at risk</dt>
+<dd>To be eligible to be dropped early, the feature must be approved
+by the Working Group to be on the list of at-risk features prior to
+CR.</dd>
+
+<dt>2. Nominating for early removal.</dt>
+<dd>If an at-risk feature does not have a thorough test
+suite, and also does not have even a single reasonably complete
+implementation, it may be nominated for early removal. Nominations
+for early removal may be entered before entering CR, or up to 3 months
+after entering CR.</dd>
+
+<dt>3. Chair review</dt>
+<dd>Chairs will review nominations to ensure that requests for early removal are
+reasonable.</dd>
+
+<dt>4. Opportunity to present an implementation or tests</dt>
+<dd>If a nomination is reviewed and approved, advocates of the feature
+have up to 3 months from the date of the request to present a thorough
+test suite or a reasonably complete implementation.</dd>
+
+<dt>5. Early removal</dt>
+<dd>If no one presents a thorough test suite or
+a reasonably complete implementation by the date 3 months after the
+request is made, then such features will be removed early. Such
+features may still be pursued in standalone specifications, and may be
+reintegrated into the core specification if they meet the CR exit
+criteria and have WG consensus.</dd>
 
 </section>
 
+
 </article>
 </body>
 </html>