If you've imported risks via CSV but they aren't appearing under Frameworks > Assess > Risks, the Linked Objectives column in your CSV was likely left blank during import. When this field isn't populated, ControlMap creates the risks successfully but doesn't associate them with any framework objectives. Risks without an objective association only appear in the main Risk Register and are hidden from the framework-specific risks view.
This can be confusing because you may download the CSV template from the framework risks page, complete the file, upload it, and then still see an empty risks page in the framework — even though the risks were actually created.
Who can use this feature?
Super Admins and Compliance Managers
Link an imported risk to a framework objective
In your ControlMap account, navigate to Frameworks and select the affected framework.
Open the Objectives tab.
Open the objective that corresponds to the risk you want to link and click the Attach icon.
Select Risk.
Search for the risk by name or identifier used during import.
Select the risk and save.
Repeat for each unmapped risk and its corresponding objective.
Once a risk is linked to a framework objective, it immediately appears under the Risks tab within that framework.
Prevent this issue in future imports
To avoid this issue, populate the Linked Objectives column in your CSV before importing. This field associates each risk with its corresponding framework objective automatically, so the risks appear in the framework risks view as soon as the import completes.
If you've completed the steps above and the risk still isn't appearing, reach out to our support team by submitting a ticket.
