How to Document Duty to Warn and Tarasoff Situations in Clinical Practice

Why Duty to Warn Documentation Is Its Own Category

Most of what therapists document carries clinical weight: what the client reported, how they presented, what interventions were used, what the plan is for next session. The stakes are real, but the documentation rhythm is manageable.

Duty to warn situations are different. When a client discloses a credible threat of serious harm to an identifiable third party, the documentation you produce in the next hours carries weight that can follow you for years. A licensing board investigation, a civil lawsuit, or a coroner's inquiry will all return to that note. What did the clinician know? When did they know it? What did they assess? What did they decide, and why? Did they act?

These are not hypothetical questions. They are the actual questions that get asked when something goes wrong.

This guide is for therapists, licensed counselors, clinical social workers, and psychologists who want a concrete documentation framework for duty to warn situations: one that is legally defensible, clinically complete, and practical to write under pressure.

The Legal Framework: Tarasoff and What Followed

Tarasoff v. Regents of the University of California (1976) is the foundational case in U.S. duty to warn law. A graduate student at UC Berkeley, Prosenjit Poddar, told his campus psychologist that he intended to kill Tatiana Tarasoff. The treating psychologist reported the threat to campus police but did not warn Tarasoff directly. Two months after the therapist's notification to police, Poddar killed her. The California Supreme Court held that therapists have a duty to protect identifiable third parties from a patient's credible threats of serious violence.

The ruling produced two important principles. The first is the duty to protect, which is the broader obligation to take reasonable steps to prevent foreseeable harm to third parties. The second is the duty to warn, which is one mechanism for fulfilling that duty, specifically the act of notifying a potential victim directly.

Since 1976, nearly every U.S. state has enacted its own statute addressing this obligation. The specifics vary significantly: some states require warning (mandatory), others permit it as a shield from liability (permissive), and some define the triggering threshold differently. What counts as a credible threat, who must be warned, whether law enforcement notification alone satisfies the duty, and whether the duty can be triggered by property threats as well as bodily harm all depend on your state's law.

This matters enormously for documentation. Before you write anything else, you need to know your state's specific statutory requirements. Your note should reflect that you acted in accordance with those requirements, not a generic duty to warn framework.

What Triggers the Duty

Not every expression of anger or frustration toward another person triggers a duty to warn. The threshold is typically described in terms of three elements:

A serious and imminent threat of violence. Venting frustration about a difficult coworker does not meet this threshold. A specific statement of intent to harm, with access to means, and a target the client can reach, often does. The imminence component is clinically significant: a threat expressed in the context of acute crisis is different from a future-oriented statement made in a stable presentation.

An identifiable potential victim. The threat must be directed at a person (or persons) who can be specifically identified, not toward a general class of people. "I want to hurt someone" typically does not trigger the duty. "I am going to hurt my landlord David at the address I've been evicted from" typically does.

A nexus between the client's history or mental status and the plausibility of follow-through. Clinical context matters. A client with no history of violence, organized thinking, and strong protective factors who expresses frustration with a family member presents differently than a client with a prior assault conviction, active paranoid ideation, and recent access to firearms who names a specific target.

Your documentation should reflect that you assessed all three components, not just that a threat was stated.

Documenting the Threat Assessment Process

When a client makes a statement that you assess as potentially triggering the duty to warn, the documentation task is to show your clinical reasoning, not just your conclusion.

Capturing the Threat Statement

Document the client's words as specifically as possible. Direct quotes are defensible; paraphrases are not. A note that records "client stated he would 'blow up' his sister's car if she did not return his belongings" is more useful than "client expressed anger toward family member." The more specific the threat, the more important it is to document the exact language.

If the threat emerged partway through a session, note when in the session it appeared. If it came after a significant emotional escalation, document the sequence. Context shapes clinical meaning, and the note should capture that.

Assessing Imminence and Credibility

Document each element you assessed to evaluate the seriousness of the threat. A structured format helps here. Consider recording:

History of violence. Has this client made similar statements before? Have those statements ever preceded behavior? Are there prior arrests, convictions, or documented violent incidents? A client who has threatened previously and acted before is a different risk profile than one with no behavioral history.

Specificity of plan. Did the client name a target? A location? A method? A time frame? The more specific the details, the more clinically significant the threat. Document what the client disclosed and what you asked about.

Access to means. Does the client have access to weapons, particularly firearms? Have they described how they would carry out the act? Means access elevates the clinical significance of any threat that has specificity.

Mental status at time of disclosure. Was the client organized, disorganized, intoxicated, or in a dissociative state? The reliability of the client's self-report and the clinical weight of the threat statement are both affected by mental status. Document your observations.

Precipitating context. What prompted the disclosure? A recent loss, a perceived grievance, an acute stressor? Understanding what triggered the statement helps assess whether the risk is situationally bound or more pervasive.

Protective factors. Are there factors that reduce the likelihood of follow-through? Strong social support, insight into the consequences of violence, stated motivations not to act (children, employment, values), engagement in treatment? Protective factors belong in the threat assessment note alongside risk factors, not as a counterweight that eliminates concern, but as clinical data that informs the full picture.

