Sunlight Foundation

Senate Homeland Security Committee Votes to Advance Whistleblower Protections

Policy Fellow Matt Rumsey wrote this post.

The Senate Homeland Security Committee held a business meeting yesterday morning where they discussed a number of measures, including S. 743, the Whistleblower Protection Enhancement Act of 2011. The Act is intended to renew and strengthen previous whistleblower protection legislation passed in 1989.

According to the Project on Government Oversight, the bill has 14 cosponsors and support from more than 400 groups and 50 members of the Make it Safe coalition.

According to Senator Daniel Akaka (D-HI), who sponsored the bill, federal courts have interpreted the original act in a way that is inconsistent with congressional intent. These interpretations have proved harmful for whistleblowers. Akaka introduced his bill in order to solve these issues.

Senator Susan Collins (R-ME) noted that a similar bill had been passed by the Senate last year, but the House of Representatives had stripped it of provisions protecting intelligence community personnel. The bill ultimately failed. This year, according to Collins, the two chambers "worked to achieve a consensus on how intelligence commuity personnel should be handled" that is now reflected in the bill.

Before voting on the bill, Senator Akaka introduced an amendment to clarify provisions on nondisclosure agreements, give the Government Accountability Office more time to review the bill, and provide the Defense Department with access to information and consultation rights in some of the intelligence provisions. The amended bill was passed by the committee via a voice vote and will now advance to the full Senate.

The committee also considered and passed S. 1409, the Improper Payments Elimination and Recovery Act of 2011 and S. 237, the Government Accountability Office Improvement Act of 2011, in addition to a number of other measures.

A webcast of the entire hearing is available here.

Thanks to PopVox, you can view and search the bill text below.

Stimulus Bill Amendments

The House Rules Committee approved amendments for consideration during the floor debate on the stimulus bill (H.R. 1). There are a couple which would be important to enact. They are:

Amndt. 22 (Platts/Van Hollen): Would insert the text of the Whistleblower Protection Enhancement Act (H.R. 985 in the 110th Congress) regarding protections for federal employees who report waste, fraud, and abuse.

Amndt. 89 (Teague): Would require that the Recovery.gov website contain links and other information on how to access job information created at or by entities receiving funding under the bill; including links to local employment agencies, state, local, and other public agencies receiving recovery funds, and private firms contracted to perform work funded by the bill.

The Whisteblower Protection Enhancement Act was introduced in the 110th Congress and would extend and enhance protection for whistleblowers reporting on national security, science, and contractor waste and fraud. The protections include contractors who are whistleblowers. The details are available here.

The Teague amendment gets at something that is often overlooked when discussing transparency and web sites like Recovery.gov. The site should not only serve as a place for openness and accountability regarding the programs and projects authorized in the stimulus bill, but should also aim to serve the public that the programs and projects intend to aid. The requirement in the Teague amendment would provide an immediate service of helping the job-seeking unemployed connect to jobs created by the bill. This can't be overlooked as service provision, along with information dissemination, must be an important aspect of government web sites.

Obama and Affirmative Disclosure

The Obama transition team released two new policies this week, a Creative Commons license and a radical disclosure policy. These changes don't just signal a new relationship to the public, but also create a paradigm shift in how government manages information, and could lead to much bigger things to come from the administration. Requirements for affirmative disclosure move the onus of dissemination to the government (unlike FOIA, which relies on citizen requests), and might just revolutionize the way our government views its communications.

Creative Commons

