Deadlines
See every due date of your compliance work in one calendar, from evidence reviews to vendor reassessments, and add them to your own calendar app.
Deadlines collects the due dates from all of devguard in one place: evidence and policy reviews, records, risk reviews, treatment actions, trainings, vendor reassessments, audit findings, tasks and more. It shows what is overdue and what falls due in the next 90 days. Use it to plan the coming weeks and to make sure nothing is missed before an audit.
You do not enter deadlines on this page. Each deadline comes from a record that has a due date, and it leaves the list when you finish the work on that record. The tasks below follow the order of the work:
Scripts and integrations: see API below.

See what is due
- Open Deadlines. The page opens on the Calendar.
- Read the Overdue block at the top first. Its badge shows how many deadlines are past their date.
- Read the calendar. Each deadline sits on its due date. When a day has more deadlines than fit, it shows a link such as +2 more. Choose it to see the rest.
- Use the arrows to move to the next month, and Today to return. You can move forward until the month that holds the 90th day. Past months are not shown.
- To see the weeks as a list, choose Timeline. It groups the same deadlines by calendar week, starting with This week.
- Choose a deadline to open the record it comes from. Recurring processes and assignments open in the employee portal, where people complete them.
In the Overdue block and the Timeline, each deadline shows its due date, the title of its record and a badge. The badge reads Overdue, Due today or the number of days left. Red means overdue, orange means due within seven days. The calendar lists only deadlines that are not yet overdue: its dot is orange when one is due within seven days and gray otherwise.

Show one kind of deadline
- Open Filter by type.
- Choose a type, for example Evidence Reviews. The calendar, the timeline and the Overdue block show only that type.
- Choose All types to see everything again.
The page address keeps the view and the type. A copied link opens the same view. All types are listed in Deadline types.
Clear a deadline
A deadline is cleared on its record, never on this page.
- Choose the deadline to open its record.
- Do the work that the deadline asks for. For example, approve the evidence, finish the risk review or close the audit finding.
- Return to Deadlines. The entry is gone. A recurring deadline, such as a policy review, now shows its next date.
What finishes each type is listed in Deadline types.
Watch out: archiving a record also removes its deadline. Archive only records that are really retired, not records with work you want to skip.
Why a deadline appears
The page has no deadlines of its own. It reads them from the records every time you open it. So a date you change on a record shows here at once. A deadline leaves the list as soon as the work on its record is done.
The page shows the next 90 days, about three months. It does not show later months. A recurring deadline appears only once, on its next date. So later months would show few deadlines, even when work is planned. Overdue deadlines stay at the top until they are cleared, however old they are.
Other places show a shorter window. The Deadlines widget on the dashboard shows the next seven deadlines, overdue or due in the next 30 days. The calendar feed also covers 30 days.
Add the deadlines to your calendar app
The calendar feed puts the deadlines into Google Calendar, Outlook, Apple Calendar or any app that reads iCal links. The feed is off until an owner or admin turns it on.
- Choose Subscribe.
- If the dialog shows Subscription Deactivated, read the note and choose Activate subscription. Only owners and admins can do this.
- Copy the Calendar Feed URL.
- In your calendar app, add a calendar from a URL and paste the link. Your app then updates the deadlines on its own schedule.

