Incident Reporting Process

Key Facts

• Current state: Inconsistent. Serious incidents are documented; minor incidents often are not
• Root cause: Manager works 16-hour shifts; exhaustion at 3am prevents thorough documentation
• No template exists: Staff create ad-hoc notes without standardised categories or escalation paths
• Compliance risk: Liquor licence requires documented incident record and CCTV retention for evidence
• Solution: Standardised form + dictation software for tired staff + security coordination

The Problem

Pride of Our Footscray’s incident reporting process is fragmented and unreliable. While serious incidents (violence, injury) are typically documented, smaller incidents (patron ejection, alcohol refusal, confrontation) often go unrecorded. This leaves gaps in the venue’s safety and compliance record.

The root cause is structural: managers work long shifts and are too fatigued at the end of the night to write detailed incident reports. Without a fast, easy method to capture incidents as they happen, documentation suffers.

Current Workflow Gaps

• No standardised form — each staff member documents differently (if at all)
• No incident categorisation — unclear whether incidents are “information only” or require escalation
• No integration with security — VCPG Security may not be notified of incidents relevant to patron banning decisions
• Documentation burden — writing detailed reports by hand when exhausted is impractical

Solution Pathway

Phase 1: Standardised Form

Create a one-page incident reporting form capturing:

• Date, time, location (bar/entry/dancefloor)
• Incident type (patron ejection, alcohol refusal, violence, harrassment, medical, property damage, other)
• Persons involved (names/descriptions)
• Brief description of what happened
• Actions taken (immediate response)
• Escalation required? (yes/no)
• Recommended follow-up (patron ban, police report, etc.)

Phase 2: Dictation Solution

Introduce dictation software (e.g., Otter.ai, Google Recorder) so staff can speak incident summaries instead of writing them. Recordings are transcribed and attached to forms.

Phase 3: Security Coordination

Link incident reports to Banned Persons List. Management reviews incidents quarterly to identify patrons who should be banned.

Mandatory Notification Requirements

Source: Late Night Venue WHS Research — full regulatory analysis including Victorian OHS Act 2004, LCRA 1998, and Private Security Act 2004 amendments.

The Occupational Health and Safety Act 2004 (Vic) imposes a two-category incident notification system. Failure to report is an indictable offence carrying a $244,000 body corporate penalty (s 38).

Category 1 — Death or Serious Injury (s 37(1))

Notifiable if any person (worker or patron) suffers:

• Death
• Hospital admission requiring immediate treatment
• Amputation
• Serious head, eye, or spinal injury
• Loss of bodily function
• Serious burns
• Medical treatment required within 48 hours of exposure
• Serious lacerations

Category 2 — Dangerous Occurrences (s 37(2))

Notifiable regardless of injury:

• Collapse of plant or structure
• Implosion or explosion
• Electric shock
• Hazardous atmosphere
• Immediate threat to life

Notification Procedure

1. Immediate verbal notification: Phone WorkSafe Victoria on 13 23 60 immediately upon becoming aware
2. Written notification: Within 48 hours of becoming aware of the incident
3. Site preservation: Maintain the incident site undisturbed until a WorkSafe inspector directs otherwise (exception: attendance necessary to protect life or property)

Patron Injuries

Patron injuries are notifiable on the same basis as worker injuries under s 23 (duty to non-employees). A patron hospitalisation at Pride triggers the same reporting obligation as a staff injury.

Parallel Reporting Obligations

In addition to WorkSafe notification, the following may apply:

Obligation	Trigger	Contact/Action
Victoria Police	Criminal conduct suspected, or death	000 or local station
WorkCover	Worker injury and claim likely	Lodge claim
CCTV preservation	Any incident	Minimum 4 weeks retention (LCRA requirement)
Liquor licence incident register	Any incident	VGCCC requirement — log in venue register

Case Study: Cheeky Squire (Frankston, 2023)

Delayed incident notification resulted in enforcement consequences. This case demonstrates the practical risk of inadequate reporting procedures for late-night venues.

See Late Night Venue WHS Research for the full regulatory analysis including Victorian OHS Act 2004 obligations, LCRA 1998 requirements, and Private Security Act 2004 amendments.

Related Pages

• Late Night Venue WHS Research — source: mandatory notification framework and WHS obligations
• Banned Persons List — Output of incident review process
• Operational Safety — Broader safety management
• VCPG Security — Security partner
• Late Night On-Premises Licence — Regulatory requirement