IT Incident Report Drafter

Drafts a technology incident report in the RMiT format.

ConfidentialGenAIBNM reportableTechnology incident reporting · by Daniel Wong · v1.3

★ 4.4 180 runsUpdated 2026-07-12

Prompt template

3 variables

Draft a technology incident report from the timeline below, in the structure Group IT uses for incidents that may need reporting under BNM RMiT.

Incident ID: {incident_id}
Service affected: {service}
Timeline:
{timeline}

Sections: summary; customer and business impact; timeline (local time, MYT); root cause (confirmed or suspected, say which); containment and recovery; whether regulatory notification criteria appear to be met (for the Technology Risk team to confirm); follow-up actions with owners.

{incident_id}{service}{timeline}

Playground

Simulated sandbox

{incident_id}{service}{timeline}

Ownership and sensitivity

Owned by

Group Data & AI Platform Engineering

Accountable owner: Hafiz Othman

Who approves access

Owner, Platform Engineering, Hafiz Othman

Confidential

Business-sensitive. Models and data products scoped to named business units.

Entitlement per business unit, approved by the owner; conditions attach.

GenAI: Generates text; prompt screening for customer data and output review apply.
BNM reportable: Feeds a regulatory return or a figure reported to Bank Negara Malaysia.

Example input & output

Example input

{incident_id}: INC-2026-0712
{service}: Vertex AI shared endpoint serving card-fraud-detector
{timeline}: 02:14 p95 latency rises from 40ms to 900ms. 02:19 card authorisations fall back to rules-only scoring. 02:31 on-call Daniel Wong paged. 02:48 cause identified: autoscaling min replicas set to 1 after config change. 02:55 replicas restored to 4. 03:02 latency normal, model scoring resumed.

Example output

Summary: For 48 minutes (02:14 to 03:02 MYT) the fraud scoring endpoint degraded and card authorisations fell back to rules-only screening. Impact: no authorisations were declined because of the incident; fraud screening ran on rules only between 02:19 and 03:02. The number of transactions screened on rules only is [to confirm with Financial Crime]. Timeline: 02:14 latency rise; 02:19 automatic fallback to rules; 02:31 on-call paged; 02:48 cause found; 02:55 replicas restored; 03:02 recovered. Root cause (confirmed): a configuration change reduced the endpoint's minimum replicas from 4 to 1. Containment: replicas restored; fallback worked as designed. Regulatory notification: the criteria may be met because a customer-facing control was degraded. For Technology Risk to confirm. Follow-up: add a policy check that blocks minimum replicas below 4 on Tier 1 endpoints (Daniel Wong); alert on fallback activation within 2 minutes (ML Platform).

Details

Author: Daniel Wong
Version: v1.3
Rating: ★ 4.4
Runs: 180
Licence: BU Restricted
Updated: 2026-07-12

Powered by

policy-rag-copilot →

This template is tuned for the target model above. Forked copies keep the same target model binding until republished.

Community · 0 threads

Questions, findings and requests from the business units that use this asset. Owners reply here; threads with upvotes surface to the owning team's inbox.

No threads yet. Be the first to ask, or to share what you found.