Shows & Panels
- The 2014 Big Picture on Cyber Security
- AFCEA Answers
- Ask the CIO
- Building the Hybrid Cloud
- Connected Government: How to Build and Procure Network Services for the Future
- Continuing Diagnostics and Mitigation: Discussion of Progress and Next Steps
- Federal Executive Forum
- Federal Tech Talk
- The Future of Government Data Centers
- The Future of IT: How CIOs Can Enable the Service-Oriented Enterprise
- The Intersection: Where Technology Meets Transformation
- Maximizing ROI Through Data Center Consolidation
- Mitigating Insider Threats in Virtual & Cloud Environments
- Modern Mission Critical Series
- Moving to the Cloud. What's the best approach for me
- Navigating Tough Choices in Government Cloud Computing
- The New Generation of Database
- Satellite Communications: Acquiring SATCOM in Tight Times
- Targeting Advanced Threats: Proven Methods from Detection through Remediation
- Transformative Technology: Desktop Virtualization in Government
- The Truth About IT Opex and Software Defined Networking
- Value of Health IT
- Air Traffic Management Transformation Report
- Cloud First Report
- General Dynamics IT Enterprise Center
- Gov Cloud Minute
- Government in Technology Series
- Homeland Security Cybersecurity Market Report
- National Cybersecurity Awareness Month
- Technology Insights
- The Cyber Security Report
- The Next Generation Cyber Security Experts
Shows & Panels
Good government means untangling regulation language
Tuesday - 1/10/2012, 11:56am EST
Federal News Radio
More than a year ago, President Obama signed the Plain Writing Act of 2010 requiring agencies to write their regulations in plain English.
Cass Sunstein, administrator of the Office of Information and Regulatory Affairs (Whitehouse.gov photo)
"Rules are often long and complex," said Cass Sunstein, OIRA's administrator. "Sometimes they're well over 1,000 pages. And, to figure out exactly what they're doing and what the public is supposed to respond to, both in the comment period when there's a proposed rule and when the rule is finalized, what they're supposed to do in response, is often a lot of work."
Sunstein told The Federal Drive with Tom Temin this lack of clarity compromises open government and makes it difficult for people to provide input and makes compliance more costly and difficult.
Sunstein said the executive summary should include three key components:
- The purpose of the regulation.
- A summary of each major provision.
- A summary of the costs and benefits.
"One thing we've found, in the last few days even, that is really helpful is to say to agencies, What are the five or six key provisions of a rule? If there are five or six, list them upfront. Have an italicized or bolded section to tell the public what it is ... Then you don't get lost in the detail of, in one recent case, a 1,700-page regulation," he said.
Adding the executive summary is a "simple, small step," but, Sunstein said, "I think it's a quite big deal."
OIRA is also taking stock of "significant regulations" already on the books and reviewing which ones can be streamlined or repealed altogether, Sunstein said. The department's goal is to make that retrospective review process "as open to the public as possible," he said.