FIELD CONTACT AND SUSPICIOUS ACTIVITY REPORT

[FCR REFERENCE - ENGAGEMENT REF]

The Field Contact and Suspicious Activity Report (FCR) is the standing format by which any detail member converts a field observation into a structured, gradable report. It is the observation half of the protective intelligence cycle: EP-019 PIR Management states what the detail is looking for; this report is how the detail says what it saw. Every filed FCR flows to Threat Assessment and Management case intake in D-01 (OSINT-052) as ART-field-contact-report. Contrast with EP-008: the Surveillance Detection Report is the deliberate product of a planned SD operation with designed routes, static OPs, and correlation counting across legs; the FCR is the incidental single-observation report filed by any operator in the course of normal duties. Repeated FCR correlation is a standing trigger for a deliberate EP-008 operation. This is a repeatable format standard. All incident-specific values are bracketed placeholders. Do not assert fictional findings or invent data.

---

Document Control

Field	Value
Report Reference	[FCR-YYYY-###]
Date of Report	[YYYY-MM-DD]
Classification / Handling	[internal / CONFIDENTIAL]
Client	[CLIENT NAME]
Engagement Reference	[ENGAGEMENT REF]
Prepared By (Observer)	[INITIALS]
Received By (Detail Leader)	[INITIALS]
Graded By (Detail Intelligence Officer)	[INITIALS]
Version	[0.1.0]
Distribution	[NAMED RECIPIENTS]

Handling & Legal Caveat

Handling: [internal / CONFIDENTIAL]. Access restricted to detail command, protective intelligence, and the submitting operator.

IMMINENT DANGER: This report never substitutes for immediate response. If danger to the principal or detail is imminent, execute the radio or duress protocol first and file the written report after the incident is resolved (Section 3).

Nature of this product: A single-observation field report. It records what an operator saw, heard, or received; it does not assess threat, assign concern, or predict behavior. Assessment happens downstream in D-01 case intake (OSINT-052).

Collection boundary: Content is limited to lawful observation from places the observer was entitled to be. No pretext contact, no surveillance of third parties, no intrusion into private spaces (Section 8).

Duty to warn / report: Where an observation implicates a duty to warn an identifiable potential victim or a mandatory-reporting duty, those obligations are triggered independently of this report and must be actioned per counsel and jurisdiction (cc02-standards/DOCTRINE.md).

Report Snapshot

Field	Value
Observer	[INITIALS]
Observation DTG	[YYYY-MM-DD HH:MM ZONE]
Location	[VENUE / ADDRESS / COORDINATES]
Threshold Claimed	[Immediate / Routine]
Operator Grade	[A-F / 1-6]
Analyst Re-Grade	[A-F / 1-6]
Disposition	[NEW / MRG / WLST / CLB]
BOLO Issued	[Y / N - BOLO REF]

---

Table of Contents

1. Purpose and Position in the Protective Intelligence Cycle
2. Filing Triggers
3. Reporting Thresholds and Imminent Danger Escalation
4. Report Format
5. Grading: Operator Grade and Analyst Re-Grade
6. Routing, Matching, and Disposition
7. BOLO Issuance
8. Retention and Legal Handling
9. Quality Standard

Annex A: Grading Matrices

---

1. Purpose and Position in the Protective Intelligence Cycle

Instructional tradecraft: Fix what this report is, who files it, and where it sits relative to the adjacent products, so no observation dies in an operator’s memory or gets misrouted into the wrong product.

• What it is: the single standing format for converting any field observation by any detail member into a structured, gradable, correlatable report. One incident, one FCR; unrelated observations never share a report.
• Who files: any detail member (BR, RF, MR, JM, or any engagement-rostered operator; initials only, never names). Filing authority is universal; no rank or role gate exists on submission.
• Requirements half / observation half: EP-019 PIR Management defines what the detail is tasked to look for (PIRs, indicators, NAIs). The FCR is the reporting instrument that answers those indicators from the field. An FCR that answers a PIR indicator is cross-logged against the EP-019 collection plan with the FCR reference as the answer pointer.
• Contrast with EP-008 (related product): EP-008 is the deliberate surveillance-detection product: a planned SD operation with designed detection routes, static OPs, sighting legs, and a correlation-count decision tree. The FCR is incidental: one operator, one unplanned observation, filed below the EP-008 threshold. The Detail Intelligence Officer correlates FCRs over time; a correlation pattern across FCRs is a standing trigger to stand up a deliberate EP-008 operation. FCR subject and vehicle descriptors follow the same correlation-key discipline as the EP-008 sighting log so the two products cross-match.
• Downstream seam: every filed FCR, with its analyst grade and disposition, is provided to D-01 as ART-field-contact-report and consumed by OSINT-052 Threat Case Assessment and Management as case intake (Section 6).

2. Filing Triggers

Instructional tradecraft: Triggers are mandatory floors, not permission. The norm is file on instinct: if an operator’s attention snagged on something, that is reportable. The analyst grades it; the operator does not pre-filter.

Mandatory triggers (an FCR shall be filed when any of these occurs):

#	Trigger	Notes
T-1	POI approach or contact	Any approach to, or attempted contact with, the principal, family, residence staff, or detail by a known or suspected person of interest
T-2	Suspected hostile surveillance sighting	Any single sighting suggesting surveillance (loitering with observation, photography of the principal or posts, TEDD-type anomaly) below the EP-008 correlation threshold
T-3	Anomalous correspondence, gift, or delivery	Unsolicited, threatening, fixated, or otherwise anomalous letters, packages, gifts, or digital messages reaching the principal or detail
T-4	Boundary probing	Testing of perimeter, access control, or procedures: attempted entry, tailgating, credential challenge failures, drone overflight of the property
T-5	Unusual questioning or elicitation	Third-party questioning about the principal’s schedule, residence, vehicles, security posture, or detail staffing, directed at any detail member, staff, or vendor
T-6	Repeated presence	The same person or vehicle noticed across separate locations or separate times without an evident lawful pattern

The do-not-hesitate norm: when in doubt, file. A filed FCR that grades out benign costs ten minutes; an unfiled observation that later matches a case costs the detail its earliest warning. Operators are evaluated on the clarity and timeliness of their reporting, never on whether the observation proved benign. No FCR is ever treated as a false alarm.

3. Reporting Thresholds and Imminent Danger Escalation

Instructional tradecraft: The threshold decides how fast the observation moves, not whether it moves. Every threshold ends in a written FCR.

IMMINENT DANGER ESCALATION

If the observation involves a weapon, an active approach in progress, a breach in progress, or any immediate danger to the principal or detail: radio or duress protocol first, report after. Execute the detail net alert and immediate-action drill per the standing communications plan and emergency action plan. The written FCR is completed after the incident is resolved and never delays or replaces the alert.

Threshold	Applies To	Timeline	Channel
Immediate	T-1 in any form; T-2 where surveillance appears ongoing; T-4 at an occupied site; T-5 where elicitation is in progress or same-day	Voice notification to Detail Leader without delay; written FCR within [1 HOUR]	Detail net voice, then written FCR
Routine	All other triggers, including observations recalled after the fact	Written FCR before end of shift, not later than [12 HOURS] after observation	Written FCR

• A late recollection is still filed: an observation remembered a day later is a Routine FCR with the delay noted in the narrative, not a lost report.
• The Detail Leader may upgrade any Routine FCR to Immediate handling on receipt; downgrading an operator’s Immediate claim requires a recorded reason.

4. Report Format

Instructional tradecraft: Blocks 1, 2, 5, and 6 are mandatory in every FCR; remaining blocks are completed as observed. Record facts as observed; label inference as inference. Never delay filing to perfect a descriptor: partial descriptors correlate, unfiled ones do not.

Block 1: Observer and Administration

Field	Value
FCR Reference	[FCR-YYYY-###]
Observer	[INITIALS]
Observer Role / Post at Time	[POST / ASSIGNMENT]
Observation DTG	[YYYY-MM-DD HH:MM ZONE]
Report DTG	[YYYY-MM-DD HH:MM ZONE]
Location	[VENUE REF / ADDRESS / COORDINATES]
Trigger Claimed	[T-1 / T-2 / T-3 / T-4 / T-5 / T-6 / INSTINCT]
Threshold Claimed	[Immediate / Routine]

Block 2: Narrative

Chronological, first person, plain language. What drew attention, what was observed, what happened, how it ended. Separate observation (“subject photographed the gate”) from inference (“appeared to be casing”), and mark inference as such.

[NARRATIVE]

Block 3: Subject Descriptor(s)

One column per subject. Fill what was observed; leave the rest blank rather than guessing.

Field	Subject 1	Subject 2
Sex / Apparent Age	[ ]	[ ]
Height / Build	[ ]	[ ]
Hair / Facial Hair	[ ]	[ ]
Clothing	[ ]	[ ]
Distinguishing Features	[MARKS / TATTOOS / GAIT / ACCENT]	[ ]
Demeanor	[ ]	[ ]
Verbatim Statements	[EXACT WORDS WHERE HEARD]	[ ]
Direction of Travel / Departure	[ ]	[ ]
Seen Before	[Y / N / UNSURE - WHERE, WHEN]	[ ]

Block 4: Vehicle Descriptor(s)

Field	Vehicle 1	Vehicle 2
Make / Model / Color	[ ]	[ ]
Plate / State or Country	[FULL OR PARTIAL]	[ ]
Damage / Stickers / Modifications	[ ]	[ ]
Occupant Count / Descriptions	[ ]	[ ]
Direction of Travel	[ ]	[ ]
Seen Before	[Y / N / UNSURE - WHERE, WHEN]	[ ]

Block 5: Principal Proximity and Exposure

Field	Value
Principal Present	[Y / N / EN ROUTE]
Closest Distance to Principal	[METERS / NOT APPLICABLE]
Line of Sight to Principal	[Y / N]
Principal Aware	[Y / N]
Detail Posture at Time	[POST CONFIGURATION / MOVEMENT PHASE]

Block 6: Action Taken

Field	Value
Action	[OBSERVED ONLY / REPOSITIONED PRINCIPAL / CHALLENGED SUBJECT / PHOTOGRAPHED / NOTIFIED LE / OTHER]
Taken By	[INITIALS]
Outcome	[SUBJECT DEPARTED / LE RESPONDED / NO CHANGE / OTHER]

Block 7: Witnesses

Witness	Type	Contact (where lawfully obtained)
[INITIALS OR THIRD-PARTY DESCRIPTION]	[Detail / Staff / Vendor / Public]	[CONTACT OR NONE]

Block 8: Sensor and Photo References

Reference	Type	Custody
[PHOTO / VIDEO / CCTV / DASHCAM REF ID]	[SOURCE DEVICE]	[CHAIN-OF-CUSTODY POINTER]

Block 9: Operator Grade

Completed by the submitting operator per Section 5 before submission.

Datum	Grade	Basis
[DISCRETE OBSERVATION OR RELAYED ITEM]	[A-F / 1-6]	[DIRECT OBSERVATION / RELAYED BY WHOM]

5. Grading: Operator Grade and Analyst Re-Grade

Instructional tradecraft: Two grades, two owners, both retained. The operator grades at submission so the receiving analyst knows how the observer weighs their own observation; the analyst re-grades on intake against holdings. The analyst grade is authoritative downstream; the operator grade is never overwritten.

• Operator grade (at submission): the submitting operator assigns an Admiralty two-character grade (Annex A) to each discrete datum in the report. Direct personal observation by a trained operator is typically graded [B2]; information relayed to the operator by a third party is graded on that party’s reliability and is never upgraded by retelling. Uncertainty defaults toward [F/6], never toward false precision.
• Analyst re-grade (on intake): the Detail Intelligence Officer (CS) re-grades each datum against existing holdings: prior FCRs, TAM case files, watchlist entries, and open collection. Corroboration by an independent prior report can raise credibility; contradiction lowers it.
• Disagreement handling: where the analyst grade differs from the operator grade, both grades are retained in the record with a one-line basis for the change. Silent overwrites are prohibited; the divergence itself is analytic signal.
• Grades, not judgments: the FCR carries grades only. Any likelihood or confidence language about what the observation means belongs to the downstream D-01 assessment, not to this report.

6. Routing, Matching, and Disposition

Instructional tradecraft: The route is fixed and short, and forwarding is mandatory at every hop. A Detail Leader may annotate an FCR; no role may suppress one.

Routing sequence:

1. Operator files to the Detail Leader within the Section 3 threshold (voice first where Immediate).
2. Detail Leader acknowledges receipt, takes any immediate protective action within standing authority, may annotate operational context, and forwards the FCR to the Detail Intelligence Officer (CS) without filtering. Forwarding every FCR is mandatory.
3. Detail Intelligence Officer (CS) logs the FCR under its serial in the engagement FCR log, re-grades per Section 5, and matches it against: open and monitored TAM cases (OSINT-052 threat-actor register), the current watchlist, active PIR indicators (EP-019, ART-pir-set), and prior FCRs on correlation keys (subject and vehicle descriptors).
4. Disposition assigned within [24 HOURS] of intake, recorded on the FCR, and reported back to the Detail Leader and the submitting operator. Every FCR receives a disposition; none remains unadjudicated past the deadline.
5. Seam handoff: the graded, disposed FCR is provided to D-01 as ART-field-contact-report for OSINT-052 case intake.

Disposition codes:

Code	Disposition	Meaning	Downstream Action
NEW	New case opened	Observation warrants a new TAM case	OSINT-052 case opened (status Active); BOLO assessed per Section 7
MRG	Merged to existing case	Observation relates to a known case or actor	Appended to the case chronology and threat-actor register; case review triggered; BOLO assessed per Section 7
WLST	Watchlisted	Below case threshold but worth tracking	Subject or vehicle entered on the engagement watchlist (maps to the OSINT-052 monitored-node posture); future FCRs auto-matched
CLB	Closed benign	Graded and explained; no threat nexus	Retained in the FCR log for future correlation; no further action

ART-field-contact-report handoff spec:

{
  "fcr_id": "FCR-YYYY-###",
  "observer": "INITIALS",
  "dtg_observation": "ISO-8601-TIMESTAMP",
  "location": "string",
  "trigger": "T-1|T-2|T-3|T-4|T-5|T-6|INSTINCT",
  "threshold": "Immediate|Routine",
  "operator_grade": "A-F/1-6",
  "analyst_grade": "A-F/1-6",
  "disposition": "NEW|MRG|WLST|CLB",
  "case_pointer": "string|null",
  "pir_pointer": "PIR-###|null",
  "bolo_ref": "string|null"
}

7. BOLO Issuance

Instructional tradecraft: Intelligence flows back down or the reporting loop dies. When an FCR opens or updates a case, the detail that generated the observation gets the lookout product built from it.

• Trigger: any FCR disposed NEW or MRG, and any WLST entry the Detail Intelligence Officer judges the detail needs eyes on, generates a BOLO back to the detail.
• Content: subject and vehicle descriptors (correlation keys included), last known location and DTG, associated case or watchlist reference, specific behavior to watch for, and the standing instruction: observe and report only, no intercept, no contact, no follow beyond assigned post or duties.
• Dissemination: flash traffic on the detail net per the EP-011 communications plan for urgent BOLOs; otherwise carried in the daily brief per EP-016 until expiry.
• Expiry and review: every BOLO carries an expiry or review date [YYYY-MM-DD]; the Detail Intelligence Officer renews, revises, or cancels at review. Stale BOLOs are cancelled, not left on the net.
• Feedback loop: any detail sighting against an active BOLO is itself filed as a new FCR citing the BOLO reference, closing the loop between observation and lookout.

8. Retention and Legal Handling

Instructional tradecraft: The FCR is lawful evidence or it is nothing. Every line in it must survive scrutiny by counsel and, where escalated, by law enforcement.

• Lawful observation only: FCR content is limited to what the observer saw, heard, or received from a place they were lawfully entitled to be. No pretext contact with any subject, no following a subject beyond the observer’s assigned post or movement duties, no intrusion into private spaces, no interception of communications.
• Photography and recording: permitted only as lawful in the jurisdiction of observation; consult the area-of-operations legal annex for local photography, recording, and data-protection constraints before relying on imagery. Where local law restricts capture, the descriptor blocks carry the observation instead.
• Privacy constraints: subject descriptors are personal data. Handle per the engagement data-protection regime and CLASSIFICATION.md; distribution is restricted to the Section 6 routing chain and named recipients; no onward dissemination without Detail Leader approval.
• Duty to warn: where FCR content implicates a duty to warn an identifiable potential victim or a mandatory-reporting duty, the obligation is actioned per counsel and jurisdiction as defined in cc02-standards/DOCTRINE.md, independently of report routing.
• LE handoff: where a disposition leads to law-enforcement referral, the original FCR, its grades, imagery references, and chain-of-custody pointers form part of the handoff package; originals are preserved unaltered.
• Retention: all FCRs, including CLB dispositions, are retained for the life of the engagement plus [RETENTION PERIOD PER CLASSIFICATION.md]; closed-benign reports hold correlation value and are never purged early.

9. Quality Standard

• Ten-minute rule: a complete FCR (mandatory Blocks 1, 2, 5, 6 plus descriptors as observed) is completable in under 10 minutes from a phone in the field. Any format change that breaks the ten-minute rule is rejected.
• Cold-start test: an analyst with no prior knowledge of the incident can grade, match, and dispose the FCR from the report and its referenced artifacts alone, without calling the observer. A call-back for basics is a format defect, not an operator defect.
• Fact and inference separated: every narrative distinguishes observation from inference; a report that blends them is returned for one correction pass, then filed as-is with the defect noted.
• No pre-filtering: operators file on instinct per Section 2; grading and adjudication belong to the analyst. Report quality is judged on clarity, timeliness, and descriptor discipline, never on outcome.
• Correlation-key discipline: subject and vehicle descriptors follow the same descriptor conventions as the EP-008 sighting log so FCRs and SD sightings cross-match in analysis.

Annex A: Grading Matrices

NATO Admiralty source reliability (A-F): A Completely reliable · B Usually reliable · C Fairly reliable · D Not usually reliable · E Unreliable · F Reliability cannot be judged.

NATO Admiralty information credibility (1-6): 1 Confirmed by other sources · 2 Probably true · 3 Possibly true · 4 Doubtful · 5 Improbable · 6 Truth cannot be judged.

END OF REPORT

Model wiring

Generated from cell frontmatter at publish time.

• Related: EP-008
• Provides: ART-field-contact-report