Help Centre · 7 articles
Programmes
How a framework becomes a path: phases, steps, gates, the SoA, overlap credit.
01The GDPR programmeThe GDPR binds every system that processes personal data. Its organisation duties are a programme under Frameworks you switch on, free on every plan, and the same rows on Obligations.02Programmes: a standard as a path, not a listSwitch on ISO/IEC 42001, ISO/IEC 27001 or NIST AI RMF and it becomes a programme — ordered steps in gated phases, each producing a record, on one page under Frameworks.03Phases and gates: why the next step is lockedEach programme runs in phases; a phase is locked until the one before it is complete — the rule the EU AI Act journey uses, applied to the standards. GDPR's duties are grouped, never gated.04Steps: Aria drafts, a person approves, then it countsOpen a step, answer its questions or let Aria draft from what you already have, then the assigned approver approves. Only approval files the record as evidence and marks the step Done.05Credit for work already on file: done once, never twiceA record that answers two frameworks is one record. A step whose every part is already evidenced elsewhere reads Done · credited — with the record that did it.06The Statement of Applicability, generated from what you didEach ISO programme has its own SoA tab: every Annex A row, pre-filled from your approved records and credited EU AI Act work. An exclusion needs a justification sentence.07The auditor: the Clauses tab, the seat, the packA programme's Clauses tab shows every clause and the step that handles it. Give your auditor a read-only seat and the records; the certificate comes from them, not from us.