Home › Failure to Protect Allegations

Failure to Protect Allegations in LA County DCFS Cases.

DCFS alleges that you "failed to protect" your child by failing to act when you knew or reasonably should have known of a risk. It is the most common allegation in California juvenile dependency cases — and the most defensible. The keystone is the "knew or reasonably should have known" standard under Welf. & Inst. Code § 300(b)(1). Most failure-to-protect cases are won or lost on whether that standard is met.

"Failure to protect" is an allegation that you failed to act when you knew or reasonably should have known of risk to your child.

Under Welf. & Inst. Code § 300(b)(1), DCFS must prove four elements: (1) the child suffered or is at substantial risk of suffering serious physical harm or illness, (2) the harm or risk resulted from a parent's failure or inability to adequately supervise or protect, (3) the parent knew or reasonably should have known of the risk, and (4) the parent's failure was unreasonable under the circumstances. The third element is where most defenses succeed. California appellate decisions including In re B.T. and In re Esmeralda B. require DCFS to prove actual or constructive knowledge, not mere hindsight. If you genuinely did not know, did not have reason to know, or took reasonable protective action when you did know, the petition fails on this element. Call (866) 811-4255 for a free 24/7 consultation.

What "failure to protect" actually means.

Failure to protect is the most common allegation in California juvenile dependency court. It appears in roughly half of all DCFS petitions, often combined with other allegations like physical abuse, substance abuse, or domestic violence.

The allegation says, in essence, that the parent did not cause the harm or risk — but failed to act to prevent it. The other parent assaulted the child, but you didn't intervene. Your partner used drugs around the child, but you allowed it to continue. Your roommate had access to the child despite a known criminal history, and a problem occurred. Your mother watched the children, but you knew she had untreated mental health issues that put them at risk.

In each scenario, the parent's alleged wrongdoing is an omission — failing to do something that, in DCFS's view, a reasonable parent would have done. That structural feature is why failure to protect cases are so defensible: omissions are inherently harder to prove than acts, and the "reasonably should have known" element creates substantial space to challenge what the parent actually knew and when.

The statute, Welf. & Inst. Code § 300(b)(1), creates dependency court jurisdiction when a child "has suffered, or there is a substantial risk that the child will suffer, serious physical harm or illness, as a result of the failure or inability of the child's parent or guardian to adequately supervise or protect the child."

The 4 elements DCFS must prove under WIC § 300(b)(1).

At the jurisdiction hearing, DCFS must prove each element by a preponderance of the evidence. If even one element fails, the petition fails.

The 5 fact patterns that drive most cases.

"Knew or reasonably should have known" — the keystone of every defense.

California appellate decisions have repeatedly emphasized that failure-to-protect jurisdiction requires actual knowledge or constructive knowledge — not retrospective inference from the fact that something bad happened.

In In re Esmeralda B., the court rejected jurisdiction where the mother had no specific reason to suspect a co-parent's abusive conduct toward another child. In In re B.T., the court required specific evidence that the parent actually knew or had factual basis to know — not just that the parent should have figured it out in retrospect. In In re Drake M., the court held that mere parental proximity to a substance-using partner does not establish failure to protect absent specific evidence of awareness and unreasonable response.

A successful defense on this element typically involves one or more of the following facts: (1) the parent was actively deceived by the other adult (substance use concealed, abuse hidden, criminal history misrepresented); (2) the parent took protective action when concerns first emerged (called police, sought a restraining order, separated, sought services); (3) the alleged risk was speculative rather than concrete; or (4) the parent was themselves a victim of the same conduct and could not have safely intervened.

The defense work happens in the documents. Texts, emails, prior law enforcement records, restraining order applications, custody filings, prior service involvement, medical records, school records, and witness statements all become evidence of what the parent actually knew and when.

When you are also a victim.

When the offending conduct is committed by one parent or partner against the family, the other parent is often described as the "non-offending parent." California law and practice recognize that holding a non-offending parent strictly responsible for a co-parent's conduct creates perverse incentives and frequently punishes victims.

In In re V.L., the court reversed jurisdiction findings against a mother who had herself been a victim of domestic violence, holding that the mother's status as a victim significantly informed what she could reasonably be expected to do. In In re Cole C., the court held that a non-offending parent should be released the child under WIC § 361.2 absent a specific showing of detriment.

If you are a non-offending parent — whether because the abuse was directed at you, because the substance use was your partner's, or because you took reasonable protective action when you learned of the risk — your defense is structurally different and structurally stronger than the offending parent's defense.

A key strategic point: the non-offending parent's case should be presented separately from the offending parent's. Joint defenses can collapse weaker positions into stronger ones. Coordinated, separate counsel for each parent is typically the right structure.

How a failure-to-protect defense is actually built.

A successful failure-to-protect defense is typically built around three pillars: an attack on what the parent actually knew, an affirmative showing of protective conduct, and (where applicable) the non-offending parent posture.

Pillar 1: The knowledge attack. Pull every document that demonstrates what the parent knew and when. Then pull every document that demonstrates what the parent did not know — concealed text messages between the other adult and third parties, financial records showing the parent was not the one paying for substances, witness statements from people who confirm the parent expressed surprise when they learned of the conduct.

Pillar 2: The protective conduct showing. Catalog everything the parent did when concerns first emerged. Police reports filed. Restraining orders sought. Therapy initiated. Custody filings made. Separations attempted. Calls to family, friends, or services. The narrative is: "I was not passive. I acted as soon as I had reason to act." This pillar often turns a failure-to-protect case into a non-jurisdictional case.

