Monitoring
Event-driven KYB
A fixed re-check schedule catches change on a delay. Event-driven KYB is the idea of re-checking specifically when something worth reacting to happens instead.
Schedule-driven vs. event-driven
A scheduled re-check runs on a fixed interval regardless of whether anything actually changed in between. An event-driven approach instead ties a re-check to a specific trigger - a new filing appearing at a register, for instance - so the check happens closer to when the underlying change actually occurred, not just whenever the next scheduled window arrives.
Why this is harder than it sounds
Event-driven monitoring depends on having a reliable signal that something changed in the first place - and most official registers don't publish change notifications themselves. In practice, an "event" is usually detected by the same re-fetch-and-compare process described in how registry change detection works, just run more frequently or triggered by an external signal, rather than genuinely pushed by the register itself.
Related
See it work on a real company.