The trigger is not tied to the evidence
Reminders live in a calendar, not on a certificate. Moving the date only moves the entry.
Available now
The first run is behind you. The second one is the hard part: evidence expires, contracts get renewed, subprocessors change. Leapfacto records when the next review falls due and shows which piece of evidence is missing for it.
Reminders live in a calendar, not on a certificate. Moving the date only moves the entry.
A certificate expires on a date nobody maintained. You notice when it has already lapsed.
What was decided in the first run sits in a log nobody opens again.
The data points the next date is derived from.
Per provider: when it was last reviewed and when the next run is due.
Certificates and reports with their validity dates, not as files without context.
What is coming up in the next weeks, together with the evidence that is missing.
Your supervisory duties and your contract set the rhythm, not the software. Leapfacto records the date and shows which evidence is missing for it.
It derives the date from the expiry of evidence and the interval you set Responsibility for carrying it out stays with your team.
It stays available. The new run sits next to it and the log carries both decisions with date and person.
The file shows dates and evidence even when you assess nothing new. You still have to review: seeing a date is not a review.
We set up the file for one provider and show how dates and evidence relate in it.
Book a demo →