Workforce Wonkery Learning Foundations Course Workforce in Practice Quickstarts Tools Topic Library

TOPIC LIBRARY · MONITORING + COMPLIANCE

Source + trust status

Automated source check completed September 18, 2026. Source basis: WSD24-11, 2 CFR 200.332, and WSIN25-17. Check result: Annual subrecipient monitoring, risk assessment, expanded testing, findings/corrective action, and the distinction between monitoring and a Single Audit are supported by current sources. Material change: The page now flags the current $1 million Single Audit threshold instead of allowing readers to carry forward the older $750,000 amount from legacy audit guidance. This AI-assisted page does not receive human legal or compliance review. Official sources and applicable local policy, agreement, grant terms, and procedures control. Trust standard →

Workforce Wonkery Learning · Functional track

Monitoring + Compliance

Monitoring is how a workforce system checks whether the rules, money, services, records, and contracts are working the way they are supposed to. A strong monitoring system finds problems early, documents what happened, provides technical assistance, and makes sure corrective action actually fixes the problem.

30-second takeaway

Monitoring is not just an audit at the end. It is an ongoing oversight process.
California requires annual fiscal and programmatic monitoring of WIOA subrecipients, with risk assessment used to decide where extra attention is needed.
A finding is a specific compliance violation. An area of concern or observation is a warning sign that may not yet be a violation.
A monitoring file should show the requirement, evidence reviewed, conclusion, corrective action, response, follow-up, and closure.

Why this matters

Good monitoring protects participants, public funds, the Local Board, and providers. It also gives managers an early-warning system. The goal is not to “catch” a provider. The goal is to know whether the system is compliant, effective, and fixable when something goes wrong.

The monitoring cycle

Step	Stage	What happens
1	Plan	Define who must be monitored, the monitoring calendar, responsibilities, tools, records, and review process.
2	Assess risk	Review prior findings, audits, staff changes, spending, performance, award size, systems changes, and other risk factors.
3	Scope + test	Choose fiscal and program areas, sample transactions and participant files, interview staff, and compare evidence to requirements.
4	Report	Document compliance, findings, observations, questioned costs, required corrective action, and deadlines.
5	Resolve	Review the response, evidence, corrective action plan, and any initial or final determination.
6	Follow up + close	Verify the fix was implemented, the problem did not repeat, and the monitoring record can support closure.

Who monitors whom?

Relationship	Oversight responsibility
EDD → Local Areas	The state reviews local compliance, performance, fiscal systems, data, and other requirements tied to federal and state awards.
Local Board + CEO → local WIOA system	The Local Board, in partnership with the Chief Elected Official, oversees Title I activities and the AJCC system under the local plan.
Pass-through entity → subrecipient	The pass-through entity must assess risk and monitor the subrecipient to ensure the subaward is used for authorized purposes, requirements are followed, and performance goals are achieved.
Organization → contractor	Contractors are not monitored exactly like subrecipients, but the organization still must verify procurement compliance, contract performance, receipt of goods or services, invoices, and payment.

California’s baseline: WSD24-11 requires on-site fiscal and programmatic monitoring of all subrecipients at least once per program year. Risk assessment does not replace that annual review. It helps determine where additional depth, frequency, or technical assistance is needed.

What gets tested?

Area	Examples of what a monitor may test
Eligibility + participant files	Eligibility evidence, priority of service, assessments, service plans, case notes, training approvals, supportive services, and follow-up documentation.
CalJOBS + data	Activity codes, dates, participant status, MSGs, credentials, exits, source documentation, and consistency between the file and CalJOBS.
Fiscal	Allowable costs, payroll, cost allocation, supportive-service payments, training costs, indirect costs, cash, expenditures, and supporting documentation.
Procurement + property	Competition, quotes, bids, conflict-of-interest controls, approvals, contracts, equipment records, inventory, and disposition.
Performance	Progress toward deliverables, enrollment targets, service levels, training outcomes, expenditures, and required performance indicators.
EO + accessibility	Nondiscrimination, equal opportunity, accessibility, notices, complaint systems, language access, and accommodations.
Subawards + contracts	Correct classification, required terms, risk assessment, invoice review, monitoring, performance management, corrective action, and closeout.

Monitoring deep dive

The pieces that make a review defensible

Risk assessment · Where should we look more closely?

WSD24-11 requires risk assessment of subrecipients. Useful factors include prior experience with similar awards, audit results, staff or system changes, prior findings, disallowed costs, spending concerns, award size, federal monitoring, data-entry problems, and whether deliverables are on track.