Fictionalized Example: Well-Documented Threat Assessment

Consider this example of how a clinician might document the threat assessment component of a duty to warn note:

Threat disclosure: Client stated during the final 20 minutes of the session: "I bought a gun last week and I swear to God I'm going to use it on Marcus [last name omitted, relationship identified as client's former employer] if he doesn't pay me back by Friday." Client was asked to elaborate. He confirmed the firearm purchase ("a 9mm, I keep it in my truck"), stated the target's first and last name and place of work, and indicated the threat was not hypothetical ("I'm not just venting, I'm serious"). Client appeared organized, articulate, and not intoxicated.

Risk assessment: History of one prior domestic violence charge (2021); no documented prior threats to non-partners; no prior psychiatric hospitalizations. Access to means confirmed (client disclosed firearm ownership). Specific plan named with time frame (by Friday). Identified victim is accessible (client knows his employer's location and work schedule). Precipitating factor: client terminated from employment and alleges withheld wages. No current protective factors reported as sufficient to contain the risk; client declined to consider voluntary disarmament; stated he "doesn't see another way."

That level of specificity is what turns a note from a documentation artifact into a defensible clinical record.

Documenting the Decision-Making Rationale

The moment after the threat assessment is where the most consequential documentation happens. You need to record not just what you decided but why you made that decision.

When You Determine the Duty Is Triggered

Document that you determined the legal threshold for duty to warn was met in your jurisdiction and cite the specific elements that led to that determination. You do not need to recite the statute, but your note should reflect that you considered whether the threat met the threshold. A line such as: "Based on the client's specific statement of intent, named victim, confirmed access to means, and imminent time frame, I determined this disclosure met the threshold for duty to warn under [your state's statute or equivalent standard]" makes your reasoning legible.

If you consulted a supervisor, a colleague, or a licensing board ethics line before making the decision, document that consultation in the note. Record the name of the person you consulted, the date and time, and the gist of what they advised. Consultation is both clinically appropriate and legally significant: it demonstrates that your decision-making was not made in isolation.

When You Determine the Duty Is Not Triggered

This is an equally important documentation scenario that many clinicians underestimate. If you assessed a threat and determined it did not meet the threshold for duty to warn, document that determination explicitly and with reasoning.

A note that says "client expressed frustration toward colleague, no duty to warn action taken" is inadequate. A note that says "client expressed frustration toward a workplace colleague in the context of a work conflict; statement was general and did not include specific intent to harm, no named method or plan, no imminence, and client denied any intention to act. Client has no prior history of violence. Risk assessed as low; no duty to warn or protect action indicated at this time" tells a defensible story.

Clinicians who fail to document the reasoning behind non-action create the same liability risk as those who fail to document action. If the situation later escalates, reviewers will look for evidence that you took it seriously and made a reasoned decision, not that you overlooked it.

Ambiguous Threats

Many duty to warn situations are not clear-cut. The client may express something that feels alarming but falls short of a specific, imminent, credible threat. The clinician must decide whether to take protective action and document both the ambiguity and the reasoning.

In ambiguous cases, document that you assessed for the threshold elements and that the evidence was equivocal. Document what additional information you sought (follow-up questions, collateral contact) and how the answers affected your assessment. If you chose to defer a duty to warn determination pending further information, document that too, along with your plan to reassess. Document what you would do differently if the clinical picture changed.

Documenting the Notification

If you determine a duty to warn situation exists and act on it, the notification itself requires documentation that is as careful as the threat assessment.

Notifying Law Enforcement

Most clinicians in most states satisfy the duty to warn at least in part by contacting law enforcement. When you do, document:

• The date and time of the call
• The agency contacted (jurisdiction, specific department or unit)
• The name and badge number of the officer or dispatcher you spoke with, if obtainable
• What you disclosed: the nature of the threat, the identity of the client (if your state's duty to warn statute provides a liability shield for confidentiality breach in this context), the identity of the potential victim, and any relevant details about means or timeline
• The officer's stated response or plan
• Any follow-up actions they indicated they would take

Keep a written record of this call in the clinical file, separate from or appended to the session note. If you left a voicemail or were unable to reach a live officer, document the attempt, the time, and your follow-up actions.

Notifying the Potential Victim

In many states, notifying the potential victim is either required or strongly advisable as part of fulfilling the duty. This notification is sensitive and requires clinical judgment about how to communicate a credible threat without causing disproportionate panic or further elevating danger.

Document that the notification occurred, including:

• The date and time
• The method (phone call, in-person if the person was reachable, contact through law enforcement)
• Whether you reached the person directly or left a message
• What information you conveyed (that you were a mental health professional, that you had received information indicating they may be at risk, any specific safety recommendations such as contacting police or avoiding a particular location)
• The person's response if you spoke with them directly

If the potential victim could not be reached, document your attempts. Multiple documented attempts demonstrate good-faith effort.

Fictionalized Example: Notification Documentation

Law enforcement notification: Called [City] Police Department at 4:47 PM on [date]. Reached Officer R. Torres, badge number 2241. Disclosed client's stated intent to harm Marcus [full name provided to officer], provided victim's workplace address as stated by client. Described client's means (9mm firearm in client's vehicle). Officer Torres stated he would attempt to contact the potential victim and conduct a wellness check at the victim's residence. Officer provided case number [number].

Victim notification: Attempted to call Marcus [last name] at the number provided in the clinical record at 4:52 PM; no answer. Left a message identifying myself as a mental health professional and requesting he contact police or my office urgently. Called again at 5:18 PM; spoke with Mr. [last name] directly. Informed him that I had received information suggesting he may be at risk and strongly advised him to contact law enforcement. He confirmed he would call 911. I provided the officer's case number for reference.

Post-Notification Session Documentation

If the client returns after a duty to warn situation has occurred, the documentation of that session requires its own attention.

Document whether the client is aware that a notification was made. In most duty to warn situations, the therapist is legally permitted to breach confidentiality to protect a third party; the client's awareness that this occurred is a clinical, not a legal, event. But how you handle the therapeutic relationship after a duty to warn disclosure is clinically significant and belongs in the record.

Document the client's current threat level in the subsequent session: has the situation resolved, escalated, or shifted? Has the intended victim responded in a way that increased or decreased the client's stated motivation? Are there new developments (legal intervention, voluntary disarmament, reconciliation) that affect the risk picture?

Document your continued risk assessment, not as a one-time event but as an ongoing clinical process. Duty to warn situations rarely end cleanly. The note should reflect continued clinical attention to the threat landscape.

Handling Ambiguous Situations: A Documentation Checklist

Some situations will be genuinely difficult to assess. The client expresses something alarming, then minimizes it. The threat is vague. The potential victim is not clearly identifiable. The time frame is unclear. In these situations, use the following documentation approach:

1. Write down exactly what the client said, using direct quotes where possible.
2. Document your follow-up questions and the client's responses to each.
3. Assess each threshold element explicitly: imminence, identifiability of victim, plausibility of follow-through.
4. Document the basis for your final determination, including what factors were present and what factors were absent.
5. Record any consultation you conducted.
6. Document your plan for reassessment and what would change your determination.

Common Documentation Errors in Duty to Warn Situations

Recording only the conclusion, not the reasoning. "Assessed as not meeting duty to warn threshold" without the analysis that led there is a documentation failure. The reasoning is the protection.

Failing to use direct quotes. Paraphrasing what a client said can inadvertently minimize the severity of the statement. Quotes are more defensible and more accurate.

Omitting the consultation. If you consulted with a supervisor or colleague, that conversation belongs in the note. Undocumented consultation did not happen from a legal standpoint.

Vague threat descriptions. "Client expressed violent ideation" is not clinically adequate. Document what the client actually said, toward whom, and with what specificity.

Treating a notification as sufficient without follow-up. If law enforcement says they will follow up and the clinical risk remains elevated, document your continued monitoring and whether the law enforcement response occurred.

Failing to document attempts that were unsuccessful. If you tried to reach the potential victim and could not, document those attempts. Good-faith effort requires evidence.

Treating the duty to warn note as a one-time event. Risk does not resolve at the moment of notification. Document continued threat assessment in subsequent sessions.

Ignoring state-specific requirements. Duty to warn law varies by state. A documentation framework based on California's Tarasoff interpretation may not satisfy a different state's statutory requirements. Know your jurisdiction's law and reflect it in your documentation.

A Note on Template-Based Documentation for High-Stakes Situations

High-stakes documentation like duty to warn notes benefits from a structured template that prompts you to capture every required element, even under pressure. A template that includes fields for threat language, risk assessment domains, consultation, and notification steps reduces the likelihood of omitting a critical component because you were managing an acute situation.

NotuDocs lets you build and save note templates with your own field structure. A duty to warn template with dedicated sections for each documentation domain ensures you capture what matters without having to reconstruct the framework from memory while your hands are shaking.

Documentation Checklist for Duty to Warn Situations

Threat Assessment

• Client's exact statement (direct quote)
• Context in which the threat arose (time in session, precipitating content)
• History of violence (prior threats, charges, behavior)
• Specificity of plan (target, method, timeline)
• Access to means
• Mental status at time of disclosure
• Protective factors assessed

Decision-Making Rationale

• Determination of whether the threshold was met, with reasoning
• Reference to state-specific duty requirements if applicable
• Consultation documented (name, date, time, substance of advice)
• Plan for reassessment if threshold was not yet met

Notification Documentation

• Law enforcement notification: agency, officer name/badge, time, content disclosed, response
• Victim notification: method, time, whether contact was made, what was conveyed, victim's response
• Documentation of unsuccessful attempts with timestamps

Post-Notification

• Client awareness of notification and clinical response
• Updated threat assessment in subsequent session
• Continued monitoring plan

General

• Session note timestamped or completed as close to the event as possible
• Documentation kept in clinical record consistent with your state's retention requirements
• Supervisor or attorney notified if you are unsure of your obligations

---

Related guides: How to Document Crisis Intervention and Suicide Risk Assessments | How to Document Therapy Sessions Using Standardized Outcome Measures | How to Document Forensic Mental Health Evaluations and Court-Ordered Therapy