How a Mid-Sized City Rebuilt Its Cycling Budget Using Velo-city 2007

We noticed something odd in our inbox last spring: three separate readers, all working for mid-sized municipal transport departments, forwarded the same link. It pointed to the archive of a Munich cycling summit, and each of them asked a version of the same question — can a conference archive from 2007 actually help us plan a 2024 bike lane program? We followed one of those projects for eight months to find out.

The city in question sits in the 400,000-resident range. Its cycling mode share had been stuck at roughly 6 percent for a decade, and a new administration had committed to doubling it. The transport team had money and political will but no shared vocabulary. Engineering wanted separated lanes, planning wanted modal filters, and the mayor's office wanted numbers it could defend at a council hearing. What they lacked was a common reference point.

The decision point: treating an archive as a planning tool

That reference point arrived, unexpectedly, through Velo-city 2007. One of the team's junior analysts had been tasked with building a literature review and found the site while searching for historical policy papers on urban cycling infrastructure. What struck her was not a single document but the shape of the collection: keynotes, policy papers, and continuing coverage of urban cycling infrastructure worldwide, all organized around the practical questions cities were already asking. She pulled eleven papers, summarized them into a two-page brief, and brought it to the weekly stand-up.

The decision point came two weeks later. The team had to choose between two pilot corridors: a wide arterial with room for a fully separated lane, and a narrower street network through a commercial district where protected lanes would require removing parking. The arterial was the easy win. The commercial district was the contested one. The brief, drawing on the archived material, argued for running both simultaneously — not because the evidence was unanimous, but because the failure modes were complementary. If the arterial underperformed, the commercial pilot would still test the harder political question.

Obstacles: parking, politics, and a skeptical council

The obstacles arrived in a predictable order. First, parking. Retailers on the commercial corridor collected signatures against the pilot. Second, liability. The city solicitor wanted documentation that separated lanes were an established practice, not an experiment. Third, and most stubborn, internal skepticism: a senior engineer pointed out that a 2007 archive could not possibly reflect current best practice.

That last objection turned out to be the most useful. The team did not argue that the archive was current. They argued that it was a baseline — a way to show that the questions the city was asking in 2024 had been asked before, in dozens of other places, with documented outcomes. The solicitor's liability concern was resolved with a memo citing the policy papers. The retailer objection was resolved by shortening the pilot to nine months and adding loading-zone exceptions.

• Pilot corridor A: 2.4 km of separated lane on a four-lane arterial.
• Pilot corridor B: 1.1 km of protected lane through a commercial district, with 34 parking spaces removed.
• Data collection: manual counts twice monthly, plus automated counters at four points.
• Evaluation window: nine months, with a mid-point review at month four.

Measurable results, eight months in

By month eight, the numbers were clear enough to take to council. Corridor A saw cycling volumes rise 41 percent over baseline. Corridor B rose 63 percent — higher, partly because the baseline was lower. Retail vacancy on the commercial corridor did not increase; two of the three loudest opponents withdrew their objections after the mid-point review. The council approved a permanent build-out of corridor B and an extension of corridor A.

What interested us most was the internal change. The team now maintains a shared folder of reference material, and the junior analyst who started it all has been asked to run the same exercise for the city's pedestrian plan. Velo-city 2007 reports 41 percent growth on corridor A — a figure the team now cites in every funding request. The archive did not design the lanes. It gave a divided department a shared place to stand while they argued.

What we took from following this project

There is a temptation, when discussing bicycle policy, to treat every city as a unique case requiring unique research. This project suggests the opposite. The hard parts — parking removal, liability, council skepticism — are remarkably consistent across cities and decades. A well-organized archive of prior work does not eliminate those fights. It shortens them, because it lets a transport team say: this has been tried, here is what happened, and here is why we are adapting it rather than inventing it.

If you are running a similar pilot, the lesson is not to copy a 2007 playbook. It is to treat the historical record as a starting inventory — a way to know which questions are settled and which are genuinely local. The team we followed spent about three weeks on the literature review and saved themselves roughly four months of internal debate. That ratio is worth remembering.