Entry: Assurance > Relationship map, or the relationship-map action on a risk. Availability: Deployed to the JPWTech application on 26 October 2026. Scoped runtime reads and the served release assets were verified; editing and layout interactions were validated locally. Other installations must confirm their release and permissions.
- Start with the focused risk and its neighbouring controls. Choose Focus record to explore another risk, control or requirement, or Show all loaded records for the wider overview. Hover or keyboard-focus a node for its summary; select it to inspect details without rearranging the view. Focus on connections and Follow target move to that record's neighbourhood. Search and type filters apply to loaded records. The details panel opens the risk itself or the relevant controls/requirements register.
- Drag a node to arrange the view, pan the background, zoom, fit or reset the layout. Keyboard users can select a focused node with Enter and reposition it with arrow keys. Use the accessible record list as an alternative to the canvas. Layout is remembered only in this browser for this organisation/user; moving a node does not edit a business record.
The workflow-style presentation uses compact icon tiles: a warning triangle for risks, a shield for controls and a checklist for requirements. Titles, references and statuses sit below each tile. Curved lines join the circular connection points; arrows indicate direction and dashed lines indicate overlap. These points are visual markers, not drag-to-create controls: use the relationship form below the map to add or change a link. The refreshed layout uses separate browser storage so earlier card positions are retained but do not crowd the new labels. This remains a relationship view, not an executable workflow designer.
- To maintain a relationship, choose the source control, relationship type and target, then provide a meaningful rationale. Mitigates links a control to a risk; Maps to links it to a framework requirement. These reuse the existing record mappings.
- For control crossover, choose Supports, Depends on or Overlaps. Supports and Depends on have a direction; Overlaps is symmetric. Review both endpoints before saving. Duplicate and self relationships are rejected.
- Select an existing relationship to inspect it. Control-to-control type/rationale can be edited; changing endpoints or an existing risk/requirement mapping requires deliberate removal and recreation. Removing a link requires deletion permission for both endpoints and confirmation; it does not delete either record. Changes are audited. If a concurrent edit is detected, refresh before retrying.
Only records within the user's access appear. Maintenance requires write authority for both endpoints; deletion requires delete authority for both. Legacy installations restrict maintenance to manager/admin accounts. A broad graph view does not grant additional record access.
The map loads at most 80 records per type and bounded relationship sets; a partial-data notice identifies truncation. Search covers the loaded view, not the entire database. Missing from this view is not proof that a record or link does not exist. A relationship may affect calculated framework coverage, but it does not change risk scores or prove control effectiveness or compliance.
Complete when: The intended relationship appears against the correct records with an understandable rationale, and the underlying records remain accurate. Use control tests and evidence-backed assessments for assurance conclusions.