Use risk to change the review: higher risk may justify larger samples, more topics, more frequent desk review, extra technical assistance, or additional site visits.

Desk review vs. on-site review · What is each good for?

Desk review is useful for financial reports, performance trends, policies, contracts, prior findings, audits, invoices, and preliminary file review. On-site review lets the monitor observe service delivery, interview staff, inspect source records, test internal controls, and see whether written procedures match actual practice.

Alternative methods can be used in extraordinary circumstances, but California requires those alternatives to be documented and justified.

Sampling · Why one clean file proves very little

Monitoring normally tests a sample rather than every transaction or participant record. The sample should be large enough and targeted enough to test the risk area. WSD24-11 specifically calls for expanded sample testing when an area of concern appears in participant data, procurement, expenditures, or another topic.

Practical rule: if the first sample reveals a pattern, do not stop because the planned sample is complete. Expand the test enough to understand the extent of the issue.

Evidence · What should support the conclusion?

A monitoring conclusion should be traceable to evidence. Depending on the topic, that may include participant files, CalJOBS, payroll, invoices, ledgers, procurement files, contracts, board actions, written policies, emails, interview notes, bank records, property records, performance reports, or third-party verification.

Good working papers answer: What requirement did we test? What sample did we select? What evidence did we review? What did we find? How did we reach the conclusion?

Finding vs. observation · How serious is the issue?

Finding: a violation of a specific law, regulation, federal or state policy, grant term, TEGL, or agreement that requires corrective action. Findings can include questioned or disallowed costs.

Area of concern or observation: not a specific compliance violation, but a condition that may harm effectiveness or lead to a future finding if it is not addressed.

Do not write a finding without a requirement. A monitor should be able to cite the rule that was violated and explain how the evidence shows the violation.

Corrective action · Fix the system, not just the sampled file

A corrective action plan should identify the specific action, responsible person, due date, evidence of completion, and how the organization will prevent recurrence. Fixing one sampled transaction may not be enough if the root cause is a weak policy, missing control, staff-training problem, or system error.

Close only after verification. The monitoring record should show why the corrective action is sufficient and what evidence supports closure.

Questioned costs, disallowed costs, and debt · The financial side of a finding

A questioned cost is a cost identified during monitoring or audit because there is a compliance concern, inadequate support, or another reason it cannot yet be accepted. The resolution process determines whether the cost can be supported or must be disallowed.

If a cost is disallowed, the organization may need to recover or repay funds under the applicable audit-resolution and debt-collection procedures.

Single Audit does not replace monitoring · Different tools, different purposes

A Single Audit can provide important information about financial systems and federal programs, but WSD24-11 states that it does not replace required oversight or monitoring of a subrecipient, AJCC, contractor, or training provider.

The pass-through entity should review relevant audit findings, confirm required audits are completed on time, and use audit information as part of risk assessment and corrective-action follow-up.

Current threshold alert: WSIN25-17 increased the Single Audit expenditure threshold from $750,000 to $1 million for the federal adjustments it covers. Do not rely on the older threshold in legacy audit guidance without checking the current award and adjustment notice.

Show me a monitoring problem

A provider paid transportation support to 40 participants.

The local policy allows transportation support when it is necessary for participation and properly documented. A monitor samples 10 payments. Four files contain the payment record but no documented need.

Weak response: add notes to the four files and close the issue.

Stronger response: determine whether the problem is isolated or systemic, expand the sample, identify the requirement, assess questioned costs, examine the provider’s procedure and staff training, require corrective action, and later test whether the fix is working.

Before you close a monitoring review

Can every finding be tied to a specific requirement?
Do the working papers show the sample, evidence, and conclusion?
Were questioned costs and financial impact addressed?
Does corrective action fix the root cause, not just the sampled item?
Is there evidence that the corrective action was implemented?
Did the issue repeat in follow-up testing?
Could a state or federal reviewer understand why the issue was closed by reading the file?

Policy connections

Topic	Policy brief	Why it matters
Monitoring standards	WSD24-11	Current California framework for Local Board oversight, annual subrecipient monitoring, risk assessment, reports, corrective action, and records.
Audit resolution	WSD22-06	How complex deficiencies and questioned costs move through resolution.
Audit requirements	WSD20-03	Federal audit responsibilities and the relationship between audits and grant oversight.
Substantial violations	WSD24-08	What happens when noncompliance rises to a more serious level.
Incident reporting	WSD24-03	Certain suspected criminal activity or serious incidents require a separate reporting path, not ordinary monitoring resolution.