Reviewing change and keeping assurance current
A proposed vendor, tool or data-use change can affect commitments already made. Reviewing those relationships before accepting a change helps the team find the questions that need an owner.
Foresight
General meaning: Assessing a proposed change before applying it to the accepted record.
Why it matters
A proposed vendor, tool or data-use change can affect commitments already made. Reviewing those relationships before accepting a change helps the team find the questions that need an owner.
With Kanonik
Foresight compares a proposed change with your approved promises before you make it: adding a vendor or replacing one. For each promise it shows No conflict, Conflict, Needs information or Not applicable, with the facts it used, and it writes nothing to the accepted record. It is a check against recorded commitments, not an automatic legal verdict.
What to consider
The assessment depends on the modeled scope and the information supplied. Missing support is an unresolved question, not an automatic legal breach.
Live assurance
General meaning: Keeping assurance conclusions under review as the supporting information changes.
Why it matters
An answer accepted for one review may need attention when its supporting record changes. Connecting answers to their basis makes that review more focused than starting the research again.
With Kanonik
Saved claims connect to their evidence and decisions so changes to recorded support can bring an answer back for review. This keeps answers current between audits for changes that are recorded in Kanonik. Changes in systems that are not connected are not detected.
What to consider
Kanonik can assess available supporting information. An unreported change in an unconnected system remains outside that view.
Rechecking on change
General meaning: Revisiting an earlier check when information it relied on changes.
Why it matters
A team can revisit the decisions affected by updated evidence instead of assuming an earlier approval lasts indefinitely.
With Kanonik
When a record that a check relied on changes in Kanonik, the check is revisited. Kanonik does not watch unconnected systems, so a change that nobody records is not picked up.
What to consider
Rechecking does not itself fix a system or authorize a change. An owner must review the result and any follow-up work.
Related scenarios: Rechecking on change | Glossary definition
Continue reading
Run your own record on Solo.
Solo is $99 a month and starts with a 14-day trial.