Notes on Local Policing, Intelligence-Led Policing, and Jurisdictional Structure

Local governance and interagency dynamics

The speaker questions if actions would involve collaborating with larger districts or metropolitan areas (e.g., Metro), implying autonomy and potential limitations: "It's like, you're gonna do what you're gonna do… We're not gonna enable you or help you in any way. We're not providing extra security… If you wanna do this in our community, you're gonna it's gonna be as resource intensive as it needs to be for you. So you figure it out. Not our job."
Emphasis on staying local and resisting external control: communities want to protect their own ability to do their jobs in the future; there are political positions, but the focus is on practical protection of local operations.
The discussion uses concrete examples to illustrate tension between local and other law enforcement bodies:
- Iron County example: highway patrol vs. Cedar City police; tension where one side feels the other is "killing us here." The point is about delineating boundaries and avoiding unwanted coordination that undermines local aims.
- The speaker suggests the goal is to make a clear line: stay local, do what has been done, and not engage with outsiders; communicate this stance to the public so communities don’t conflate different law enforcement agencies.
The takeaway is about perception: people will associate law enforcement with law enforcement, so local agencies want to project a sane, local-focused image and avoid alignment with outside groups.
Question and participation prompts are used to gauge interest and agreement from students.

Intelligence-led policing: origins, definitions, and misconceptions

There is a distinction between community policing and intelligence-led policing; the textbook’s portrayal of intelligence-led policing as a medical-led approach is criticized.
Post-9/11 context: many police and FBI personnel were mobilized for functions in places like Afghanistan and Iraq, and many contributed as National Guard or Reserves; this helped shape intelligence-driven approaches in law enforcement.
Intelligence-led policing did not originate from medicine; it emerged from fusion centers, operations, and international collaborations. The FBI and other agencies developed and refined these methods; there are liaisons across embassies and various command structures that contribute to intelligence activities.
The Department of Defense (via Joint Chiefs of Staff) and military doctrine influenced intelligence operations; Joint Pub 2-0 outlines doctrine for intelligence operations and is similar in spirit to FBI-led approaches.
Agencies involved in intelligence-driven work include the FBI, with public discussions and articles from the FBI Academy; the Joint Chiefs of Staff publication (Joint Pub 2-0) provides formal guidance for intelligence operations.
The broader point: intelligence-led policing has permeated national, state, and local levels, though it may be more fully implemented by larger departments with resources to run complete intelligence cycles.

The intelligence cycle: planning, collection, IRs, NAI, and exploitation

Core workflow: collect, evaluate, exploit information to support operational decision-making.
Collection plan: a structured approach to what information will be gathered and how it will be used.
Intelligence requirements (IRs): prioritization of information needs; examples include Priority Intelligence Requirements (PIRs) and other IRs.
PIRs (Priority Intelligence Requirements): the things the agency wants collected; act as guiding targets for the collection effort.
Other IR types:
- EIR: Enemy Intelligence Requirements
- FFIR: Friendly Forces Intelligence Requirements
Named Area of Interest (NAI): the geographic focus for collecting information about a target activity.
The cycle emphasizes deliberate planning: a defined plan, explicit IRs/NAIs, and purposeful collection (e.g., confidential informants, drones, full-motion video) to achieve a decision advantage.
Operational cycles: information is digested and delivered in a timely way to support decisions (where to deploy assets, which targets to prioritize).
The field requires synthesis and analysis to reduce uncertainty and provide decision advantage in policing operations.
The lecturer notes that there are many practitioners (e.g., analysts, agents) who spend their careers on intelligence work across national security, local policing, and corporate sectors.
The trend is toward formalized, large-scale intelligence cycles in major departments, with ongoing efforts to push these methods down to local levels over time.

Jurisdictional landscape: who does what

The U.S. Attorney General (DOJ) is the top law enforcement officer for the U.S. government; DOJ runs law enforcement agencies like the FBI, DEA, and U.S. Marshals; DOJ also oversees prosecutions via U.S. Attorneys.
Department of Homeland Security (DHS) has components such as ICE and others that perform law enforcement roles, but prosecutions are handled through DOJ.
Bureau of Prisons (BOP) is a DOJ component for federal corrections.
State-level structure: patrol vs. police; patrol primarily handles highway patrol/travel safety; police cover the broader spectrum of law enforcement within a state.
Local jurisdictions: thousands of variants due to the diversity of local needs; resources and structures vary significantly by locality and state; there can be territorial and tribal variations.
Tribal police: jurisdiction over tribal lands is distinct; there are 81 tribal lands and over 200 tribal police agencies.
Territorial and other specialized police: structures are diverse and tailored to local circumstances; special police exist for specific purposes.

