I’ve been talking about some of the shortcomings of the Commission’s proposed update to our rule on certificates of compliance, Part 1110. I’ve looked at our unwillingness to present all the costs, our inability to provide clarity on certifying to bans, and our refusal to engage the public on how to handle testing exemptions. Today, my concern is with my colleagues’ break with our staff on recordkeeping for the certificates.
The 1110 rule requires manufacturers and importers to include certificates with their products attesting to the products’ tested compliance with all applicable CPSC safety standards. These can be Children’s Product Certificates or General Certificates of Conformity, depending on the product. Most CPC requirements are already covered in Parts 1107 and 1109, leaving GCCs to 1110. As proposed, this revision contains a one-size-fits-all requirement to keep GCCs for five years. On its own, this might not be a problem; we have to set a mark, and five years might be as good as three or seven. But we cannot look at this rule on its own, as my colleagues are unfortunately doing, because doing so creates unnecessary confusion.
This rule rests on the testing rules, and those rest on safety standards. These other rules frequently contain their own recordkeeping provisions. Our rule on flammability standards for mattresses, for example, requires manufacturers to test prototypes and then keep the records for as long as the product is on the market, plus three years. Those test records, then, could be discarded after four years or hang around for decades. Even within one product, the requirements that already exist vary with circumstance, and that variation exists throughout our regulatory arena.
Recognizing the differences in the standards’ requirements and my colleagues’ preferences for keeping records for longer, I proposed a compromise tying the retention requirement for GCCs to their underlying standards, defaulting to five years for any certificate based on a standard with no recordkeeping mandate. My colleagues did not agree, and insisted on a universal five-year mandate. Since CPCs all have a five-year minimum, they argued, imposing the same requirement for GCCs would “harmonize” our certificate rules.
“Harmonizing” requires that the notes be in the same key. Imposing one regulatory scheme’s parameters on another simply for the virtue of nominal similarity while ignoring their underlying differences is as unsound as “harmonizing” your children’s closets by giving them all the same size pants, no matter their ages. Yes, they’re in harmony, but someone’s going to wind up with a bad fit.
In this instance, the more valuable harmonization would have been matching the certificate’s retention time to that of the rule that creates the standard and the test on which that certificate is based. I was pleased my colleagues were at least willing to include a request for the public to comment on the recordkeeping retirement, and I hope they read those comments with open minds.

1110 Series: If We Wanted Your Opinion…
Published May 8, 2013 1110 Series , Burden Reduction , Certification , Children's Products , Comment Request , Congress , CPSIA , Uncategorized 3 CommentsOver the past couple days, I’ve talked about how the Commission hid the ball on costs and actively avoided clarity for product bans when we proposed to amend our certificates of compliance rule, the 1110 rule. Today, the issue I wanted to highlight is not our failure to make the rule as intelligible as it should be; it’s my colleagues’ refusal to seek intelligibility in our own deliberative process, specifically in how the new rule will deal with products that are exempt from testing to any applicable safety standard.
Our staff originally proposed what I thought was an acceptable approach: If your product is subject to multiple rules and exempt from testing for only some of them, then you have to certify to the ones in force and claim your testing exemption(s) for the rest. But if your product is exempt from testing under any applicable standard—whether your product has one or more testing exceptions—you don’t need a certificate just to say that. To me, this seemed not only a reasonable opportunity to minimize unnecessary burdens but also more consistent with the law, which bases certificates on testing. Requiring a certificate with no information other than an exemption is wasteful and contrary to the purpose of the testing regime.
My colleagues were uninterested in these benefits. Arguing that having more pieces of paper to shuffle would expedite work at the ports, they amended the proposed rule to require companies to create, provide, and maintain certificates that say nothing more than, “I’m exempt from testing to the standard.” Although I do not think such a certificate is necessary, I thought public input on the question could be helpful, so I proposed returning to the staff’s original language and asking for comment on the safety, efficiency, and cost implications of my colleagues’ approach. My colleagues were not interested in asking a question, and decided to plow ahead. (My colleagues did less-than-helpfully note that the public could still comment on the approach.)
The rule they insisted on might turn out to be the efficient one. We might hear from commenters that consistency in certificates is more useful than skipping hollow ones. What baffles me is my colleagues’ refusal to even solicit public input on the point, particularly when they are claiming benefits that, if real, the regulated community would likely endorse. Dogged refusal to invite any other perspectives is not the hallmark of reasoned decision-making.
Tomorrow, we’ll continue this discussion of the areas where the 1110 rule could use improvement before it’s final.