Reopen a Saved RiskSensai Assessment and Understand What Can Be Compared

A saved assessment is a dated record

When you return to a self-assessment, the first question should be “Which record am I looking at?” rather than “Has our score improved?” A score is meaningful only when you understand the answers, the organization, the questionnaire and the date behind it.

RiskSensai’s organization assessment includes run history and saved-run detail. The workflow helps you revisit informational results based on self-reported answers. It does not create a continuous independently measured risk rating.¹

This distinction becomes important when a team runs a Quick check first and a full assessment later. Both can be useful, but their results should not be casually placed on a single improvement chart as if the questions and coverage were identical.

Open the correct organization’s history

Sign in through the existing assessment workflow and confirm the organization. If you support multiple businesses, use the explicit organization entry step rather than relying on a browser tab that has been open since another session.

Open the assessment history and review the listed dates and modes. Select the saved run you want to examine. Current history is ordered with newer records first and loads a bounded set of records. Do not assume that every assessment ever taken must appear on the first screen.

An empty history means there are no records displayed for that authorized context. It is not evidence that the organization has no risk or that nobody ever performed an assessment elsewhere. If you expect a record, check organization selection, access and whether an older browser-held result needs the separate recovery workflow.

Inspect the saved result before sharing it

When a saved run opens, check these items:

1. The organization is the one the discussion concerns.
2. The date is appropriate for the decision being made.
3. The mode is Quick check or full assessment as expected.
4. The answers reflect what was known at that time.
5. Any priorities are treated as prompts for follow-up, not verified findings.

If a colleague says the score is wrong, identify the particular answer or assumption at issue. “We now have an incident process” may mean a later change occurred, not that the historical result should be silently rewritten. Preserve the distinction between what was answered then and what is known now.

Understand the comparison rule

RiskSensai’s saved-run comparison requires compatible assessment mode and question-bank information. It selects an appropriate older comparable record from the loaded history rather than subtracting any two visible numbers.

A missing change value is not the same as a change of zero. Zero means a comparison was possible and the compared scores were equal. Missing comparison means the system cannot support that subtraction in the current context.

Read a trend without overstating it

If compatible records exist, a displayed change can help you decide where to look next. It does not prove that the risk of an incident has moved by the same amount. Answers can change because practices improved, because the respondent learned more, or because a previous assumption was corrected.

The assessment trend presentation uses a consistent score range rather than turning a small movement into an exaggerated visual change. With too few compatible points, a meaningful trend is not shown. That restraint is useful: one result is a snapshot, and two or more records still require interpretation.

Avoid explaining a positive movement as “verified improvement” unless there is separate evidence for the underlying practice. The platform’s readiness boundary remains informational; formal assurance requires a separately appropriate process.²³

Worked example: a better answer, not a better control

Imagine that an earlier assessment used a favorable answer about access reviews. During preparation for the next run, a colleague discovers that the review covered ordinary users but excluded service accounts. The new assessment records that limitation honestly, and its score falls.

That fall does not necessarily mean the control deteriorated. It may mean the organization now understands the scope more accurately. A useful comparison note would say:

The newer response reflects a newly identified coverage gap. We need to confirm ownership of service-account reviews before treating this as a change in operating practice.

The note explains what happened without using the score as a substitute for evidence. A subsequent assessment might improve after the review process changes, but the team should still retain the dated review records supporting that conclusion.

Build a small comparison record

For a leadership discussion, prepare a compact table outside the assessment if no suitable field is available:

Do not include another organization’s answers or private documents just to complete the table. Access to the assessment is separate from permission to distribute every underlying file.

When an older result is missing

Some older browser-held results have a separate recovery path. That workflow requires explicit ownership and organization context; it is not an automatic import at sign-in. A recovered record with unknown questionnaire information may remain unsuitable for comparison.

If opening a run fails, retain the error and check the saved state through the supported interface. Do not invent a replacement result or repeatedly submit a write operation to recreate it. Ask the organization owner or support to investigate a reference you can safely provide.

Finish the review by separating three conclusions: which saved record you reopened, whether the comparison is supported, and which real-world questions the answers raise. That produces a useful discussion even when the correct numerical comparison is “not available.”

Sources and references

1. RiskSensai. Free Digital Trust Assessment. Explains self-reported scope and authenticated assessment entry. ↩

2. RiskSensai. RiskSensai Security. Describes current evidence and access-control limits. ↩

3. RiskSensai. RiskSensai Trust Center. States readiness and formal-assurance boundaries. ↩