Organizational Context

This case examines prosecutorial case complexity triage across the Department of Justice, including U.S. Attorney’s Offices, DOJ litigating divisions, and supervisory review layers. The focus is on how cases are assessed early to determine the appropriate level of legal, evidentiary, and organizational effort required.

Cases enter complexity triage after intake or early investigation, when prosecutors must decide how much senior oversight, coordination, and time investment a matter will require before committing limited prosecutorial resources.

• Case volume consistently exceeds available prosecutorial capacity.

• Cases vary widely in complexity even when statutes are identical.

• Early misclassification creates downstream litigation risk.

• Attorney experience and workload distribution vary across offices.

How the Work Was Intended to Function

From a prosecutorial management perspective, case complexity triage was expected to function as a stabilizing control:

• Cases are reviewed early for legal and evidentiary complexity.

• Appropriate prosecutors and support resources are assigned.

• Supervisory oversight is calibrated to complexity.

• Timelines and litigation posture are established.

• Cases progress with predictable risk management.

Because experienced prosecutors and supervisory review were embedded in the process, the system appeared governed at an aggregate level.

What Was Actually Happening

Observed reality diverged materially:

• Routine cases were over-managed with excessive review.

• Highly complex cases were under-resourced early.

• Complexity was conflated with public visibility or sensitivity.

• Reassignments occurred late, increasing trial risk.

• Attorney burnout and uneven outcomes increased.

The underlying issue was not prosecutorial competence, but the absence of a shared, explicit way to classify the complexity of a single case before committing resources.

How FLOW Was Introduced

Leadership sought a stabilizing lens that preserved prosecutorial discretion while improving consistency. Specifically, they needed:

• A common language to explain why cases behave differently.

• A method to separate legal complexity from case visibility.

• A unit-centered lens instead of portfolio-level intuition.

• Governance aligned to litigation risk rather than urgency alone.

FLOW was introduced as a classification lens applied early, before assignments, oversight decisions, or litigation commitments were finalized.

Identifying the Unit of Effort

The organization anchored complexity triage on a single, stable unit of work:

• Unit of Effort: one prosecutable case requiring litigation judgment.

• A case may involve multiple charges, defendants, or motions — these inform the same unit.

• Parallel legal analyses do not create new units.

• The case remains constant as governance and oversight scale.

How Complexity Was Determined

Complexity was defined as the amount of legal, evidentiary, and procedural judgment required to prosecute the case effectively.

• Low complexity: clear facts and settled law.

• Moderate complexity: contested facts or evidentiary disputes.

• High complexity: novel legal theories or extensive motions practice.

• Very high complexity: sensitive, classified, or national security evidence.

How Scale Was Determined

Scale was defined as the breadth of institutional and public consequence if the case is mishandled.

• Resource commitment required.

• Precedent or policy impact.

• Public trust and visibility.

• Risk of adverse systemic outcomes.

Applying FLOW to Prosecutorial Case Complexity

With complexity and scale definitions fixed, each case was classified consistently. The unit of effort remains constant across all examples below — this is still one case.

• Classify complexity first.

• Classify scale second.

• Assign the single FLOW classification that best fits the unit.

FLOW A — Routine, Low-Complexity Cases

This example involves one prosecutable case. This is still one case.

Example: a straightforward prosecution under settled law with uncontested evidence.

• Complexity: low.

• Scale: low.

• Handling implication: streamlined prosecution with light supervision.

Built-out handling: junior prosecutors manage the case with minimal supervisory intervention, timelines remain predictable, and litigation risk is low.

FLOW B — Coordinated, Low-Complexity Cases

This example still involves one prosecutable case. This is still one case.

Example: a multi-defendant case under clear statutes requiring coordination across offices.

• Complexity: low.

• Scale: moderate.

• Handling implication: coordinated management without added legal uncertainty.

Built-out handling: supervisory prosecutors coordinate assignments, ensure consistent strategy, and manage dependencies across teams. The distinction from FLOW A is coordination, not complexity.

FLOW C — High-Complexity, Judgment-Driven Cases

This example still involves one prosecutable case. This is still one case.

Example: a case with contested facts, disputed evidence, or novel legal issues.

• Complexity: high.

• Scale: low-to-moderate.

• Handling implication: senior prosecutorial judgment and active risk management.

Built-out handling: experienced prosecutors guide strategy, test legal theories, and explicitly manage uncertainty throughout litigation.

FLOW D — System-Level Impact Cases

This example still involves one prosecutable case. This is still one case.

Example: a case with precedent-setting implications or national policy impact.

• Complexity: variable.

• Scale: high.

• Handling implication: senior DOJ governance and enterprise oversight.

Built-out handling: DOJ leadership aligns litigation posture, manages institutional risk, and coordinates across components.

FLOW S — Exceptional Prosecutorial Cases

This example still involves one prosecutable case. This is still one case.

Example: time-sensitive cases requiring immediate prosecutorial action.

• Complexity and scale vary.

• Handling implication: emergency prioritization and executive oversight.

• Key risk: irreversible legal or public harm.

Built-out handling: immediate escalation, rapid filings, and direct leadership involvement.

What Changed After FLOW Classification

• Case complexity became explicit and explainable.

• FLOW A cases moved faster with less overhead.

• FLOW B cases received structured coordination.

• FLOW C cases received appropriate expertise.

• FLOW D cases received senior governance.

• FLOW S cases followed emergency pathways.

Organizational Implications

• Improved workload balance across prosecutors.

• Reduced downstream reassignment and rework.

• Clearer expectations for attorneys.

• More consistent litigation outcomes.