WORKFORCE WONKERY · QUICKSTART · MONITORING · WORKING · ABOUT 12 MIN
Review a Monitoring Finding
Decide whether a finding is supported, what risk it creates, and whether the proposed corrective action is strong enough to fix the underlying problem.
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 →
Decide whether a finding is supported, what risk it creates, and whether the proposed corrective action is strong enough to fix the underlying problem.
You should know whether the finding has clear authority and evidence, whether costs or outcomes are at risk, and what would be needed for closure.
The current controlling federal or California source, grant or agreement terms, and your adopted local policy.
Finding, cited authority, sampled records/transactions, monitoring workpapers, agreement terms, questioned-cost information, management response, and corrective action.
Authority → condition → evidence → extent → cause/risk → financial/program effect → corrective action → verification → closure.
1. Confirm the authority
Identify the exact federal, state, grant, contract, or local-policy requirement. A formal finding should not rest only on preferred practice unless the applicable agreement or policy makes that practice a requirement.
2. State the condition precisely
Describe what happened, how many records or transactions were affected, and what evidence supports the statement. Avoid conclusions broader than the sample or evidence.
3. Decide whether you know the extent
Repeated errors may justify a larger sample or universe review. Four errors in ten files can signal a process problem rather than four isolated mistakes.
4. Separate finding, observation, and questioned cost
A finding identifies a requirement not met. An observation identifies risk or improvement without asserting a violation. A questioned cost is a cost that may be unallowable or unsupported and still requires resolution.
5. Test corrective action against root cause
If the cause is unclear policy, training, workflow, system configuration, workload, or supervision, fixing only the sampled files will not close the underlying risk.
Finding review
| Element | What good review asks |
|---|---|
| Authority | Does the cited requirement actually apply? |
| Evidence | Is the condition supported and stated precisely? |
| Extent | Do we know whether this is isolated or systemic? |
| Impact | Are costs, participants, outcomes, or controls affected? |
| Correction | Will the proposed action fix the process and can closure be verified? |
WORKED EXAMPLE
A monitor samples ten participant files and finds the same required eligibility document missing in four. The system field is marked complete in all four cases.
Strong response: cite the exact requirement, document the four-file condition, assess whether testing should expand, evaluate eligibility/cost impact, identify why the control failed, and require corrective action that fixes the process rather than only the four files.
What good documentation looks like
Preserve the requirement + sample/universe + condition + evidence + impact + management response + corrective action + owner + due date + verification evidence + closure decision.
Stop and escalate when
- The legal or policy authority is unclear.
- The finding could create questioned or disallowed costs.
- The same issue may affect a larger universe.
- The monitored entity disputes the facts or applicability.
- Corrective action requires contract, fiscal, legal, or board action.
SOURCE + TRUST RECORD
Source checked as of September 18, 2026. Source basis: WSD24-11 · Oversight and Monitoring Standards for Substate Entities · 2 CFR 200.332.
Check result: California’s current monitoring directive supports distinguishing findings from observations/areas of concern, documenting the specific authority and condition, requiring corrective action for noncompliance, and following issues through resolution. The page’s root-cause analysis, expanded sampling, and response structure are recommended review practices unless the monitoring authority or local procedure requires them. 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.