New signups are temporarily closed.Existing customers can still sign in. Contact us to be notified when we reopen.
Skip to main content
Documentation

Ongoing operations

The compliance calendar and reporting dashboard

Every other guide in this documentation covers a single framework or a single feature. This one covers the view that sits above all of them: the calendar that pulls every deadline into one place, and the reporting dashboard that scores your compliance posture across every framework you've enabled at once.

Transcript

Every other guide covers one framework or one feature. This is the view that sits above all of them: your obligations, your deadlines, and your overall posture.

Open the Calendar from the Overview section of the sidebar. It pulls in real events: system review dates calculated from risk classification, and every deadline the platform knows about.

Each event is a date you can plan around, so your whole compliance year is visible in one place instead of scattered across spreadsheets.

Urgent events, like this breach notification deadline, are also a direct link. Clicking it takes you straight to where you act on it, not just to a description of it.

That lands on the Breach Center, with the same deadline counting down against the hours your organisation has configured for notifying the supervisory authority.

The Obligations page is the mechanic behind most of what this documentation covers. Every framework's obligations land here, filtered to what actually applies to your organisation.

Items are auto-evidenced from your data where possible, and flagged for your action where not. Each one still under Your Action can take a note, an uploaded evidence file, or a direct mark-complete.

A note records why something is handled without waiting for a document. Marking an item complete directly moves it out of Your Action immediately, and Revert is right there if that was premature.

The dashboard rolls all of it up further: an overall health score, a score per framework, and the trend over time, so you can see whether you are getting more or less compliant.

Why this is required

Accountability, under GDPR Article 5(2) and equivalently under the AI Act's documentation duties, is as much about not missing things as it is about doing them correctly. A missed deadline you didn't know existed is not a defensible position with a regulator; a missed deadline you can show you tracked and escalated is a different conversation entirely.

Compliance work also spans functions: legal, security, engineering, and whoever owns a given AI system all have deadlines that matter, and none of them naturally see each other's calendars. A single aggregated view is what turns individually-tracked obligations into an organisation-wide operating rhythm.

What EuroCompliant does

The Calendar page aggregates real events from across the platform: per-system AI Act compliance review dates (calculated from each system's risk classification and last assessment), checklist item due dates, open incidents, and GDPR's 72-hour breach countdowns with a live hours-remaining display, all sorted chronologically and colour-coded by priority.

The Obligations page is the underlying mechanic behind most framework-specific guidance in this documentation: it splits every enabled framework's requirements into items needing your action, items the platform manages and auto-evidences for you, and items marked not applicable to your organisation, with a progress summary and a next-action shortcut.

The dashboard's reporting section gives you the highest-level view: an overall compliance health score, a score per enabled framework, a breakdown by AI system, and a gap analysis highlighting your weakest areas. There's no export or PDF button for this dashboard view itself; if you need a shareable report, generate one of the individual compliance documents instead and download that.

Walking through it

1

Check the calendar regularly

Not just when something's urgent. A five-minute weekly look catches deadlines before they become emergencies.

Open /calendar →
2

Work from the Obligations page's next action

It always points at your most pressing incomplete item across every enabled framework, so you don't have to hunt for what to do next.

Open /obligations →
3

Review your framework scores periodically

The dashboard's per-framework scores and gap analysis are the fastest way to see where your compliance posture is genuinely weak, not just where the most recent fire was.

Open /dashboard →

The law

Frequently asked

Can I export the dashboard as a report for a client or auditor?

Not directly as a dashboard export today. Generate the specific compliance document you need (a system's technical documentation, a GDPR record of processing, an ISO Statement of Applicability) and download that instead; those do have working export buttons.

Why does a calendar item's link sometimes not go anywhere useful?

Breach, DORA, and AI-incident deadline events link straight to where you act on them (the Breach Center, DORA ICT Incidents, and the AI Monitoring & Incidents register respectively). If a different calendar link ever doesn't land where you expect, the underlying obligation is still real. Navigate to it directly from the relevant guide instead.

Related guides

Try it on your own systems

Everything in this guide runs in the live product. Start a free trial and follow along with your own data.

Start free trial