Ongoing operations
Compliance plans, milestones, and deadlines
Compliance obligations tell you what needs doing. Compliance plans tell you who is doing it, by when, and what is already done. This guide covers creating plans, adding tasks with dependencies, tracking milestones, viewing the Gantt chart, and auto-generating plans from your pending obligations.
Transcript
Compliance obligations tell you what needs doing. Compliance plans tell you who's doing it, by when, and what's already done. This is where obligations become trackable work.
Create a plan with a name and target completion date. Each plan lives inside your organisation's workspace and only your team can see it.
Add tasks with start and end dates, set a priority, and link them to specific obligations. Each task tracks its own status: to do, in progress, or done.
Some tasks can't start until others finish. Set a dependency and the platform calculates the critical path: the longest chain of linked tasks that determines your earliest possible completion date.
Switch to the Gantt chart to see every task on a timeline. Drag a task to reschedule it. The critical path highlights in red so you always know which delays matter most.
Milestones group tasks into phases. Create a milestone like Phase One Complete, link your tasks to it, and track completion percentage across the whole phase at a glance.
Don't want to build a plan from scratch? Auto-generate one from your pending obligations. The platform groups them by framework and chapter, spreads deadlines evenly, and sets priorities based on expiry urgency.
Every task deadline feeds into the compliance calendar alongside your other obligations, so nothing falls through the cracks between your plans and your broader compliance programme.
Why this is required
Accountability, under GDPR Article 5(2) and the AI Act's documentation duties, requires more than knowing what to do: you need to show who is doing it, by when, and what progress has been made. A plan that tracks deadlines and status is the evidence a regulator expects to see.
Compliance work spans legal, security, engineering, and product. Without a shared plan, each function tracks its own deadlines in its own system, and nobody sees the full picture until something is overdue. A compliance plan gives everyone the same view of what matters most right now.
What EuroCompliant does
The Compliance Plans page lets you create plans with a target completion date, add tasks with start and end dates, set priorities, and track status through a to-do, in-progress, and done lifecycle. Each plan shows an overall completion percentage and the number of tasks completed.
Tasks can depend on other tasks: when task B depends on task A, task B cannot start until task A is done. The platform calculates the critical path automatically, the longest chain of dependent tasks that determines your earliest possible completion date.
The Gantt chart view renders every task on a visual timeline. Drag a task to reschedule it. The critical path is highlighted in red so you always know which delays will push out the whole plan. You can zoom in and out to see days, weeks, or months.
Milestones group tasks into phases like Foundation Complete or First Audit Ready. Create a milestone, link tasks to it, and track completion percentage across the whole phase at a glance. Milestones appear on the Gantt chart as diamond markers.
Auto-generate takes the work out of starting from scratch. The platform pulls your pending obligations, groups them by framework and chapter, spreads deadlines evenly between now and your target date, and sets priorities based on how urgently each obligation expires.
Every task deadline feeds into the compliance calendar alongside your other obligations, so plan deadlines never fall through the cracks between your plans and your broader compliance programme.
Walking through it
Create your first plan
Give it a name and a target completion date. Start with one plan for your most pressing framework and expand from there.
Open /plans →Add tasks with dates and priorities
Each task should have a clear title, a start and end date, and a priority level. Link tasks to obligations when possible so you can track which requirements each task addresses.
Open /plans →Set dependencies for linked work
When one task blocks another, set a dependency. The critical path calculation will show you the longest chain of work and where delays will matter most.
Open /plans →Create milestones to track phases
Milestones let you group related tasks into phases and track overall phase completion. Use them to report progress to stakeholders.
Open /plans →Use the Gantt view for the big picture
Switch to the Gantt chart to see your entire plan on a timeline. Drag tasks to reschedule, and watch the critical path update in real time.
Open /plans →The law
Accountability
The controller must be able to demonstrate compliance, not merely assert it. A plan with tracked deadlines and status is demonstrable evidence.
Risk management system
A continuous iterative process throughout the entire lifecycle of an AI system. Compliance plans are how you operationalise that process into tracked work.
Post-market monitoring
Providers must establish and document a post-market monitoring system. Plans and milestones are how you track that monitoring is actually happening on schedule.
Frequently asked
Can I auto-generate a plan without building one from scratch?
Yes. Click Auto-Generate from Obligations and the platform pulls your pending obligations, groups them by framework and chapter, and creates a plan with tasks, priorities, and evenly spread deadlines. You can then adjust individual tasks as needed.
What happens if I delete a milestone that has tasks linked to it?
The tasks are not deleted. They remain in the plan with the milestone link removed, so you can reassign them to a different milestone or leave them ungrouped.
Do plan deadlines show up in the compliance calendar?
Yes. Every task with a target date appears as a calendar event, so you see plan deadlines alongside your other compliance obligations in one unified view.
What is the critical path and why does it matter?
The critical path is the longest chain of dependent tasks in your plan. It determines the earliest date your plan can be completed. If any task on the critical path is delayed, the whole plan is delayed. Tasks not on the critical path have some slack.
Can two tasks depend on each other?
No. The platform rejects circular dependencies. If task A depends on task B, task B cannot also depend on task A.
Related guides
The compliance calendar and reporting dashboard
The cross-framework view: every deadline in one calendar, and where your overall compliance posture is measured.
Compliance checklists
How Articles 9 to 15 become tracked, owned, evidenced work rather than a document nobody reads.
Evidence vault & audit trail
Turning completed checklist items into artefacts a regulator can inspect, and the logging duties behind Articles 12 and 26.
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