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 within minutes of 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 — within minutes of standard inputs
- 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.
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.
During scoping we run the comparison on your actual material: your own AI output, an Essentials baseline, and the version a person has reviewed the rhythm is built on. The differences are visible in minutes and the comparison is yours to keep.
What goes to the meeting
- 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
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.