> For the complete documentation index, see [llms.txt](https://standards.spdci.org/standards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://standards.spdci.org/standards/dci-standards/employment-support-systems/employment-support-systems-and-sp-system-interface/1.-crvs/1.2-process/prs.emp.05-status-verification-for-compliance-monitoring.md).

# PRS.EMP.05 Status Verification for Compliance Monitoring

The Status [PRS.EMP.05 Status Verification for Compliance Monitoring](/standards/dci-standards/employment-support-systems/employment-support-systems-and-sp-system-interface/1.-crvs/1.2-process/prs.emp.05-status-verification-for-compliance-monitoring.md)process ensures beneficiaries fulfill the established program requirements. This process involves systematically checking and confirming the current compliance-related status of individuals. The verification can be conducted by either the social protection system or the employment support system.

This process can be implemented independently or as a step within processes [PRS.EMP.01: Referral of Social Protection Program Beneficiaries to Employment Support Programs](/standards/dci-standards/employment-support-systems/employment-support-systems-and-sp-system-interface/1.-crvs/1.2-process/prs.emp.01-referral-of-social-protection-program-beneficiaries-to-employment-support-programs.md) and [PRS.EMP.02: Referral of Employment Support Programs Applicants to Social Assistance Programs](/standards/dci-standards/employment-support-systems/employment-support-systems-and-sp-system-interface/1.-crvs/1.2-process/prs.emp.02-referral-of-employment-support-programs-applicants-to-social-assistance-programs.md).

To uphold data minimization principles, the process can be restricted to a simple confirmation of an individual’s status within a program, with the responding system providing a clear ‘yes’ or ‘no’ answer. If more detailed verification is required, additional requests can be made to obtain specific information about the individual.

The data shared for compliance monitoring varies from program to program, depending on each program's specific monitoring requirements. For example, updates such as program enrollment statuses, [CD.EMP.03 enrolment\_status](/standards/dci-standards/employment-support-systems/employment-support-systems-and-sp-system-interface/1.-crvs/data/code-directory/cd.emp.03-enrolment_status.md) and unemployment reasons, [CD.EMP.02 unemployment\_reason](/standards/dci-standards/employment-support-systems/employment-support-systems-and-sp-system-interface/1.-crvs/data/code-directory/cd.emp.02-unemployment_reason.md), can be shared between programs.

## API Reference 

 [API.COM.05 SYN Enrolment Status(Sync approach)](/standards/dci-standards/employment-support-systems/employment-support-systems-and-sp-system-interface/1.-crvs/api/methods/api.com.05-syn-enrolment-status-sync-approach.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://standards.spdci.org/standards/dci-standards/employment-support-systems/employment-support-systems-and-sp-system-interface/1.-crvs/1.2-process/prs.emp.05-status-verification-for-compliance-monitoring.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.