With your domains in place, you can manage the categories inside them. Categories refine your framework's structure by grouping related requirements under each domain, giving you greater granularity and clarity.

1. Add, Edit and Organise Categories

  • Add New Category: add a category from the Framework Structure panel or from its parent domain; a display code is suggested automatically.
  • Edit: update the display code, name and description from the details panel.
  • Delete: remove a category from its More options menu; its subcategories are deleted with it after confirmation.
  • Reorder and move: drag and drop categories to reorder them or move them to another domain. Invalid moves (for example nesting too deep) are flagged immediately; confirmed moves are applied when you click Save in the save bar.

2. Define Applicability

The applicability status records whether an element is relevant to your scope and where its implementation stands. The options are:

  • Unknown: the default status; the applicability of this element has not been assessed yet.
  • Implemented: the element is fully in place and operational. Elements marked Implemented are the ones that can flow into your policies through Framework Updates.
  • Not Implemented: the element applies but is not yet implemented. Explain why (for example organisational immaturity, pending implementation, or alternative measures in place) and the plan to address it.
  • Not Applicable: the element does not apply to your scope. Explain why in the justification.

Each status change can carry a Justification, and you can apply the status recursively to all child elements.

3. Assess and Assign

  • Maturity: set current and target maturity levels (Not defined to Optimized), with descriptions, optionally applied recursively to subcategories.
  • Weighting: weight the category in the overall assessment using your workspace weighting scale.
  • Owners: assign one or several owners, optionally recursively to the underlying subcategories.
Owners button

4. Monitor Policy Coverage

The Control Progression section of each category shows the policy controls linked to it and their average completion. When every required control is linked, use Mark as Complete; if the category does not need policy links, use Mark as Not Required. These statuses feed the framework's Controls Completion progress.

5. Evidence, Reviews and Collaboration

  • Evidences: attach supporting documentation to substantiate the category.
  • Periodicity Review: schedule recurring reviews with automatic owner reminders.
  • Comments and Share: collaborate on the element and share it externally through expiring links.

Note: each category carries a permanent registered code (e.g. FC_00001) alongside its editable display code, ensuring uniqueness within your framework.