WORKFORCE WONKERY · QUICKSTART · PROGRAM + COMPLIANCE · WORKING · ABOUT 12 MIN
Review a Participant File
A strong file does more than contain documents. It tells one consistent story from eligibility through assessment, services, payments, data, exit, and outcomes.
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 →
A strong file does more than contain documents. It tells one consistent story from eligibility through assessment, services, payments, data, exit, and outcomes.
You should be able to decide whether the file is defensible, identify the highest-risk gaps, and know what needs correction or escalation.
The current controlling federal or California source, grant or agreement terms, and your adopted local policy.
Eligibility records, assessment/plan, activities, case notes, authorizations, invoices/payments, CalJOBS data, exit/follow-up records, and local procedures.
Eligibility → assessment + plan → services → fiscal → data → exit/follow-up → outcomes → contradictions.
1. Eligibility
Confirm each required eligibility element is supported by acceptable evidence and that the determination matches the program enrolled.
2. Assessment and service plan
Ask whether barriers, skills, employment goal, service choice, and partner resources make sense together. The plan should explain the logic of the case.
3. Services and approvals
Check that activities and services were allowable, timely, approved when required, and consistent with the plan and local policy.
4. Fiscal records
Tie training authorizations, supportive services, invoices, refunds, and payments to the approved service and participant record.
5. Data, exit, and outcomes
Verify dates, activity codes, credentials, MSGs, outcomes, exit timing, and source documentation. Data entry should match what actually happened.
Seven-pass review
| Pass | What to test |
|---|---|
| Eligibility | Every required element is supported. |
| Assessment + plan | Needs, goals, barriers, and services align. |
| Services | Services are allowable, approved, and consistent with the plan. |
| Fiscal | Payments match approved services and support. |
| Data | System entries match source records. |
| Exit/follow-up | Exit timing follows actual service activity. |
| Outcome | The file can support reporting and monitoring. |
WORKED EXAMPLE
Riley completed training and the certificate is in the file. The service plan and invoice are sound, but the credential was never entered in CalJOBS.
Conclusion: the source documentation is strong, but the data control failed. Correct the record through the applicable process and assess whether the workflow problem could affect other files.
What good documentation looks like
A reviewer should be able to follow one uninterrupted story: why the participant qualified, what the assessment showed, why each service was chosen, who approved it, what was paid, what happened, what was entered, and how the case ended.
Stop and escalate when
- An eligibility element appears unsupported.
- A service was provided before required approval.
- The file suggests duplicate payment, overpayment, or unallowable cost.
- Data corrections could affect reporting or exit.
- The same defect appears across multiple files.
SOURCE + TRUST RECORD
Source checked as of September 18, 2026. Source basis: WSD24-04 · WIOA Title I Eligibility Technical Assistance Guide · WSD24-05 · CalJOBS Activity Codes · WSD24-16 · WIOA Data Validation.
Check result: The need to support eligibility, service, and reported data with appropriate source documentation is supported by current California guidance. The page’s seven-pass review, sequencing, and “reviewer lens” are Workforce Wonkery quality-control practices rather than a state-prescribed file-review protocol. Program-specific approvals, fiscal documents, and local file standards remain subject to current local policy and grant terms. No human legal or compliance review was performed. Official sources and applicable local policy control.
Do not let the Quickstart replace the controlling source or turn a local practice into a rule.
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 →
Check the current directive, regulation, grant term, agreement, and adopted local policy before acting.