01
Dates are derived on their own
As you work, due dates flow onto one calendar: a risk review’s deadline, an asset retention date, an audit finding’s closure, a vendor reassessment. You don’t keep a separate list; the list is the work.
Every review, renewal and finding due in the next 30 days on one calendar, derived from the work you already track, from risk, asset and access reviews to audit findings, treatment actions and vendor reassessments. Subscribe to the calendar feed and your own calendar app reminds you before each date is due, so nothing you have to act on quietly lapses.
Dates are derived onto one calendar from the work you already track, the next 30 days shown, with a feed your own calendar can subscribe to.
As you work, due dates flow onto one calendar: a risk review’s deadline, an asset retention date, an audit finding’s closure, a vendor reassessment. You don’t keep a separate list; the list is the work.
The calendar shows what’s due in the next 30 days, a hard cap. Anything further out stays off the view until it comes within range, so what you’re looking at is what you can act on now.
Subscribe to the iCalendar (.ics) feed and your deadlines land in your own calendar, each event carrying an alarm your calendar app fires before the date is due. devguard emails you as well, ahead of the date and again the day before, so a reminder reaches you even when you are nowhere near the calendar.
Because the feed flows into the calendar you already check, an upcoming date surfaces where you’ll see it, and no renewal becomes a last-week scramble.
Four choices behind how deadlines work here — each one something you can check, not an adjective.
Deadlines are derived from risk, asset and access reviews, audit findings, treatment actions, asset retention and vendor reassessments. You don’t re-enter dates you’ve already set on the work.
The calendar shows what’s due in the next 30 days, a hard cap, so the view stays the things you can act on now instead of a wall of far-off dates.
An email reaches you a week ahead of a date, again the day before, and once if it slips, never twice for the same point. Recurring training and policy assignments follow their own cadence instead, up to a month ahead of a yearly one. Subscribe to the iCalendar feed as well and every date also lands in your own calendar with an alarm.
Reviews, renewals and findings sit on a single calendar, so nothing important lives only in one person’s memory or one team’s spreadsheet.
Hosted in Switzerland by default, in German and English, with on-premise possible. Your data and evidence are yours and exportable in full at any time, with no lock-in.
A deadline isn’t typed in by hand — it’s a date that already lives on a review, an audit, a vendor or an action, surfaced here so it can’t slip.
Surface each finding’s closure date before it slips.
Surface every vendor reassessment before it’s overdue.
Bring each risk and treatment review onto the calendar.
Bring each treatment action’s due date onto the calendar.
Mostly they pull in on their own. A risk, asset or access review, an audit finding, a treatment action, an asset retention date or a vendor reassessment already carries a date, and that date surfaces here automatically. You’re not keeping a separate list in parallel with the work.
Both by email and in your own calendar. devguard emails you ahead of each date, again the day before, and once if it goes overdue, never twice for the same point, and each category has its own setting in your notification preferences: as it happens, gathered into one weekly digest, or off. You can also subscribe to an iCalendar (.ics) feed of your deadlines, where every event carries an alarm your own calendar app fires. The view itself shows what’s coming up in the next 30 days.
Reviews (risk, asset, access), audit findings, treatment actions, asset retention dates and vendor reassessments — the recurring review and renewal dates an ISMS has to keep, in one place. Anything due more than 30 days out stays off the view until it’s within range.
A spreadsheet of dates goes stale the moment the underlying work changes, and someone has to remember to look at it. Here the dates are derived from the reviews, findings, vendors and actions you already track, so the calendar stays current without anyone maintaining it.
Swiss-hosted by default, in German and English, with on-premise possible. You can subscribe to an iCalendar (.ics) feed of your deadlines and take them into your own calendar, so there’s no lock-in.
Put every review, renewal and finding due in the next 30 days on one calendar, derived from the work you track, and subscribe to the feed so your own calendar reminds you before anything lapses.