Common public buyers
Where opportunities appear
- Municipal water departments
- Water and wastewater districts
- Joint powers authorities
- State water and environmental agencies
- Regional utilities and public works departments
California industry bid guide
Separate real utility fit from attractive-sounding scope.
Water and utility buyers often combine field operations, engineering, asset systems, public communication, regulatory context, and long contract terms. A credible pursuit needs the right team and verifiable utility evidence.
Pursuit context
Separate advisory fit from operational and licensed scope.
A utility solicitation may combine planning, engineering, field work, asset data, software, training, outreach, and operational change. Classify each workstream before deciding whether the team can prime, needs a committed partner, or should Pass.
Conditions at operating sites can matter as much as the written deliverables. Verify site access, safety, outage coordination, records, travel, response coverage, and continuity expectations without assuming that general public-sector experience transfers to a utility environment.
Opportunity patterns
Scopes worth monitoring
- Asset management and CMMS or EAM modernization
- Operational planning and process improvement
- Engineering and technical support
- Conservation and public outreach
- Training, data, inspection, and field services
Hard gates
Requirements to verify before investing in the response.
Treat a stated mandatory condition as unresolved until the current official documents and the responsible person support it.
Professional responsibility
Determine whether any task requires a stated professional license, signed work product, specialist credential, or licensed subcontractor.
Verify in: scope tasks, deliverable descriptions, minimum qualifications, and the draft agreement.
Field and safety capability
Confirm site-access, training, protective-equipment, background, vehicle, inspection, emergency, and geographic obligations stated by the buyer.
Verify in: site rules, safety attachments, meeting materials, the schedule, and insurance provisions.
Asset and technology boundaries
Identify required platforms, data formats, integrations, ownership, migration duties, system access, and vendor authorizations.
Verify in: technical exhibits, asset inventories, data samples, interface requirements, and pricing sheets.
Continuity of service
Test staffing, travel, response time, transition, training, and support commitments against actual capacity for the full term.
Verify in: service levels, staffing plans, geographic requirements, transition tasks, and the contract term.
First-pass qualification
Questions that should change the decision.
01
Does the team have comparable utility references and field context?
02
Are engineering or professional licenses required for any scope element?
03
Does delivery require a software, engineering, construction, or outreach partner?
04
Can insurance, site access, safety, records, and travel requirements be met?
Potential pass conditions
Disqualifiers to surface early
- Required professional licensing is absent
- Mandatory utility references cannot be documented
- Field, safety, or geographic coverage is not credible
- The scope requires a platform implementation partner not yet secured
Evidence tests
Turn capability claims into reviewable proof.
A credible Chase connects each material claim to evidence, identifies the remaining gap, and avoids treating marketing language as verification.
We understand utility operations.
- Acceptable proof
- Comparable work showing the relevant facility or system context, bidder role, field constraints, affected stakeholders, deliverables, and verified result.
- If the proof is missing
- Limit the claim to the workstream actually demonstrated or add utility-specific leadership.
The team covers the technical obligations.
- Acceptable proof
- Current licenses or credentials where required, named specialists, partner commitments, platform experience, and a responsibility map for every technical task.
- If the proof is missing
- Keep the pursuit at Verify until responsibility and evidence are assigned.
Implementation will work in the field.
- Acceptable proof
- A plan covering site coordination, data quality, safety, outages, stakeholder communication, training, transition, and operational acceptance.
- If the proof is missing
- Resolve field assumptions through official questions or Pass if the operating constraints remain unsupportable.
Response evidence
Documents to prepare or verify
The exact format comes from the solicitation. This list identifies the evidence categories most likely to affect the pursuit decision.
Water or wastewater project evidence
Licenses and partner commitments where required
Field and stakeholder engagement approach
Asset, data, workflow, and change-management methods
Training, transition, safety, and quality plans
Prime, partner, or pass
Build the team around responsibility, not logos.
Prime only when the company can govern the complete scope and accept responsibility for interfaces among technical, field, operational, and stakeholder work.
Prime when
Own the core obligation
- The core scope and utility evidence sit with the prime’s own leadership.
- The prime can coordinate site work, data, schedules, acceptance, and change management.
Partner when
Close a defined gap
- Engineering, platform authorization, construction, field safety, specialty inspection, or multilingual outreach falls outside current capability.
- A partner supplies required utility references or licensed responsibility.
Set boundaries
Assign responsibility
- Assign design responsibility, signing authority, site safety, data migration, outage coordination, warranties, and support.
- Verify that the solicitation permits the proposed allocation of work.
Source verification
Confirm the decision in the official procurement record.
Do not infer operating conditions from the opportunity title. Trace the decision through the buyer’s current documents and site information.
- Scope and task attachmentslicensed tasks, field duties, facilities, systems, outputs, and acceptance.
- Site informationmandatory visits, access limits, safety rules, operating schedules, and known conditions.
- Technical materialsasset data, platforms, integrations, records, ownership, migration, and security.
- Addenda and agreementrevised assumptions, insurance, indemnity, response coverage, term, and partner obligations.
Related guides
Build a repeatable pursuit process.
RFP analysis
How to read a government RFP
Read a government RFP in the order that exposes deadlines, mandatory requirements, scope, evaluation, and contract risk.
Teaming strategy
California government subcontracting opportunities
A practical framework for evaluating California public-sector subcontracting and teaming opportunities.
Evidence library
Use past performance in government proposals
Organize public-sector references and project evidence so they can support faster, more credible bid decisions.
One opportunity, one documented decision
Have a live California opportunity to evaluate?
Get a source-linked Chase, Verify, or Pass memo before your team commits proposal time.