Organize sections and plan the work

Open Management systems, choose a system, then open its Structure tab to browse sections and their requirements. Expand the outline or open a section card to read its guidance. Framework sections follow the declared framework order; custom sections are shown separately where applicable.

Add or move a sectionCopy Anchor Link

Workspace administrators can choose Add section for a top-level section, or open a section and choose Subsection to add a child.

1. Enter Clause, Title, Summary, and Guidance as needed. Guidance supports Markdown.
2. Choose a Parent section, or Top level.
3. Set Position if you need a specific place, or leave it to place the section last.
4. Choose Add section, then check the new section in the outline.

To change an existing section, open Edit section, update the fields, and select Save changes. A section cannot be its own parent or be moved under one of its descendants.

Use Move earlier and Move later to reorder siblings. Save or discard pending edits before moving or deleting. Reload current values loads the saved section when you need to reconcile a conflicting change.

Remove a section and place its requirementsCopy Anchor Link

Choose Delete section only after reading the confirmation. Requirements become unplaced, while their linked content and assessments are kept. Review unplaced requirements in Structure afterwards.

To place an entry, open the requirement's editor and choose its Home section. Save and return to Structure to check its placement. Moving a register entry changes its organization within that system; read the underlying framework requirement when you need its definition.

Follow the document planCopy Anchor Link

The document plan in Structure groups expected content and shows which requirements are connected. Filter by framework, domain, or topic to review a specific area. Open a template or requirement to understand a missing item before creating content.

The system Overview also shows Documentation coverage, with the most missing required and auditor-expected documents first. Open a topic to reach its filtered requirements. Use Show more topics when offered; if the preview is truncated, use the register for the rest.

Use readiness and the roadmapCopy Anchor Link

The Management systems home includes a workspace readiness view. Within a system, Implementation roadmap groups requirements into phases and shows their status and missing documents. Open a phase or priority group to review its requirements. A group without a phase can be read in the register even when it has no direct phase link.

Use these views to choose the next entries to inspect. A document being in place, a document being approved, and a requirement being assessed as met remain separate signals.

Review change historyCopy Anchor Link

Open History in the system for changes to requirements, owners, applicability, and linked content, newest first. Use the requirement's activity control for changes focused on that entry.

If a history refresh fails, the page can retain the last loaded changes. Choose Try again before treating them as current. If a later history page is empty, use Previous to return to earlier pages.