Recovery is a deliberate ownership step
An older assessment may have been held in a browser before the current organization workflow. Recovering that work means reviewing which saved result belongs to you and which organization should receive it. It is not a reason to claim every browser-held record automatically when someone signs in.
RiskSensai provides an explicit saved-assessment recovery route. The page confirms the selected organization and offers a path to choose another. Existing ownership, organization and writing-role boundaries remain in effect. The free assessment remains self-reported and informational after recovery.1
Use this workflow only for your own permitted saved work. A recovery reference supplied by another person is not automatic permission to claim their record.
Use the browser that holds the older work
Start in the browser where the older assessment was saved. Browser-held context may not exist on another device or in another browser profile. If the saved work is not present, do not fabricate a reference or use a colleague’s browser session to make the workflow continue.
Sign in through the existing access flow and open recovery. Read the organization displayed on the page. If it is wrong, use the existing organization-selection path and confirm the correct organization before taking a linking action.
The organization matters because a result about one business should not become another business’s assessment. A shared device or a familiar account name cannot establish that the saved answers concern the currently selected organization.
Review the available saved-work context
The recovery interface reports whether this browser tab holds a saved public-assessment reference; it does not present a full preview of the old answers. Confirm the subject and ownership from your own recollection and permitted working records before linking. Do not treat the existence of a reference as proof that it concerns the selected organization.
| Check | Why it matters |
|---|---|
| Ownership | You should be linking your own permitted saved work |
| Organization | The answers must concern the selected organization |
| Result context | A familiar score alone does not prove the record is the right one |
| Current permission | A read-only reviewer is not authorized to perform the writing action |
If you cannot establish that the record is yours, stop and ask for help. Do not expose recovery handles publicly or paste them into unrelated conversations. The privacy and access principles applying to saved work remain relevant.23
Link only after the context is correct
Use the explicit recovery action when the interface permits it and the review is complete. Linking is a human decision, not a background consequence of signing in or choosing an organization.
If your organization changes while the form is open, re-establish the context before proceeding. A stale organization state should not be interpreted as permission to link the result elsewhere. Close or refresh the workflow as appropriate and confirm the current destination.
Submit once and wait for the response. Do not use repeated clicks to overcome a slow operation or a role denial. The action has to preserve the existing ownership and tenant boundary, not merely produce a success-looking screen.
Distinguish linking from importing into history
Recovery can involve more than one operation: establishing the saved record’s link and making an assessment-history record available. If one part succeeds and another fails, the correct outcome is partial or uncertain—not a fabricated complete success.
Read the feedback carefully. A warning about history import should lead you to inspect the saved state and preserve the safe error reference. Do not automatically repeat the linking request on the assumption that every step failed.
| Feedback | Appropriate next step |
|---|---|
| Confirmed recovery | Inspect the resulting saved record |
| Ownership or organization denial | Resolve the legitimate context; do not bypass it |
| Linked work but unconfirmed history import | Check saved state and ask support to reconcile |
| Uncertain response | Establish what was saved before another write |
This separation prevents duplicate or conflicting recovery attempts from disguising the actual outcome.
Do not turn an older result into a compatible trend
An older record may lack the question-bank information required for current score comparison. Recovery does not invent that missing context. A result can be useful as a historical record while remaining unsuitable for a numerical trend.
When you reopen it, check the available mode, date and result information. Compare only where the system supports compatible records. An absent comparison means comparability was not established; it does not mean the organization’s readiness has remained unchanged.
If the old result differs from current practice, treat it as a dated snapshot of answers rather than an automatically corrected present-day assessment. Run a new assessment through the existing workflow when you need a current self-reported picture.
Worked example: a recovered record with unknown scope
Suppose you saved an older assessment in your usual browser. You now belong to two organizations. Recovery identifies the saved work, but its questionnaire version is not known well enough for current comparison.
You confirm which organization the answers concerned and link it deliberately. After checking the saved record, your working note says:
Older self-reported result recovered into the intended organization. It remains a historical reference. Current questionnaire comparability is not established, so we will not present a numerical improvement claim based on this record.
That note makes the recovery useful without overstating what it proves. A new run can then provide a clearer current baseline with known mode and question-bank context.
When recovery is not available
If the browser no longer holds the saved context, or your role cannot link work, do not assume the route is broken. First distinguish missing local information from an authorization restriction. Ask the organization owner or support to help with the actual issue.
Avoid sending passwords, complete confidential answers or recovery handles unnecessarily. A description of the problem, the intended organization and a safe error reference can be enough to begin investigation.
Recovery is complete when you know which record was linked, where it belongs and which limitations remain. It preserves older work; it does not grant new access, create verified evidence or convert historical self-attestation into formal assurance.
Sources and references
-
RiskSensai. Free Digital Trust Assessment. Explains self-reported scope and authenticated assessment entry. ↩
-
RiskSensai. RiskSensai Security. Describes current evidence and access-control limits. ↩
-
RiskSensai. RiskSensai Privacy Policy. Provides the published data-handling policy. ↩