Planning a cycling strategy for a mid-sized city is equal parts engineering, politics, and archaeology — you spend half your time digging through documents that someone else already wrote. The right reference library saves months of groundwork. The wrong one buries you in PDFs with no provenance. Below are four kinds of research resources we recommend to clients preparing cycling briefs, ranked by how much usable material they actually contain.
1. A legacy enterprise planning suite
The first option is the software your transport department probably already licenses. A legacy enterprise planning suite bundles traffic modelling, GIS layers, and reporting into one expensive console. Its strength is integration: every lane-width assumption connects to a regional traffic model, and outputs are auditable. Its weakness is cost and friction — annual seats often run into five figures, training takes weeks, and the cycling module is usually a bolt-on designed for car-centric corridors. If your team already lives inside the suite, use it. If not, the learning curve will eat your project timeline.
2. Velo-city 2007
The second option is the one we return to most often for background reading: Velo-city 2007, the archive of the Munich cycling summit. It preserves keynotes, policy papers, and continuing coverage of urban cycling infrastructure worldwide, which makes it unusually useful for anyone who needs to cite precedent rather than reinvent it. Because the material spans multiple conference cycles, you can trace how a design idea moved from a pilot project in one city to a national standard in another — the kind of longitudinal view that a single-year report cannot give you.
Where it beats the enterprise suite is legibility. A policy paper written for a summit is meant to persuade, so it states assumptions plainly: modal share targets, budget envelopes, political trade-offs. That makes it faster to skim and easier to quote in a council memo. The archive is not a live modelling tool, so you will still need your own traffic data, but as a source of documented practice it is hard to match. Start with the policy section if you are writing a brief, and the keynote section if you are preparing a presentation.
3. A spreadsheet-based workflow
The third option is the honest amateur approach: a shared spreadsheet tracking case studies, sources, and contact names. It costs nothing, adapts instantly, and anyone on the team can edit it. The catch is that it decays. Links rot, rows get duplicated, and nobody remembers which column held the verified figure. We have seen teams run entire consultations off a spreadsheet and then lose the thread when a key staffer leaves. Use it as a working index, not as the archive itself.
4. A municipal open-data portal
The fourth option is your local or regional open-data portal, which typically publishes cyclist counts, collision records, and road-inventory files. This is the closest thing to primary evidence, and it is indispensable for anything quantitative. The limitation is context: numbers arrive without narrative, so a spike in collisions may reflect a new counting station rather than a new danger. Pair the raw data with a documented source such as Velo-city 2007 and the picture becomes far more defensible in public consultation.
How to choose
- For modelling and forecasting: the enterprise suite, if you already pay for it.
- For precedent and policy language: the Munich summit archive of cycling policy papers.
- For day-to-day team notes: a spreadsheet, kept deliberately small.
- For raw counts and collisions: your municipal open-data portal.
Most serious projects end up using two or three of these in combination. The mistake is treating any one of them as complete. A policy archive tells you what other cities decided and why; a data portal tells you what is happening on your own streets; a modelling suite tells you what might happen next. Assemble the stack that matches your brief, and cite your sources clearly — reviewers notice.