You cannot detect a threat if you have never defined normal. This course teaches you to build deliberate baselines across four community domains, recognize meaningful deviations from those baselines, and translate field observations into actionable intelligence products. That process begins here, with understanding why untrained observers routinely miss what trained ones see — and what changes when you approach your environment analytically instead of emotionally.
The Problem With Reacting
When something feels wrong, most people react. They tense up, they move, they mention it to someone. What they almost never do is document what they saw, compare it to an established baseline, or apply a framework to determine whether the deviation is meaningful.
This is not a character flaw. It is the predictable result of operating without a system.
Intelligence tradecraft addresses this by separating two distinct phases of analytical work:
Baseline Development
The deliberate, pre-incident documentation of what your environment looks like when it is operating normally. This is the work that happens before anything goes wrong.
Deviation Analysis
The structured process of comparing current observations against that documented baseline and determining whether the difference is significant, coincidental, or the leading edge of a threat.
Without the first phase, the second phase is impossible. You are not comparing observations against a baseline — you are comparing them against a feeling. Feelings are not auditable. They do not transfer between team members. They degrade under stress.
FM 34-2-1 (Reconnaissance and Surveillance) and FM 2-22.3 (HUMINT Collection Operations) both treat pattern-of-life analysis as a foundational collection discipline — not an advanced one. The premise is consistent across doctrine: before you can report what is wrong, you must be able to articulate what is right.
What “Normal” Actually Means
In intelligence tradecraft, normal is not a vague impression. It is a documented record of observable behaviors, patterns, and conditions across a defined environment during a defined period.
Normal includes:
- Who moves through the area — and when, how, and at what intervals
- What infrastructure does — traffic loads on roads, power usage patterns, water pressure cycles
- How people behave at routine moments — school drop-off, shift changes, mail delivery, market days
- What the communications environment looks like — which nets are active, which vehicles have which configurations, what the ambient radio traffic pattern is
These are your four baseline domains. INT-08 builds competency in all of them. For now, understand that each domain has its own rhythm — and disruptions to that rhythm are observable, documentable, and intelligence-relevant.
A baseline is not what you think the environment looks like. It is what you have documented it to look like. The difference between those two things is the difference between intuition and intelligence.
The Trained Observer vs. the Untrained Observer
The distinction between trained and untrained observation is not primarily one of attention span or situational awareness. It is one of method.
An untrained observer walking through a neighborhood notices things that are unusual enough to register emotionally — the stranger who looks out of place, the car parked in an odd spot, the conversation that stops as you walk past. These observations may be valid signals. But without a baseline, there is no way to know whether they represent genuine anomalies or simply unfamiliar elements of a pattern the observer has not yet learned.
A trained observer does something different: they document first. They establish what the environment looks like on a Tuesday morning at 0730 before anything happens. Then they compare subsequent observations against that record.
A neighborhood preparedness team in a semi-rural area began conducting weekly area walks in the spring, using a simple activity register to log vehicle counts, pedestrian timing, and any infrastructure observations. Four months later, during a period of civil unrest in the regional hub city, one team member noticed that a particular crossroads — which normally saw two to four vehicles per hour in the early morning — was seeing twelve to fifteen. The team had the data to confirm it. They did not rely on a feeling. They filed a deviation report and shared it with their MAG network. Three other teams confirmed similar patterns on adjacent routes.
That is pattern of life analysis working as designed.
What This Course Teaches
INT-08 is organized around five lessons that follow the full analytical cycle from baseline development through reporting:
- Lesson 0 (this lesson): The conceptual foundation — why baselines matter and what changes when you operate with one.
- Lesson 1: The four baseline domains and how to build a documentation system for each one.
- Lesson 2: How to read your collected data — the analytical tools drawn from FM 2-22.3 and FM 34-2-1 adapted for civilian use, including pattern analysis plot sheets and activity registers.
- Lesson 3: Cascade indicators — how disruptions in one domain often predict disruptions in others, and how to recognize compounding signals before they converge into a crisis.
- Lesson 4: Translating observations into reporting products that can be shared with your MAG or integrated into a Community SITREP.
INT-08 feeds directly into PLN-01: Community Situational Awareness. The Community Lifelines framework you will encounter there — Safety & Security, Food/Water/Shelter, Communications, Energy, Transportation, Health & Medical, Hazardous Materials — maps directly to the four baseline domains you will learn to track here. If you complete INT-08 before PLN-01, you will find the SITREP framework immediately recognizable. You will have been baselining those exact systems all along.
How Each Lesson Is Structured
Every lesson in this course follows the same adult-learning cycle:
- Doctrine first. Each concept is grounded in FM 34-2-1, FM 2-22.3, and where appropriate, the Camp X SOE Training Manual. You learn why the method works, not just what the steps are.
- Application second. Every concept is applied to realistic community and neighborhood scenarios. Abstract tradecraft is translated into actions you can take this week.
- Knowledge checks. Questions test application, not recall. Correct answers include the full reasoning. Incorrect answers direct you back to the specific section containing the answer.
This course does not teach surveillance. It teaches observation and baseline documentation — two things that happen in public, in your own community, as a natural extension of being present in a place. The distinction matters legally, ethically, and operationally. If you are unclear on it, read the OPSEC section of the curriculum before proceeding.
Before You Continue
Before moving to Lesson 1, answer one question for yourself in writing:
What does your block, street, or neighborhood look like at 0700 on a Tuesday?
Write down what you think you know: vehicle counts, pedestrian patterns, infrastructure behavior, anything you would characterize as “normal.” Be specific. Then set that document aside. At the end of this course, you will compare what you thought you knew against what a trained baseline approach reveals.
Most students find the gap significant.