Workforce Wonkery bee logo

Workforce Wonkery

Policy. Data. Practice. Decoded.

Workforce Wonkery LearningFoundations CourseWorkforce in PracticeQuickstartsToolsTopic Library

WORKFORCE WONKERY · QUICKSTART · PERFORMANCE · WORKING · ABOUT 12 MIN

Read a WIOA Performance Report

Use this before reacting to a red number. Diagnose the result, benchmark, population, and data before deciding what to fix.

Before you act

Orientation, not instruction. This AI-assisted playbook does not receive human legal or compliance review. Automated source check completed September 18, 2026. Consequential claims were compared against the primary authorities identified in the Source + Trust Record below. Local policy, grant or contract terms, and required approvals may add rules or procedures, so check those before acting. Trust standard →

USE THIS WHEN

Use this before reacting to a red number. Diagnose the result, benchmark, population, and data before deciding what to fix.

YOU NEED TO DECIDE

You should be able to explain what the result means, what benchmark is being used, what may be driving it, and what needs investigation.

VERIFY AGAINST

The current controlling federal or California source, grant or agreement terms, and your adopted local policy.

HAVE THESE READY

The report, actual result, negotiated and adjusted goals if available, denominator/cohort details, trend data, provider/program breakouts, and relevant data-quality information.

60-SECOND PATH

Actual result → goal → score → denominator/cohort → trend → data quality → concentration → service/process explanation → response.

1. Separate the result from the score

The actual result is the outcome itself. A performance score compares that result with the applicable negotiated or statistically adjusted benchmark. A score of 100% means the result equaled the benchmark; it does not mean 100% of participants achieved the outcome.

2. Identify which goal is being used

Reports may show negotiated goals, adjusted goals, or both. Statistical adjustment can change the benchmark used for assessment, but it does not change the actual result.

3. Check denominator and cohort

Small denominators can make percentages move sharply. Confirm who is included, which exit or program-year cohort is being measured, and whether changes in exits, service timing, participant mix, credentials, skill gains, or wage matching explain movement.

4. Test data quality before service quality

Confirm required fields, dates, credentials, skill gains, exits, and wage data are complete before treating the result as a service-performance problem.

5. Find where the issue is concentrated

Break the result by program, provider, office, service type, training pathway, participant group, or time period where the data allows it.

Measure diagnostic

QuestionWhy it matters
What is the actual result?Prevents the score from being mistaken for the outcome.
Which goal is being used?Shows the benchmark behind the assessment.
Who is in the denominator?Defines the population behind the percentage.
Could data be incomplete?Separates data-quality problems from service problems.
Where is weakness concentrated?Points to the process that may need intervention.

WORKED EXAMPLE

A Local Area shows an 86% performance score for Credential Attainment. The first instinct is to tell staff to improve training outcomes.

Better diagnosis: examine the actual credential rate, the goal used for the score, denominator, who was included, whether credentials were entered correctly, and whether the issue is concentrated in particular providers or pathways.

What good documentation looks like

Preserve the report/date + measure + actual result + goal/score + denominator/cohort + data-quality check + analysis of drivers + action owner + follow-up date. That prevents the same number from being reinterpreted differently at each meeting.

Stop and escalate when

  • Different reports show different denominators or goals.
  • A score appears inconsistent with the actual result.
  • Large changes occur without an obvious explanation.
  • Data corrections would affect a closed reporting period.
  • Service changes are proposed before data quality is checked.
Related learning: Workforce in Practice · Performance + Data · Title I Program Operations.
Go deeper: Performance + Data →

SOURCE + TRUST RECORD

Source checked as of September 18, 2026. Source basis: TEGL 10-16, Change 3 · EDD Active Directives, including WSD24-07 and WSD20-02 · PY 2024 Performance Scores.

Check result: The distinction between actual results, adjusted levels, and performance scores, the core indicator definitions, and the role of the statistical adjustment model are supported by current guidance. Performance assessment rules and negotiated/adjusted goals can vary by program year, so a report should be read using the goal and assessment rules for the period shown rather than assuming an older threshold remains current. No human legal or compliance review was performed. Official sources and applicable local policy control.

Watch out

Do not let the Quickstart replace the controlling source or turn a local practice into a rule.

Escalate when

The authority is unclear, an exception is needed, the facts are unusual, or the decision creates material fiscal, legal, civil-rights, data, procurement, or governance risk. Use the escalation guide →

Verify

Check the current directive, regulation, grant term, agreement, and adopted local policy before acting.