The feed holds the overdue deadlines and those of the next 30 days, one all-day event per deadline, with a reminder before it. Each event links back to its record in devguard. Incident events link to the Deadlines page instead, so that no incident detail leaves devguard.
Watch out: the link works without a sign-in. The feed shows titles and short ids, but never the name of an incident or the content of a report. Reports filed in an anonymous process are never in the feed. If the link is shared too widely, turn the feed off.
To turn the feed off, open Settings for your organization and turn off Calendar Subscription. The old link stops working at once. If you turn the feed on again, devguard creates a new link, and everyone has to subscribe again. Only owners and admins can change this setting. The audit log records each change.
Reference
Deadline types
| Type | Comes from | Leaves the list when |
|---|---|---|
| Treatment Actions | The due date of a treatment action | The action is Implemented, Deprecated or archived |
| Risk Reviews | The deadline of a risk review | The review is finished or archived |
| Asset Reviews | The deadline of an asset review | The review is finished or archived |
| Access Reviews | The deadline of an access review | The review is finished or archived |
| Asset Retention | The end of an asset's retention period. It counts from the last finished review, or from the asset's creation. | The asset is reviewed again or archived. Or its retention period is removed. |
| Audit Findings | The deadline of an audit finding | The finding is closed, or it or its audit is archived |
| Vendor Reassessments | The next review date of a vendor's assessment, from the vendor's reassessment frequency | That assessment's next review date is changed or removed, the assessment is deleted, or the vendor is archived |
| Evidence Reviews | The next review of an evidence record with a review schedule | The record is approved, which moves the date on |
| Automated Evidence | A file sent by the devguard CLI that is no longer valid. It appears only after the date has passed. | A new file arrives |
| Document Validity | The Valid until date of an uploaded document, such as a SOC report or a certificate | A newer document of the same kind replaces it, or the vendor is no longer active |
| Policy Reviews | The next review of a policy with a review schedule, drafts included | The policy is reviewed or approved, which moves the date on |
| Recurring Processes | The next due date of a process that repeats on a schedule, for example every month | A run is submitted, which moves the date on |
| Submission Due Dates | The response date of a filed report | The report is done |
| Incident Notifications | Each open reporting stage of an incident | The stage is marked submitted or not required |
| Tasks | The deadline of a task | The task is done, cancelled or archived |
| Records | The due date of a record | The record is final or archived |
| Recurring Records | The next entry of a record category that repeats on a schedule, for example every six months. It counts from the last final entry. | A new entry is final, which moves the date on |
| Record Reviews | The next review of a record with a review schedule | The record is reviewed, which moves the date on, or archived |
| Assignments | The due date of the current cycle of a policy or training assignment, with "x of y completed" | Everyone has completed an overdue cycle. Or the date passes and the next cycle starts. Or the assignment, its policy or its training is archived. |
| Device Check-ins | A device whose agent has stopped reporting. Or a phone whose owner has not confirmed its settings again. The date is the last check-in plus the stale period. It appears when half that period has passed. | The device reports again. Or it is archived, or its agent key is revoked. Or the stale period is turned off. |
A repeating record category with no final entry yet has no date to count from. So it shows no deadline.
Permissions
| Action | Owner, admin | Member | Auditor |
|---|---|---|---|
| See the deadlines | yes | yes | yes |
| Copy the calendar feed link | yes | yes | yes |
| Turn the calendar feed on or off | yes | no | no |
Each deadline opens its record. What you can do there depends on your rights for that record.
API
- Base URL:
https://app.devguard.ch/api. - Authentication: an API token, sent as
Authorization: Bearer <token>. A personal token acts with the role of its owner. An organization token may read the deadlines too. - Scope: the API lists deadlines. Turning the calendar feed on or off is in the app only.
Known issue: the calendar feed answers on the same address as the list. So today GET /deadlines/ with a token returns 401 with {"error":"Subscription ID is required"} instead of the list. Until this is fixed, read the deadlines through the calendar feed below, or ask the AI assistant, whose tool listDeadlines reads the same list.
GET /deadlines/ is published with these query parameters:
| Parameter | Default | Content |
|---|---|---|
organizationId | required | Your organization id |
daysAhead | 30 | How many days ahead to look, from 1 to 90 |
includeOverdue | true | Whether to include overdue deadlines |
filterByType | all | One type, for example evidence-review |
page, limit | 1, 100 | Paging; limit from 5 to 1000 |
The type values are treatment-action, risk-review, asset-review, entitlement-review (Access Reviews), asset-retention, audit-finding, vendor-assessment, evidence-review, evidence-file-expiry (Automated Evidence), certificate-expiry (Document Validity), policy-review, process-cadence (Recurring Processes), process-run (Submission Due Dates), incident-breach-notification, task, record, record-cadence, record-review, assignment and device-check-in.
The response is { "items": [...], "total": 42, "page": 1, "limit": 100 }, sorted by due date. Each item has:
| Field | Content |
|---|---|
id, type | The id of the source record and the deadline type |
title, description | The title and description of the source record |
tag | A label: a short id such as RTA-004, or a category name |
dueDate, isOverdue | The due date, and whether it has passed |
daysUntilDue | Days left; negative when overdue |
url, portalUrl | The path of the record in the app and in the employee portal |
confidential | true for reports of an anonymous process. The feed leaves them out; the list does not. |
A call without a valid token gets 401. A token of another organization gets 403 ("No membership found"). Errors return as { message, code, status }.
Calendar feed
The feed is the link from the Subscribe dialog: GET /api/deadlines/?id=<subscription id> on the app's address. It needs no token and returns an iCal file (text/calendar) with the overdue deadlines and those of the next 30 days. FEED_ID is the id from that link:
curl -sS -o deadlines.ics \
"https://app.devguard.ch/api/deadlines/?id=$FEED_ID"Without an id the feed returns 401, and with an unknown id it returns 404. Both errors are { "error": "..." }.
How is this guide?