Quarterly RCSA cycles
Run the same scored questionnaire across business units so residual risk is comparable rather than a matter of local scoring habits.
— Risk & Compliance
Runs a scored risk and control self-assessment questionnaire and calculates residual risk identically every time, producing a register comparable across teams and quarters.
2–3 days → ~5 minutes
For one document, brief or record at a time
No coding required
— USE CASES
Run the same scored questionnaire across business units so residual risk is comparable rather than a matter of local scoring habits.
Give process owners a structured self-assessment that outputs a register with owners and actions, not a free-text form.
Produce a register where every inherent and residual score can be traced back to the answers that produced it.
— HOW IT BEHAVES
The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.
Each risk is scored from a fixed scoring form rather than model judgement, which is what makes the risk universe in scope comparable across runs and reviewers.
Findings on the risk universe in scope are written up as a document that reads like professional output, with each claim tied back to a risk.
The risks land as a clean table you can sort, filter or drop straight into the deliverable.
Risk and control self-assessments usually live in a spreadsheet that every assessor scores slightly differently. In practice it shows up as quarterly RCSA cycles: run the same scored questionnaire across business units so residual risk is comparable rather than a matter of local scoring habits. The value sits in the rigour, not the typing — yet the rigour is exactly what gets traded away when there is only 2–3 days of capacity for it.
As a Skill, the work is already sequenced. You bring the evidence, and the run produces a risk register table: inherent score, key controls, residual score, action, owner plus deterministic weighted scoring applied identically every run. The judgement is built in — how items are broken up, what standard they are held to, and where the run stops for a human review. The practical effect: 2–3 days of manual work becomes a ~5 minutes run, held to an identical standard on the tenth engagement as on the first.
RCSA questionnaire → risk register exports as a structured SKILL.md file and is MCP-ready, so the same method runs in ChatGPT, Claude, Copilot or your own AI products. Adapt it to your methodology, and the intelligence stays yours — not locked to one vendor.
Assesses a data subject access request end to end and returns a governed decision on whether to fulfil it, fulfil it in part, refuse it with reasons or extend the deadline, having verified identity, mapped the request to the systems that actually hold the data and held the outcome for a data protection sign-off before anything is disclosed.
Fans multiple audit or review reports into individual findings, deduplicates repeats, and sorts them by severity into one consolidated register with sources retained.
Pairs a full evidence set against every audit assertion or PBC item to produce a coverage matrix, naming the assertions nothing supports and the documents supporting nothing.
Reads a submitted claim against the policy wording that governs it and returns a coverage assessment showing whether it appears covered, potentially excluded or in need of specialist review, mapped clause by clause and never issued without a handler's sign-off.
Assesses a reported incident against your response playbook and policies, assigns the severity band the evidence supports, and returns the matching response plan with the notifications, owners and timelines that band requires.
Assesses personal-data processing and cross-border transfers against privacy policy and jurisdiction rules, producing a documented approval outcome with conditions, policy evidence and grounds for referral.