Item 27 asked Council to commit Hopkins Street to one-way Class IV separated bikeways on both sides of the street. The recommendation's opening clause made a Fire Department finding the stated predicate for the entire referral: “Given new information presented by the Fire Department that pedestrian and bike safety infrastructure on Hopkins Street 'retains workable emergency access,' refer to the City Manager to repave Hopkins Street… with inclusion of one-way Class IV separated bikeways on each side.”
Page 7 of the item carries the heading “Updated Review by Fire Department Shows Class IV Separated Bikeways Can Retain Workable Emergency Access,” and states that the fire safety objections which had paused the project since 2023 “no longer exist.”
At 01:31:48 elapsed — roughly four hours before the vote — Fire Chief David Sprague was asked directly for the Fire Department's position. He said the Department had not reviewed the configuration before Council.
The Council adopted the plan 7–2 at 06:15:05.
1. What the item claimed — Agenda Packet p.7 of 28, on Councilmember Kesarwani's office letterhead:
“Updated Review by Fire Department Shows Class IV Separated Bikeways Can Retain Workable Emergency Access… Fire staff have confirmed that lane widths of 11 feet preferred and 10.5 feet minimum are acceptable—the same widths that a one-way Class IV separated bikeway configuration on each side of Hopkins would maintain. The fire safety objections that contributed to the indefinite pause of this project… no longer exist.”
2. What the Fire Chief said — live testimony, 01:31:48 elapsed:
“FIRE has reviewed and approved the traffic calming features in the Hopkins Alternative 1 and 2… We also generally have confirmed that lane widths… are acceptable. However, for the new… proposed configuration that you're discussing tonight… There is not a design yet, so we have not seen that, we have not reviewed it, and we would need a complete design set from Public Works. Once that's available, we can evaluate… potential impacts to evacuation times, and confirm that design maintains workable access for day-to-day fire and medical emergencies.”
Asked how long that review would take, Sprague said two to four weeks once Public Works delivers a complete design set.
3. What the item's own footnote points to — the quoted phrase “retains workable emergency access” is sourced in footnote 1 to “Hopkins Street Alternatives 1 and 2 Overview,” FITES Policy Committee, April 15, 2026. That document uses the phrase exactly twice, and scopes it explicitly both times:
“Fire: Alternative 1 retains workable emergency access overall.”
“Fire: Alternative 2 retains workable emergency access overall.”
The two alternatives the Fire Department actually reviewed were not the plan Council adopted.
| Configuration | Description | Fire reviewed? |
|---|---|---|
| Alternative 1 | A two-way cycle track on one side, Gilman–McGee and Josephine–Sutter; ~84 parking spaces repurposed; $14–15M | Yes |
| Alternative 2 | Pedestrian safety only — crosswalks, refuge islands, bulbouts, sharrows; no protected bikeway; $11–12M | Yes |
| Adopted July 28 | One-way Class IV separated bikeways on both sides, The Alameda to Peralta/Ohlone Greenway | No |
The FITES source document mentions a cycle track exactly once, describing Alternative 1's two-way design. The one-way-both-sides configuration is a third geometry that document never evaluated. Sprague confirmed as much: his approval covered Alternatives 1 and 2 and the lane-width standard in the abstract, not the design on the table.
The item's move is an inference presented as a finding: Fire approved certain lane widths → the Class IV configuration would use those widths → therefore Fire's approval extends to Class IV. Sprague rejected that inference on the record the same evening. Lane width is one input to emergency access; the Chief identified evacuation-time impact and day-to-day apparatus access as the questions still requiring evaluation.
A search of the complete July 28 agenda packet returns zero instances of “has not been reviewed,” “not yet reviewed,” “pending fire review,” or “subject to fire review” in connection with this item. The written record contains no qualification. It asserts the opposite — that the fire safety objections “no longer exist.”
The claim also carries budgetary weight. The item's Fiscal Impacts section states that the February 2026 pedestrian-only version “was based on our prior understanding of the need for significant infrastructure upgrades to meet concerns raised by the Fire Department,” and that “With Fire concerns addressed without the need for costly infrastructure upgrades,” the added cost is worth bearing. The unreviewed fire finding is therefore the stated basis for both the design choice and an approximately $3–4 million increase, from $11M to $14–15M.
Kesarwani authored the item, wrote the page 7 heading, supplied the footnote, and led the item through the meeting. The heading asserts a Fire Department review of Class IV separated bikeways. The footnoted source evaluates Alternatives 1 and 2 and scopes its finding to each by name. The Fire Chief stated on the record that the adopted configuration had not been reviewed.
Her spoken remarks were narrower than the written item and, read alone, defensible: at 01:08:51 she said the April FITES committee “confirmed that bike safety infrastructure on Hopkins retains workable emergency access,” calling it “a significant development that made this item possible.” That is a fair characterization of the April finding. What she did not do — in remarks, in the item, or after Sprague's testimony — was tell Council that the configuration in front of them was outside the scope of that review.
The severity here is not the inference itself. Councilmembers advocate, and reasoning from an approved lane-width standard toward a compatible design is a legitimate argument to make. The severity is that it was presented as a completed Fire Department review in the operative clause of a binding referral, in a heading, and in the fiscal justification — and that after the Chief publicly corrected the record four hours before the vote, neither the item nor its author was amended to reflect it.
This is the most consequential documented accuracy failure in the scorecard period. It concerns emergency access and evacuation on a designated Emergency Access and Evacuation Route in a city whose own wildfire planning identifies constrained ingress and egress as a core vulnerability. It supplied the stated basis for a multi-million-dollar cost increase. And it was contradicted by the responsible department head, in public, before the vote it was used to secure.
Both co-sponsored the item and both voted for it after hearing Sprague's testimony. Neither moved to amend the recommendation's predicate clause, to hold the item pending the two-to-four-week review the Chief described, nor to correct the page 7 characterization.
Their culpability is materially lesser than the author's — they did not write the claim — but a co-sponsor who hears the responsible department head contradict the item's stated basis and proceeds without addressing it has adopted the claim.
Not a finding that the project is unsafe. Sprague did not say the configuration would fail review. He said it had not been reviewed and that the Department needed a complete design set to evaluate evacuation impact and apparatus access. The design may well pass. The finding is that Council was told the question was settled when it was not.
Not a finding about intent. The record establishes what the item said, what its source said, and what the Chief said. It does not establish whether the mischaracterization was deliberate, a genuine misreading of the April findings, or advocacy that outran its evidence. No motive is asserted here.
Not a challenge to the safety case. Kesarwani's collision analysis for the corridor — a pedestrian fatality, severe bicycle injuries, and a severe pedestrian injury at identified intersections — was the most disciplined problem definition offered at the meeting and is unaffected by this finding.
One element remains unverified. A speaker quoted Sprague from the April FITES meeting audio as saying of bike lanes and emergency response, “it feels risky to me. I don't know that it's not an option, but it doesn't feel super safe.” That audio has not been reviewed for this record and the quotation is not relied on here.
A councilmember may argue that a design will satisfy the Fire Department. A councilmember may not tell Council that the Fire Department already has.
Berkeley's council operates on staff findings it cannot independently verify. Nine members cannot re-derive fire code compliance, evacuation modeling, or apparatus clearance; they rely on the record in front of them being an accurate account of what the responsible departments have concluded. That reliance is the entire basis on which a part-time legislature can govern a technical city. An item that presents an inference as a completed departmental review does not merely overstate a point — it defeats the mechanism by which the body checks itself.
The failure here was also uniquely recoverable, which is what elevates it. This was not an error discovered months later in an audit. The Fire Chief stated the correction in open session, in response to a direct question, four hours before the vote. Any member could have moved to hold the item for the two-to-four-week review Sprague described. Blackaby's analysis-first substitute would have accomplished nearly that and failed 4–5. The Council had every fact it needed and voted on the original predicate anyway.
The subject matter compounds it. Hopkins is a designated Emergency Access and Evacuation Route. Berkeley's Community Wildfire Protection Plan identifies narrow streets, constrained ingress and egress, and evacuation capacity as core vulnerabilities. Fire Department concerns are what paused this project in 2023. Telling Council those concerns “no longer exist,” when the department had not evaluated the geometry being adopted, removes the one check specific to the risk the corridor actually carries.
Two members — O'Keefe and Blackaby, representing the districts that bear the consequences — voted no. The seven-vote majority that carried the item rested on a stated finding that the Fire Chief had already told them was not a finding.