Contra Costa County Workforce Access & Equity
A split-county East Bay profile where homelessness, youth transitions, disability access, reentry, public-assistance pathways, multilingual access, service geography, and Tribal systems must be analyzed without folding Richmond into the local workforce area. Use this page to decide what to test, who to bring in, and what evidence to watch.
Talk with people who experience it and partners who see it every day.
Try a better handoff, paid experience, language access, supportive service, or employer practice.
Track who gets in, what they receive, what they complete and what happens next.
Who may benefit most from a different approach?
FeaturedPeople experiencing homelessness or housing instability
Strong formal housing-workforce partnership signal; exact Richmond-excluded outcomes unresolved
People experiencing homelessness or housing instability
Strong formal housing-workforce partnership signal; exact Richmond-excluded outcomes unresolved
What is happening locally
WDBCCC maintains a formal Homeless-Workforce Partnership with county Health, Housing & Homeless Services to serve a shared client base. The case is retained because it supports a concrete WDB design or decision question while the missing comparative evidence remains explicit.
What to try
Integrate housing + employment
Measure referrals, workforce participation, training, placement and housing-to-work transitions through the Homeless-Workforce Partnership with Richmond excluded from exact claims.
Partners to bring in
Bring in: the Continuum of Care/housing system, AJCC, human services, behavioral health, benefits, transportation and employers willing to use low-barrier pathways.
What we still need to learn
Exact WDBCCC-area homelessness geography excluding Richmond, workforce reach, referrals, training, placement and housing-to-work transitions.
View evidence, practice notes and sources
Evidence status
Need: Strong Reach: U Service: U Outcome: U Confidence: B
Practice evidence
No case-specific practice has been verified yet. Use the examples below as design inspiration, not proof of local effectiveness.
Reopen trigger
Reopens when: New participant/subgroup performance evidence, material local data release, major program evaluation, source-status change, or geography correction.
FeaturedYouth and young adults ages 16-24 facing education and employment barriers
Strong current youth-service signal; disconnected-youth Reach and outcomes unresolved
Youth and young adults ages 16-24 facing education and employment barriers
Strong current youth-service signal; disconnected-youth Reach and outcomes unresolved
What is happening locally
WDBCCC supports year-round youth services with intensive case management, training, educational support and work experience for young people facing employment barriers. The case is retained because it supports a concrete WDB design or decision question while the missing comparative evidence remains explicit.
What to try
Scale youth career transitions
Track intensive case management, work experience, training, credentials and post-exit employment for ages 16-24 across the WDBCCC area.
Partners to bring in
Bring in: WIOA Youth providers, schools/COE, community colleges, foster/probation/housing systems when relevant, youth CBOs and employers offering paid experience.
What we still need to learn
Disconnected-youth denominator excluding Richmond, reach, work experience, training, credentials and post-exit outcomes.
View evidence, practice notes and sources
Evidence status
Need: Strong Reach: U Service: U Outcome: U Confidence: B
Practice evidence
No case-specific practice has been verified yet. Use the examples below as design inspiration, not proof of local effectiveness.
Reopen trigger
Reopens when: New participant/subgroup performance evidence, material local data release, major program evaluation, source-status change, or geography correction.
FeaturedPeople with disabilities
Strong current accessibility/service signal; comparative employment outcomes unresolved
People with disabilities
Strong current accessibility/service signal; comparative employment outcomes unresolved
What is happening locally
WDBCCC explicitly identifies disability as a priority barrier within AJCC and youth service pathways and provides auxiliary-aid/accessibility infrastructure. The case is retained because it supports a concrete WDB design or decision question while the missing comparative evidence remains explicit.
What to try
Strengthen accessible employment pathways
Track accommodations, DOR/WIOA coordination, training, competitive employment, wages and retention with Richmond excluded from exact measures.
Partners to bring in
Bring in: Department of Rehabilitation, AJCC/WIOA staff, schools and colleges, supported-employment providers, accessible transportation, health/behavioral-health partners and employers.
What we still need to learn
Working-age disability denominator excluding Richmond, DOR/WIOA coordination, accommodations, training, placement, wages and retention.
View evidence, practice notes and sources
Evidence status
Need: Strong Reach: U Service: U Outcome: U Confidence: B
Practice evidence
No case-specific practice has been verified yet. Use the examples below as design inspiration, not proof of local effectiveness.
Reopen trigger
Reopens when: New participant/subgroup performance evidence, material local data release, major program evaluation, source-status change, or geography correction.
MonitorJustice-involved residents
Current priority-service signal; reentry pathway scale and outcomes unresolved
Justice-involved residents
Current priority-service signal; reentry pathway scale and outcomes unresolved
What is happening locally
Justice involvement is explicitly identified as a priority barrier within current WDBCCC youth and AJCC service pathways. The case is retained because it supports a concrete WDB design or decision question while the missing comparative evidence remains explicit.
What to try
Strengthen reentry pathways
Map justice-system referrals, training and fair-chance employer connections and measure placement, wages and retention.
Partners to bring in
Bring in: probation/corrections, reentry CBOs, AJCC/WIOA providers, legal aid, housing/behavioral health, training providers and fair-chance employers.
What we still need to learn
Eligible population excluding Richmond, referral pathways, training, fair-chance employer engagement, placement and retention.
View evidence, practice notes and sources
Evidence status
Need: Moderate Reach: U Service: U Outcome: U Confidence: C
Practice evidence
No case-specific practice has been verified yet. Use the examples below as design inspiration, not proof of local effectiveness.
Reopen trigger
Reopens when: New participant/subgroup performance evidence, material local data release, major program evaluation, source-status change, or geography correction.
MonitorLow-income residents and people receiving public assistance
Current priority-service signal; eligible-population Reach and mobility outcomes unresolved
Low-income residents and people receiving public assistance
Current priority-service signal; eligible-population Reach and mobility outcomes unresolved
What is happening locally
Current WDBCCC AJCC and youth services explicitly prioritize people who are low income or receive public assistance, supporting a co-service and mobility question. The case is retained because it supports a concrete WDB design or decision question while the missing comparative evidence remains explicit.
What to try
Integrate supports + advancement
Track public-assistance and low-income referrals, co-enrollment, training completion, wage progression and retention without treating priority status as a disparity finding.
Partners to bring in
Bring in: human services and benefits, AJCC/WIOA, childcare, housing, food security, health, transportation and legal-aid partners.
What we still need to learn
Eligible population excluding Richmond, workforce reach, co-enrollment, training completion, wage progression and retention.
View evidence, practice notes and sources
Evidence status
Need: Moderate Reach: U Service: U Outcome: U Confidence: C
Practice evidence
No case-specific practice has been verified yet. Use the examples below as design inspiration, not proof of local effectiveness.
Reopen trigger
Reopens when: New participant/subgroup performance evidence, material local data release, major program evaluation, source-status change, or geography correction.
MonitorEnglish learners, immigrants and refugees
Current planning and public-input signal; exact language/immigrant Reach unresolved
English learners, immigrants and refugees
Current planning and public-input signal; exact language/immigrant Reach unresolved
What is happening locally
The 2025-2028 Local Plan and public-input process emphasize reaching marginalized populations and coordinated partner service delivery, requiring a direct test of language and immigrant access. The case is retained because it supports a concrete WDB design or decision question while the missing comparative evidence remains explicit.
What to try
Strengthen multilingual pathways
Use trusted-community outreach and language access to connect residents to training and quality jobs, while measuring outcomes within the Richmond-excluded geography.
Partners to bring in
Bring in: AJCC/WIOA staff, adult education and ESL, community colleges, immigrant/refugee organizations, trusted language-access partners and legal aid.
What we still need to learn
Exact language/foreign-born baselines excluding Richmond, trusted-partner routes, training access, placement and wage outcomes.
View evidence, practice notes and sources
Evidence status
Need: Moderate Reach: U Service: U Outcome: U Confidence: C
Practice evidence
No case-specific practice has been verified yet. Use the examples below as design inspiration, not proof of local effectiveness.
Reopen trigger
Reopens when: New participant/subgroup performance evidence, material local data release, major program evaluation, source-status change, or geography correction.
MonitorResidents facing access differences across the county remainder
Strong split-county/subarea research signal; utilization and outcomes unresolved
Residents facing access differences across the county remainder
Strong split-county/subarea research signal; utilization and outcomes unresolved
What is happening locally
The WDBCCC area spans diverse central, east, west and rural/suburban communities while excluding Richmond, making travel, service location and digital access a distinct design question. The case is retained because it supports a concrete WDB design or decision question while the missing comparative evidence remains explicit.
What to try
Design service access around subareas
Measure AJCC utilization, transportation, broadband, training availability and employer geography across central, east, west and rural/suburban communities with Richmond excluded.
Partners to bring in
Bring in: Rapid Response, affected employers and workers, community colleges, training providers, labor/worker representatives, sector intermediaries and business-services staff.
What we still need to learn
Subarea AJCC utilization, transportation, broadband, training availability, employer geography and outcomes with Richmond excluded.
View evidence, practice notes and sources
Evidence status
Need: Moderate Reach: U Service: U Outcome: U Confidence: C
Practice evidence
No case-specific practice has been verified yet. Use the examples below as design inspiration, not proof of local effectiveness.
Reopen trigger
Reopens when: New participant/subgroup performance evidence, material local data release, major program evaluation, source-status change, or geography correction.
MonitorNative American families served through Tribal TANF and distinct sovereign workforce systems
Distinct sovereign-system signal; exact Richmond-excluded service overlap unresolved
Native American families served through Tribal TANF and distinct sovereign workforce systems
Distinct sovereign-system signal; exact Richmond-excluded service overlap unresolved
What is happening locally
California Tribal TANF identifies the Scotts Valley Band of Pomo Indians program as serving Contra Costa County, creating a distinct sovereign workforce route that must be tested separately from ordinary county services. The case is retained because it supports a concrete WDB design or decision question while the missing comparative evidence remains explicit.
What to try
Coordinate with sovereign systems
Map Tribal TANF service overlap, preserve sovereignty and build optional WDBCCC/AJCC, training and employer connections.
Partners to bring in
Bring in: Tribal governments and Native workforce systems, Section 166 providers, Tribal TANF, trusted Native community partners, AJCC staff, education providers and employers. Keep sovereign systems distinct.
What we still need to learn
Exact service-population overlap excluding Richmond, WDBCCC/AJCC coordination, training, employment outcomes and pathway transitions.
View evidence, practice notes and sources
Evidence status
Need: Moderate Reach: U Service: U Outcome: U Confidence: C
Practice evidence
No case-specific practice has been verified yet. Use the examples below as design inspiration, not proof of local effectiveness.
Case sources
Reopen trigger
Reopens when: New participant/subgroup performance evidence, material local data release, major program evaluation, source-status change, or geography correction.
Build the local team around the barrier.
The workforce board is one part of the response. The cards below show the systems that should be connected around the eight cases. Named organizations are shown only where they are already supported by the current governed evidence.
Workforce Development Board of Contra Costa County
Use the local board/AJCC network as the convener, funder and connector, not as the only service provider.
Adult education, ESL, community colleges and trusted language-access partners
Connect language and foundational skills directly to career pathways and assisted navigation.
Human services, housing, food, health and benefits systems
Coordinate supports around participation and persistence rather than expecting career staff to solve basic-needs barriers alone.
Department of Rehabilitation, accessible transportation, supported-employment and health partners
Build co-service routes around accommodation, mobility and health-related barriers.
WIOA Youth, schools/COE, colleges, foster/probation partners and employers
Create a visible handoff from education and community programs into paid experience, training and jobs.
Probation/corrections, reentry CBOs, legal aid, housing and fair-chance employers
Coordinate reentry services with training, stabilization and hiring.
Tribal governments, Section 166 providers and Tribal TANF
Partner across systems while keeping sovereign roles, eligibility and performance separate from WIOA Title I.
Resources already linked in this profile
This is an ecosystem map, not a referral directory. Eligibility, service capacity and handoff procedures should be verified locally before use.
Ideas worth borrowing, not copying
These examples match themes in this profile. They show operating choices, not proof that the same approach will work locally.
Map the ecosystem before building another program
WorkSBC interviewed more than 50 cross-sector stakeholders, mapped navigation and pathway gaps, then moved into shared career-navigation infrastructure.
Borrow: map roles, handoffs and missing connections before adding a new service.
See the example ↗Make community outreach a funded system function
Oakland made community outreach and referrals explicit parts of workforce procurement rather than extra duties.
Borrow: pay for trusted outreach and define what a completed handoff looks like.
See the example ↗Use existing youth infrastructure for disability-focused work experience
Tulare embedded a disability-focused STEP grant inside existing WIOA youth contracts with paid work experience.
Borrow: add specialized expertise without making young people find a separate front door.
See the example ↗Combine training, paid experience and support
Verdugo combines college coursework, paid work experience, tutoring and employer hiring commitments in its ECE pathway.
Borrow: connect learning, income, support and a real next job.
See the example ↗Keep these blind spots visible.
Blind-spot scan
- BS-12 explicitly tested immigrant, refugee, English-learner, Indigenous-language and other language-access evidence before the broader community-based scan.
- Countywide Contra Costa figures can include Richmond, which operates a separate workforce board. Exact WDBCCC findings therefore exclude Richmond.
- The Homeless-Workforce Partnership is treated as a cross-system service pathway, not as proof that WIOA is under-serving people experiencing homelessness.
- Scotts Valley Tribal TANF remains a distinct sovereign-system signal whose exact service overlap with the Richmond-excluded workforce area is unresolved.
- Veterans remain visible as a nested watchlist because priority-service evidence alone does not establish comparative Reach or outcomes.
Geographic evidence fit
The profile covers Contra Costa County outside Richmond. Countywide, survivor-service, Tribal, and other cross-county evidence remains labeled when its geography cannot be narrowed to the WDBCCC area.
Useful evidence stays visible when it has limits, but a proxy, priority-service rule, shared plan, program investment, or adjacent-system need is not silently converted into a workforce-system performance finding.
See what supports the action ideas.
The page supports a decision. It does not assign an equity score.
Each case is checked against Need, Reach, Service, Outcome, local barriers, ecosystem response, hidden subgroups, a second-pass search across adjacent systems, and direct workforce-system performance. Unknown remains unknown until compatible evidence becomes available.