A risk explorer is useful when you need to make the register's rating definitions and unresolved evidence visible before interpreting a risk map. The result should make the underlying records easier to inspect and the next decision easier to explain. This guide develops a specific risk explorer with a source schema, operating rules, a fictional example, and observable review checks. It is intended for someone who already has the underlying material and needs a dependable way to organize it.
Product references checked: 7 October 2026. The examples and implementation specifications below are original editorial guidance. They illustrate expected behavior and have not been presented as a benchmark or as a completed tool tested inside another product.
Define the deliverable and its scope
This is an exploratory view of an approved risk register, not quantitative forecasting or automatic risk acceptance.
Write the acceptance standard before asking Claude for a draft. A reviewer should be able to identify the risk identifier, inspect the probability rating, and understand the mitigation state without guessing what a blank field means. Decide which records belong in the deliverable, which are out of scope, and who can confirm the final interpretation. Keep those choices visible in the working specification rather than leaving the assistant to supply convenient defaults.
Prepare the source package
Gather risk IDs, approved probability and impact scales, rating evidence, owners, and review dates. Assign source IDs and preserve original wording wherever a small difference could change the outcome. Record the collection date and the version of each source. If two files disagree, keep both references and mark the conflict. Do not replace a disputed value with whichever one produces the cleanest display.
Use a small representative subset for the first draft. Include one ordinary record, one incomplete record, and one record that challenges an important rule. For this task, use the following as the incomplete-record check: Clear one rating and reconcile plotted plus incomplete counts with the register total. Preserve the original package separately from the assistant's transformed output. A polished result is easier to audit when its IDs still lead back to the original supplied material.
Define the record schema
| Field | Required meaning |
|---|---|
| Risk identifier | A stable ID for an uncertain event, separate from the impact description. |
| Probability rating | A supplied estimate tied to the approved scale and its stated timeframe. |
| Impact rating | The supplied severity for a defined consequence and population. |
| Rating evidence | The observation or rationale supporting the assigned ratings. |
| Review date | When the estimate was reviewed and when it requires reconsideration. |
| Mitigation state | The approved response, owner, and evidence of completion, kept separate from residual risk. |
Treat risk identifier as a deliberate part of the data model. A stable ID for an uncertain event, separate from the impact description. Keep its representation consistent when you sort, filter, or revise the output. The probability rating field has a different job: A supplied estimate tied to the approved scale and its stated timeframe. Combining these fields into one sentence can hide the distinction the reviewer needs to inspect.
Pay particular attention to impact rating and rating evidence. The former means: The supplied severity for a defined consequence and population. The latter means: The observation or rationale supporting the assigned ratings. Store them separately and label both in the detail view or report. This makes disagreements visible at the exact point where they affect the result instead of burying them in a general note at the bottom.
Apply the task rules
Rule 1. Ordinal scale numbers are category codes; multiplying them does not turn the result into a measured probability.
Rule 2. Use the approved matrix boundaries instead of inventing red, amber, and green thresholds.
Rule 3. Separate inherent and residual ratings so a proposed mitigation cannot imply reduced risk before review.
Rule 4. Missing ratings should appear outside the plotted complete set with a visible incomplete count.
Make these rules inspectable alongside the risk explorer. Ask Claude to describe how each rule affects a record and what should happen when the supplied data does not establish an answer. A rule written in prose still needs a defined output state. Use an explicit missing, disputed, or not-applicable label where appropriate, and reserve a valid zero or an empty result for cases where it has a defined meaning.
Work through a fictional example
A fictional delivery risk R-3 has probability category three and impact category four on an approved five-category scale. The explorer may place it in that matrix cell. It should not label the event as 60 percent likely merely because three is three-fifths of five. A mitigation is proposed, but no residual assessment has been approved. Show the proposal separately and retain the original ratings. Another risk lacking impact information belongs in an incomplete-record list rather than disappearing.
Use the example as a review fixture rather than as real operational data. Before generating the output, write down which fields should be populated and which should remain unresolved. Then compare the generated result with that expectation. If Claude supplies an unsupported value, correct the underlying instruction or calculation rule instead of merely editing the one visible record. Otherwise, the same error may return when the next record is processed.
Build the first version
Ask for the simplest interactive artifact that displays the schema and supports the specific review task. Start with the fictional example and an obvious detail panel. Keep the source data separate from display labels and interaction state. A selected row, a filter, or an open panel should change what the reviewer sees, not silently rewrite the underlying evidence. Add editing only to fields that the specification explicitly identifies as user inputs.
For the first interaction pass, prioritize review date: When the estimate was reviewed and when it requires reconsideration. Then add the mitigation state behavior: The approved response, owner, and evidence of completion, kept separate from residual risk. Use visible text labels for both. Test the core logic before spending time on animation or visual polish. Provide a keyboard path through the controls and preserve a readable empty state when the selected view has no records.
A reusable prompt
Create a risk explorer from the supplied source package. Goal: make the register's rating definitions and unresolved evidence visible before interpreting a risk map. Use these fields: Risk identifier: A stable ID for an uncertain event, separate from the impact description.; Probability rating: A supplied estimate tied to the approved scale and its stated timeframe.; Impact rating: The supplied severity for a defined consequence and population.; Rating evidence: The observation or rationale supporting the assigned ratings.; Review date: When the estimate was reviewed and when it requires reconsideration.; Mitigation state: The approved response, owner, and evidence of completion, kept separate from residual risk.. Preserve source IDs. Rules: Ordinal scale numbers are category codes; multiplying them does not turn the result into a measured probability. Use the approved matrix boundaries instead of inventing red, amber, and green thresholds. Separate inherent and residual ratings so a proposed mitigation cannot imply reduced risk before review. Missing ratings should appear outside the plotted complete set with a visible incomplete count.. First explain the proposed data model and unresolved inputs. Then build the smallest usable version. Use only supplied facts; label the demonstration fictional. Do not invent approvals, thresholds, owners, or external integrations. Include an empty state and explain the expected result for these checks: Clear one rating and reconcile plotted plus incomplete counts with the register total. Switch between inherent and residual views without copying ratings across them. Select a risk and inspect the evidence supporting both scale choices.
Review behavior and edge cases
Check 1. Clear one rating and reconcile plotted plus incomplete counts with the register total. Record the observed result beside the expected result. If the check fails, isolate the affected rule and request a focused correction before rerunning the same case.
Check 2. Switch between inherent and residual views without copying ratings across them. Record the observed result beside the expected result. If the check fails, isolate the affected rule and request a focused correction before rerunning the same case.
Check 3. Select a risk and inspect the evidence supporting both scale choices. Record the observed result beside the expected result. If the check fails, isolate the affected rule and request a focused correction before rerunning the same case.
Repeat the checks after adding another source record or changing the presentation. A working first example does not prove every record is handled correctly. Pay attention to retained selections, stale derived values, and unexplained changes in the number of displayed records. For risk explorer work, the reviewer must be able to tell whether a difference comes from new evidence, an edited rule, or merely a changed view.
Maintain the reviewed version
Keep a version label, source cutoff, and short change record with the finished risk explorer. Record who approved the rules and which demonstration cases were reviewed. When the source package changes, preserve record IDs and revisit the checks affected by the change. Do not treat yesterday's verified result as evidence that today's replacement input is complete.
Before handing the output to another person, review its audience and the material it contains. Use a sanitized demonstration for general feedback when the real source package is confidential. Explain whether changes are saved, whether the output is a preview, and which source remains authoritative. If persistence or sharing is required, verify that behavior in the actual account and intended environment instead of assuming it from a successful preview.
Frequently asked questions
Can Claude fill missing information automatically?
For this task, missing values should remain visible. Ordinal scale numbers are category codes; multiplying them does not turn the result into a measured probability. Ask for the evidence needed to complete the record instead of letting a plausible substitute become an apparent fact.
What should happen when the source records disagree?
Keep the conflicting records with their identifiers. Use the approved matrix boundaries instead of inventing red, amber, and green thresholds. Ask the responsible owner to resolve the discrepancy or leave the affected outcome unavailable when it depends on the disputed information.
What is the smallest useful review example?
A fictional delivery risk R-3 has probability category three and impact category four on an approved five-category scale. Add the missing or conflicting case described above so the review covers more than a clean successful record.
How do I know the first version is ready?
The required fields are present, the rules are visible, and the three listed checks produce their expected outcomes. In particular: Select a risk and inspect the evidence supporting both scale choices. Review the result in the intended reading or interaction environment.
Should the assistant replace the original source?
Keep the source authoritative and review the transformed output separately. This is an exploratory view of an approved risk register, not quantitative forecasting or automatic risk acceptance. Save revisions with a source cutoff so another reviewer can reconstruct which material produced the current result.
Sources and related reading
Consult the current primary references for account-specific availability and controls: Current Claude artifact documentation, Claude sharing documentation. The schema, examples, prompts, and review checks here are editorial recommendations rather than documented built-in features.
For broader context, read the related Claude workflow guide.
