Risk Record
One page per risk with its description, assessment, actions, mappings, exposure, files and history, laid out the way your organisation set it up.
How It Works
Describe
Title, cause, consequence and triggers, in the fields and sections your admin chose.
Assess
Pick likelihood and impact on your organisation’s scales. The server works out the band and the expected value from the numbers you enter.
Plan the Response
Add actions with owners and due dates on the Actions tab.
Link to the Model
Map the risk to schedule activities and cost elements, and set correlations, on Mappings & Correlations.
Look Back
The History tab lists changes to the risk and its actions. Revert a single change from there.
Details
What You Get
- Tabs: Description, Assessment, Actions, Mappings & Correlations, Quality, Exposure, Files, History, Discussion and Export / Import.
- Threats and opportunities on the same scheme, each with its own response strategies.
- Scales of up to ten levels, with impact scales per category and a rationale for each input.
- Risk codes from your organisation’s template, such as RSK-001.
- Required, read-only and hidden fields follow the screen layout, and the server applies the same rules when a risk is saved.
- Files up to 50 MB each.
- Export one risk to Excel or PDF.
Limits and Conditions
- Custom fields come from a fixed set of text, dropdown, number, date and yes/no fields. Multi-select, person and rating fields are not available.
- Assumptions, early warnings and risk events have no screen of their own.
Discussions
Talk about a risk where the question is: on a field, an action, a mapping or a correlation. Mention a colleague or the assistant, react, or propose a new value.
- Threads on the whole risk, a field, an action, a schedule or cost mapping, or a correlation pair.
- @mentions for people, and for the assistant, which answers in the thread.
- Six reactions on each message.
- A proposal suggests a new value for fields such as owner, status, strategy, description, review date or an action’s due date. The people your organisation allows to approve accept it, and it is saved like any other edit.
Limits and Conditions
- Proposals cannot change ratings, bands, quantities or mappings.
- There is no inbox across risks. Mentions and replies arrive as notifications.
- An admin can turn Discussions off for the organisation.
Related Features
- Workspace
Actions and Mitigation
Actions with owners, dates and status on each risk, and the effect each action has in the Monte Carlo model.
- Workspace
Configuration
Organisation admins shape the product without code: scoring schemes, the folder hierarchy, the risk breakdown structure, phases, screen layouts, defaults and currencies.
- QRA Engine
Risk Mapping and Risk Types
Map each risk to the activities and cost elements it would hit, choose how its impact applies, and model risk types a register alone cannot hold.