Rather than writing policies from a blank page, you can grow your policy structure directly out of the frameworks you have framed. Elements you mark as Implemented in a framework surface in the Policies module, where you decide exactly where each one lands.

1. Make the Framework Available to Policies

On the framework's card in the Frameworks section, switch In policies on. Only frameworks with this switch enabled feed the Policies module and appear when creating framework links.

2. Mark What You Implement

In the framework, set the applicability of the relevant domains, categories and subcategories to Implemented. Implemented elements are the ones proposed to your policies; elements left Unknown, Not Implemented or Not Applicable are not proposed.

3. Implement the Incoming Elements

  1. In the Policies section, open the Framework Updates drawer. The Incoming Changes tab lists each pending element with a NEW, UPDATED or REMOVED badge.
  2. Click Implement on an element and choose where it lands: Create as Root Policy or Create Inside an existing policy, category or subcategory.
  3. Review the confirmation screen; a framework link is created automatically so the new policy element stays traceable to its framework source.
  4. Elements you do not want in your policies can be Discarded instead. Everything you implement or discard is recorded in the History tab.

4. Import Several Frameworks

Repeat the process for each framework that applies to you. Because every implemented element carries its framework link, you can merge requirements from several frameworks into one policy set and cross-map them; the implement screen warns you when an element is already linked, so you never import the same requirement twice.

Note: later changes in the framework (new elements, deletions, applicability changes) keep flowing into Framework Updates, so your policies never silently drift away from your frameworks.