Monitor compliance signals before they become queue blockers.
ComplianceSig surfaces the policy, accreditation, program, and workforce-alignment signals that affect program verification decisions. It is designed for staff who need a clearer view of what has changed, what requires follow-up, and where operational review should be focused next.
Use this page to identify patterns across open review work, assess which signal categories are driving risk, and move directly into related verification workflows when action is required.
Open cases with refund or policy-related review needs
Programs or institutions requiring standing confirmation
CIP-SOC or program metadata mismatches
Cases routed for senior reviewer confirmation
Institution and approval signals
Review the institutional standing of providers and the approval context surrounding each submitted or reviewed program.
Policy and compliance signals
Surface issues that may affect program approval, continued eligibility, or downstream compliance review.
Program and workforce alignment signals
Compare submitted program information against workforce and coding references used in Arkansas AI-Verify review flows.
Move from signal monitoring to operational review.
Review signal summaries
Start by examining which categories contain active issues, recent changes, or unresolved exceptions needing staff attention.
Open the related verification queue
Move from signal monitoring into case-level review when a program, provider, or policy issue requires operational action.
Escalate, document, or resolve
Use the signal workspace to guide what should be reviewed next, which evidence to validate, and where follow-up belongs.
Use ComplianceSig when the question starts with a signal.
This workspace is best used when staff are trying to understand why a program is at risk, which policy area needs review, or which source should be checked next before a case moves forward.
It is especially useful for identifying broad patterns, such as repeated refund-policy issues, accreditation changes, coding inconsistencies, or documentation gaps that affect multiple providers or categories of review work.
When a signal requires case-level action, move from this page into the verification queue or a specific case record so the issue can be documented, escalated, or resolved.