Primary Proof Pressure: High

Multiple major proof-pressure areas appear present. The matter may face serious friction in proving negligence, linking the alleged error to the outcome, overcoming defensible medicine, or justifying the expert and litigation cost burden. These are structural concerns, not sympathy concerns.

Primary Proof Pressure: Elevated

Several meaningful proof-pressure areas appear present. The matter may be difficult to advance without a clearly articulated, well-supported theory connecting breach, causation, and litigation economics. Structured review of the proof architecture before intake or continued development is likely warranted.

Primary Proof Pressure: Moderate

Some proof-pressure areas appear present across one or more of negligence proof, causation linkage, defensibility, expert cost, or timing. The matter may be manageable but will require clear proof architecture before development decisions are made.

Primary Proof Pressure: Low

Based on the responses entered, no major proof-pressure zone strongly dominates the matter. That does not indicate viability — only that the common friction points screened here do not appear heavily concentrated based on your inputs.

Pressure Pattern: Focused in a Single Area

Proof pressure appears concentrated in one area rather than distributed across the proof architecture. This may indicate a focused structural problem rather than a broadly unviable matter and may be worth a closer, isolated review of that specific zone before a final decision.

When pressure is concentrated in one area, that is a different situation from broad failure. A focused problem may have a focused answer (or may not). But it is worth separating from general difficulty.

Note: This label is the primary mechanism by which the tool reframes previously-declined cases. A concentrated single-bucket result invites a second look at whether the binding constraint can be addressed.

Pressure Pattern: Present Across Multiple Areas

Proof pressure appears present in more than one area. This may reflect compounding difficulty or two distinct problems that each need to be addressed, rather than a single binding constraint.

Two pressure zones in tension are different from a single focused problem and from everything failing at once. Knowing which two and whether they compound each other is the useful question.

Pressure Pattern: Distributed Across Multiple Areas

Proof pressure appears distributed across multiple areas of the case architecture. This typically reflects systemic proof difficulty rather than an isolated problem.

Negligence Proof Pressure

The records may not show a clear departure from the standard of care without substantial expert interpretation, which adds a proof-development burden and increases the risk that the breach theory relies heavily on expert willingness rather than record evidence.

Attorney-use language:

"The threshold question is whether the negligence theory comes from the records or from an expert reading into the records. Those are different proof situations."

Outcome-Change Causation Pressure

The most significant friction may be proving that the alleged error changed the clinical outcome in a way that can be sustained through expert testimony and cross-examination — not just that care was imperfect, but that the imperfection altered what would otherwise have happened.

Attorney-use language:

"Outcome-change causation is where many med mal cases that feel strong actually fail. The question is not whether the care was wrong — it is whether the outcome would have been different if the care had been right."

Defensible Medicine Pressure

The records may support a medically reasonable non-negligent explanation that a defense expert could credibly advance — meaning the plaintiff's theory must not only be coherent, but it must also overcome an alternative explanation that the jury may find plausible.

Attorney-use language:

"The question is not just whether you can build a theory — it is whether your theory survives a credible defense explanation that the records also support."

Expert Burden / Cost Pressure

The matter may depend on multiple experts, significant record synthesis, or unusually high proof development cost, which creates tension between the attorney's investment and the likely outcome, independent of the legal merit of the underlying claim.

Attorney-use language:

"Expert burden is a threshold question separate from merit. A case can be legally valid and still not be one a firm can responsibly file given the cost and recovery structure."

Timing / Filing Pressure

Timing constraints (statutes of limitations, pre-suit requirements, or late-intake deadlines) may materially limit the ability to complete the review this matter requires before a filing deadline. Filing without adequate review carries its own risk.

Attorney-use language:

"Timing pressure is not just a logistics problem. Filing before the proof architecture is established is a different risk than not filing at all."

Economics Pressure

Litigation costs and likely recovery may be in tension even if the underlying concerns are legitimate. This is a structural constraint on the case, not a reflection of its merit.

Attorney-use language:

"A case can be right on the law and still not be a case a firm can responsibly carry. That tension deserves a clear-eyed look before intake."

Sympathy-Proof Mismatch

The matter may feel compelling on harm or fairness grounds, yet still face serious structural problems in the proof architecture. These are separate questions, and the tool is designed to isolate them.

Attorney-use language:

"Turning down a case is often a proof problem, not a sympathy problem. A family can be telling the truth, the harm can be devastating, and the case can still face proof constraints that a firm cannot overcome in litigation."

Sympathy-Proof Mismatch

The matter may feel compelling on harm or fairness grounds, yet still face serious structural problems in the proof architecture. These are separate questions, and the tool is designed to isolate them.

Attorney-use language:

"Turning down a case is often a proof problem, not a sympathy problem. A family can be telling the truth, the harm can be devastating, and the case can still face proof constraints that a firm cannot overcome in litigation."

• Is proof pressure concentrated in one zone or distributed,  and does that change what a closer review would need to accomplish?

• What is the clearest record-based departure from standard of care, and does it come from the records or from expert inference?

• Can the outcome-change theory be articulated step by step, not just as a general claim?

• What is the strongest non-negligent explanation the defense could advance on the face of the records?

• How many experts would likely be required, and does the likely recovery support that investment?

• Is there enough time to complete the review this matter requires before any filing deadline?

• Does the likely recovery justify the expert burden, deposition cost, and overall litigation investment this matter would require?

• Is the difficulty here about proof architecture or about the emotional weight of the case, and are those being kept separate in the evaluation?

• Is the difficulty here about proof architecture or about the emotional weight of the case, and are those being kept separate in the evaluation?

What This Often Means

In practice, matters with these pressure patterns typically require earlier clarification of the proof architecture: where the breach theory comes from, how the outcome-change argument is supported, what non-negligent explanations need to be overcome, and whether the timing and economics support full litigation development. Cases that are declined on instinct are not always declined because the problem is everywhere — sometimes the binding constraint is concentrated, and knowing where it lives changes what a structured review needs to accomplish.

If a matter was declined on general difficulty and the pressure here appears concentrated rather than distributed, a structured review of the specific pressure zone may clarify whether the constraint is fixed or addressable.