Compliance calendar
What's coming at you, not just what you put in the diary
A compliance tool gets bought because of the audit and abandoned because of daily life. The deadlines that actually hurt are the ones nobody diarises: a certificate expiring, a register that hasn't been reviewed in fourteen months, a retainer renewing on its own.
Screens from DSA Compliance v6.2 in a demo environment. All data shown is fictitious.
What the rule requires, and in which article
For information only, not legal advice. Always check against the consolidated text in force.
To an inspector, a breach that crept up looks no different from a deliberate one. Expired training stops counting as training the day it expires, not the day somebody remembers.
The badges identify the obligation the program digitises. They are not certifications or conformity accreditations.
What gets handed over when somebody asks
- A consolidated calendar with each event's source identified
- Advance warning of expiring certificates, by person and by date
- The next review date for the processing register, and whether it was met
- Recurring service renewals projected before they get invoiced
Lo que nos preguntan sobre Calendar
No. Each program still owns its dates and the calendar projects them on the fly. Duplicating them would mean keeping two copies in sync and deciding which wins when both change at once.
That nobody diarised it: it follows from data already in the platform. A certificate with an expiry date raises its own warning without anyone creating an event.
Yes. The source filter separates cases, training, appointments, engagements, certificate expiries, data protection and renewals.
A 30-minute guided demo on the real platform, or a one-hour assessment session with a consultant.
