Council did not approve construction. It referred the project to the City Manager and told staff which design to work from. The money has not been appropriated and no contract has been awarded — both are separate Council votes, still ahead, taken by a council that will include whoever wins in November. So I'm not going to tell you how this ends. Below: why I'd have voted the way I would have, what's actually left to decide, and what I'll do in each case that can happen.
Nothing about Hopkins Street came before Council on September 15 or 29, and nothing is on the October 13 agenda. The report-back on another corridor redesign, two grant resolutions and the traffic-count contract all passed on consent or as information.
The City Manager’s response to Council’s October 28, 2025 motion on refinements to the Telegraph Multimodal Corridor Project design was received and filed as an information report. Same sequence as Hopkins: a design approved, a motion to change it, a report back afterwards, and no discussion of the report on the dais.
Resolutions 72,450, 72,451 and 72,452-N.S. back the Alameda County Transportation Commission applications, including the Sacramento Crossings Improvement Project and the North and West Berkeley Safe Routes to Schools Project, both in or beside District 1. The applications went in during July; Council’s support is dated September 29.
IDAX Traffic Data, LLC, Resolution 72,454-N.S. This page argues that the counts belong before the asphalt. This is the contract that buys the counts.
Resolution 72,457-N.S. accepts the Transportation Fund for Clean Air grant. A quick-build is the low-cost, reversible version of the treatment Hopkins received in concrete.
Filed under “Hopkins” in the communications section. Communications are public record and are not decisions. No Hopkins item is on the October 13 agenda.
Outcomes come from the City Clerk’s annotated agendas. Sources: the September 29 annotated agenda, the September 15 annotated agenda and the October 13 Council agenda, posted October 1.
No on the Hopkins bike lane design. Yes on comparing it to the other route first. Berkeley has two plausible ways to connect North and West Berkeley by bike: Hopkins itself, or a route a few blocks over on Ada and Rose. Councilmember Brent Blackaby, co-sponsored by Councilmember Bartlett, moved to have staff work the Ada/Rose route up properly and lay both options side by side before the city committed to either. It would not have delayed the repaving or the bike lanes by a single day, because Hopkins isn't due for repaving until 2027–28. It lost by one vote. Berkeley declined to spend zero extra days finding out whether the other route was better. That's the vote I'd want back.
The operative words in the item are "refer to the City Manager." Council told staff which design to work from and sent them off to do the engineering. That is a strong instruction and I won't pretend otherwise — but it is not an approval to build, and it did not spend a dollar. The project has been widely described as settled, in relief and in anger. It isn't.
One-way Class IV separated bikeways became the "established foundation" design for the work staff now advances into detailed engineering. Staff aren't starting from a blank page, and a future council reversing course would be overriding a standing direction, not filling a vacuum. But what Council adopted was an instruction to design, not a decision to build.
The stakeholder outreach, the curb management plan, the real cost estimate, the Fire Department's analysis of the full design set, the evacuation sensitivity study. Every one of those produces information that did not exist on July 28. This is the stage where the project either firms up or develops problems, and it happens mostly out of public view.
The adopted item directs staff to "immediately identify and secure funding" — which tells you the funding isn't secured. Appropriating it is a Council action, on a public agenda, with a roll call. A project priced somewhere between $14 and $20 million has to find that money in a city carrying a structural deficit, and that conversation hasn't been had.
Berkeley Municipal Code §7.18.010: expenditures for public improvement projects over $200,000 require Council approval. A Hopkins construction contract will exceed that by roughly two orders of magnitude. There will be a vote, in public, with an engineered design and a real number attached — which is exactly the vote that should have had those things the first time.
Seats change in November, including this one. I'm not going to dress that up as a promise to stop the project — a standing Council direction carries real weight and staff will advance it. But anyone telling you the Hopkins question is closed is describing a process that hasn't happened yet.
Because the framing decides the behavior. If July 28 was final, the only options left are celebration or resentment, and the next two years are a grudge. If July 28 was a referral with funding and contract votes still ahead — which is what the record says — then the useful thing anyone can do is make sure those votes arrive with honest numbers attached. That's work, it's available to residents on both sides, and it starts now rather than after the pavement is cut.
This gets argued as cyclists against seniors, or bikes against businesses. That framing is wrong, and it's why the argument never ends. Hopkins is one street of fixed width and one response clock, and every foot and every second allocated to one kind of safety comes out of another. Nobody is against safety. People are weighing different safeties, and the city has named every one of these tradeoffs in its own documents without attaching a number to any of them.
Repaving doesn't move the curbs. A protected bikeway, two travel lanes, parking, loading zones and ADA spaces all draw from the same curb-to-curb feet. Fire's stated needs are specific: 11-foot travel lanes preferred, 10.5 feet minimum acceptable, and 26-foot curb-to-curb within 20 feet of a hydrant wherever feasible. Under the 2023 design, fire staff found roughly four blocks below the preferred 11 feet though still at or above the 10.5-foot minimum. The margin on this street is measured in inches, and whoever gets those inches is a decision, not a formality.
Raised crosswalks and traffic calming protect people crossing the street by making vehicles slow down. Fire engines are vehicles. The city's own April 2026 materials say so directly: a raised crosswalk "will slow emergency vehicles," which the city calls "a pragmatic trade-off." It may well be the right trade. How many seconds has never been published — and seconds are the unit that matters to somebody having a heart attack on Hopkins.
A protected lane works because it is uninterrupted. Accessible drop-off works because it happens at the door. Every ADA space, loading zone and short-term space is a deliberate interruption of the first thing in service of the second. That's the curb management plan the direction defers — and it is where "cyclists versus seniors" stops being a slogan and becomes a solvable list of specific locations.
Hopkins feeds a hills-adjacent street network, and a narrower or reconfigured roadway behaves differently when several thousand people leave at once. The city's answer in April was a sensitivity study that will incorporate the design into Berkeley's evacuation model — future tense, and still unpublished.
If the choice is safety versus parking, one side is simply wrong and the fight is worth having forever. If the choice is inches and seconds between four kinds of safety, it is an engineering problem with an answer — and the answer can be measured, published, and checked afterward. That is the entire difference between this page and the last eight years of argument about this street.
The direction went the other way from where I'd have taken it, and the design phase will decide a lot of what happens next. These six things are owed whether the Class IV design proceeds as drawn, comes back changed, or never gets funded — which is exactly why I'd push for them either way. What it costs block by block, who verifies it, and whether the record behind it holds up are answerable now. The motion promises refinement; refinement without numbers is a mood. Each ask is a target and a report — nothing more.
One row per block of Hopkins, one column per tradeoff, published and kept current as the design changes: parking spaces today and after; where ADA spaces land; loading zones and delivery windows; how waste collection operates; driveway conflicts; trees affected; Fire Department signoff status; segment cost and funding source. The curb management plan the motion already requires contains all of this — the ask is that it be published as one plain table before the design locks, not summarized in a report after.
"Refine the design" needs limits to mean anything. The design should state what parking loss it budgets for, what tree removals, what cost ceiling — and what post-construction result (collisions, speeds, merchant indicators, transit delay) would trigger modification. A yes vote that can't name its thresholds hasn't finished deciding.
On July 28 the Fire Chief said his department would analyze emergency-vehicle turning movements, evacuation-time impacts, and access on and near Hopkins once Public Works produces a full design set. That analysis is the substantive one. But the adopted direction's engagement list names businesses, schools, houses of worship and residents — not the Fire Department — and the written fire approval already in the record is narrower than it sounds: it covers the proposed traffic-calming features under Berkeley Fire Code §503.4.1, plus a lane-width review. So the stage where the Chief said the real analysis happens carries no requirement that it happen, and no requirement that it be published. One sentence in a motion fixes that: BFD review of the full design set, with the turning-movement analysis and the evacuation sensitivity study released as public documents before construction.
Parking occupancy by block and time of day; loading and delivery patterns; accessible-space usage; traffic speeds and volumes; the tree inventory; merchant indicators where businesses volunteer them. Measure it now, re-measure after construction, publish both — whichever way the comparison cuts. If the predicted harms don't materialize, the after-data will say so, and so will this page. Once the pavement work starts, the clean baseline is gone for good.
The correspondence Council received is a ready-made row list: concern raised → staff response → how the engineered design treats it → what the after-data shows. That turns the most extensively warned-about street project in recent Berkeley memory into the best-documented one — and it gets more informative every year it runs.
The Clerk's communication packets show what Council was told from outside. How the proposal developed inside — the alternatives weighed, the staff cautions, the cost work — is the half a $15–20 million decision still owes the public, and it's the half that tells you how the coming design process will actually be run. A resident's Public Records Act request produced the Clerk packets; the City closed the request there. The internal record is still owed. I'll press for its release, and this page will link it the day it appears.
Not a campaign to reverse the direction. I've told you where I'd have come down and I've told you I wasn't there to say it — both of those are true, and I'd rather you have them than a story where I was right all along. A councilmember whose only move is relitigating decisions made before he arrived is useless to everyone, including the people who agreed with him. Every ask above would improve this project if it proceeds as designed, and every one would apply just as hard to my own preferred alternative if it ever came back. That's the point. If I have a date or a number wrong, tell me and the page changes.
"Detailed engineering" sounds like a technical formality. It isn't. It is where every question the direction left open gets an answer — usually one block at a time, usually without an agenda item, and usually without anyone outside Public Works watching. Here is the sequence, and the question that decides whether each stage went well.
The direction requires outreach to businesses, schools, houses of worship, residents and other stakeholders. The test: is there a published list of who was consulted, what they said, and what changed in the design because of it? Outreach that produces no visible design change is a mailing list, not a process.
Loading zones, short-term parking, ADA space placement, waste collection, metered parking, RPP expansion. The test: does it arrive as one plain table covering every block — spaces before and after, where each ADA space and loading zone actually lands — and does it arrive before the design is locked, when changing it is still cheap? (Ask 01.)
The $14–20 million range becomes a real number here, and this is the stage the Fire Chief named for the turning-movement, evacuation-time and access analysis. The test: is the segment cost published with the design and its funding source named; does the design state what parking loss, tree loss and cost it budgets for, so that exceeding them is visible rather than absorbed; and does BFD's review of the full design set get released as a public document rather than described second-hand? (Asks 02 and 03.)
By this point the pre-construction street is gone as a measurement. The test: was the baseline captured first — parking occupancy, loading patterns, accessible-space use, speeds, trees, merchant indicators — and is there a committed date to publish the after-numbers next to it? (Asks 04 and 05.)
Every item above was raised in writing to Council before the direction was adopted, by people who live and shop on this corridor: parking and curb access, disabled and senior access to the market district, deliveries and waste pickup, driveway sightlines, trees, traffic diverted onto neighboring streets, emergency access, and cost. The record is specific, and it is public. Treating it as a checklist for the design process is worth more than treating it as a scoreboard for a decision already made.
Everything above assumes the decision itself was arrived at properly. Several people who have followed this corridor far longer than I have say it wasn't — that the underlying data was wrong, and that the City did not follow its own adopted rules. I take that seriously enough to check, and checking has turned up three things I can document and one I can't. They are set out here, unresolved, rather than left out because they're inconvenient to a tidy page.
Berkeley's Complete Streets Policy, adopted by Council on December 11, 2012, is not advisory. It says departments "shall perform annual programmatic evaluations" collecting baseline and follow-up data, that a coordinator "shall develop appropriate performance metrics," and that the Public Works Director "shall provide an annual Complete Streets Policy Implementation Report to City Council." Searching the City's published documents, I could find no such implementation report. That matters twice over: it is the same before-and-after measurement this page asks for in Ask 04, and Berkeley committed to it fourteen years ago. If those reports exist and I've missed them, I will link them here and say so.
The same policy states that the Bicycle and/or Pedestrian Subcommittees "shall be consulted early in the planning and design stage," and that projects seeking an exemption from the policy must produce a written finding with written approval from the Public Works Director. I have not been able to establish from published minutes when, or whether, that early consultation occurred for Hopkins, or whether any exemption finding was ever made. This is a records question with a definite answer.
The January 23, 2018 referral that began all of this asked for a Hopkins Corridor Traffic and Placemaking Study — a corridor-wide look. Councilmember Sophie Hahn, who authored that referral, later said publicly that staff ran a process "mainly focused on the bike lane" rather than the holistic and comprehensive review she had requested. That is the referral's own author saying the delivered work was narrower than the direction. It is a characterization, not a finding — but it is the sponsor's, and it has never been formally answered.
The three-year halt came through an off-agenda memo from the City Manager in April 2023, not a Council action. Work Council had directed was set aside, and the public record contains two different explanations for why — staffing vacancies in that memo, emergency-access objections in later accounts. A City Manager controls staff assignment, so this is not obviously a rule violation. It is, however, three years of a Council direction going unperformed with no public vote and no reconciled reason.
The most serious claim made to me is that the counts and analysis underlying the original design were incorrect, and that a flawed foundation carried forward into what Council adopted. If true, it would matter more than anything else on this page. I have not found documentation establishing it, and I will not publish it as fact on the strength of assertion — not even assertion I'm sympathetic to. If you have the documents, send them. I will read them, and this section will say what they show.
A campaign page that only listed the questions it could already answer would be a worse document than this one. Three of the five items above are sourced to the City's own adopted policy and its own record. One is unresolved. Publishing the unresolved one as though it were settled would make this page exactly the kind of thing it criticizes. This section will change as documents arrive, and the changes will be visible.
After pedestrian fatalities on the corridor, Councilmember Sophie Hahn's budget referral initiates the Hopkins Corridor Traffic and Placemaking Study. Community process begins October 2020; design workshops run through March 2022.
Council approves a Hopkins plan with protected bike lanes, then agrees within months to reconsider portions of it amid objections over parking removal and disabled access. The fight becomes one of the most bitter in recent Berkeley memory.
An off-agenda memo from then–City Manager Dee Williams-Ridley pauses the project, citing vacancies in Public Works' Transportation Division. The pause holds for three years. Note the discrepancy: the memo of record gives staffing as the reason, while later reporting and the July 2026 Council item both describe Fire Department emergency-access objections as what stalled the project. Two accounts of the same three years, and they have never been reconciled in public.
A council referral revives the paving project with pedestrian-safety improvements only — no bike lanes. Three years after the pause, the corridor is back in process.
The policy committee sends the paving item to Council with a qualified negative recommendation — reject unless amended to include protected bike lanes from Sutter to Gilman. The design question is back open, and the version that reaches Council in July is written to answer it.
The same day, Public Works and the Fire Department present jointly on two alternatives. This is where the emergency-access record is actually made: "Fire has approved them per Section 503.4.1 of the Berkeley Fire Code" — "them" being the proposed traffic-calming features — plus a lane-width review (11 feet preferred, 10.5 minimum; roughly four blocks under the 2023 design fall below the preferred width while still clearing the minimum), and a hydrant rule of 26 feet curb-to-curb within 20 feet, "whenever possible." Evacuation impact is left to a sensitivity study that will be run against the city's evacuation model.
Council refers the project to the City Manager, naming Class IV separated bikeways as the established foundation design, with stakeholder engagement and a curb management plan to follow during detailed engineering. Alternative approaches are put forward and rejected. A substitute amendment from Councilmember Blackaby, co-sponsored by Councilmember Bartlett — develop a viable alternative through the Hopkins/Ada/Rose corridor and compare the options side by side, without delaying the repaving — fails by one vote. The Fire Chief tells Council his department will analyze emergency-vehicle turning movements, evacuation-time impacts and access on and near Hopkins once Public Works produces a full design set — that is, the substantive emergency-access analysis is ahead of the project, not behind it. The item itself states that the fire safety objections which contributed to the pause "no longer exist."
The City produces the Clerk's communication packets in response to a resident's Public Records Act request, then closes the request. The internal decision-making record — office communications, staff cautions, alternative development — remains unproduced. Still owed.
The four stages above — engagement, curb management plan, detailed engineering and costing, then construction with the repaving, currently indicated for 2027–28. None of them carries a posted public date yet. That is precisely why Asks 01–04 belong on the record now, before the design locks.
I don't know how the design phase ends, and neither does anyone telling you they do. So here is what I'll do in each case that can actually happen, written down now, before any of it is known — including the case where I turn out to have been wrong.
Collisions down, businesses steady, access preserved, cost near estimate — then the design was right and my judgment was wrong, and this page will say that plainly rather than quietly going stale. I've spent twenty-five years verifying whether claimed results were real. That's worth nothing if I only publish the verifications that flatter me.
If parking loss guts the market district, if response times slip, if disabled access gets worse, the before-and-after numbers turn that from an argument into a finding. Then the job is remediation on the record — loading zones added, curb management revised, signal timing corrected — not a victory lap. This is why Ask 04 matters more than anything else here: without a baseline measured before construction, nobody can prove harm or disprove it, and we'll be having the 2022 argument forever.
If the engineering comes back at a number the city can't carry, or the fire and evacuation findings are bad, the appropriation or the contract award is where that shows up — and then some version of my preferred package is back on the table. If that happens, repaving with painted lanes and enforcement has to clear exactly the bar I'm setting here: what it costs, what it changes block by block, what safety result it promises, and who measures whether it delivered. I don't get to demand evidence from the design I dislike and wave through the one I prefer. If my alternative can't show its numbers, it doesn't deserve the vote either.
Hopkins is eight years of a city arguing about a street without ever agreeing on what would count as evidence. I'd have voted differently. But the thing that actually went wrong here isn't which design won — it's that Berkeley committed in 2012 to measuring what its street projects do, and then didn't. Fix that and the next Hopkins is a shorter, calmer, better-informed argument. That's the job I'm asking for.
Everything on this page is sourced to a public document or named press account. If you think I've read one of them wrong, tell me and I'll correct the page.