Workforce Wonkery. Policy. Data. Practice. Decoded.

Workforce Wonkery · Analysis

Issued

WSD24-16 — WIOA Data Validation

Source + trust record

Source checked as of September 18, 2026. Primary authority: EDD WSD24-16.

Check result: WSD24-16 remains an active California directive. EDD conducts annual data validation using Local Area cohorts, gives sampled CalJOBS State IDs in advance, requires source documentation within 15 business days, and provides technical assistance when the final total-program or single-data-element error rate is 10% or higher. Local Areas should use current source-documentation and correction guidance with this directive. This AI-assisted brief does not receive human legal or compliance review. Official sources control.

WDB decision strip

STATUSACTIONPRIMARY OWNERCURRENT TIMINGIMPACT
FINAL · ACTIVEALIGN VALIDATION + CORRECTION WORKFLOWSMIS + Performance LeadershipStanding data-validation cycleData quality · Performance · Source documentation · Monitoring

The bottom line

Data validation is an operating discipline, not a year-end cleanup exercise. Local Areas should connect acceptable source documentation, routine file review, correction ownership, and CalJOBS data quality so performance reporting can withstand validation and monitoring.

Why data validation starts long before EDD selects a case file

WSD24-16 makes source documentation, CalJOBS accuracy, and error correction part of an annual statewide control system. For Local Areas, the practical question is whether every reportable data element can be supported when EDD pulls the sample, not whether staff can reconstruct a file after the review begins.

At a glance

Agency
California EDD

Directive
WSD24-16

Issued
March 14, 2025

Local action
Required


Programs
Adult · DW · Youth · Wagner-Peyser · TAA · NDWG · JVSG

Cycle
Annual validation; Local Areas rotate through 3-year cohorts

Key threshold
10% error rate triggers technical assistance

Executive takeaway

EDD must validate participant data reported to the U.S. Department of Labor. WSD24-16 explains California’s annual Data Element Validation process, or DEV, and assigns Local Area MIS Administrators a central role in making source documents available, coordinating corrections, and receiving results.

The review is not limited to active participants. EDD’s sample can include people who exited within the prior eight quarters, and samples can target particular barriers or services. A Local Area therefore needs durable documentation practices across programs and providers, not only a clean current caseload.

Five things to know

  • DEV begins each year in January, while Local Areas are reviewed on a repeating three-year cohort schedule.
  • EDD uses second-quarter PIRL data and can sample both active participants and people who exited during the prior eight quarters.
  • The Local Area generally has 15 business days after receiving sampled CalJOBS State IDs to make source documentation available.
  • A missing or unusable source document is an Unable to Validate outcome and counts as an error.
  • EDD provides technical assistance when the final Total Program Error Rate or a Single Data Element Error Rate meets or exceeds the state threshold.

How the annual validation cycle works

1. Prepare

EDD holds a cohort kickoff. MIS Administrators confirm how source documents will be provided and should have routine documentation controls in place before sample IDs arrive.

2. Sample

EDD uses the PIRL sampling tool to select program records. Sample size is tied to program population, and EDD may target barriers, services, or general records.

3. Validate

Reported values are compared with allowable source documents. Each element is marked pass, fail, unable to validate, or not applicable.

4. Correct

EDD issues preliminary results and correction instructions. Local program staff correct data before EDD finalizes results and before annual reporting locks the data.

How large is the sample?

EDD uses a 95% confidence level and a confidence interval of 15. The sample rises quickly for small programs and then levels off. Even a program serving 5,000 or more people has a standard sample of 43 records.

Program populationCase files sampledProgram populationCase files sampled
0-14All records100-19935
15-1914200-29937
20-2918300-49939
30-4923500-69940
50-9930700-99941
1,000-4,99942
5,000+43

What counts as an error?

OutcomeMeaningCounts as error?
PassAllowable source exists and matches the reported value.No
FailAllowable source exists but does not match the reported value.Yes
Unable to ValidateSource is unavailable, unusable, or illegible.Yes
Not ApplicableSpecified PIRL values such as participant did not self-identify or information not yet available.No validation performed

EDD calculates both a Total Program Error Rate and a Single Data Element Error Rate. The numerator includes both failures and Unable to Validate outcomes. Missing documentation is therefore a data-quality problem even when staff believe the underlying service or status was correct.

WDB implementation checklist

  1. Assign clear ownership. The MIS Administrator should know who can produce source documentation for every covered provider and program.
  2. Document as services occur. Do not rely on retroactive file reconstruction after EDD identifies the sample.
  3. Use allowable source documents. Align local checklists with WSD22-15 and current EDD validation guidance.
  4. Prepare for the 15-business-day window. Make sure sampled files can be produced quickly in one of EDD’s permitted formats.
  5. Fix the process behind the error. When a data element fails repeatedly, change the intake, case-management, or data-entry workflow rather than correcting only the sampled record.
  6. Complete corrections before annual reporting. Validation and annual WIOA reporting are connected; late corrections can miss the reporting window.

Implementation traps

  • Assuming an unavailable document is neutral. It is an Unable to Validate result and counts in the error rate.
  • Preparing only active files. EDD can sample participants who exited in the prior eight quarters.
  • Treating DEV as an MIS-only exercise. Source documents are created across eligibility, case management, training, follow-up, providers, and partner workflows.
  • Waiting for the cohort year to train staff. Data being reviewed may have been entered well before the review begins.

Source basis and interpretation

Primary policy: EDD WSD24-16 — WIOA Data Validation

  • Related source-document policy: WSD22-15, WIOA Data Validation Source Documentation.
  • Related performance policy: WSD24-07, Performance Guidance.
  • Related reporting policy: WSD20-10, CalJOBS Participant Reporting.

How to use this brief: Policy statements summarize WSD24-16. Recommendations about workflow design, ownership, and recurring quality checks are implementation considerations, not additional EDD requirements. The official directive controls if there is any conflict.

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.