Cold-Review Escalation

Route post-signoff cold-review findings by impact and remediation status.

Description

Post-signoff review findings can require follow-up based on impact and unresolved remediation.

Post-signoff review findings can require follow-up based on impact and unresolved remediation. Action uses fixed priority.^[1]

Route post-signoff cold-review findings by impact and remediation status.

When to use Cold-Review Escalation

Use this tool to route post-signoff cold-review findings by impact and remediation status.

Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.

How to use Cold-Review Escalation and understand its results

Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
Enter materialFinding, reportImpact, regulatoryImpact, remediationComplete, governanceNotified using the field table and calculation rules, then run the tool.
Read escalationScore, action, followUpRequired. The explanation below defines the units, signs, ordering and any flags or placeholder values.
If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.

Input field	Meaning	Value type; see rules below	Requirement
materialFinding	Finding is material	boolean	Required
reportImpact	Finding affects issued report	boolean	Required
regulatoryImpact	Finding has regulatory impact	boolean	Required
remediationComplete	Remediation complete	boolean	Required
governanceNotified	Governance notified	boolean	Required

Enter booleans. Regulatory AND report→legal-review; else material without notification→notify-governance; else incomplete→remediate; else document. Follow up if incomplete OR report OR regulatory.

score=max(0,3material+3report+2regulatory−2complete)

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
escalationScore	Escalation score	integer; minimum: 0
action	Cold-review action	string; one of "document", "remediate", "notify-governance", "legal-review"
followUpRequired	Follow-up required	boolean

json

{
  "input": {
    "materialFinding": true,
    "reportImpact": false,
    "regulatoryImpact": false,
    "remediationComplete": false,
    "governanceNotified": false
  },
  "output": {
    "escalationScore": 3,
    "action": "notify-governance",
    "followUpRequired": true
  }
}

Limitations and assumptions

No notification is sent, report withdrawn or legal/reporting duty determined.

Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.

Alternative or Complementary methods

Use Sensitive-Matter Routing: Route sensitive audit matters from supplied indicators. For a complementary task, use Remediation Aging: Age remediation findings against a caller-supplied target.

References

Cold-Review Escalation — tool.io

Similar or alternative tools

Sensitive-Matter Routing
Route sensitive audit matters from supplied indicators.
Remediation Aging
Age remediation findings against a caller-supplied target.