Importing risks

Copy risks from one location in Diligent One to another to build out your own templates or programs, or re-use existing projects or frameworks.

Before you start

Before you can import risks, you need to:

  1. Create a project or a framework.
  2. Define objectives in the project or framework.
  3. Define risks.
  4. Ensure that both your source project / framework and target project / framework have the custom attributes and fields you need.
Note

Depending on your organization's project or framework configuration, objectives may also be called sections, processes, cycles, functional areas, application systems, or another custom term.

How it works

You can import risks from active projects, archived projects, and frameworks within the same Diligent One instance.

Requirements

Importing risks requires that both projects / frameworks:

Other important information

Limitations

Each objective in a project or framework can contain a maximum of 1000 risks and 1000 procedures / controls.

How items are copied when project types are different

When importing a risk, if the target project has a required field that is blank, the first available value from the required field is chosen.

Example

You are importing a risk with an associated control from Project A to Project B. The projects have different project types.

The Prevent or Detect? control field in Project A is blank. When you import the control to Project B, the field will also be blank. However, because the field is required, this will cause the import process to fail.

To complete the import process successfully, the first available value (Prevent) is automatically chosen from the following list of values: Prevent, Detect, N/A.

Items copied only when project types are the same

The following associated items are copied only if the project type of the source project / framework and target project / framework are the same:

If the project type of the source project / framework and target project / framework are not the same, only field values from the above items are copied.

Including associated procedures / controls

Note

In an Internal Control workflow, you have the option to include associated controls. In a Workplan workflow, you have the option to include associated procedures.

When you import risks, you can choose whether or not to also include associated procedures / controls. If you choose to include associated procedures / controls, the following occurs:

Scenario What happens
The procedures / controls do exist in the project or framework
  • Risks are imported
  • Risks are associated with existing procedures / controls
The procedures / controls do not exist in the project or framework
  • Risks are imported
  • Procedures / controls are imported and associated with risks

If you do not choose to include associated procedures / controls, only the risk is imported.

What happens when I import a risk?

The inclusion or exclusion of items is the same regardless of the method you use to import risks.

Note

  • Interface terms are customizable, and fields and tabs are configurable. In your instance of Diligent One, some terms, fields, and tabs may be different.
  • If a required field is left blank, you will see a warning message: This field is required. Some custom fields may have default values.
Method Included items Excluded items

Importing from an active project to another active project

  • Risk attributes Title, Description, Risk ID, Custom Risk Attributes, Custom Risk Scoring Factors
  • Risk associations Evidence linked from Results, Entities

If Include each associated Control is selected, the following occurs: 

  • If the controls do exist in the target destination Controls are associated with risks
  • If the controls do not exist in the target destination Controls are imported and associated with risks
Note

In an Internal Control workflow, you have the option to include associated controls. In a Workplan workflow, you have the option to include associated procedures.
  • Issues, requests, to-dos, and time entries associated with risks
  • Control associations, such as execute procedures / walkthroughs, test plans, and testing rounds

Importing from an archived project to an active project

Same as importing from an active project to another active project Same as importing from an active project to another active project

Importing from an archived project to a framework

Same as importing from an active project to another active project Same as importing from an active project to another active project

Importing from an active project to a framework

Same as importing from an active project to another active project Same as importing from an active project to another active project

Importing from a framework to an active project

Same as importing from an active project to another active project

Same as importing from an active project to another active project

Importing from a framework to another framework

Same as importing from an active project to another active project Same as importing from an active project to another active project

Permissions

Professional Managers and Professional Users can import risks.

Import risks to active projects

Import risks from an active project, archived project, or a framework to another active project.

Note

  • Interface terms are customizable, and fields and tabs are configurable. In your instance of Diligent One, some terms, fields, and tabs may be different.
  • If a required field is left blank, you will see a warning message: This field is required. Some custom fields may have default values.

  1. From the Launchpad home page (www.highbond.com), select the Projects app to open it.

    If you are already in Diligent One, you can use the left-hand navigation menu to switch to the Projects app.

    The Projects home page opens.

  2. Open a project you want to import risks to.

    The project dashboard opens.

  3. Click the Fieldwork tab.
  4. Click Go To next to the appropriate objective, and select Risk Control Matrix.

    In a Workplan workflow, the label may be Project Plan.

  5. Next to View by:, select Risk.
  6. Click Import Risk.
  7. Select the appropriate project under the Active or Archived list, or a framework from the Framework list, that you want to import risks from.

    A list of risks, organized by objective, displays.

  8. Select the risks you want to import.
  9. Include each associated Control Keep this option selected to include associated controls in your import:
    • If the controls do exist in the target destination Controls are associated with risks
    • If the controls do not exist in the target destination Controls are imported and associated with risks
    Note

    In an Internal Control workflow, you have the option to include associated controls. In a Workplan workflow, you have the option to include associated procedures.

  10. Click Import.
    Result The import process begins.

Import risks to frameworks

Import risks from an active project, archived project, or a framework to another framework.

Note

  • Interface terms are customizable, and fields and tabs are configurable. In your instance of Diligent One, some terms, fields, and tabs may be different.
  • If a required field is left blank, you will see a warning message: This field is required. Some custom fields may have default values.
  1. Open Frameworks.

    The Frameworks home page opens.

  2. Open a framework you want to import risks to.

    The framework dashboard opens.

  3. Click the Sections tab.
  4. Click Go To next to the appropriate objective, and select Risk Control Matrix.

    In a Workplan workflow, the label may be Project Plan.

  5. Next to View by:, select Risk.
  6. Click Import Risk.
  7. Select the appropriate project under the Active or Archived list, or a framework from the Framework list, that you want to import risks from.

    A list of risks, organized by objective, displays.

  8. Select the risks you want to import.
  9. Include each associated Control Keep this option selected to include associated controls in your import:
    • If the controls do exist in the target destination Controls are associated with risks
    • If the controls do not exist in the target destination Controls are imported and associated with risks
    Note

    In an Internal Control workflow, you have the option to include associated controls. In a Workplan workflow, you have the option to include associated procedures.

  10. Click Import.

    Result The import process begins.