Six situations we see repeatedly. Each one gives the problem, what you do about it, and where the documentation explains it properly.
The register lives in Excel, one person owns the file, and it is out of date the week after the workshop.
Map your existing columns onto Risk Companion fields and import the register in one pass, so nothing gets retyped. From then on the whole team works in the same list, filtered to what each person needs, and you can still export to Excel or CSV for anyone who wants a spreadsheet.
Imports and exportsThe people who know the risks are contractors, engineers and external partners. Getting them accounts is a project in itself.
Participants join a session through a shared link and a PIN, with no account and nothing to install. They suggest risks in real time and upvote each other, and the facilitator imports the ones worth keeping straight into the project register.
Risk sessionsA row in a register tells someone a risk is red. It does not tell them why, or what would have to fail first.
A bowtie lays the risk out along its pathway: causes on the left, the risk event in the middle, consequences on the right, with prevention and mitigation measures on the paths between them. A cause with nothing standing in front of it is obvious at a glance in a way it never is in a list.
Bowtie diagramsSix months in, half the assessments are stale, owners have moved on, and nobody is sure which entries still mean anything.
Automated health checks test every risk against data quality rules and group what they find, so gaps surface before they reach a report. A defined status lifecycle and a review rhythm keep entries moving rather than quietly ageing.
Health checksSomeone asks how much contingency the project needs, and the honest answer is currently a guess.
EMV and ETV give a risk-weighted figure for cost and for schedule. Where you have a range rather than a single number, three-point estimation feeds a Monte Carlo simulation that produces an S-curve and percentile confidence levels. Most teams grow into this rather than starting with it, and nobody has to be a data scientist to read the output.
EMV and ETVEvery reporting cycle turns into somebody copying numbers out of several registers into slides.
Five dashboards cover different audiences, from a summary view for a steering group to a focus view for whoever is doing the work this week. Filter and order a register to show exactly what a stakeholder needs, then export precisely that.
DashboardsAny of them, and that is a design choice rather than a marketing line. The probability and impact scales, the number of levels, the category names and the risk score bands are all configured by you rather than picked from a fixed list, and a different framework can apply to each phase of a project. That is why the same tool fits a capital project, a compliance programme and an operational risk register without a sector-specific edition.
It also means Risk Companion is not the right answer everywhere. If you need barrier-based safety-critical control management, insurance claims administration or internal audit, the comparison pages say plainly which tools do that and we do not.
Settings and frameworksYou will learn more in one afternoon with your own register than from any page describing what other people do.
30 days, no credit card, no sales call