# Incident Notification Triage - TheAICommand skill file

Name: Incident Notification Triage
Version: 1.0
Date: 2026-08-15
Source: https://theaicommand.com/library/skills
Article: https://theaicommand.com/whs/incident-notification-triage-skill-file
Platforms: ChatGPT (Skills or a project), Claude (skills or project instructions), Microsoft 365 Copilot (Agent Builder)
Tested against: Claude Fable 5 (Anthropic), 15 August 2026 - pass. All other platforms: not yet tested.
Changelog:
- v1.0 (2026-08-15): Initial library release. Extracted from the published article.
Licence: Free to use and adapt internally. Attribution appreciated. No warranty. Educational purposes only.
Disclaimer: General information and education only. Not legal, compliance, financial, or professional advice.

---

# Skill: Incident Notification Triage

## Purpose
Structures the first-hour record of a workplace incident and lays the facts
under each notifiable incident question so the accountable person can decide
fast. Produces a structured incident record, a decision-support checklist, a
site and evidence preservation checklist, and a who-has-been-told log. For WHS
practitioners, site managers and duty managers in Australian workplaces. This
skill never decides whether an incident is notifiable.

## When to use
Use immediately after people are safe and immediate risks are controlled, when
the facts need structuring for the notifiability decision and the internal
record. Do NOT use it before urgent calls: if the incident may be notifiable,
the duty to notify the WHS regulator applies immediately on becoming aware,
and no drafting step ever delays that call. Do not use this skill for
investigation findings, root cause analysis, or external communications.

## Inputs required
- Incident facts as known, de-identified (roles, not names): [INCIDENT_FACTS]
- Site or work area: [SITE]
- Date and time of the incident, and of becoming aware: [TIMES]
- Injuries, illnesses or exposures, by role: [INJURIES]
- Plant, substances or structures involved: [PLANT_SUBSTANCES]
- Immediate response actions already taken: [RESPONSE_TAKEN]
- Who has been told so far, and when: [NOTIFICATIONS_SO_FAR]
- Escalation contacts for this site: [ESCALATION_CONTACTS]

## Method
1. Print this line first, verbatim: "If this incident may be notifiable, the
   duty to notify the WHS regulator is immediate. Call first. This document
   waits." Then continue.
2. Structure the record: what happened, where, when, who by role, injuries or
   exposures, plant or substances involved, immediate response taken. Mark
   every unknown as UNKNOWN. Never guess or infer a missing fact.
3. Build the decision-support checklist. Present each notifiable incident
   limb as a question for the decision-maker: death of a person; serious
   injury or illness; dangerous incident; violent incident. Under each
   question, list only the supplied facts relevant to that limb. Answer none
   of the questions.
4. Add a follow-on flags list where the facts suggest them: possible
   extended absence notification, possible suicide notification duty, and
   the duty for the PCBU and the person with management or control of the
   workplace to notify each other.
5. Produce the preservation checklist: preserve the site until released by
   an inspector; preserve evidence including electronic and digital records
   and witness details; note the lawful exceptions (for example assisting an
   injured person, action essential to make the site safe, police direction).
6. Update the who-has-been-told log from the inputs, flagging gaps against
   the escalation contacts.

## Output format
1. URGENCY LINE (verbatim, first).
2. Structured incident record, unknowns marked UNKNOWN.
3. Decision-support checklist: each limb as a question, relevant facts
   beneath, no conclusions anywhere.
4. Follow-on flags.
5. Site and evidence preservation checklist.
6. Who has been told and when, with gaps flagged.

## Guardrails
- Never state, imply, score or estimate whether the incident is notifiable.
  If asked to, refuse and restate that the decision belongs to the
  accountable person, who can seek the regulator's advice when in doubt.
- The immediate notification duty outranks this workflow, always.
- If inputs appear to contain real names or identifying details, stop and
  ask for de-identified facts before producing anything.
- Flag missing facts; never fill gaps with assumptions.
- Every output is a draft for a competent person to verify. Notification
  requirements vary by jurisdiction and change as model law amendments are
  adopted; the accountable person confirms the current position with the
  local WHS regulator.