Workforce Wonkery. Policy. Data. Practice. Decoded.

Workforce Wonkery · Analysis

Issued

WSD18-02 — Data Change Request Form Procedure

Source + trust record

Source checked as of September 18, 2026. Primary authority: EDD WSD18-02, active WSD24-13, and active WSD24-16.

Check result: WSD18-02 remains active California guidance for CalJOBS Data Change Requests. It provides a controlled process for correcting protected data fields that cannot appropriately be changed locally, preserving source evidence, supervisory review, and an audit trail. Current MIS-administrator and data-validation responsibilities in WSD24-13 and WSD24-16 should be used with this older procedure. This AI-assisted brief does not receive human legal or compliance review. Official sources control.

WDB decision strip

STATUSACTIONPRIMARY OWNERCURRENT TIMINGIMPACT
FINAL · ACTIVECONTROL SYSTEM DATA CORRECTIONSMIS Administrator + Program LeadershipWhen protected CalJOBS data cannot be corrected locallyData integrity · Performance · Audit trail · CalJOBS

The bottom line

A Data Change Request should correct a documented error without erasing the audit trail. Local Areas should require source evidence, supervisory review, and clear explanation before requesting EDD changes to protected CalJOBS fields, then retain the approved correction with the participant record.

Some CalJOBS corrections need more than a local edit—the Data Change Request creates a controlled audit trail for changes that require EDD action

WSD18-02 establishes the Data Change Request procedure for correcting CalJOBS information that Local Area users cannot appropriately change themselves. The process protects data integrity by requiring a documented request, justification, supporting evidence, and EDD review for covered changes.

At a glance

Issued
July 31, 2018

Revised
January 22, 2019

System
CalJOBS

Control
EDD-reviewed change request

Executive takeaway

The purpose is not to make corrections difficult; it is to prevent unsupported changes to records that affect eligibility, performance, reporting, or audit history. Local Areas should distinguish routine corrections within authorized user permissions from changes that require the formal state process.

A defensible request includes

  • The exact participant or employer record affected.
  • The field or data element to be changed.
  • The incorrect value and requested corrected value.
  • A clear explanation of why the correction is necessary.
  • Supporting documentation that substantiates the corrected information.
  • Required local review before submission to EDD.

Data-governance principle: Corrections should fix the record without erasing the reason the error occurred. Repeated change requests are a signal to review training, workflow, permissions, or data-entry controls.

Operational considerations for Local Boards

  1. Limit submission authority to trained staff.
  2. Keep a local log of requests, approvals, denials, and completion dates.
  3. Retain supporting documentation with the case or system record.
  4. Review recurring error types for process improvement.
  5. Coordinate the procedure with WSD24-16 data validation and WSD24-12/13 CalJOBS access and MIS responsibilities.

Source basis

Primary source: EDD WSD18-02 — Data Change Request Form Procedure

Learn the system

Need the concept behind the policy?

Use Workforce Foundations for the system underneath the brief, then return here for the policy details.

Workforce Foundations →

Build the WIOA foundation.

Workforce in Practice →

See how the system operates.

Quickstarts →

Apply policy to the task at hand.