Govern change

A change to the model is never made in place. It is made in a project, reviewed, approved and only then activated — with a record of who did what.

Projects and their life cycle

Every change is made in a project: a branch of the model with its own team, taken through phases and phase gates to activation. The life cycle is itself an URDAD model, with a Testing phase for projects that target execution.

Roles, governance and sign-off

Project roles say who drives which transition and who signs what. A project’s governance profile adds the checklists that the regulatory regimes applying to it require (project governance), and a project is approved by sign-off — on test reports where it was tested, each signed by the execution environment that produced it.

Working alongside other projects

Projects on the same model run concurrently and are realigned with the main line as others are activated, automatically or by a manual rebase. A project no longer worked on is archived, and can be restored.

Audit log

A permanent record of who changed, reviewed and approved what, in the model’s history and the audit log, which can be exported.

Access control and data protection

Security policies per responsibility domain decide who may see and change which part of the model, on top of team membership, with separation of duties on checklist signatures. Personal data is pseudonymised and erasable.