VSI GLOBAL // ENTERPRISE ARCHITECTURE

OSINT-003-locate-and-skip-trace-report-collection

10 min read

[SUBJECT FULL NAME] - Collection Map

OSINT-003 Locate & Skip-Trace Report - collection workspace. Central topic = the subject to be located. Branches = data-point categories for the locate/skip-trace product. Drop each collected value as a child node; expand it with where it was found and recency. Paste raw tool output into the node’s Notes. This is a locate product - the operative question is WHERE IS THIS PERSON NOW, not a full background profile. → feeds deliverable OSINT-003.

00 · Collection Plan - PIRs & EEIs

The locate requirements this collection must satisfy, mapped to deliverable sections. Tick each EEI as satisfied. → drives §1 BLUF/Locate Summary, §2 Tasking/Inputs/Locate Objectives, §9 Verification & Confidence Assessment, §10 Collection Gaps & Recommended Next Actions.

L-1 - Current residential address: can the subject be located?

  • EEI: at least one current candidate address with source and recency date
  • EEI: two or more independent sources corroborating the lead address (Confirmed/High confidence threshold)
  • EEI: same-name / same-DOB candidates identified and excluded
  • EEI: any evidence subject is intentionally evading location or at a mail-drop

L-2 - Reachable phone / email: how can the subject be contacted or served?

  • EEI: at least one active phone number with carrier and recency
  • EEI: at least one active email address with confirmation of currency
  • EEI: social / messaging channels that could be used to reach the subject

L-3 - Serviceability / best contact window: when and where is service or contact feasible?

  • EEI: work address / employer confirmed as secondary contact channel
  • EEI: habitual routine or movement pattern supporting a service window
  • EEI: any legal constraints on contact (protected person, ACP program, do-not-contact)

L-4 - Identity confirmation: is the located person the correct individual?

  • EEI: name + DOB/age match against located records
  • EEI: prior address linkage to client-provided starting data
  • EEI: relative or associate linkage corroborating identity
  • EEI: same-name confusion risk assessed and documented

Collection gaps / RFIs (running)

  • [open item] → route to [product / field tasking]
  • [open item]

01 · Identity & Biographic

Anchor identifiers that bind located records to the right individual - lighter than a full dossier but explicit enough to support §6 Identity Confirmation. → feeds §6 Identity Confirmation, §2 Client-Provided Inputs.

Names

  • Full legal name:
  • Middle name / initial:
  • Maiden / former name:
  • AKA / aliases:
  • Transliterations / native script:

Birth & nationality

  • DOB / YOB:
  • Place of birth:
  • Nationality / citizenship(s):
  • Partial SSN / national ID (as provided by client, redacted per DPPA/GLBA):

Physical description

  • Description (for field / service verification):
  • Distinguishing features:

Starting data (client-provided)

  • Last-known address (client-supplied):
  • Last-known phone / email (client-supplied):
  • Employer / other input (client-supplied):
  • Verified vs. client-claimed:

02 · Contact & Selectors

The pivot core for the locate. Each selector is its own clonable block - clone per value. → feeds §4 Contact Information, §6 Identity Confirmation, §1 BLUF. Tool hints: phones → truecaller/NumLookup/carrier lookup; emails → holehe/h8mail/hunter.io; usernames → idcrawl/sherlock/whatsmyname.

Phone numbers

→ feeds §4 Contact Information. Clone the block per number. Distinguish active from historical.

  • [number - e.g. +1 555-0142]
    • Type / carrier: [mobile / landline / VoIP]
    • Status: [Active / Disconnected / Unknown]
    • Last verified / reported:
    • Linked accounts / apps (WhatsApp, Signal, Telegram):
    • Where found (source + URL):
    • Source grade (A–F / 1–6):
    • Attribution confidence: [Confirmed / Probable / Possible]
    • Notes / tool output: ← (truecaller, NumLookup, caller-ID, carrier lookup)
  • [number 2]

Email addresses

→ feeds §4 Contact Information. Clone the block per address.

  • [email]
    • Status: [Active / Bouncing / Unknown]
    • Last verified / reported:
    • Linked accounts (account discovery):
    • Breach / paste appearances:
    • Where found (source + URL):
    • Source grade (A–F / 1–6):
    • Attribution confidence: [Confirmed / Probable / Possible]
    • Notes / tool output: ← (holehe, h8mail, hunter.io)
  • [email 2]

Usernames / handles