First, the transition team changed its copyright policy, and is now publishing under a Creative Commons Attribution 3.0 License. This is great news, since, contrary to popular opinion (see the comments here), transition materials aren't automatically in the public domain, despite the .gov web address. This means that reuse of their work is now encouraged, within carefully crafted guidelines, and, more importantly, that the transition team is thinking about the real effects of their publication methods. That's exactly what the Creative Commons was designed to do: to add a level and control and nuance to a legal framework designed around limitations. Whereas Copyright is about control, the Creative Commons and copyleft movements are about empowerment, through carefully crafted designations created by brilliant lawyers. (For example, "You are free to Reuse... or Remix, [so long as you] attribute the work in the manner specified by the author or licensor...)

Creative Commons licenses are affirmative designations with real legal force, enabling creativity and reuse through a carefully crafted set of nuanced licenses. (Keep that in mind...)

At the Table

Next, the transition team introduced their Seat at the Table feature. At first glance, "Your Seat at the Table" might look like a kitschy PR portal. What is the entire change.gov site supposed to be, if not a seat at the table? A closer look, however, reveals that this specific feature is in fact different from the rest of the site -- it's the result of a significant policy change. From the (actual) memo sent out from John Podesta, as posted on the site (pdf):

Scope: The following information will be posted on our website: 1. Documents: All policy documents1and written policy recommendations from official meetings2 with outside organizations. 2. Meetings: The date and organizations represented at official meetings in the Transition headquarters or agency offices, with any documents presented as noted above.

This scope is a floor, not a ceiling, and all staff are strongly encouraged to include additional materials. Such materials could include documents (recommendations, press releases, etc.) presented in smaller meetings or materials or made public by the outside organization without a connection to an official meeting.

The footnoted section contains the real meat, since it defines what must be disclosed:
1This policy does not apply to non-public or classified information acquired from the Agency Review Process and internal memorandum. 2 An “official meeting” is defined as a meeting with outside organizations or representatives of those organizations to which three or more outside participants attend.
To summarize, the transition team has decided that all policy documents and recommendations presented at official meetings with outside groups will be posted online, and they're defining "official meetings" as those at which three or more representatives attend.

Now, it's tempting to quibble with the definition of "official meeting", but remember, this is the transition team, not the administration. They're only operational for a few months, and nothing like this has been tried before in this context, so their policy is entirely appropriate. They're posting primary resources, in near real time, and at least acknowledging the public's role as overseer and partner, and nothing says they have to. They've created a new designation (the official transition meeting), and used that designation to generate public access and oversight.

This is a brave, bold move, and the transition team deserves our praise.

Affirmative Disclosure?

All this raises a more significant question, however. What could such a program look like across the entire executive branch? In other words, does "Your Seat at the Table" scale? Could there be a system of affirmative designations that broadly opens executive branch information, just as Creative Commons has in the creative sphere?

This is pretty complex question, but we do have some other examples of government information programs that are based on managing carefully crafted records designations. Here are two...

First, think of classification, the official process by which our government keeps secrets. It's so prolific that it costs about $8 Billion per year (pdf). (That doesn't count the CIA's classification budget, which is, well, classified.)

Second, we have General Records Schedules, which are designations that the National Archives uses to standardize how administrative records are kept across the government. The FDA issues regulations on meat, and NARA issues regulations on paperwork. (Though NARA has initially resisted playing any enforcement role, despite failing preservation procedures government-wide.)

These are two enormous government programs dedicated to controlling public information. My question is this: If we have set up a complex, $8 Billion system for making secrets, and have created a complex system for managing the flow of paper throughout government, where is the public disclosure system? Who should be deciding what the public can see, and how they see it?

Should we be thinking about creating a system for proactive disclosure, where documents or data can be designated for release, RSS, API, upload, download, IG review, FTP, or whatever?

Especially after the last administration has made it easier to make secrets and obfuscate, shouldn't the Obama administration make it easier to say "Hey, someone should really be taking a look at this!".

This makes sense as a whistleblower provision, or even as a data management practice. Imagine if witnesses to malfeasance were empowered to flag troublesome documents for publication, or at least for further review, and that those designations carried some administrative or legal force, like Creative Commons licenses, or the designation of a "public meeting". Imagine if a Webmaster or CIO were capable of submitting requests to the OMB data task force, or to the Public Data Advisory Team.

Even better, imagine if all government data were given a proactive designation by an empowered centralized Information Officer, Transparency Czar, or Deputy CTO. We already do this for secret-keeping, and for historical preservation. Real-time public access should be at least as important as history and secrecy.

(discussion also on the Open House Project google group.)