Report or Don't Report: Liability, Cultural Context, and Documentation in Mandated Reporting Decisions
Most of us were taught that when in doubt, we report. Most of us have also sat with a case where that answer felt too simple. In our most recent group supervision, we worked with that discomfort directly, using the Balancing Risk Assessment Tool (BRAT) and two composite cases that arrive at opposite answers under the same framework.
The frame for the day was one sentence: document your reasoning, not just your conclusion.
Why the reasoning matters more than the answer
Reasonable cause to suspect abuse or neglect is a low bar. That means a report is often defensible. It also means a decision not to report can be defensible, if the clinician can show how they got there. What isn't defensible is a record that says "no report made" with nothing underneath it.
A report is also an intervention, not a neutral act of safety. Surveillance lands unevenly across families, and in high-conflict divorce a report can become a litigation tool. Dorothy Roberts's work is useful background here. None of this changes the law. It does change how carefully we think before and after we act.
Case one: A child in a high-conflict divorce
The child is nine, in counseling for anxiety, with divorced parents who are joint managing conservators. After a weekend with Dad, Mom sends a photo of a bruise and asks for a letter supporting a custody modification, plus all session notes. In session, the child says Dad "yanked" their arm over a tablet. It hurt. It happened once. The child isn't afraid of Dad and wants to keep seeing him. The clinician hasn't seen the bruise. Then Dad emails asking for all session notes and says Mom is "coaching" Jordan.
Under Texas Family Code §261.001, physical abuse requires substantial harm or a genuine threat of it, and excludes reasonable discipline that doesn't create substantial risk. A single arm-yank, an unobserved bruise, no fear, and a child who wants the relationship points toward concerning, not reportable, at least for now.
The skills we practiced:
Write "Mother reports..." and "The child states..." rather than adopting conclusions.
Separate observation from allegation.
Document the decision whether or not a report is made.
Assume both parents may read every line.
Center the child's voice. Not being afraid and wanting the relationship is clinical data, not something to override by default.
Don't investigate. Ask open, non-leading questions, and don't interrogate a child to settle a parental dispute.
Name your re-evaluation triggers: new injury, fear, escalation.
The custody letter is outside our role. The records requests need a careful, even-handed response to both parents.
Case two: A teen with intersecting vulnerabilities
The teen is sixteen, referred for depression and school avoidance. Their family recently immigrated, the teen often interprets for their parents, and the teen is nonbinary and not out at home. In session four, the teen discloses that their father hit them with a belt after seeing a text on their phone. The teen describes marks on their back and says this kind of discipline is "normal" at home. The teen begs the clinician not to report: "If CPS comes, my parents could get deported." Meanwhile, the teen's father wants portal access, and the practice portal auto-shares visit summaries with parents of minors.
Here the answer is different. A belt with marks is physical injury outside reasonable discipline under most analyses, and Texas has no exception for cultural norms or for fear of immigration consequences. A report is required. The teen's fear is real, and it does not change the duty.
What the fear does change is the method. The duty is fixed, the method isn't:
No surprises. Tell the teen before you report, explain what you must do and why, and bring the teen into decisions about how, where, and when.
Name the fear honestly. You can say DFPS is a child welfare agency, not an immigration enforcement agency. You cannot guarantee outcomes, so don't falsely reassure.
Report what the duty requires. That means the abuse facts. Leave out immigration status and family details. Include the teen's identity only if it's necessary to the abuse facts, and never disclose it to parents.
Stay with the teen. The report is not the end of the clinical work. Safety planning, contact, and advocacy continue.
Let culture inform approach, not threshold. Understand the family's context without pathologizing it and without letting it soften a legal duty. Use an interpreter for the parents, never the teen.
The portal question is where many practices get caught. Check your workflow before a case like this arrives, and turn off auto-share for this client immediately. Parental access is presumptive, but Health & Safety Code §611.0045 allows withholding where disclosure would harm the patient, and HIPAA has an endangerment exception (45 CFR §164.502(g)(5)). Consult an attorney before denying access.
Where we struggled
This case was the one that stayed with us. The law is clear: a belt with marks meets the reasonable cause standard, and Texas has no exception for fear of immigration consequences. But the group did not experience it as clear. With immigration enforcement active in Texas, the teen's fear that a report could harm their family is not irrational, and none of us could promise otherwise. We can accurately say DFPS is a child welfare agency, not an immigration enforcement agency. We cannot guarantee what happens after a report leaves our hands.
We didn't resolve that discomfort, and I don't think we should have. The duty is fixed. What we control is how we carry it out: no surprises for the teen, no false reassurance, only the abuse facts in the report, and staying with the teen afterward.
The documentation exercise
We asked participants to write two versions of Sam's session note: one that could safely be seen by Sam's father, and one that reflects clinical reasoning. The exercise is uncomfortable on purpose. It shows how the structure of the record shapes what we can safely write, and why keeping process notes separate from progress notes matters where your framework allows.
A model note stays tight: the disclosure, what was and wasn't observed, the reasonable cause finding, that the client was informed before the report, the fear expressed, the safety plan, and no identity or immigration details beyond what was clinically necessary.
What the two cases share
The same framework, applied honestly, produced no report in the first case and a report in the second case. The BRAT is a reasoning tool, not a proxy for caution.
Both cases ask where the clinician's power sits, and whether we are using it to serve the client or to manage our own risk. That question doesn't resolve neatly, and I don't think it should. Reports and records carry consequences beyond the clinical ones, and our work is to name that tension rather than resolve it artificially.
The cases above are composites created for training using AI. This post is educational and is not legal advice. Consult an attorney or your professional board about specific situations.
If this resonates with you, I'd love to connect!
Whether you're a fellow therapist looking for community, an associate seeking supervision, or a person simply trying to understand what a thoughtful therapist looks like, this is the work I'm committed to. Ongoing, honest, and never finished.
References
Mandatory Reporting is Not Neutral. (n.d.).Mandatory Reporting is Not Neutral. Retrieved August 3, 2026, from https://www.mandatoryreportingisnotneutral.com/
Texas Behavioral Health Executive Council & Texas State Board of Examiners of Professional Counselors. (2026, March 25). Rules [PDF]. Behavioral Health Executive Council. https://bhec.texas.gov/wp-content/uploads/2026/03/LPC-Rulebook-2026-March.pdf
Tex. Fam. Code Ann. § 261.101 (West 2026). https://statutes.capitol.texas.gov/?tab=1&code=FA&chapter=FA.261&artSec=261.101
