Common App problems: A meltdown worthy of

High School Seniors! If You Liked, You’ll Love the Common App.

High School Seniors! If You Liked, You’ll Love the Common App.

Decoding the tech world.
Nov. 13 2013 10:54 AM

Because the College Application Process Just Wasn’t Stressful Enough

The Common App meltdown was ridiculous and totally avoidable.

frustrated high school student
Common Application user

Photo by iStockphoto/Thinkstock

In my updating of Flaubert’s Dictionary of Received Ideas, his satirical handbook of “Tradition, Order, and Sound Conventions,” I have added the following entry:

David Auerbach David Auerbach

David Auerbach is a writer and software engineer based in New York, and a fellow at New America.

private sector: Always efficient, always competitive. Cure for all governmental ails.

Members of Congress doing Monday-morning quarterbacking on have frequently claimed that such a screw-up could never happen in the private sector. In fact, it happens all the time. Remember Microsoft’s Kin phone? The Apple III? Or the Edsel?


There’s now an even closer comparison available: the college Common Application. Created to facilitate reusing data and admissions materials across multiple college applications, this year’s Common Application, which services 517 colleges and universities, has become a technological fiasco thanks to the interaction of two famously inefficient parts of the (mostly) private sector: programming contractors and educational administration. They came together in the form of the nonprofit membership association Common Application Inc. (I will use “Common App” below to refer to the company.)

On Aug. 1, this year’s upgraded Common Application software rolled out, consisting of a major overhaul to the application process that was, according to Common App senior director of policy Scott Anderson, “a completely new system built from the ground up.” It immediately crashed. Since then, an assortment of problems and terrible user interface issues around what Anderson calls its new “choose your own adventure” branching application process have created increasing consternation for colleges, high schools, and especially high school students, who are already stressed enough about the application process. Forty-six schools have pushed back their early admissions deadlines. Common Application’s Facebook page has been barraged with complaints. “The only browser that worked for our counselors was [Internet Explorer]… Support was never helpful. We never heard anything from anyone regarding our issues,” said Facebook user and Common App guinea pig Chleo Harley. “It’s been a nightmare,” said Cornell associate vice provost Jason Locke to the New York Times.

Anderson, however, maintained that the delays were unnecessary. “Nobody had to move their deadlines,” he said. “The colleges that moved it beyond Nov. 1 did so to help ease the anxiety that applicants were feeling that they might not possibly be able to submit their applications because of problems they were experiencing.”

Easing that anxiety should have been the job of the Common Application, not of the member colleges. The complaints are justified. From an engineering standpoint, what happened is ridiculous. The parallels with are evident: A system designed to serve as the broker between consumers and hundreds of companies fails to get the connections right. After two months of eliding the blatant problems, the Common App folks did become more upfront about the problems, posting a partial list of fixed bugs and a list of bugs to be fixed, as well as a pledge to rebuild trust. But was an entirely new system built from scratch; the people behind Common App—a nonprofit with a board of directors drawn from a dozen or so colleges—took a working system and, in the process of “upgrading,” broke it.

I worked primarily on servers in my time as a software engineer, and there were some pretty simple rules of thumb when upgrading. Whenever possible, you roll out a server upgrade to a fraction of your users first, to make sure it doesn’t instantly break. This is sometimes called the “canary” server, as in coal mine. If it does break, you make sure to have a process in place to roll back the upgrade and restore the system to its previous state—the one that was working. The same goes when you roll out to everyone: If something breaks, you roll back so you can find the problem and fix it off the clock, without users and managers pointing at their watches asking when things will work again like they did yesterday.