Organizational Context

This case examines federal case intake and prioritization across the Department of Justice, including U.S. Attorney’s Offices, DOJ litigating divisions, investigative agency referrals, and interagency task forces.

Cases enter the system through law enforcement investigations, regulatory referrals, whistleblower complaints, victim reports, grand jury matters, and interagency intelligence.

• Case volume consistently exceeds prosecutorial capacity.

• Case types vary widely in complexity and consequence.

• Political sensitivity and public interest vary sharply.

• Similar referrals often receive very different treatment.

Leadership sought consistent, defensible prioritization decisions, but the deeper problem was that individual case referrals were being treated as equivalent when they were not.

How the Work Was Intended to Function

From a federal law enforcement and justice perspective, intake was assumed to function predictably:

• Case referrals are received and logged.

• Legal sufficiency is assessed.

• Investigative merit and jurisdiction are evaluated.

• Cases are prioritized or declined.

• Resources are assigned to approved matters.

Because charging standards, prosecutorial discretion frameworks, and review processes existed, the system appeared governed at an aggregate level.

What Was Actually Happening

Observed reality diverged materially:

• Low-impact cases consumed screening time.

• High-consequence cases were sometimes delayed by backlog.

• Prioritization relied heavily on heuristics (visibility, age, pressure).

• Escalation thresholds varied across offices.

• Documentation of declination rationale was inconsistent.

• Assistant U.S. Attorneys experienced workload saturation.

The underlying issue was not prosecutorial judgment, but the absence of a shared way to interpret a single case referral before deciding priority and resource commitment.

How FLOW Was Introduced

Leadership sought a stabilizing lens without restricting prosecutorial discretion or increasing staffing. Specifically, they needed:

• A common language to explain why case referrals behave differently.

• A method to separate volume from justice impact.

• A unit-centered lens rather than docket-level aggregation.

• Governance aligned to legal and societal consequence rather than pressure alone.

FLOW was introduced as a classification lens applied before formal case opening, assignment, or declination decisions.

Identifying the Unit of Effort

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

• Unit of Effort: one federal case referral requiring assessment, prioritization, and disposition.

• A referral may include multiple allegations or investigative threads — these inform the same unit.

• Parallel legal reviews do not create new units.

• The case does not change as impact expands; only handling and governance change.

How Complexity Was Determined

Complexity was defined as the amount of legal and factual judgment required to pursue prosecution.

• Low complexity: clear statutory violation with strong evidence.

• Higher complexity: multi-defendant or multi-jurisdiction cases.

• Higher complexity: novel legal theories or evidentiary challenges.

• Higher complexity: sensitive investigative techniques or classified evidence.

How Scale Was Determined

Scale was defined as the breadth of legal, societal, and institutional consequence.

• Number of victims or affected parties.

• Public trust and deterrence implications.

• Resource commitment required.

• Precedent or policy impact.

Applying FLOW to Federal Case Intake

With complexity and scale definitions fixed, each case referral was classified consistently. The unit remains constant across all examples; only consequence and governance change.

• Classify complexity first.

• Classify scale second.

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

FLOW A — Local, Contained Case Referrals

This example involves one federal case referral. The unit does not change.

Example: a straightforward federal offense with clear jurisdiction and limited harm.

• Complexity: low.

• Scale: low.

• Handling implication: routine prosecution or declination.

Built-out handling: prosecutors assess evidence, confirm charging standards, and proceed efficiently without extended review.

FLOW B — Broader Coordination from One Case

This example still involves one case referral. The unit remains the same; coordination requirements expand.

Example: a case requiring coordination between multiple DOJ components or agencies.

• Complexity: low.

• Scale: moderate.

• Handling implication: coordinated prioritization and assignment.

Built-out handling: offices align jurisdiction, share resources, and establish a lead prosecutorial authority.

FLOW C — Complex, Judgment-Driven Cases

This example still involves one case referral. Judgment requirements increase materially.

Example: a case with ambiguous evidence or novel legal questions.

• Complexity: high.

• Scale: low-to-moderate.

• Handling implication: deeper legal analysis and review.

Built-out handling: prosecutors evaluate risk, consult subject-matter experts, and document uncertainty before proceeding.

FLOW D — System-Level Impact from One Case

This example still involves one case referral. The unit remains unchanged; dependency becomes enterprise-wide.

Example: a case setting major precedent or affecting national policy.

• Complexity: variable.

• Scale: high.

• Handling implication: senior-level governance and coordination.

Built-out handling: DOJ leadership aligns strategy, manages risk, and coordinates communication across components.

FLOW S — Exceptional Case Referrals

This example still involves one case referral, but normal governance pathways are inappropriate.

Example: an imminent threat requiring immediate legal action.

• Complexity and scale vary.

• Handling implication: emergency authority.

• Key risk: irreparable harm.

Built-out handling: immediate filing or injunction, rapid judicial coordination, and emergency oversight.

What Changed After FLOW Classification

• Case prioritization became proportional and explainable.

• FLOW A cases moved efficiently.

• FLOW B cases received structured coordination.

• FLOW C cases received disciplined legal judgment.

• FLOW D cases received senior governance.

• FLOW S cases followed emergency pathways.

Organizational Implications

• Improved resource allocation.

• Reduced backlog pressure.

• Clearer prosecutorial accountability.

• Increased public confidence in consistency.