San Francisco Government Contracting: Procurement Rules and Process

San Francisco operates one of the most structured municipal procurement systems in California, governed by a layered framework of local ordinances, the City Charter, and state law. This page covers how the City and County of San Francisco awards contracts for goods, services, and construction; the rules that govern competitive bidding; local preference and equity requirements; and the decision points that determine which procurement pathway applies to a given contract. Understanding this framework is essential for vendors, community organizations, city departments, and oversight bodies.

Definition and scope

Government contracting in San Francisco refers to the formal legal process by which the City and County of San Francisco enters binding agreements with private vendors, contractors, and nonprofit organizations for the purchase of goods, professional services, and public works construction. The authority to contract is derived from the San Francisco City Charter, which assigns procurement oversight primarily to the City Administrator's Office of Contract Administration (OCA) and the San Francisco Controller's Office.

The procurement framework is codified in the San Francisco Administrative Code, particularly Chapter 6 (Contracts for Services), Chapter 21 (Construction Contracts), and the San Francisco Environment Code, which imposes environmental requirements on purchased goods and services. The San Francisco Ethics Commission enforces related conflict-of-interest and lobbying restrictions that intersect with the contracting process.

Scope boundaries and limitations: This page addresses contracting conducted by City and County of San Francisco departments and commissions. It does not cover procurement by the San Francisco Unified School District, the San Francisco Community College District, or independent special districts such as the Bay Area Rapid Transit District (BART), which operate under separate enabling statutes. State contracts awarded through California's Department of General Services also fall outside City procurement rules, even when the work is performed within San Francisco. Federal pass-through grants introduce additional requirements from the Uniform Guidance (2 CFR Part 200) that supplement but do not displace local rules.

How it works

The San Francisco procurement process follows a tiered structure based on contract dollar value and type. The San Francisco Annual Budget Process appropriates departmental funds that departments then deploy through contracts, subject to OCA review and Board of Supervisors approval thresholds.

The general contracting pathway operates as follows:

  1. Needs determination: A city department identifies a requirement and prepares a scope of work or technical specification.
  2. Procurement method selection: OCA or the department determines the applicable solicitation method based on contract type and estimated value.
  3. Solicitation issuance: The City posts Invitations for Bid (IFBs) for construction and commodity purchases, or Requests for Proposals (RFPs) for professional and consultant services, through the City's online procurement portal (SF City Partner).
  4. Evaluation and award: Bids are evaluated on price (IFB) or a combination of price and qualifications (RFP). Construction contracts above $10,000 require competitive sealed bidding under Administrative Code Chapter 6.
  5. Board approval: Contracts exceeding $10 million generally require approval by the San Francisco Board of Supervisors before execution.
  6. Contract execution and monitoring: OCA registers executed contracts; the Controller's Office audits expenditures and monitors compliance.

Local Business Enterprise (LBE) preference is a mandatory overlay administered by the Human Rights Commission (San Francisco Human Rights Commission) under the San Francisco Vendor Utilization Program. LBE-certified firms receive bid price adjustments of up to 10 percent on most city contracts, and departments must meet annual LBE subcontracting goals on larger contracts.

IFB vs. RFP — the key distinction: An Invitation for Bid awards solely on lowest responsive, responsible bid price. A Request for Proposals allows the evaluation committee to weigh technical approach, organizational capacity, and price together. Construction contracts default to the IFB model; professional services, IT, and social service contracts use the RFP model.

Common scenarios

Three procurement scenarios account for the majority of city contract activity:

Professional and consultant services — Departments such as the San Francisco Planning Department and San Francisco Department of Public Health regularly issue RFPs for planning studies, environmental assessments, clinical services, and program management. These contracts are governed by Administrative Code Chapter 6 and must post publicly for a minimum of 10 calendar days.

Public works and construction — Infrastructure projects managed by the San Francisco Public Works Department or the San Francisco Public Utilities Commission require prevailing wage compliance under California Labor Code Section 1720, certified payroll reporting, and, for projects above $1 million, a Project Labor Agreement (PLA) may be required under city policy. The San Francisco Capital Planning framework identifies projects in the 10-year capital plan that will require future construction contracts.

Nonprofit social service contracts — The San Francisco Human Services Agency and the San Francisco Department of Homelessness contract extensively with community-based organizations to deliver shelter, case management, and supportive services. These agreements often follow a grant-style RFP process under Administrative Code Chapter 12B, which requires equal benefits compliance for contractor employees.

Decision boundaries

Several threshold questions determine which rules apply to a given procurement:

Factor Rule triggered
Contract value exceeds $10,000 Competitive solicitation generally required
Contract value exceeds $10 million Board of Supervisors approval required
Construction work involved Prevailing wage (CA Labor Code §1720) applies
Goods purchased SF Environment Code purchasing requirements apply
Subcontracting anticipated LBE subcontracting goals set by Human Rights Commission

Sole-source exceptions are permitted under Administrative Code Chapter 6 when only one responsible source exists, when an emergency threatens public health or safety, or when a competitive process would compromise security. All sole-source contracts above $10,000 require the City Administrator's written approval and public notice. The San Francisco Controller's Office reviews sole-source justifications as part of its audit authority.

Protest procedures allow unsuccessful bidders to challenge award decisions. Protests must be filed within 5 calendar days of the notice of intent to award, and OCA issues a written decision. Unresolved protests may be appealed to the City Administrator.

City contracting intersects with the broader governance structure described on the San Francisco Metro Authority index, which covers how city departments, commissions, and elected offices relate to one another. Vendors navigating required registrations or local preference certifications may also encounter San Francisco lobbyist registration requirements if their engagement with city officials extends beyond routine contract administration.

References