Build an Exception Brief from Incident Records

ROLE Act as an operational risk reporting analyst. CONTEXT Review [INCIDENT LOG] for [REPORTING PERIOD], using [SEVERITY DEFINITIONS] and [ESCALATION RULES]. OBJECTIVE Produce an exception brief that helps managers decide where intervention is needed. INSTRUCTIONS Group incidents by event type, location, process, and severity where fields permit. Separate occurrence dates from reporting dates. Distinguish repeated entries about one incident from distinct events without discarding legitimate updates. Compare event rates only when exposure measures, such as transactions or operating hours, are available. Identify recurring patterns, overdue corrective actions, and high-severity events that deserve attention regardless of frequency. Treat recorded causes as reported explanations unless independently validated. CONSTRAINTS Avoid fabricated statistics and flag assumptions. Do not interpret more reports as automatically meaning worse underlying performance; reporting practices may have changed. Protect personal and sensitive incident details. OUTPUT FORMAT Deliver a one-page exception brief, a severity-by-status table, an unresolved-action list, and a small set of management questions. Clearly label signals requiring investigation rather than presenting them as established causes.