Home / Essentials
MyRISK Essentials · practical risk management for growing organisations
Know where you stand, and show it when someone asks.
Insurers, customers, banks, tenders and the board all ask for the same kind of proof — and each time it is assembled from scratch.
The offer
A ten-minute baseline, then a monthly rhythm
MyRISK Essentials builds a First Risk Baseline from standard inputs from the spreadsheets, action lists and adviser notes you already have: what matters, who owns it, what has not moved and where the evidence is thin.
A monthly refresh keeps it current, so the next request is a retrieval rather than a scramble. The baseline shows position; the refresh is what shows change.
Cadence, not register.
The 90-day rhythm
- First Risk Baseline from what already exists — the first one free
- Monthly refresh: what closed, what aged, what stalled, what evidence arrived
- A monthly leadership summary the meeting actually uses
- Three review cycles, then a decision: continue, adjust, or stop
- A reusable proof pack for the next insurer, customer or tender request
Who runs it
Built for the person who gets the proof request
One condition applies to every sale: a named person on your side will keep the rhythm running. We do not sell a rhythm nobody will run.
Introducing a client rather than buying for yourself? For advisers and brokers →
The honest comparison
You could put your spreadsheet through an AI tool today
Many teams already have. It produces a plausible register that reads well and cannot be shown to anyone, because nothing traces to a source and nobody owns any line of it.
We have run it both ways on fourteen sector cases built from public information — a custom GPT or Copilot against a full Essentials baseline, from the same starting profile. It returned thirty ranked risks and 270 actions in every single case, and in all fourteen, no sourced observation, no modelled scenario and no traceability row.
More risks is the problem, not the selling point. Thirty risks times nine actions is two hundred and seventy things to do, and nobody sequences two hundred and seventy things. Deciding which eight to twelve actually matter here is the work, and a list of thirty has handed that decision straight back to you.
30 RANKED RISKS · 9 ACTIONS EACH · 0 SOURCED · 0 SCENARIOS
What a custom GPT or Copilot returns
- One risk of thirty: cyberattack compromising banking services and customer data
- Patch internet-facing vulnerabilities to risk-based deadlines. Harden privileged access with phishing-resistant multi-factor authentication. Segment critical systems, deploy behavioural detection, adopt zero trust
- Every one of those is good advice, and every one of them would appear for any bank on earth
- Nothing says this is where your exposure is. The ranking is by plausibility, not by anything measured about you
- And it costs you the capacity you needed elsewhere. For this bank the material exposure was regulatory, and a cyber programme of that size consumes exactly the control-delivery effort the regulatory remediation was short of
Correct advice, pointed at the wrong risk, is not a neutral outcome.
6–15 BOARD RISKS · 4 SCENARIOS · 6–15 TRACED ROWS
What Essentials gives instead
- One page: what moved this month, and why
- Actions closed, actions aged, and the named owner of each stalled item
- Where the evidence is thin, stated plainly
- The proof request received this month, and how it was answered from the pack
- The one decision the meeting is being asked to make
Every line traces back to the baseline underneath it.
For your reviewers
The boundaries, in writing
Where Essentials stops
- Not assurance, not certification, and not a compliance opinion — and it must never be presented as one.
- Not enterprise GRC, and not a risk register you file and forget. If a static register is the need, this is the wrong product.
- Not automatic: action closure and follow-through improve because the rhythm runs, not because software promises it.
- Not a managed service by stealth. That person owns the rhythm; we support it.
Who asked you to prove something in the last 90 days?
Send that request, and the spreadsheet you answered it from. The Baseline is built from what you already have.