DPO Radio

Teams often need the same review across operating environments. A versioned package helps them carry the reviewed procedure and its dependencies with it.
Use the package version and dependency information when reusing a review. The receiving team can check the import before people start relying on its output.
Find the imported copy among your own workflows.
Take an eligible workflow or bundle with its version and declared dependencies.
Review findings for format and unresolved citations before importing.
Import the reviewed package into the appropriate workspace as a user-owned workflow.
Verify the workspace provides the required frameworks and the person has the applicable permissions.
Use the Add-ons catalogue alongside built-in and user workflows and review the package version.



See a package version and its required frameworks.

Identify a reference that blocks an import.

Find the imported copy among your own workflows.
See a package version and its required frameworks.


Start a pilot using a built-in, add-on or user-owned workflow.

Talk to us about how workflow packages fits your team's work.
Yes. Packages and bundles have a version, and the import checks their format and references.
Imports create or update user-owned copies. The catalogue's built-ins remain managed by ComplianceOne.
The workflow still depends on the installed frameworks and capability checks declared for it.
The package and add-on features are available on Standard and Enterprise to people with the appropriate access.
A workflow package carries its reusable definition and supported assets. An organisation exit export is a separate request.