SB 1340 directs each state agency’s designated small business liaison to deliver an annual accounting of the agency’s contracts that involve small businesses to the Office of Small Business Advocate (OSBA). The Office must then publish the information it receives on its website.
The bill creates a routine public record intended to show where state contracting dollars flow to small firms and subcontracts. That visibility could shape outreach, oversight, and small‑business policy — but it also creates practical work for agency liaisons and raises questions about data format, definitions, and confidentiality that the statute does not resolve.
At a Glance
What It Does
The law requires each agency’s small business liaison to submit, every year, lists of contracts involving small businesses and contracts that include small‑business subcontracts, together with dollar amounts for each contract and amounts actually paid to small businesses. The Office of Small Business Advocate must post the collected information to its website.
Who It Affects
State agencies with designated small business liaisons, OSBA staff who will receive and publish the data, procurement and compliance teams that must compile contract and payment records, and small businesses that hold prime contracts or subcontracts with the state.
Why It Matters
The measure would create the first statutory, centralized public dataset on state contracting flows to small firms, useful for policymakers, advocates, and vendors. It also imposes recurring data‑collection and publication responsibilities without specifying formats, deadlines, or confidentiality protections, creating implementation and compliance risks for agencies and vendors.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
SB 1340 adds Section 11148.5.1 to the Government Code to make contract-level information about small-business participation in state procurement publicly available. The duty to report falls on the existing small business liaison that each qualifying agency already designates; under the bill that liaison must annually compile information about contracts that involve small businesses and deliver it to the Office of Small Business Advocate.
The Office then posts the information to its website.
The statute lists four types of data the liaison must provide: (1) a list of current contracts between the agency and small businesses, (2) a list of agency contracts that include a subcontract with a small business, (3) the total dollar amount of each listed contract, and (4) the total dollar amount paid to a small business under a contract or subcontract. The bill does not define data formats, reporting deadlines beyond “annually,” or whether numbers represent awarded values, invoiced amounts, or payments actually disbursed, which will shape how agencies implement the requirement.Because the law requires public posting, agencies should expect external scrutiny of both completeness and accuracy.
That creates two immediate operational needs: (1) internal mapping to identify which contracts and subcontracts meet whatever small‑business standard applies, and (2) accounting coordination to extract payment totals for primes and subs. The statute centralizes disclosure at OSBA but leaves technical specifications, redaction rules, and enforcement mechanisms to future administrative practice or guidance.Absent further direction, agencies will confront practical tradeoffs: do they publish machine‑readable, queryable datasets or simple PDF lists; how do they avoid double‑counting a subcontract across multiple reporting categories; and how do they protect competitively sensitive information (for example, prices in a small vendor’s sole contract) while honoring the public posting requirement?
Those choices will determine how useful the resulting dataset is for policy analysis and vendor outreach.
The Five Things You Need to Know
The statute places the reporting duty on each agency’s small business liaison and requires annual submission of contract information to the Office of Small Business Advocate.
Liaisons must provide a list of current contracts between the agency and small businesses (prime contracts with small‑business primes).
Liaisons must also provide a separate list of agency contracts that include a subcontract with a small business (prime contracts containing small‑business subcontractors).
For each listed contract the liaison must report the contract’s total dollar amount and separately report the total dollar amount actually paid to the small business under the contract or subcontract.
The Office of Small Business Advocate must post the submitted information on its internet website, but the statute includes no specific deadline, data format, enforcement penalties, or confidentiality exceptions.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Report primes: list of current agency contracts with small‑business primes
This clause requires liaisons to compile a list of the agency’s current contracts where the prime contractor is a small business. Practically, that forces agencies to identify which of their active vendor records meet the applicable small‑business definition (which the bill does not restate), and to set a cut‑off for what “current” means. Procurement systems may not store a single, ready‑made flag for that combination, so agencies should expect to reconcile vendor size data with active contract status.
Report subs: list of contracts that include a small‑business subcontractor
This subsection targets contracts where the agency’s prime contractor has engaged a small business as a subcontractor. Identifying those arrangements typically requires prime contractors to disclose subcontractor identities in invoices or contract reports. If existing procurement records don’t capture subcontractor details consistently, agencies will need new collection processes or vendor certifications to build the list the statute requires.
Contract dollar values: report total dollar amount of each contract
The statute instructs liaisons to report the total dollar value for each listed contract. The text does not specify whether agencies should report original award value, amended contract value, or a remaining not‑to‑exceed amount, creating a data‑definition choice that will affect comparability across agencies and over time. Accurate reporting will require procurement and budget offices to agree on a single valuation basis.
Payments to small businesses: report actual amounts paid to small‑business primes and subs
Liaisons must also report the total dollar amount paid to small businesses under each contract or subcontract. This provision shifts the focus from awarded amounts to flow‑of‑funds, which is more informative but harder to assemble: agencies must map payments to specific vendors and subcontracts and ensure accounting systems can aggregate payments by vendor across multiple invoices and fiscal years.
Public posting by the Office of Small Business Advocate
OSBA must publish the information it receives on its internet website. The statute does not prescribe file formats, frequency of publication beyond receipt, or guidance on redaction of sensitive data. OSBA will therefore control user access and presentation choices, but its ability to produce a usable, searchable dataset depends on the quality and consistency of agency submissions and on whether OSBA issues implementation guidance.
This bill is one of many.
Codify tracks hundreds of bills on Government across all five countries.
Explore Government in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Small businesses bidding on state work — they gain visibility into which agencies award contracts and where subcontracting opportunities exist, supporting business development and partnership formation.
- Office of Small Business Advocate and state policymakers — they receive centralized, auditable data to measure small‑business participation and to target outreach or program changes.
- Procurement transparency advocates and researchers — public posting creates a new empirical basis for tracking spend and evaluating small‑business inclusion across agencies.
- Small‑business support organizations and trade associations — they can use the published data to identify referral or training targets and to benchmark member performance.
Who Bears the Cost
- State agencies and their small business liaisons — they must collect, validate, and submit contract and payment data annually, which will consume staff time and likely require system changes.
- Office of Small Business Advocate — OSBA must ingest, vet, and publish datasets, and may need to develop technical capacity for hosting, formatting, and responding to data quality issues.
- Prime contractors and subcontractors — they may have to disclose subcontracting relationships and payment details to support agency reporting, raising potential confidentiality and commercial‑sensitivity concerns.
- Finance and accounting units within agencies — they face the burden of mapping payments to vendor records and assembling historical payment totals to satisfy the reporting requirement.
Key Issues
The Core Tension
The bill balances two legitimate aims — public visibility into how state contracting dollars reach small firms and streamlined, low‑burden procurement operations — but it does so without specifying the technical rules needed to reconcile them: greater transparency requires detailed, consistent reporting that costs time and can expose commercially sensitive data, while minimizing burden and protecting confidentiality reduces the dataset’s usefulness.
The bill’s transparency objective is straightforward, but several implementation gaps create practical and policy tensions. First, the statute omits critical definitional and technical details: it does not define “small business” for reporting purposes, fails to specify whether contract dollar values are awarded amounts or payments, and leaves “annual” timing and data formats unspecified.
Those omissions will produce inconsistent datasets unless OSBA issues clear guidance. Second, the requirement to publicly post contract and payment figures creates potential confidentiality conflicts: small firms may regard payment details or contract values as competitively sensitive, and agencies will need a legal basis to redact or withhold information if disclosure risks harm.
The statute contains no redaction standard.
Third, the bill imposes recurring administrative work without identifying funding or staffing support. Smaller agencies with limited procurement data infrastructure could face disproportionate burdens to extract subcontractor payment detail.
Finally, the reporting model risks measurement pitfalls such as double‑counting payments across reporting categories, mismatched fiscal periods, and inconsistent vendor identifiers; these data‑quality issues could mislead users and undermine the dataset’s utility unless OSBA enforces standardized submission rules or validation checks.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.