Skip to main content

Reporting should lead to learning, not blame.

A strong safety culture focuses on systems, not blame. When teams feel safe to speak up, we uncover the real issues, take meaningful action, and prevent harm.

Better reviews. Better learning. Better outcomes.

A six-stage loop - speak up, be heard, understand, respond, learn, trust grows - captioned safe to speak, fair and systems focused, and learning is shared. Fair response and visible learning strengthen our culture, and a return path from trust back to speaking up reads: more willing to speak up.

Systems thinking

Look beyond the person. Learn from the system.

In patient safety, the most useful question is not simply who made the mistake. It is what conditions allowed this event or near miss to happen, and what can we improve so the risk is less likely to repeat.

Accountability in Nexus means ownership of follow-up, not ownership of blame.

A ring of five conditions - tools, communication, training, workflow and environment - around a central system lens captioned: ask what shaped the outcome.

Teams speak up when they trust the response.

When people feel respected, supported, and confident that reporting leads somewhere useful, they are more willing to raise concerns.

Fair review starts with contributing factors, not assumptions.

Look at tools, training, environment, communication, and workflow before reducing an event to one person's actions.

Accountability is different from blame.

A fair culture still expects follow-through. The goal is clear responsibility for improvement without turning responsibility into punishment.

Fair review

A fair review starts with contributing factors, not assumptions.

Patient safety events often involve communication gaps, workflow friction, unclear handoffs, training needs, policy ambiguity, environmental factors, or competing demands in a busy environment.

Reported event

Near miss or patient safety concern

The first review step is to understand what happened before deciding what should change.

Initial risk
Visible concern
Review stance
Curious, structured, fair

Fair review asks better questions.

  • What conditions shaped the event?
  • What made the right action harder?
  • What helped prevent greater harm?
  • What can we improve before it happens again?
  1. Communication gapsUnclear information, incomplete updates, or messages that did not reach the right person.
  2. Handoff issuesInformation lost during shift changes, transfers, discharges, or transitions.
  3. Workflow frictionProcesses that rely on memory, workarounds, or unclear ownership.
  4. Training or policy clarityExpectations, protocols, or responsibilities that may need reinforcement.
  5. Operational pressureBusy caseloads, interruptions, staffing strain, or competing priorities that increase risk.

Support after difficult events

Some events may require more than routine review.

Event severity, context, and the needs of the people involved may indicate that additional support is appropriate alongside the safety review.

Review contextLeaders see signals that may need additional support.
  • Patient impact
  • Human impact
  • Event context

Some signals need attention before patient harm tells the story.

Shared clarification

When a signal reveals uncertainty, conflicting expectations, or an opportunity to make the safer path clearer for everyone.

Team reflection

When a near miss, recurring concern, or difficult event would benefit from structured discussion of what happened, what made the situation difficult, and what the team needs going forward.

Supportive check-in

When the human impact of an event suggests that someone involved may benefit from timely acknowledgment, follow-up, and support.

Culture in practice

When something goes wrong, start with support.

Hard cases happen in every hospital. What defines a safety culture is what comes next: for the patient, and for the person who was there.

Two gowned and masked veterinary team members working together at the surgical table, one passing an instrument to the other.
  1. A difficult caseA veterinary nurse is shaken after a patient is harmed despite the team doing everything they knew to do.
  2. Start with supportHer leader checks in first. Review comes next, focused on understanding what happened rather than assigning fault.
  3. Understand the systemThe review identifies a workflow gap that could have made the same step difficult for anyone on the team.
  4. Bring the learning backThe team makes a change, shares what was learned, and the person involved can see that speaking openly led to improvement.

Learning loop

Trust grows when teams can see what happens next.

Reporting builds trust only when people can see that concerns are heard, reviewed fairly, acted on, and turned into learning.

Six stages circling a centre marked trust grows, captioned: visible follow-through builds trust. One, speaking up. Two, fair review. Three, meaningful action. Four, visible learning. Five, greater trust. Six, more willingness to speak up, which leads back to speaking up.

Common questions

The objections this usually raises.

If we stop blaming people, don't we lose accountability?

Accountability is different from blame. Judge the behavior, not the luck of the outcome. A fair review separates error, at-risk behavior, and recklessness, and responds differently to each.

What if someone genuinely was reckless?

Then that is addressed, and it always was. Systems thinking adds a second step rather than removing the first: after you have dealt with the person, the conditions are still there for the next one.

Our team doesn't report much. Where do we start?

People don't report for one of two reasons: they are afraid of what happens to them if they speak up, or they have never seen anything come of it when they did. A low report count measures trust, not safety.

How does Nexus support someone after a serious event?

We're not a counseling service, and we don't pretend to be. What Nexus does is make sure a serious event doesn't slip through the cracks just because a patient wasn't harmed. Our human impact scoring catches the cases that hit a team hard, even when the clinical outcome was minor, so they get flagged for a debrief the same way a major clinical event would be.

From there, we lean on the people who actually do this work: Not One More Vet, the Veterinary Hope Foundation, and AVMA's wellbeing resources. If someone needs to talk to someone right now, call or text 988, or reach out to NOMV's hotline.

How long before culture changes?

That depends on leadership more than on anything else. Culture does not shift because a policy was published. It shifts when the people in charge commit to it visibly, invest in it, and hold to it when it is inconvenient. Teams read that faster than any announcement, and they recalibrate on whether the last report went anywhere. Nexus is built to make that commitment visible: it shows leaders what is being raised, keeps the follow-through in the open, and gives the team something to see rather than something to take on faith.