Skip to main content

Document Hierarchy

  • April 18, 2026
  • 1 reply
  • 5 views
D
Forum|alt.badge.img+2

This is a very minor issue.   I just want to bring to this up to the community.   In Control Map, Governance is always listed last.   Ideally, it should be listed first where the Information Security program is started before building the policies and procedures.   The order presented is contrary how we explain governance to our customers and their leadership.

  • Policies
  • Procedures
  • Governance:

I think this order makes more sense when looking at hierarchy

  • Governance:
  • Policies
  • Procedures

    1 reply

    Shay Macgabhann
    Rocketeer
    Forum|alt.badge.img+2

    Hey Dennis,

    Thanks for raising this.
     

    I get the conceptual point, governance sits above policies and procedures in a hierarchy.
     

    That said, I don’t think the Control Map needs to mirror that model. In practice, most teams don’t start with fully defined governance, they build policies and procedures first and mature into governance over time. The current order feels more aligned to how people actually work in the tool.
     

    So while the hierarchy is valid in theory, I’m not convinced changing the order would improve usability. This feels more like a messaging alignment point than a product issue.

    Terms & ConditionsCookie settingsAccessibility statement