Anatomy of a 28-page California state RFP
A walkthrough of a representative 28-page state-of-California RFP — the structure, the scoring framework, the compliance language, and the patterns that recur across California state procurements.
This post is a structural teardown of a state-of-California Request for Proposal. The document we describe is a composite — built from the patterns we’ve seen across multiple California state procurements posted on Cal eProcure — rather than any specific live solicitation. We’re describing the structure, not lifting any particular state’s intellectual property, and we’ll flag where a real document might deviate from what we describe.
If you’re responding to a California state RFP for the first time, this post is the orientation. If you’ve responded to several, the value here is in the cluster patterns we name explicitly.
The shape of the document
A representative 28-page California state RFP, formatted under the California Department of General Services contracting standard, breaks into eight sections.
| Section | Pages | What it contains |
|---|---|---|
| 1. Introduction & purpose | 2 | Background, agency description, scope summary |
| 2. Schedule & key dates | 1 | Q&A deadlines, submission deadline, anticipated award |
| 3. Statement of work | 6-8 | Detailed task descriptions, deliverables, performance standards |
| 4. Mandatory requirements | 3-4 | Pass/fail items the offeror must demonstrate |
| 5. Evaluation criteria | 2-3 | Weighted scoring framework, reviewer rubric |
| 6. Proposal format & content | 3-4 | Required sections, page limits, attachment specifications |
| 7. Cost proposal | 1-2 | Pricing schedule template, allowable costs |
| 8. Standard terms & references | 4-5 | DGS standard terms, GTC clauses, references to incorporated documents |
The 28-page count is the surface; the references in Section 8 to incorporated documents (the GTC, DVBE requirements, contractor certification clauses, the SCM itself) push the practical surface area well past 28 pages. A response that addresses only the visible 28 pages and not the incorporated documents is a non-compliant response.
The structural patterns that recur
Three patterns to internalize before drafting.
The DVBE participation requirement. California state procurements typically require offerors to demonstrate Disabled Veteran Business Enterprise (DVBE) participation, either by meeting a 3% goal or by documenting a good-faith effort. This is not a soft preference. It is a structural requirement; non-compliance is grounds for disqualification. A response that handles DVBE in a paragraph in the executive summary and not as a structured artifact is a response that’s missing a required document.
Mandatory minimum qualifications. Section 4 typically enumerates the minimum qualifications an offeror must meet to be considered. These are pass/fail. A response that doesn’t address each minimum qualification with a specific reference to evidence is non-compliant. The DGS evaluator will mark the proposal as non-responsive and not score it; the substantive sections won’t be read.
Format and page-limit compliance. Section 6 specifies the format the response must take — section structure, page limits per section, font, margins, attachment naming. State evaluators in California, in our experience, are stricter on format compliance than commercial buyers. A response that exceeds a page limit in Section 4.2.1 by half a page is occasionally rejected without being scored.
These three are the disqualifiers. Get them right or the rest of the response doesn’t matter.
The scoring framework
Section 5 typically breaks the weighted scoring across four to six dimensions.
| Dimension | Typical weight | What’s evaluated |
|---|---|---|
| Technical approach | 35-45% | Methodology, work plan, proposed solution |
| Personnel qualifications | 15-20% | Resumes, named team, references for key personnel |
| Past performance | 15-20% | Three or more references on similar engagements |
| Cost | 20-30% | Total cost, allowable cost structure |
| DVBE participation | Pass/fail or 5% bonus | DVBE goal achievement or good-faith effort |
| References | Embedded in past performance, occasionally separate | Verifiable past customer contact |
The weights vary by procurement. The dimensions are stable across most California state RFPs.
A note on cost weighting. California state procurements rarely award purely on lowest cost; the technical-plus-personnel weight is typically more than 50%. A response that wins on cost and loses on technical approach is a response that loses. Cost is a meaningful factor, not the factor.
The compliance language
The compliance verbs in California state RFPs cluster around six terms. Naming them helps with extraction.
- Shall. Mandatory; non-compliance is non-responsive.
- Must. Mandatory; same effect as shall.
- Will provide / will demonstrate. Mandatory; the offeror commits to delivering.
- Should. Preference; non-mandatory but graded.
- May. Permissive; offeror’s option.
- Is required to. Mandatory; legal-formality variant of shall.
A compliance matrix built against a California state RFP is going to lean heavily on shall/must/will-provide. The should/may language is for the technical-approach drafting, where the offeror has discretion in how the response addresses the preference.
What good looks like in a response
A few patterns we’ve seen win.
The compliance matrix is the table of contents. Some California state procurements explicitly request a compliance matrix as a required attachment; many do not, but most evaluators welcome one as the first attachment after the executive summary. A matrix that maps each shall/must to the section of the response that addresses it makes the evaluator’s job easier and signals professional discipline.
Past performance is specific and verifiable. Three references on similar engagements (typically defined as similar in scope, scale, and customer type — California state agencies rarely accept private-sector references as direct equivalents to state-government references). Each reference has a named contact, a current phone number, a project description that maps to the SOW dimensions of the current procurement. Vague references — “we have done many similar projects” — fail the evaluation.
Personnel section names humans, not roles. The state evaluator is reading the names. They want to know who, specifically, will do the work. Resumes attached as exhibits, with the named individuals’ commitment to the engagement explicit, beat a section that describes a “team of senior consultants.”
The cost section is built against the procurement’s cost template, not the offeror’s preferred format. California state procurements typically include an Excel template for the cost proposal. Use the template. Do not submit a custom-formatted cost proposal that approximates the template. The evaluator will reject.
Where this teardown stops being useful
A real California state RFP will have details we haven’t covered. The specific agency posting the RFP will have idiosyncratic preferences; the program area will have technical requirements we haven’t enumerated; the SOW will reference statutes and regulations specific to the program. A composite teardown like this one gives you the structural orientation, not the substantive answer.
For the actual response work, read the document end-to-end before drafting begins. Read the incorporated GTC. Read the DGS State Contracting Manual sections cited in the RFP. Run the compliance language through a structured extraction so the matrix is in front of the team before the first writer drafts the first paragraph. The state of California’s procurement framework is not friendly to teams that skip these steps.
The honest part
We’ve described patterns. Patterns are useful for orientation. They are not a substitute for reading the specific document in front of you. If you have a real California state RFP open right now and you’re using this post as a checklist, the right next step is to put this post down and finish reading the actual RFP. The patterns will be there. The specifics that will decide whether you win are in the document, not in this post.