Our Response to Chicago's RFP for a Lobbyist Registration System
by Derek Eder
The RFP’s objectives are for an outside contractor to build a system that will
- enable lobbyists registered with the City to file, on line, all required registration documents and activity reports.
- enable the Department to review and approve these filings as quickly as possible and communicate with lobbyists who must and have not completed their filing requirements.
- make data compiled from all lobbyists’ filings publicly available on line in various searchable, queriable reporting formats.
Because of the work we have already done, and our goal to help bring openness and transparency to the City of Chicago, the people who created Chicago Lobbyists have decided to respond to this RFP.
Responding to an RFP for the City of Chicago is a herculean task. In the 152 pages, in addition to the usual cover letter, cost proposal, timeframe, etc, the responder must provide
- a project management/implementation plan (including org chart, all software and third party products used, etc)
- audited financial statements for the past 3 years
- an economic disclosure statement and affidavit (EDS)
- proof of $500k workers compensation and employers liability
- proof $2 million in professional liability insurance
Needless to say, this approach to an RFP results in proposals from one type of contractor: firms that are very large and able to jump through all the hoops that the City has to ensure the minimum amount of risk and liability for the City itself. The idea is, if they remove all apparent risk in the selection process, no one will be to blame if the project fails since they vetted the options so thoroughly. What the contractor actually builds and how they plan on going about it is completely secondary. This type of process rarely provides high quality products at a reasonable price, especially in software development.
As a group of volunteers working in our free time on this project, we are not what this RFP is targeting. We are, however, very competent developers and designers and have become experts on this lobbying data and how to display it. If the third objective of the RFP (above) sounds familiar to you, that’s because you’ve been to ChicagoLobbyists.org. We have already met objective 3.
Despite not being able to fulfill most of the requirements of the RFP, we went ahead and responded anyway. We expect the city to pick one of their usual contractors, but hope that they will consider us as additional consultants for the design and front end development.
Download our proposal (PDF)
In the proposal, besides showcasing the work we have already done, we offer to do the following:
- Design research, initially involving interviews with lobbyists entering the data, with the public that views data visualizations, and with city personnel charged with carrying out the ordinance
- User interface design and HTML/CSS
- Usability testing
- Web strategy
- Adapting ChicagoLobbyist.org design and code under a new city-controlled URL to fulfill the public facing website requirement
- Creating an interoperable API for exporting data in a normalized format
We also advocate releasing as much code and design as possible as open source:
We suggest that, whenever possible, the code, data schemas, and designs should be released as open source. Chicago has a unique opportunity to set an open standard for lobbying data structure, collection, and display—so other municipalities can use it. This will also set a good example for government-related projects that it makes sense to share.
Moving from proprietary systems to open source makes collaboration and sharing easier and gives access to a wider pool of highly skilled talent. Examples of successful projects include Open 311, which the city plans to implement in 2012, and Open Street Maps, a viable alternative to Google and Bing Maps.
We will have more updates the next few days. For more background information on government procurement, check out this informative article on The Information Diet: Procurement is America’s Big Problem and CivicCommons’ wiki on Legal and Procurement Issues.
blog comments powered by Disqus
An open process
In the spirit of openness, the goal of this blog is to share our milestones, setbacks and thoughts as we continue to develop and expand this project.
Who are we?
We are Open City, a group of developers and designers based in Chicago that build civic-minded apps using open data.
- Paul Baker
- President and co-founder of Webitects
- Derek Eder
- Developer at Webitects and organizer for OpenGov Chicago
- Chad W Pry
- Engineer at Groupon, Code Academy mentor, and all around charming fellow
- Nick Rougeux
- Designer and CSS wiz at Webitects