Before the Solicitation: Five Local-Government Procurement Timelines

Approved public records can identify a funded category, pilot, renewal, or authorized delivery method before a solicitation appears. Linking those records can reduce research time. It does not reveal private buyer conversations, settle the final scope, predict timing, or indicate who will receive an award.

Five traced cases make both points. The selected upstream record preceded the first later procurement milestone by 73 to 839 calendar days. That spread is a warning, not a benchmark. Processes were canceled, reissued, extended, and sometimes drew only one proposal.

The five observed paths

San Bernardino: funded, canceled, reissued, awarded

On June 10, 2025, the San Bernardino County Board approved the 2025-26 County Budget. Later project records identify a $52,510,997 approved budget for an Arrowhead Regional Medical Center parking structure. On August 19, the Board authorized design-build delivery and procurement steps.

The RFQ was released August 22, 73 days after the budget. Six qualification submissions arrived. An RFP went to three prequalified teams on November 19, and three proposals arrived on December 16.

The path then broke. On February 9, 2026, all proposers were told that the RFP was canceled because the review found defects affecting the validity of the evaluation. The County reissued the RFP on March 4, received three proposals on March 31, and sent a notice of award on June 3. The Board approved a $45,860,723 agreement with Bomel Construction on June 23. The award report documents the cancellation, reissue, protest, and award chronology.

The observed budget-to-award interval was 378 days. Funding and delivery authorization did not protect the first procurement from cancellation, and the award record does not establish construction completion.

Phoenix: renewal, failed RFP, extensions, later award

On June 17, 2020, the Phoenix City Council adopted Ordinance S-46745, extending a property-management agreement through June 30, 2021. Its report also records that a December 2019 RFP received one proposal and was canceled.

A new RFP, PTD20-009, was issued January 6, 2021, 203 days after the selected renewal. Both offerors were disqualified, and the City canceled the solicitation on April 2. Council approved another extension on June 2, 2021 and further extensions on April 20, 2022.

The cancellation did not mean permanent abandonment. On April 9, 2025, the Council approved a five-year award after evaluation of four responsive proposals. The selected 2020 renewal was 1,757 days before that award. A renewal record did not identify a reliable competition date or outcome.

Sunnyvale: a pilot and extensions before one proposal

On January 25, 2022, the Sunnyvale City Council approved Budget Modification No. 15. The approved plan included $500,000 for temporary housing and homeless services. A contemporaneous May 3, 2022 record authorized a direct HomeFirst pilot agreement. Services began June 1, and the Council later extended the pilot.

On February 27, 2024, the Council approved another amendment and explicitly directed staff to prepare an RFP. RFP F24-20 was issued May 13, 76 days later and 839 days after the original pilot funding. One proposal was received. On August 13, the Council approved a one-year award to WeHOPE, with optional renewals, in the award record.

The later award report says the first HomeFirst agreement was authorized May 10, 2022. The contemporaneous file and meeting record show May 3. This audit uses May 3 for that intermediate event and preserves the discrepancy. The public path was a direct pilot, extensions, explicit RFP direction, a one-proposal competition, and an award, not a simple budget-to-RFP sequence.

Fresno: grant appropriation to a design award

On October 20, 2022, the Fresno City Council accepted and appropriated a $496,874 CPUC Local Agency Technical Assistance reimbursement grant in File 22-1608. The City released RFQ 12303131 for last-mile broadband design engineering on June 23, 2023, 246 days later. Three proposals were submitted.

On November 16, the Council approved a $496,874 consultant agreement with Magellan Advisors. The award report supplies the RFQ chronology, and the evaluation attachment documents the scoring. The 392-day appropriation-to-award interval ended in a design-engineering contract, not a broadband construction award or proof that a complete network would be built.

Long Beach: recovery allocation to a concluded pilot

On August 24, 2021, the Long Beach City Council approved Recovery Act allocations and appropriations. A later award report identifies $1,151,400 for the micro-transit sub-program.

RFP PW22-067 was released May 2, 2022, 251 days after the allocation. The City published its public announcement on May 3. One proposal was received. On September 13, the Council approved an award to Circuit Transit. The allocation-to-award interval was 385 days.

The City now labels the program Concluded December 2024. The upstream record was relevant to the procurement, but it did not say how many proposals would arrive, establish the award outcome, or make the pilot permanent.

A document-level false positive

Sunnyvale's June 20, 2023 budget record has an overall status of Passed. Its text says a proposed $149,240 short-term-rental enforcement pilot did not pass and that staff would continue with existing resources.

A keyword match for short-term-rental enforcement pilot combined with the page-level status would manufacture an authorized project. The action must be resolved at the amendment or sub-item level before it enters a procurement watchlist.

What these timelines support

• Approved budgets, grants, pilots, renewals, and delivery authorizations can identify a relevant category before a later solicitation.
• Exact project names, solicitation numbers, contract numbers, and funding cross-references can support a public decision arc.
• Cancellation, extension, reissue, limited competition, award, and later program status all belong in the same record.
• Sub-item interpretation matters when a passed document contains a proposal that failed.

What they do not support

• The 73 to 839 day range is not a benchmark, expectation, or forecast.
• No record establishes private buyer intent, preferred vendors, vendor access, or causal influence.
• No upstream event predicts that a solicitation will occur or that the first solicitation will survive.
• No award approval proves completed delivery or project success.
• The set is not geographically representative: four cases are in California and one is in Arizona.

A minimum procurement decision arc

A usable procurement-intelligence record should preserve the approved upstream action, funding or authority, project and solicitation identifiers, actual release date, response count when public, cancellation or protest, reissue, extension, award action, later implementation status, and every source link. Observed intervals should be calculated from explicitly named events and labeled as descriptive.

Sources and method

Sources were checked through August 3, 2026. Governing-body action dates and actual release dates were preferred over webpage publication dates. Contemporaneous records were preferred when a later summary conflicted.

1. San Bernardino County: budget action; design-build authorization; cancellation, reissue, and award chronology.
2. Phoenix: 2020 renewal; failed-RFP chronology and 2022 extension; 2025 award.
3. Sunnyvale: pilot funding; RFP direction; award and procurement chronology; later status.
4. Fresno: grant appropriation; award and RFQ chronology; evaluation attachment.
5. Long Beach: recovery allocation; program announcement and later status; award chronology.
6. False-positive check: Sunnyvale budget record.

This is a public-record research example. It is not procurement, contracting, legal, lobbying, or sales advice, and it does not predict a solicitation or award.