---
title: "Manage project risks "
url: "https://help.altus.pro/pt/article/manage-project-risks"
language: "pt"
last_updated: "2026-09-02T04:36:24.045Z"
---

# Manage project risks 

While organisations will typically have their own definition of risks and issues, a risk is generally defined as a future challenge or opportunity that could impact the successful delivery of a project.

Effective risk management requires that each risk is:

-   Clearly defined
-   Assigned to a responsible individual
-   Regularly monitored and updated  
    

[Vimeo video](https://player.vimeo.com/video/1204693108)

* * *

## Creating a New Risk

1.  Ensure the relevant **project** is open
2.  Navigate to **Tracking → Risks**
3.  Select **\+ New Risk**
4.  Enter the **Name**

> **Important:**  
> The Name field is mandatory and should be clear and concise to support identification across screens, reports, and dashboards.
> 
> The **Assigned To** and **Due Date** fields should not be left blank to ensure effective tracking and reporting.

1.  Complete the remaining fields as required
2.  Select **Save & Close**

* * *

## Updating Risk Items

1.  Ensure the relevant **project** is open
2.  Navigate to **Tracking → Risks**
3.  Select the risk to update
4.  Update the required fields
5.  Select **Save & Close**

* * *

## Converting a Risk to an Issue

If a risk eventuates, it can be converted into an issue:

1.  Open the risk from the **Risks** tab
2.  Select **Convert to Issue** from the command bar
3.  Complete the **New Issue** form (pre-populated with risk details)
4.  Select **Save & Close**
5.  (Optional) Reopen the original risk:
6.  -   Update the **Status** back to Active if further related issues are expected
7.  Open the newly created issue from the **Linked Issues** section
8.  Provide additional details as required
9.  Select **Save & Close**

> **Tip:**  
> You can navigate back to the originating risk from an issue by selecting the linked **Risk** record.

* * *

## Exporting Risk Data

Risk data can be exported for reporting or analysis purposes. However, behaviour differs depending on where the data is accessed.

* * *

### Export from the Project (Risk Register)

1.  Navigate to **Tracking → Risks** within the project
2.  Locate the **ellipsis (… )** in the command bar of the risk register
3.  Select **Export to Excel**

-   The Risks tab is a **subgrid**, meaning:
-   -   Columns and filters cannot be customised
    -   Only the visible fields in the register will be exported

> **Important:**  
> The project-level risk register export will only include the fields visible in the grid and may not contain all relevant details for each risk.

* * *

### Export from the Central Risk List

For full control over reporting and export:

1.  Navigate to **Work → Risks**
2.  Change the view from **My Active Risks** to **All Active Risks**
3.  Adjust the view as required:
4.  -   Add or remove **columns**
    -   Apply **filters** (e.g. by status, owner, due date)
5.  Save the updated view for reuse
6.  From the command bar:
7.  -   Select **Export to Excel**, or
    -   Use the **ellipsis (… )** if required

> **Tip:**  
> Exporting from the central Risks list allows you to customise the dataset and capture all relevant fields, making it more suitable for reporting, analysis, and audit purposes.

* * *

### Reuse Across Other Registers

> **Tip:**  
> This same export approach for Risks and Issues applies to other registers in Altus, including:
> 
> -   Dependencies
> -   Deliverables
> -   Decisions
> -   Changes
> -   Lessons
> 
> These are also exposed as **central lists under the Work area** and as **subgrids within project, program, or portfolio records**, where the same limitations and export patterns apply:
> 
> -   Subgrid = simple export (what you see is what you get)
> -   Central list = flexible export (customise columns, filters, and views)

## Key Considerations

-   Risks should be reviewed and updated regularly
-   Ownership and due dates are critical for accountability
-   Converting risks to issues ensures continuity of tracking
-   Use the central list for reporting when full visibility is required