OSINT Analyst Workflow and Command Guide

OSINT Analyst Workflow and Command Guide

1. Requirement

Write one answerable question, its consumer, deadline, decision supported, and what would count as sufficient. “Research the organization” is not a requirement.

2. Scope and collection plan

List allowed sources, prohibited actions, collection order, likely evidence, and stop conditions. Prefer passive collection. Record rejected leads instead of silently following them.

3. Preserve

Record origin, transfer path, acquisition time, filename, size, detected type, and SHA-256. Keep originals read-only when practical and examine working copies.

4. Examine

Select tools by question:

5. Separate evidence from reasoning

Label Meaning
Source Origin of the information or artifact
Observation What the source directly displays or contains
Assumption Condition treated as true but not established
Inference Conclusion derived from observations
Judgment Answer to the requirement
Gap Missing information that could change the judgment

6. Corroborate and test alternatives

For each important judgment, ask:

7. State confidence

Confidence applies to the judgment. Source reliability and information credibility are separate considerations.

8. Handoff

# Analyst handoff
- Requirement and consumer:
- Bottom line:
- Key evidence/source IDs:
- Direct observations:
- Assumptions and inferences:
- Alternatives considered:
- Confidence and reason:
- Intelligence gaps:
- Authorized next action:
- Stop condition:
- Analyst / verifier / time:

Two-minute brief

  1. Bottom line.
  2. Two strongest pieces of evidence.
  3. Confidence and why.
  4. Main gap or alternative.
  5. Authorized next action and stop.

Privacy-safe release

Keep the preserved original internal. Create a separately hashed release copy, remove unnecessary personal data and metadata, verify the rendered result, and document each transformation. Redaction must remove underlying data, not merely cover it visually.