→ feeds §4 Contact Information (social/messaging), §5 Address History (geo-tagged posts). Clone per handle.

  • [handle - e.g. jdoe_1982]
    • Platforms / where found (URL):
    • Linked email(s):
    • Linked phone(s):
    • Other accounts reusing it:
    • Attribution confidence: [Confirmed / Probable / Possible]
    • Notes / tool output: ← (idcrawl, sherlock, whatsmyname)
  • [handle 2]

03 · Addresses & Locations

The operative branch for the locate: current candidate address(es), ranked by recency and corroboration, plus full address history as locate context. → feeds §3 Current Location Findings, §5 Address History & Associated Locations, §9 Verification & Confidence Assessment.

Current / best candidate address

Each candidate becomes its own block. Rank by confidence. Clone per candidate.

  • [candidate address - e.g. 123 Main St, City, State ZIP]
    • Rank: [1 (best) / 2 / 3]
    • Address type: [Residential / Work / Seasonal / Mail-drop / P.O. Box]
    • Last reported date:
    • Source(s):
    • Source grade (A–F / 1–6):
    • Number of independent corroborating sources:
    • Conflicting indicators:
    • Location confidence: [Confirmed / High / Moderate / Low]
    • Notes / tool output: ← (public records, licensed locate DB, LexisNexis/TLO/IRB/CLEAR)
  • [candidate address 2]

Address history (chronological)

→ feeds §5 Address History & Associated Locations. Clone per address.

  • [prior address]
    • Period (from–to):
    • Type: [Residential / Work / Seasonal / Mail-drop]
    • Source / grade:
    • Notes:
  • [prior address 2]

Other associated locations

  • [location - work / frequented / seasonal]
    • Type:
    • Basis / source:
    • Locate relevance:

Movement pattern indicators

  • Relocation cadence (frequent mover / stable):
  • Multi-state or seasonal pattern:
  • Signs of intentional evasion (mail-drop, transient, no utilities):

04 · Digital Footprint

Social and digital presence used as locate signals: geo-tagged posts, check-ins, platform activity that corroborates or contradicts the physical location. → feeds §3 Current Location Findings (corroboration), §4 Contact Information, §5 Address History.

Social media - geo signals

Clone per platform. Focus on recency and any location disclosures.

  • [platform - Facebook / X / Instagram / LinkedIn / TikTok / Nextdoor / other]
    • Handle / URL:
    • Attribution confidence: [Confirmed / Probable / Possible]
    • Status: [Active / Dormant]
    • Location disclosures (check-ins, geo-tags, mentioned city/neighbourhood):
    • Most recent activity date:
    • Notes (content relevant to locate):

Data-broker / people-search records

→ feeds §3 Current Location Findings, §5 Address History. Tool hints: Spokeo, Whitepages, Intelius, BeenVerified, FastPeopleSearch.

  • [source - e.g. Whitepages]
    • Result:
    • Recency of address listed:
    • Source grade (A–F / 1–6):
    • Notes:

Breach / paste / PII exposure

  • [indicator]
    • Source:
    • Date observed:
    • Significance to locate:

05 · Network & Associations

Relatives, co-residents, and associates as locate leads and corroborators. Employer as a contact channel. → feeds §7 Associated Persons & Locate Leads.

Family & household members (primary locate leads)

Clone per person. These are the first fallback if direct locate fails.

  • [name]
    • Relationship: [Spouse / Parent / Sibling / Child / Co-resident]
    • Known address / contact:
    • Relevance to locate: [Corroborates address / Alternate contact channel / Last-known co-resident]
    • Source / grade:
    • Confidence: [H/M/L]

Other close associates / locate leads

  • [name]
    • Relationship:
    • Known contact / location:
    • Locate relevance:

Employer / workplace

  • [employer / workplace]
    • Address:
    • Contact channel (HR / front desk):
    • Verified employment: [Y/N]
    • Source / grade:
    • DPPA / permissible-use note:

06 · Employment, Education & Affiliations

Employment and affiliations primarily as locate corroborators and service channels, not full biographical development. → feeds §7 Associated Persons & Locate Leads, §5 Address History (work address), §6 Identity Confirmation.

Employment

  • [employer]
    • Role / title:
    • Work address:
    • Dates (current / former):
    • Verified / claimed:
    • Source:

Professional licenses / registrations

License registries often carry current addresses - locate signal.

  • [license / registration type]
    • Jurisdiction / registry:
    • Address on record:
    • Date of record:
    • Source:

Memberships / affiliations

07 · Vehicle, Property & Asset Locators

Vehicles and real property as location signals - DPPA/permissible-use compliant. These are locate corroborators, not an asset trace. → feeds §8 Vehicle, Property & Asset Locators.

