What a case keeps from the day it ran
A case records what was true when its investigation ran. Changing a setting afterwards does not reach back into it.
A case records what was true when its investigation ran. Changing a setting afterwards does not reach back into it: the case keeps the vendors, the procedures and the deadline that applied at the time.
This is what makes an old case defensible. A reviewer reading a decision from eighteen months ago sees what the decider saw, not what the organisation has configured since.
What a case keeps
| Change it now | The case that already ran |
|---|---|
| Connect a vendor | Keeps the coverage it had. The new vendor is not consulted |
| Upload a new version of a procedure | Keeps the findings it had, cited against the version in force then |
| Change a priority’s resolution time | Keeps the deadline already worked out |
| Publish a new template version | A report keeps the version it was created from |
How to apply a change to an open case
Ask the agent in the case’s side panel to run the investigation again. It reads what the case holds now, with whatever you have connected or published since, and reaches its recommendation independently of the first run. See what the agent does on a case.
A closed case is not re-run. It is the record of a decision, and a decision is answerable to what was known when it was taken.
Related
Reconstructing a case for an auditor
How to show what was known, what was decided and who decided it, months after the case closed.
The audit log
Cogentic records every change to a case against whoever made it. Reading one is not a change, so it leaves no entry.
What you can show an auditor
An auditor asks what you concluded, what you knew and who decided. Cogentic holds all three, and only some of it leaves as a file.
Last checked against the product on .