Private policing and corporate policing

Private policing is expanding and includes off-duty police moonlighting, where officers may have authority off duty in certain jurisdictions.
Some jurisdictions permit off-duty police to exercise arrest powers; in others, off-duty status limits that authority but maintains networks and contacts for private security work.
Corporate policing includes security and asset protection for corporations and cargo transit; it can involve private security firms exercising police-like powers in certain contexts.
The private policing sector is growing, with corporate intelligence and security functions becoming more prominent across industries.
The collaboration between private security and public law enforcement can raise questions about accountability, jurisdiction, and effectiveness.

Practical implications, ethics, and real-world relevance

The macro trend of intelligence-driven policing has real-world relevance for large and mid-sized departments; there is ongoing discussion about decentralizing or localizing these capabilities.
The talk highlights the ethical and practical tensions of interagency collaboration, sovereignty of local jurisdictions, and the balance between security and civil liberties.
Police and public safety decisions are shaped by budget, resources, and political considerations, which can affect how aggressively intelligence-driven approaches are adopted at local levels.
The Yellowstone reference illustrates how jurisdictional powers and local enforcement can interact in real-world, rural settings (e.g., livestock enforcement), underscoring the diversity of policing roles and powers across contexts.
Tribal policing is a critical and often under-resourced piece of the security puzzle, requiring collaboration with federal and state authorities while maintaining sovereign and cultural considerations.

Real-world relevance and connections to foundational principles

Foundational principle: different agencies have distinct missions, equities, and jurisdictions; conflating all law enforcement into one umbrella is misleading and can hamper effective operations.
Practical principle: successful intelligence-led policing relies on clearly defined collection plans, IRs, and NAIs, coupled with deliberate execution and rapid analysis to gain a decision advantage.
The integration of fusion centers, interagency collaborations, and liaisons across national and international levels demonstrates how local policing is embedded in a broader security ecosystem.
The discussion emphasizes that the most effective policing strategy must be context-sensitive, resource-aware, and cognizant of local community priorities and political dynamics.

Connections to previous lectures, foundational concepts, and real-world relevance

Links to community policing discussions: move from broad community engagement to technologically supported, intelligence-driven approaches.
Fusion centers and cross-agency collaboration were introduced as mechanisms for sharing information and coordinating actions across jurisdictions.
Doctrinal grounding: Joint Pub 2-0 provides doctrine for intelligence operations; FBI guidance from the FBI Academy frames intelligence-led policing as a formalized approach.
The role of National Guard and reserve components in supporting intelligence and law enforcement missions in national and international contexts.
Real-world relevance across different levels: local departments with limited resources can leverage national-level intelligence concepts, while larger departments operationalize full intelligence cycles with dedicated analysts and technology.

Ethical, philosophical, and practical implications discussed

Balancing local autonomy with collective security: when to cooperate with outside agencies and when to preserve local control.
Resource allocation: intelligence-driven policing is resource-intensive; not every community can sustain the required capabilities, raising questions of equity and access.
Civil liberties and privacy concerns: collection and surveillance methods (e.g., drones) require scrutiny to protect individual rights while maintaining public safety.
Accountability and transparency: private policing and corporate security raise questions about oversight and accountability to the public.
The risk of conflating disparate law enforcement bodies and perceptions that can undermine trust in local communities.

Notable terms and concepts (definitions and scope)

PIR: Priority Intelligence Requirements – key information needs guiding collection priorities.
IR: Intelligence Requirements – various types used to guide intelligence efforts (e.g., PIR, EIR, FFIR).
EIR: Enemy Intelligence Requirements – information needs related to adversaries.
FFIR: Friendly Forces Intelligence Requirements – information needs related to allied or partner forces.
NAI: Named Area of Interest – geographic focus for collection and monitoring.
Fusion centers: interagency centers that coordinate information sharing and intelligence analysis across jurisdictions.
Joint Pub 2-0: Joint doctrine on intelligence operations from the Chairman of the Joint Chiefs of Staff.
DOJ: Department of Justice – top federal authority over law enforcement and prosecutions (FBI, DEA, U.S. Marshals, etc.).
DHS: Department of Homeland Security – oversees several law enforcement components (e.g., ICE) with federal responsibilities.
BOP: Bureau of Prisons – federal corrections agency under DOJ.
Off-duty policing: scenario where officers retain certain police powers outside standard duty hours for private or corporate security work.

Questions for review and reflection

How do local communities balance staying autonomous with participating in broader national security or intelligence initiatives?
What are the practical thresholds for investing in intelligence-led capabilities at the local level given resource constraints?
How do we ensure accountability and protect civil liberties when implementing intelligence-driven policing?