Pillar 3: The non-offending parent posture. Where applicable, position the client as a non-offending parent under WIC § 361.2 and the supporting case law. This pillar can result in immediate release of the child to the non-offending parent at the disposition hearing, even if jurisdiction is sustained as to the offending parent.

Failure-to-protect questions parents ask.

What is failure to protect under California law?

Failure to protect is an allegation under Welf. & Inst. Code § 300(b)(1) that the parent failed or was unable to adequately supervise or protect a child, resulting in serious physical harm or substantial risk of such harm. The parent must have known or reasonably should have known of the risk for the allegation to succeed.

I didn't do anything wrong — why am I being accused?

Failure to protect is an allegation about omission, not action. DCFS isn't necessarily saying you caused harm. They're saying you failed to prevent it. Most commonly, the alleged perpetrator is a co-parent, partner, relative, or other adult, and you are being held responsible for not intervening or removing the child from the situation.

What if I genuinely didn't know about the risk?

If you did not know and had no reasonable basis to know, the third element of WIC § 300(b)(1) fails. In re Esmeralda B. and In re B.T. require DCFS to prove actual or constructive knowledge, not retrospective inference. Documents showing concealment, deception, or the absence of warning signs strengthen this defense.

What if I was a victim of domestic violence too?

The non-offending parent doctrine under In re V.L. recognizes that holding a victim parent strictly responsible for a perpetrator parent's conduct can be inappropriate. Your status as a victim affects what you could reasonably be expected to do. WIC § 361.2 may support release of the child to you separately from the offending parent.

Can DCFS prove I should have known?

"Reasonably should have known" requires specific facts establishing that a reasonable parent in the same circumstances would have recognized the risk. Hindsight isn't enough. If the warning signs were subtle, concealed, or absent, DCFS has a much harder case.

What if I did take action when I learned of the problem?

Then the fourth element of WIC § 300(b)(1) likely fails. Calling police, seeking a restraining order, separating from the offending adult, filing for custody, or removing the child from the dangerous environment all demonstrate reasonable protective conduct. Document every protective action you took.

What is the burden of proof?

DCFS must prove each element of WIC § 300(b)(1) by a preponderance of the evidence at the jurisdiction hearing. This is a lower burden than criminal court but still requires concrete evidence. At the detention hearing, the burden is even lower (prima facie showing only) and the case is provisional.

Can I be charged criminally for failure to protect?

Possibly, under Penal Code § 273a (child endangerment). Criminal charges are separate from the dependency case and have a higher burden (beyond a reasonable doubt). If both are pending, coordination between dependency counsel and criminal counsel is essential. Statements in one case can affect the other.

Will my child be removed for failure to protect?

Not necessarily. Many failure-to-protect cases result in the child remaining home with services in place, especially where the offending adult has been removed from the home. Removal depends on whether DCFS can satisfy the four prongs of WIC § 319 at the detention hearing, including the reasonable efforts requirement.

What's the difference between failure to protect and physical abuse?

Physical abuse under WIC § 300(a) alleges that the parent caused serious physical harm. Failure to protect under WIC § 300(b)(1) alleges that the parent failed to prevent harm caused by another. A single case can include both allegations against different parents.

How long does a failure-to-protect case last?

Most resolve in 6 to 18 months from detention if jurisdiction is sustained. Many resolve faster when the protective issue (the offending adult) is addressed early. Cases dismissed at jurisdiction can resolve in weeks. Cases that proceed to reunification services typically take 12 months for children three or older.

What if DCFS is wrong about the underlying facts?

Contest jurisdiction. The jurisdiction hearing is the trial in a dependency case — witnesses, cross-examination, evidence rulings, and a written ruling. If the factual basis for the petition collapses at jurisdiction, the case is dismissed and the child returns home. Contested jurisdiction is one of the most powerful tools in dependency defense.

Go Deeper.

Accused of failing to protect? Don't wait to fight back.

Most failure-to-protect cases are won on the "knew or should have known" element. The earlier we start building that defense, the stronger it gets. The texts, the documents, the timeline — we need them now.

Free · Confidential · 24/7 · English · Spanish · Arabic

Attorney Advertising · Required California Disclosures

Attorney advertising. This page constitutes attorney advertising under the California Rules of Professional Conduct. The content is provided for general informational purposes and does not constitute legal advice for any specific situation.

No legal advice. Statutes and case law cited (Welf. & Inst. Code §§ 300(b)(1), 319, 361.2; Penal Code § 273a; In re Esmeralda B., In re B.T., In re Drake M., In re Ricardo L., In re J.N., In re V.L., In re Cole C.) are summarized for general informational purposes. Applicability to any specific case depends on its specific facts and current law.

No attorney-client relationship. Reading this page does not create an attorney-client relationship. An attorney-client relationship is formed only by a signed written engagement agreement.

Responsible attorney. Mohammad Abuershaid, Esq. (State Bar #297270), founding partner of All Trial Lawyers / Abuershaid Law, APC, is the attorney responsible for the content of this website. Pasadena office: 117 E Colorado Blvd, Suite 600, Pasadena, CA 91105.

Past results. Past dismissals and case outcomes referenced do not guarantee future outcomes. The outcome of any failure-to-protect case depends on its specific facts, the assigned bench officer at Edelman Children's Court, the evidence developed, and the relief sought.

Pasadena CPS Lawyer. A San Gabriel Valley practice of All Trial Lawyers / Abuershaid Law, APC. Pasadena office: 117 E Colorado Blvd, Suite 600, Pasadena, CA 91105. Phone: (866) 811-4255 · Free, confidential, 24/7. Lead attorney: Mohammad "Mo" Abuershaid, Esq. (CA Bar #297270)