> For the complete documentation index, see [llms.txt](https://docs.fraudcheck.co.za/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fraudcheck.co.za/product/products/monitoring.md). # Monitoring Keep previously checked people and businesses under ongoing review. Monitoring keeps people you have already checked under ongoing review by re-checking them against a chosen source on a set cadence, and alerting you to new adverse findings as they arise. It is sold per subject and returns subject data, so it sits with the products rather than the platform. {% hint style="info" %} Monitoring is coming soon. This page describes how it is planned to work; details may change before launch. {% endhint %} ## What it covers * [Watchlist, PEP and adverse media monitoring](/product/products/monitoring/watchlist.md): daily re-screening against watchlist sources. * [Criminal record monitoring](/product/products/monitoring/criminal-records.md): periodic re-screening against SAPS criminal records. ## How it works * You assign the people to monitor to a **monitoring pool**, new or existing. You can add them one at a time or in a batch, and remove them at any time. * Each pool is defined by two things: the product or source monitored, and the cadence. To set up a new pool, you choose both. * Watchlists are always monitored daily. Other products can be set to monthly, quarterly or annual cadence. * Each cycle re-runs the check for everyone in the pool against the configured source. ## What you get back * **Monitoring reports**: a record of who was monitored, against what, how often, and the findings. * **Alerts**: sent as soon as an adverse finding occurs, showing who, what and when, separately from the scheduled report cycle. ## How it connects Monitoring complements one-off [Verification](/product/products/verification.md) and [Screening](/product/products/screening.md) by keeping their results current. Use it for ongoing due diligence after onboarding: continuous watchlist exposure for higher-risk clients, and periodic re-screening for lower-risk or bulk populations. --- # 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://docs.fraudcheck.co.za/product/products/monitoring.md?ask=&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.