Feature 1
Find the right framework
Review available standards by family, version and structure before work begins.
- Browse the library
- Compare versions
- Inspect requirements
Capability
Frameworks
Browse the standards and obligations available to the organisation before adopting a version as active compliance work.
The outcome
Understand a framework's scope and requirements before committing the organisation to a compliance project.
How it helps
How Frameworks works
This capability connects with the wider Apollo platform, so information can support action, evidence and reporting without being entered again.
Feature 2
Move from obligation to active work
Start a project from the selected framework version when ownership and dates are ready.
- Select a version
- Set project defaults
- Create the project
What is included
One capability, connected to the wider platform
Use the capability you need now while keeping its records, work and evidence ready for related capabilities across Apollo.
Included features
- Framework families and versions
- Sections and requirements
- Framework library
- Tags and availability
- Version inspection
- Project starting point
Connected platform
Keep exploring Apollo
See where this capability is available and the related capabilities and solutions that use the same connected information.
Questions and answers
Questions about Frameworks
Practical answers to common questions about managing this responsibility well.
Why does frameworks matter?
Understand a framework's scope and requirements before committing the organisation to a compliance project.
What should frameworks include?
It should cover framework families and versions, sections and requirements, framework library, tags and availability and version inspection, with enough context to support action and explain decisions.
Who should be responsible for frameworks?
Ownership should sit with the person who can make decisions and keep the information current. A specialist or governance team may provide the method, but accountability should not be left with an unnamed group.
How do you keep frameworks current?
Set review dates according to risk and reassess after relevant incidents, material change, new evidence or overdue follow-up work. Preserve the history so changes remain explainable.
What evidence should be retained for frameworks?
Keep the source information, owner, review and approval history, supporting documents and resulting actions needed to show what was considered and what happened next.
See Frameworks in Apollo
Book a focused demonstration and we will show how the capability fits your current responsibilities, existing information and next practical priorities.