Vehicles

Clone per vehicle. DMV-derived data requires documented DPPA permissible use.

  • [vehicle - e.g. 2019 Honda Accord]
    • Make / model / year:
    • Plate (redact as required):
    • VIN (partial):
    • Registered address:
    • Registered address date:
    • Tie to subject: [Owner of record / Co-registrant / Household member]
    • DPPA permissible use documented: [Y/N]
    • Source / grade:
    • Notes / tool output:
  • [vehicle 2]

Real property

Clone per parcel. Owner-of-record address = strong locate corroborator.

  • [property / parcel]
    • Address:
    • Role: [Owner / Co-owner / Mortgagor]
    • Recording date:
    • County assessor / recorder source:
    • Source grade (A–F / 1–6):
    • Notes:
  • [property 2]

Other locator signals

  • Utility / voter registration:
  • Professional board / court filings address:
  • USPS change-of-address indicator:

08 · Legal & Derogatory (Locate-Relevant)

Legal records used as locate signals (court filings, judgments, case addresses). Also: protected-person screening. Not a full adverse-media or legal background - refer to OSINT-001 for that. → feeds §9 Verification & Confidence Assessment (conflicting indicators), §2 Tasking (constraints).

Court / civil records (as address source)

  • [matter / filing]
    • Jurisdiction / case #:
    • Address of record in filing:
    • Date of filing:
    • Source / grade:

Judgment / liens (as corroborator or locate constraint)

  • [judgment / lien]
    • Jurisdiction:
    • Address on record:
    • Date:

Protected-person / ACP screening

  • Address-confidentiality program check: [Clear / Flagged / Unknown]
  • Domestic-violence / stalking concern flag: [Y/N/Unknown]
  • Action if flagged: halt collection; reconfirm requestor authority and permissible purpose

Sanctions / watchlist (identity disambiguation)

  • OFAC SDN: [Clear / Hit / Near-match]
  • Other applicable list:

09 · Media & Imagery

Photos and video as identity confirmation aids and for field-verification briefing packets. → feeds §6 Identity Confirmation, §12 Appendix C Evidence Archive.

Photos of subject

  • [image ref]
    • Source / URL:
    • Recency / date:
    • Metadata (EXIF / geo-data):
    • Reverse-image search results: ← (Google Images, TinEye, PimEyes)

Avatar / profile picture

  • [image]
    • Platform / URL:
    • Reverse-image search:

Video / audio

  • [file or URL]
    • Source / metadata:
    • Locate relevance:

10 · Pattern of Life (Locate-Relevant)

OSINT-visible patterns used to identify a service window or confirm current location. No covert/physical surveillance is performed in this product - field verification is recommended as a next action. → feeds §9 Verification & Confidence Assessment, §10 Collection Gaps & Recommended Next Actions (service window recommendation).

Routine & temporal patterns (observable)

  • [observed routine from social media / public records]:

Habitual locations (regularly appearing)

  • [habitual location - workplace / gym / place of worship]:
    • Source / basis:
    • Frequency confidence: [H/M/L]

Travel & mobility signals

  • [observed travel / relocation signal]:
    • Source:

Service window indicators

  • Best time / day for contact or service attempt:
  • Vehicle typically present:
  • Any cautions for contact (security presence / intercom-only building):

Evasion indicators

  • Pattern of using mail-drops / P.O. boxes:
  • Frequent address changes:
  • Mismatch between stated and apparent location:

99 · Collection Admin

Working register - not a deliverable section, but the audit trail behind §11 Sources & Methodology and §12 Appendices. Every material datum must trace to a graded source entry here.

Source register

Every material datum traceable to a graded source. Admiralty A–F (reliability) / 1–6 (credibility).

  • [S-1 - source name / database]
    • Type: [Public record / Licensed locate DB / Digital-OSINT / Client-provided]
    • Reliability (A–F):
    • Credibility (1–6):
    • Date accessed:
    • Permissible-use basis (if DPPA/GLBA-regulated source):

Evidence archive

  • [screenshot / capture ref + hash + URL + timestamp]:

Legal / compliance log

  • Permissible purpose on file: [Y/N - matter/case ref]
  • DPPA documentation complete: [Y/N]
  • GLBA / no-pretexting attestation: [Y/N]
  • Protected-person screening completed: [Y/N]
  • Retention schedule / DPA reference:

Open gaps / verification pending

  • [item] → [recommended action / route to field tasking]
  • [item]

Running RFIs

  • [open RFI + priority]

Graph View