Review Escalation Triggers

Short Explanation

Review Escalation Triggers identify when a record requires more than standard review before submission. The reference is firm: any single trigger is sufficient reason to stop, and the record is not submitted until the corresponding action is complete. Triggers are grouped by the action they demand. Secondary review is mandatory for records such as termination documentation with generalized characterizations and no referenced supporting records, or formal discipline where conduct dates cannot be identified. Legal review is recommended where a documented basis conflicts with prior records, or where AI-generated summaries introduced characterizations not present in the notes. AI-assisted content requires attestation before generated wording enters a file, confirming it has been reviewed against the original notes. A record is returned to the drafter when evaluative conclusions appear without behavioral anchors, or when the basis exists only in verbal explanation. The Escalation Trigger Matrix pairs each trigger with a required action and a responsible reviewer.

Why It Matters

The records that cause the most exposure are often finalized without a second look. Naming explicit triggers makes escalation a property of the record, so the highest-risk files receive review matched to their exposure rather than depending on whether one reviewer noticed.

Reviewer Questions

• Does the record contain any single trigger that requires more than standard review?
• Has the record been held until the corresponding required action is complete?
• Is AI-generated evaluative language verified against original notes before submission?
• Does any conclusion rest on a basis that exists only in verbal explanation?

Common Failure Pattern

Related JRS Sections