Bakersfield Pulled a Radio Consulting Proposal Whose Fixed Price Depended on an October 1 Start

The withdrawal changes how the financial terms should be read

Bakersfield’s September radio-consulting proposal priced 15 months of work at $263,880, but its cost assumptions required a start on or before October 1. The council removed the item on September 16. The October 7 regular-meeting agenda, reviewed October 6, does not list the Federal Engineering agreement for renewed consideration. These records do not establish that the city approved the proposed direct contract or authorized work under it.

What’s the Scoop With Broach compared the staff report, proposed main agreement, attached scope and pricing conditions, September 15 withdrawal memo and draft council minutes. The original finding concerns the relationship among three different controls: a base price, a higher spending ceiling and a timetable that could trigger a negotiated increase. Treating the agenda’s $400,000 figure as a bill already incurred would misstate the record.

The proposed ceiling exceeded the priced work by $136,120

The staff report described an initial $263,880 fee and a $400,000 maximum. Subtracting the fee from the ceiling leaves $136,120—51.6 percent above the base amount. That arithmetic measures room beneath a proposed ceiling, not a contingency that the consultant could automatically collect.

The scope calls for fifteen monthly invoices of $17,592. The main agreement adds a substantive payment condition: the city must approve an itemized invoice for completed portions of the work. It also includes out-of-pocket costs and taxes in compensation. A monthly invoice schedule therefore should not be described as unconditional payment independent of performance.

The consultant’s August 13 cost assumptions say city or third-party delays can increase costs and require a mutually agreed written amendment. The main agreement goes further: modifications require City Council approval and signatures from all parties. Passing the assumed October 1 start date does not itself establish an increased price, a debt or a revised agreement.

A change in contracting route, without a documented savings comparison

The city’s draft recitals say Kern County requested high compensation for continued access to consulting through the county’s contract. Staff proposed a direct agreement instead, with a project manager dedicated to the city. The reviewed packet does not quantify the county’s requested amount. It therefore cannot support a calculation that the direct proposal would save taxpayers money.

The proposed work includes factory testing, equipment-delivery checks, coverage and system testing, acceptance, cutover and closeout. The scope ties acceptance recommendations to successful testing and correction of deficiencies. Those duties create a record readers could later test against invoices and deliverables, if a contract is approved. They do not prove that any acceptance tests have already occurred.

The main agreement controls conflicting attachments

The packet contains broad consultant terms alongside city protections. Section 14 says the main agreement prevails where an exhibit conflicts with it. The main agreement also contains indemnity, insurance and professional-standard provisions. Quoting a restrictive exhibit clause alone as the city’s final liability position would omit that controlling hierarchy. This is a comparison of proposed text, not a judicial interpretation of enforceability.

A September 15 memo requested removal to allow additional staff review. Draft minutes submitted for October 7 approval record that the consent calendar passed with this item removed. They identify the action taken, although the minutes themselves awaited approval at the time of this review.

No interviews, invoices, executed replacement contract or written notice to proceed were obtained. The public-interest question remains concrete: if a revised proposal returns, does it disclose the new schedule, any changed base price, the county alternative and the deliverables governing payment? The September packet establishes those decision points; it does not establish a completed procurement.