CalJOBS modernization has moved from planning into project execution. EDD selected Geographic Solutions as the primary solution vendor and completed California’s four-stage project approval process. The notice does not announce a cutover date, which means Local Boards should prepare the business processes, data, people, and integrations that will eventually have to move without inventing a migration timeline.
Source + trust record
Source checked as of September 18, 2026. Primary authority: EDD WSIN26-01.
Check result: EDD completed the four-stage Project Approval Lifecycle, selected Geographic Solutions as the primary solution vendor, and moved the CalJOBS modernization from planning toward project execution beginning in Summer 2026. EDD has not announced a public cutover date in this notice. The page’s process-mapping and readiness recommendations are Workforce Wonkery practice, not EDD requirements. This AI-assisted brief does not receive human legal or compliance review. Official sources control.
WDB decision strip
| Status | Action | Primary owner | Current timing | Impact |
|---|---|---|---|---|
| PROJECT EXECUTION | MAP + PREPARE + PARTICIPATE | MIS + Program + Performance + Executive Leadership | Execution began/expected Summer 2026; no cutover date announced | Case management · Reporting · Employer services · Fiscal / subgrant · Integrations |
The bottom line
Treat the modernization as a business-process redesign, not as a software swap.
CalJOBS is California’s system of record for participant tracking and state/federal reporting across major workforce programs. A replacement can affect intake, eligibility, case management, activity coding, training, employer services, subgrant administration, performance, reports, local dashboards, provider workflows, and daily staff work. Local preparation should start with how the work actually happens today and what should change.
What EDD has confirmed
| Project fact | Status | Local implication |
|---|---|---|
| Four-stage Project Approval Lifecycle | Completed | The project has moved beyond concept approval into execution. |
| Primary solution vendor | Geographic Solutions selected | The replacement is now tied to a specific implementation partner. |
| Execution | Estimated to begin Summer 2026 | Local change-readiness work is timely now. |
| Production cutover | Not announced in WSIN26-01 | Do not build local deadlines or system changes around an assumed go-live date. |
Build a CalJOBS dependency map
| Workstream | Map now |
|---|---|
| Customer intake + eligibility | Forms, signatures, verification, duplicate entry, document storage, partner handoffs, and local workarounds. |
| Case management | Activities, case notes, service sequencing, approvals, follow-up, and provider workflows. |
| Training | ETPL, ITAs, provider records, training outcomes, credentials, and supportive-service links. |
| Employer services | Employer accounts, job orders, Rapid Response, IWT/OJT, contacts, and local CRM workarounds. |
| Performance + reporting | Exports, dashboards, PIRL logic, data validation, custom reports, and manual reconciliations. |
| Fiscal + subgrant | Cash requests, subgrant coding, expenditure reporting, and locally maintained reconciliation tools. |
| Integrations | APIs, file exchanges, SSO, partner systems, local databases, and recurring spreadsheets dependent on CalJOBS data. |
Capture the right pain points
A useful modernization issue statement has four parts: user + task + friction + consequence. For example: “Career planners re-enter the same training data in three places, adding 15 minutes to each enrollment and creating inconsistent credential records.” That is more actionable than “CalJOBS is cumbersome.”
Operational considerations for WDBs
- Name a cross-functional modernization lead team. Include MIS, program, performance, fiscal, frontline, provider-management, and employer-services perspectives.
- Inventory CalJOBS-dependent workflows and reports.
- Document local workarounds and shadow systems. These are often where migration risk and redesign opportunity are highest.
- Clean current data practices. A new platform will not fix inconsistent coding, weak case notes, or unclear ownership automatically.
- Separate must-preserve requirements from habits. Ask which workflow exists because of law/policy and which exists only because the current system made staff do it that way.
- Prepare contractors and AJCC partners for change. Their workflows may be as affected as County/WDB staff workflows.
- Track official EDD implementation communications. Use state notices for testing, training, migration, freeze, and cutover decisions.
Watch out
- Do not invent a cutover date.
- Do not buy or retire local systems based on assumptions about future CalJOBS features.
- Do not migrate bad local processes unchanged simply because they are familiar.
- Do not leave frontline and contractor users out of requirements and testing discussions.
Source authority
EDD WSIN26-01 — CalJOBS Modernization Project
WSIN25-12 — Earlier CalJOBS Modernization Update
Interpretation note: EDD has confirmed project execution and vendor selection, but WSIN26-01 does not establish a production cutover date. The readiness framework above is WPU implementation guidance. Source checked September 16, 2026.
Responses
[…] Current WSIN26-01 Executive Policy Brief […]
[…] WSIN26-01 — current CalJOBS Modernization Brief […]