Skip to main content
< All Topics
Print

Incident/Event Reporting

At Cognitive Organics, we use incident and event reporting to keep clients and staff safe, improve our systems, and learn from problems or near misses.

Reporting is not about blame. It’s about safety, transparency, and improvement.

This section explains what counts as an incident, when and how to report, and what happens after you submit a report.


What is an Incident or Event?

An incident (or reportable event) is any situation that:

  • Involves actual harm or significant risk of harm to a client, staff member, or visitor
  • Represents a safety concern, error, or unusual event
  • Might require follow-up, documentation, or system review

Incidents can be clinical, safety-related, environmental, behavioral, or administrative.

Examples of incidents:

  • A client fall, injury, or medical emergency on-site or during a visit
  • A client making a credible threat of harm to self or others
  • A staff member being threatened, harassed, or assaulted
  • A serious technology failure that interrupts a session (especially in crisis situations)
  • A medication or lab-related error that could affect client safety
  • A breach or potential breach of privacy/PHI
  • A significant documentation or billing error that affects care or legal/compliance risk
  • Any situation where 911 or emergency services are called

Near Misses

near miss is an event that could have caused harm but didn’t—often because of luck or because someone caught it in time.

Examples of near misses:

  • You almost sent PHI to the wrong person but caught it before hitting “send”
  • A client nearly fell, but staff helped them stabilize and no injury occurred
  • A serious lab result was routed incorrectly but discovered before affecting treatment
  • A safety concern was identified just before a situation escalated further

Near misses are important. They show us where systems and processes need to be strengthened before someone gets hurt.

We want near misses reported.


When Should You Report?

You should complete an incident/event report when:

  • There is actual harm or a significant safety risk
  • There is a threat, escalation, or violent incident
  • You suspect a privacy/PHI issue
  • You experience or witness workplace violence or harassment
  • You are involved in or discover a serious error or near miss

When in doubt, report it.
If you’re asking yourself “Is this big enough to report?” it probably is.


Your Role in the Moment

During the incident or event, your first responsibilities are:

  1. Protect safety.
    • Address any urgent medical or safety needs.
    • Involve 911 or emergency services when needed.
    • Follow our emergency and safety procedures.
  2. Communicate.
    • Notify your supervisor or on-site lead as soon as it’s safe and practical.
  3. Stay factual.
    • Focus on what you’re observing and what actions you’re taking.

Once the immediate situation is stabilized, your role shifts to documenting and reporting.


How to Report an Incident/Event

Step 1: Use the designated incident/event report form

Step 2: Be factual and specific

In your report, include:

  • Date, time, and location of the incident
  • Names and roles of people involved (clients, staff, others)
  • A clear, factual description of what happened
    • What you saw, heard, or observed
    • What actions were taken (by you and others)
    • Any immediate outcomes (injury, transfer, 911 involvement, etc.)
  • Any follow-up steps already taken (e.g., contacted family, notified supervisor, called 911)

Avoid opinions, assumptions, or blame. Stick to objective, observable information.

Step 3: Notify your supervisor

  • Let your supervisor (and/or designated leader) know that an incident report has been submitted.
  • For serious events (violence, 911, significant injury, major privacy breach), notify leadership immediately, not just through the form.

Our Culture: Non-Punitive, Learning-Oriented

We use incident and event reporting to learn and improve—not to punish people for honest mistakes.

We expect staff to:

  • Report incidents and near misses promptly and honestly
  • Participate in follow-up discussions if needed
  • Help us identify patterns or system issues

You will not be punished for making a good-faith report about a safety concern, mistake, or near miss.

However, deliberate misconduct, repeated disregard for policy, or intentional failure to report serious issues may result in corrective action.


What Happens After You Report

Once an incident/event report is submitted, leadership will:

  • Review the information and determine the level of risk and urgency
  • Decide what additional steps are needed (e.g., client follow-up, staff support, environment changes, additional documentation)
  • Determine whether external reporting or notification is required (e.g., to clients, regulators, or payers)
  • Look for patterns or themes over time (e.g., repeated issues in a particular process or location)

You may be asked for clarification or additional details. This is part of understanding what happened—not an accusation.


How Incident Reporting Connects to Quality & Safety

Incident and event reports help us:

  • Protect clients and staff
  • Improve processes, training, and systems
  • Stay compliant with regulatory and accreditation standards
  • Identify where we need more resources, support, or clearer policies

Every time you file a report, you are contributing to a safer, more honest, and more effective organization.


What This Means For You as Staff

Practically, this means you:

  • Take safety concerns and unusual events seriously
  • Know where to find the incident/event report form and how to fill it out
  • Report incidents and near misses honestly, even if you were directly involved
  • Keep your descriptions factual and clear
  • Inform your supervisor and communicate promptly when serious events occur

You are not expected to be perfect. You are expected to be honest, safety-focused, and willing to engage in a culture of learning and improvement.

Table of Contents