RECONNAISSANCE / RECCE REPORT
[SITE / LOCATION / ROUTE - MISSION / OPERATION REFERENCE]
The Reconnaissance / Recce Report is the structured physical-intelligence product that describes, assesses, and maps a defined geographic area - a site, facility, route, neighbourhood, or AOI - for the purpose of informing operational planning, protective posture, movement security, or risk assessment. It answers, for a specific location or route and a defined mission/threat lens: what does the physical environment look like; what are the access, egress, cover, observation, communications, and security-force patterns; where are the vulnerabilities, threats, and collection opportunities; and what are the implications for a planned operation or movement? It is a terrain- and space-anchored framework product: its analytic core maps physical features through OCOKA (Observation and fields of fire, Cover and concealment, Obstacles, Key terrain, Avenues of approach) adapted for the urban/built environment, applied to specific objectives and threat scenarios defined by the client. The collection logic is PIR → Recce Question → Indicator → Source, covering overt physical inspection, imagery analysis, map/routing data, local and open-source reporting, and (where commissioned) discreet in-country human source collection. It is pre-operational intelligence for a defined activity - it does not deliver the protective/security plan itself. It consumes the environmental baseline of the Regional Study and the destination-level threat picture of the Country Risk Assessment and Country-Entry Risk Assessment where applicable; it feeds the Pre-Travel Threat Assessment, the Executive Trip Security Package, the Operational Mapping & Advance Support product, the Event & Venue Threat Assessment, and any site-specific security planning. Where a recce is conducted specifically for protective advance (principal visit with detail, secure route, vetted venues, medical/evac infrastructure), route that requirement to the Protective Advance Survey & Recce Report sibling. Where the requirement is to assess whether a subject/facility is under hostile surveillance, route to the Hostile Surveillance Vulnerability Assessment sibling. This is a physical-environment reconnaissance report; it is not a security plan, not a vulnerability assessment for a corporate facility (Facility Threat Assessment), not a threat assessment for a named individual (POI products), and not a social-engineering or cyber intelligence product - where those needs surface, raise them as RFIs in §20.
Document Control
| Field | Value |
|---|---|
| Report Reference | [REF-YYYY-###] |
| Date of Report | [YYYY-MM-DD] |
| Recce Date(s) / As-Of Date | [YYYY-MM-DD - dates of physical inspection or imagery as-of; one date if a single recce pass, range if multi-phase] |
| Classification / Handling | [CLASSIFICATION - TLP:MARKING] |
| Client | [CLIENT NAME] |
| Requesting Party | [CONTACT - ENGAGEMENT REF] |
| Site / Location / Route | [Address, coordinates, area descriptor, or named route segment - the geographic object of the recce] |
| Mission / Operational Context | [The planned operation, movement, event, or protective task the recce supports - what the intelligence will inform] |
| Recce Objective (purpose) | [Specific intelligence purpose - e.g., route security assessment, venue access/egress mapping, local threat environment survey, OPSEC/covert-movement feasibility, photographic baseline for later comparison] |
| Scope / Depth | [What the recce covers - e.g., exterior only, interior and perimeter, neighbourhood out to X km, route origin-to-destination; what it does NOT cover - stated explicitly] |
| Client Threat / Risk Lens | [The threat or risk scenario the recce is scoped against - e.g., kidnap ambush, hostile protest, active-attacker egress, surveillance detection, covert meeting feasibility] |
| Prepared By | [ANALYST NAME / ID - and recce operator(s) if distinct] |
| Reviewed By | [REVIEWER NAME / ID] |
| Approving Officer | [APPROVER NAME / ID] |
| Version | [1.0] |
| Distribution | [NAMED RECIPIENTS] |
Handling & Legal Caveat
Handling: [Classification/TLP]. Disseminate only to the named authorized recipients. Reproduction or onward sharing prohibited without originator approval. This product may contain detailed physical descriptions of a named site, its security posture, access routes, and vulnerability mappings - data that is operationally sensitive and, in the wrong hands, a threat vector itself. Store and transmit per the client data-processing agreement; restrict to those with a specific operational need-to-know.
Nature of this product (READ FIRST): This is an open-source and overt-physical-recce-based intelligence assessment of a defined geographic area, prepared to inform the client’s operational planning and risk decisions. It is not a security plan, a protective-operations plan, a vulnerability assessment meeting any regulatory or insurance standard, a structural or safety engineering survey, or a surveillance-detection product. The observations and assessments are the firm’s structured analytic judgments based on a defined recce scope and methodology - a time-bound snapshot of the physical environment as observed, not a guarantee of its current or future state. Operational decisions based on this report require integration with the client’s own security, legal, and operational teams.
Sourcing & legality: Findings derive from open, licensed, and lawfully accessed sources - overt physical inspection from public and permitted vantage points; geospatial and imagery data (satellite, aerial, street-level) within licence; map, routing, and cadastral datasets; open-source reporting; and (where commissioned) discreet in-country human-source collection - all current as of the recce date(s). No classified, proprietary-without-licence, trespass, surveillance-off-premises, or unlawfully obtained material is used. Physical recce is conducted from public-access and permitted areas only; no entry onto private property without authorisation, no intrusion into any expectation of privacy, and no photography of individuals or identifiable personal data without lawful basis. All collection complies with applicable jurisdiction law and the client’s instructions. Where a recce requires access to a venue as a guest or invitee (e.g., hotel site survey, event-venue walkthrough), this is conducted with the venue’s knowledge and permission.
Physical-recce limitations: Overt recce is observable. The recce team may be visible to security, local population, or adversarial actors, and should assume that any inspection of a sensitive site may be noticed. Covert or disguised recce methods are outside the scope of this product unless separately commissioned and lawfully authorised - state clearly if the recce was overt, discreet-but-not-covert, or conducted from remote/imagery sources only.
Perishability: Physical environments change - construction, renovation, seasonal vegetation, security-posture shifts, local-disorder alterations. This is a point-in-time snapshot; re-commission the recce if the operational date is more than [X] months later, or if a significant environmental change is known to have occurred.
Reliance: Reliance is limited to the named client for the stated operational purpose; no third-party reliance without originator consent.
Recce Snapshot
| Field | Value |
|---|---|
| Site / Location / Route | [Address / coordinates / area / route descriptor] |
| Recce Date(s) | [YYYY-MM-DD] |
| Recce Type | [Overt / Discreet / Remote/Imagery-only / Mixed] |
| Recce Objective | [The intel purpose - one sentence] |
| Client Threat / Risk Lens | [Threat scenario scoped against] |
| Overall Physical Security Posture (site) | [MATURE / ADEQUATE / BASIC / MINIMAL / NONE - assessed for the threat lens] |
| Overall Route / Access Viability | [FAVOURABLE / CONDITIONAL / UNFAVOURABLE - for planned movement] |
| Highest-Severity Observations | [The 2–3 physical findings that most affect the client’s operational plan - each with a severity rating] |
| Coverage Completeness | [FULL / PARTIAL with gaps listed - e.g., interior not accessed, roof not visible, one route not driven] |
| Principal Coverage Constraints | [Access denied to X area; imagery age/could not resolve Y; seasonal/infrastructure change since recce; time constraints] |
| Overall Assessment Confidence | [HIGH / MODERATE / LOW] |
Table of Contents
- BLUF
- Executive Summary & Scope
- Key Judgments
- Priority Intelligence Requirements (PIRs)
- Recce Framing, Taxonomy & Methodology
- Area / Location Overview
- Route & Movement Analysis
- Site / Facility Description
- Perimeter, Access & Egress Points
- Internal Layout & Key Zones
- Observation, Cover & Concealment
- Communications & Technical Environment
- Security Forces, Personnel & Local Population Patterns
- Threat / Risk Factors at the Recce Location
- Consolidated Findings Register & Severity Matrix
- Key Findings Summary
- Red Flag / Notable Observations
- Analysis of Competing Hypotheses (ACH)
- Key Assumptions Check (KAC)
- Collection Gaps & RFIs
- Recommendations
- Annex A - Sources & Methodology
- Annex B - Appendices
(Page numbers populate on export to Word/PDF.)
1. BLUF
2–3 sentences. Lead with the overall finding - whether the site/route is viable for the planned operation, the most critical physical-security or environmental observation, and the single most decision-relevant implication for the client. Written so the operational planner can act on this line alone.
[BLUF]
2. Executive Summary & Scope
Triggering requirement and operational context; the site/route recceed and the specific intelligence objective; the client’s threat/risk lens. Scope in/out stated explicitly - what area the recce covered, which vantage points or access levels were achieved, which were not, and what is deferred to sibling/downstream products (protective advance → Protective Advance Survey & Recce Report; hostile surveillance assessment → Hostile Surveillance Vulnerability Assessment; security plan or operational detail; facility-specific threat assessment). Narrative synthesis of the key observations, the overall security-posture or route-viability finding, the principal physical vulnerabilities identified, and the coverage gaps. State the overall confidence estimate here.
[EXECUTIVE SUMMARY & SCOPE]
3. Key Judgments
The analytic bottom line on the physical environment and operational implications. Each judgment carries likelihood and analytic confidence as separate columns (never combined - ICD 203) and a change-indicator stating what would shift it. Order by operational significance.
| # | Key Judgment | Likelihood | Analytic Confidence | Change Indicator (what would shift it) |
|---|---|---|---|---|
| KJ-1 | [e.g., The site’s perimeter security is assessed as [MATURE/ADEQUATE/BASIC/MINIMAL/NONE] against the stated threat lens] | [ICD 203 term] | [HIGH/MOD/LOW] | [ ] |
| KJ-2 | [e.g., Route [X] is assessed as viable for [operational movement] with [specific conditions] - see §7] | [ ] | [ ] | [ ] |
| KJ-3 | [e.g., Observation positions overlooking the primary access point exist at [location] and are assessed as exploitable for hostile surveillance] | [ ] | [ ] | [ ] |
| KJ-4 | [e.g., No evidence of recent security upgrade, renovation, or occupancy change was observed; the site appears in the same state as [imagery baseline date]] | [ ] | [ ] | [ ] |
| KJ-5 | [e.g., The area surrounding the site poses [a named threat - e.g., protest, crime, uneasy local population dynamic] that could affect access/egress during the operational window] | [ ] | [ ] | [ ] |
4. Priority Intelligence Requirements (PIRs)
Collection-management spine for a recce product: PIR → Recce Question → Indicator → Source. State each PIR, the answer, key evidence, and analytic confidence. Each PIR maps to one or more recce elements or locations. Summarize in the matrix. Adjust the PIR list to the specific recce objective - these are the default set; add or remove according to the mission lens.
- PIR-1 - Route & access viability: Is the primary route and its alternatives viable for the planned movement (principal / team / materiel), considering road conditions, traffic patterns, security-force presence, chokepoints, ambush-prone segments, and divert/escape options? [Answer / evidence / confidence]
- PIR-2 - Site perimeter & access control: What is the physical security posture of the site’s perimeter - fencing, gates, walls, barriers, lighting, coverage gaps, entry-control procedures, guard presence and professionalism? [ ]
- PIR-3 - Egress & emergency exit: What are the emergency egress routes from the site for vehicle and foot, and are they obstructed, monitored, or compromised? [ ]
- PIR-4 - Observation & overwatch: What natural or built positions around the site or route provide observation, fields of fire, or surveillance opportunities - and are they under the client’s control or ungoverned? [ ]
- PIR-5 - Cover, concealment & defilade: What cover and concealment exists for approaches, movement, waiting/loitering, and emergency response, and who controls it? [ ]
- PIR-6 - Communications & technical environment: What is the cellular, radio, and internet connectivity at and around the site; are there known jamming, intercept, or surveillance capabilities; and what is the power and utility resilience? [ ]
- PIR-7 - Security forces, police & local population: What are the patterns of security-force presence (type, density, competence, corruption exposure, shift changes); what is the local population’s posture toward outsiders; and what are the known protest/crime hotspots in the area? [ ]
- PIR-8 - Internal layout & key zones: What is the internal layout of the site - critical zones (meeting spaces, command, comms, medical, safe rooms), movement corridors, visual cover, and acoustic privacy? [ ]
- PIR-9 - Threat / risk factors at location: What dynamic threats (crime, protest, terrorism, conflict spillover, natural hazard) specifically affect the site, its approaches, and the operational window? [ ]
- [Add recce-specific PIRs - e.g., a specific discreet-entry route, a helicopter landing zone, a water-access point, a specific neighbour’s observation coverage, or a recent incident at the location.]
| PIR | Recce Element / Location | Answer (summary) | Confidence | Key Gap |
|---|---|---|---|---|
| PIR-1 | Route & access | [ ] | [H/M/L] | [ ] |
| PIR-2 | Perimeter & access control | [ ] | [H/M/L] | [ ] |
| PIR-3 | Egress & emergency exit | [ ] | [H/M/L] | [ ] |
| PIR-4 | Observation & overwatch | [ ] | [H/M/L] | [ ] |
| PIR-5 | Cover, concealment & defilade | [ ] | [H/M/L] | [ ] |
| PIR-6 | Comms & technical environment | [ ] | [H/M/L] | [ ] |
| PIR-7 | Security forces & local population | [ ] | [H/M/L] | [ ] |
| PIR-8 | Internal layout & key zones | [ ] | [H/M/L] | [ ] |
| PIR-9 | Threat / risk factors | [ ] | [H/M/L] | [ ] |
5. Recce Framing, Taxonomy & Methodology
The load-bearing methodology section - state the rules before any observation or assessment appears. Define, in order:
- Recce objective & operational context. What operation, movement, or decision this recce supports; the specific threat lens or risk scenario it is scoped against. State this explicitly so every observation is weighted against it.
- Recce type & method. Overt physical inspection, discreet pass/observation, remote/imagery analysis, or mixed - and the boundaries of each (vantage points, times of day, number of passes, whether interiors were accessed, what areas were unreachable). Any special techniques used (timed drives, photographic baseline, video sweep, countersurveillance observation).
- Area / route / site definition. Define the Area of Interest (AOI - the broad zone from which observations were collected) and the Area of Operations (AO / site - the specific site or route line). For routes, define start, end, primary and alternate legs. For sites, define the perimeter line and any buffer zone assessed.
- Analytic framework. The physical-intelligence lenses applied - OCOKA (Observation and fields of fire, Cover and concealment, Obstacles, Key terrain, Avenues of approach) adapted for the urban/built environment, plus any additional lenses (ASCOPE for urban areas, PMESII-PT for the environmental backdrop). State how each is tailored for the operational context.
- Observation severity scale. How findings are rated: the severity scale used in §15 (Critical / High / Moderate / Low / Informational), defined with concrete operational meaning (e.g., Critical = renders the planned operation infeasible or unacceptable risk; High = requires material mitigation or route/venue change; Moderate = requires adjustment or monitoring; Low = note; Informational = no operational impact).
- Threat / risk factors. How dynamic threats are scored at the location (L×I where applicable, or categorical severity if scoring is not the primary method).
- Coverage limitations. Access barriers (denied areas, restricted hours, weather, visibility conditions, time constraints), imagery age and resolution limits, seasonal/temporal changes not captured, and any recce signature risk that limited scope.
- Relationship to other products. This product feeds operational planning (Executive Trip Security Package / Travel Emergency & Evacuation Plan / Event Threat Assessment / site-specific security plan) and consumes country/area products ( Regional Study / Country Risk Assessment / Country-Entry Risk Assessment) for environmental baseline. Where a protective advance or hostile surveillance assessment is needed, route to the sibling product.
| Framing Element | Content |
|---|---|
| Recce objective & operational context | [The operation/decision supported; the threat/risk lens] |
| Recce type & method | [Overt / discreet / remote / mixed - with specific dates, times, passes, vantage points, interior access] |
| AOI / AO definition | [Geographic boundaries of the recce area and specific site/route] |
| Analytic framework (applied) | [OCOKA / ASCOPE / PMESII-PT adaptations, and how tailored] |
| Observation severity scale | [Critical / High / Moderate / Low / Informational - with operational definitions] |
| Threat / risk scoring method | [L×I register or categorical - state the rule] |
| Principal coverage limitations | [Access, timing, visibility, seasonal, signature constraints] |
| Relationship to other products | [Consumed products; products this feeds; sibling boundaries] |
6. Area / Location Overview
The broad environmental context of the recce area - what the neighbourhood, district, or route corridor looks like and feels like, independent of the specific site. Score the general character: urban density, land use, building typology, road network pattern, traffic density, pedestrian activity, street-level lighting, green/vegetation cover, and any distinctive features (waterways, rail lines, elevation). This sets the stage for every site-specific observation below and is consumed from the AOI sweep, not from the Country/Regional Study - though it cross-references it.
| Feature | Observation | Operational Relevance | Source Grade |
|---|---|---|---|
| Urban density & land use | [ ] | [ ] | [A–F/1–6] |
| Building typology (heights, materials, setbacks) | [ ] | [Cover, observation, concealment] | [ ] |
| Road network pattern & traffic | [ ] | [Route viability, chokepoints, divert options] | [ ] |
| Pedestrian & street-level activity patterns | [ ] | [Overt/covert movement, signature] | [ ] |
| Lighting & visibility (day/night) | [ ] | [Observation, surveillance, OPSEC] | [ ] |
| Vegetation / green cover (seasonal) | [ ] | [Cover, concealment, seasonal change] | [ ] |
| Distinctive features (water, rail, elevation changes) | [ ] | [Movement barriers, OCOKA obstacles/key terrain] | [ ] |
Area overview assessment: [Synthesis - the dominant environmental character, the single feature most affecting the operational plan, and any area-level risk factors (e.g., high-crime zone, known protest area, contested neighbourhood boundary) that affect all observations below.]
7. Route & Movement Analysis
For recce covering a route or routes - the primary and alternate movement corridors from the point of origin to the site/venue and back, including any planned intermediate destinations. Assess each leg for: road surface and condition; lane width and shoulders; traffic patterns (peak/off-peak, known congestion points); chokepoints (bridges, tunnels, roundabouts, checkpoints, narrow streets, market areas); security-force presence (fixed posts, patrols, checkpoints - type, density, and shift pattern); ambush-favourable segments (slow zones, choke points, limited cover, no divert); divert and escape-route availability; travel time (best-case, worst-case, most likely); and OCOKA route factors (observation and fields of fire along the route, cover/concealment for an approaching force, obstacles natural and man-made, key terrain along the corridor, and avenues of approach into and out of the site). Score each leg’s viability for the planned movement (FAVOURABLE / CONDITIONAL / UNFAVOURABLE) with the basis.
| Leg | From → To | Distance / Est. Time | Road & Traffic | Chokepoints | Security Posture | Ambush / Slow-Zone Assessment | Divert/Escape Options | OCOKA Route Factors Summary | Viability | Confidence | Source Grade |
|---|---|---|---|---|---|---|---|---|---|---|---|
| R1 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [FAVOURABLE / CONDITIONAL / UNFAVOURABLE] | [H/M/L] | [ ] |
| R2 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| … | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
Route & movement assessment: [Synthesis - the recommended primary and alternate route(s), the single most consequential chokepoint or ambush-favourable segment, the viability rating for each leg, and the conditions under which a route should not be used. For each leg assessed as UNFAVOURABLE, state the factor that makes it so and any mitigation that could shift it to CONDITIONAL.]
8. Site / Facility Description
The descriptive baseline of the specific site, building, or facility - its physical identity, typology, age, state of repair, and general layout from the exterior. This is the foundation for every subsequent section. Describe what the site looks like, the immediate environment around it (adjacent buildings, setbacks, parking, landscaping, sidewalks), and any notable features from the outside. This section is descriptive only - assessments of security, vulnerability, and threat appear in the sections that follow.
| Feature | Observation | Source Grade |
|---|---|---|
| Site type & typology | [ ] | [A–F/1–6] |
| Building height, footprint, materials, architectural style | [ ] | [ ] |
| Age / state of repair / visible construction or renovation | [ ] | [ ] |
| Setbacks (front, rear, sides) and immediate surrounds | [ ] | [ ] |
| Adjacent buildings and land use (what overlooks the site) | [ ] | [ ] |
| Landscaping, parking, and external features | [ ] | [ ] |
| Street frontage, sidewalks, and public-access areas | [ ] | [ ] |
| Notable visual features (signage, flags, markings, condition) | [ ] | [ ] |
Site description assessment: [Synthesis - the site’s physical character at a glance, the single exterior feature that most affects access/security, and any discrepancy from prior imagery or plans.]
9. Perimeter, Access & Egress Points
Detailed assessment of the site’s physical security boundary and all points of entry and exit - the primary threat surface for most recce products. Inventory every perimeter element and every access/egress point (main gate, vehicle entrance, pedestrian doors, service/loading doors, emergency exits, rooftop/balcony access, basement/service tunnel, adjacent-building connections). For each, describe the physical barrier (fence type/height, wall material/height, gate type/operation), access control (lock, card reader, guard, intercom, biometric, keypad - and visible bypass vulnerabilities), surveillance coverage (CCTV type, coverage arcs, recording posture, sight-blocked zones), lighting (type, coverage, dark zones), and the defender’s vantage of the point from the interior. Score each point’s vulnerability to: forced entry; covert/unobserved approach; social-engineering/impersonation entry; and denial/blocking of egress. Identify observation posts overlooking each point.
| Point # | Type | Location / Side | Physical Barrier | Access Control Method | Surveillance Coverage | Lighting | Vulnerability Scores (1–5 each aspect) | Overwatch / Observation From | Severity of Weakness | Confidence | Source Grade |
|---|---|---|---|---|---|---|---|---|---|---|---|
| A1 | [Main gate / Vehicle entrance / Pedestrian door / Service door / Emergency exit / Rooftop / Tunnel] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [Crit/High/Mod/Low/Info] | [H/M/L] | [ ] |
| A2 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| … | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
Vulnerability scores: Forced entry (1–5) · Covert/unobserved approach (1–5) · Social-engineering/impersonation entry (1–5) · Denial/blocking of egress (1–5).
Perimeter & access assessment: [Synthesis - the overall perimeter security posture (MATURE / ADEQUATE / BASIC / MINIMAL / NONE) against the stated threat lens; the single most vulnerable access point and why; whether egress is as well protected as ingress; and the most consequential observation position overlooking the perimeter.]
10. Internal Layout & Key Zones
Where interior access was achieved (by permission, as a guest, or via imaging/plans), describe the internal layout: room / zone inventory, movement corridors, stairwells, elevators, safe rooms / secure areas, communications rooms, utilities (power, water, HVAC, fuel), medical spaces, and any areas of restricted access within the site. For each key zone, assess visual and acoustic privacy, line-of-sight between zones, cover/concealment within the interior, and emergency egress paths. If interior access was not achieved, state this and what the gap means for the assessment (e.g., internal layout assessed from floorplan imagery, plans, or open-source only - LOW confidence).
| Zone # | Zone Type | Floor / Location | Access | Visual Privacy | Acoustic Privacy | Communication (cellular/radio inside) | Emergency Egress | Observations / Notes | Confidence | Source Grade |
|---|---|---|---|---|---|---|---|---|---|---|
| I1 | [ ] | [ ] | [Open / Restricted / Denied] | [ ] | [ ] | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| I2 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| … | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
Internal layout assessment: [Synthesis - the layout’s overall suitability for the planned operation; the most operationally consequential zone; the principal internal vulnerability (e.g., a single egress, a visually exposed meeting room, a dead zone for comms); and the coverage gap if interior was not accessed.]
11. Observation, Cover & Concealment
The OCOKA Observation and Cover/Concealment assessment - the core tactical-intelligence analysis of who can see and who can hide at and around the site. Inventory every vantage point (natural, built, rooftop, window, vehicle, park, elevation) from which the site, its perimeter, its access points, and its approaches can be observed - positively (for the client’s security team) and negatively (for a hostile actor). Mark each position’s visibility of specific points, distance, whether it is public/private/restricted, and whether the client controls it. Then assess cover and concealment on the approaches to the site and on the site itself - what provides visual screening, defilade, and hiding positions for people and vehicles. Map these onto the threat lens: is the client’s approach covertly observable? Are there concealed approach routes for a hostile actor? Can a surveillance post be established unobtrusively?
| Position # | Type | Location / Description | Vantage of What Site Points | Distance | Public / Private / Restricted | Client-Controlled? | Exploitability for Hostile Observer | Cover / Concealment Quality for Observer | Severity | Confidence | Source Grade |
|---|---|---|---|---|---|---|---|---|---|---|---|
| O1 | [Rooftop / Window / Balcony / Park / Vehicle / Elevated ground / etc.] | [ ] | [ ] | [ ] | [ ] | [Y/N/Unknown] | [ ] | [ ] | [Crit/High/Mod/Low/Info] | [H/M/L] | [ ] |
| O2 | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| … | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
Cover & concealment approach assessment (approaches to the site):
| Approach Direction / Route | Cover/Concealment for Approaching Person | Cover/Concealment for Approaching Vehicle | Overlooked From (which O positions) | Client’s Ability to Observe the Approach | Assessment | Confidence |
|---|---|---|---|---|---|---|
| [ ] | [ ] | [ ] | [ ] | [ ] | [ ] | [H/M/L] |
Observation & cover assessment: [Synthesis - the principal observation/overwatch threat to the site; whether the client can control or deny the dominant vantage points; whether there exist concealed approach routes for a hostile actor; and the single most consequential observation/cover finding for the operational plan.]
12. Communications & Technical Environment
The technical and communications environment at and around the site - what the recce observed or assessed about telecommunications, radio spectrum, internet connectivity, power resilience, and any technical surveillance or countermeasure capabilities. This is an observational assessment based on physical inspection, local knowledge, and open-source technical data; it is not a technical penetration test or RF survey. Identify cellular coverage (carriers, signal strength, 4G/5G availability at key zones), Wi-Fi availability and visible networks, landline connectivity, VHF/UHF radio environment where relevant, GPS/GNSS reception quality (especially inside buildings and in urban canyons), backup power (generators, UPS, visible fuel), and any signs of technical surveillance, jamming, or monitoring equipment. Assess resilience: can the site operate without mains power or cellular for [X] hours?
| Element | Observation | Operational Relevance | Confidence | Source Grade |
|---|---|---|---|---|
| Cellular coverage (carriers, signal, 4G/5G) | [ ] | [Primary comms / backup / dead zones] | [H/M/L] | [ ] |
| Wi-Fi / visible networks | [ ] | [Connectivity / SIGINT exposure] | [H/M/L] | [ ] |
| Landline / fixed connectivity | [ ] | [Alternative comms] | [H/M/L] | [ ] |
| VHF/UHF radio environment | [ ] | [If relevant to operation] | [H/M/L] | [ ] |
| GPS/GNSS reception | [ ] | [Tracking / timing / dead-reckoning] | [H/M/L] | [ ] |
| Backup power (generator/UPS/visible fuel) | [ ] | [Operational endurance] | [H/M/L] | [ ] |
| Signs of technical surveillance / jamming equipment | [ ] | [Hostile technical capability] | [H/M/L] | [ ] |
| Mains power reliability (known outages / brownouts) | [ ] | [Contingency planning] | [H/M/L] | [ ] |
Communications & technical assessment: [Synthesis - the comms environment’s overall adequacy for the planned operation; the critical coverage dead zone (if any); whether backup power is sufficient for the mission window; and any indicators of hostile technical capability at or near the site.]
13. Security Forces, Personnel & Local Population Patterns
The human security environment at and around the site - the visible security-force presence, their posture and professionalism, their shift patterns and observable procedures, and the local population’s relationship to the site. This section is observational and based on the recce pass(es); it is not a substitute for a dedicated threat-actor analysis. Describe: type and density of uniformed security (private guards, police, military, traffic police, neighbourhood watch); fixed posts vs. roving patrols; identification and vehicle-check procedures at checkpoints; response posture (visible weapons, communications equipment, vehicle type); professionalism and alertness observed; shift-change timing (observable pattern); local population density, activity patterns, and apparent attitude toward the site and its occupants (friendly, indifferent, hostile, extractive); known protest, crime, or disorder hotspots within the recce area; and the accessibility and reliability of local emergency services (police, ambulance, fire).
| Security Force Element | Observation | Location / Pattern | Operational Relevance | Confidence | Source Grade |
|---|---|---|---|---|---|
| Private security (guard type, density, shift, posture) | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| Police presence (type, density, patrol pattern) | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| Military / other government security | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| Checkpoints / vehicle inspection (procedures, rigour) | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| Security-force professionalism & alertness | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| Shift-change pattern (observable) | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| Population Element | Observation | Location / Pattern | Operational Relevance | Confidence | Source Grade |
|---|---|---|---|---|---|
| Local population density & activity pattern | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| Apparent attitude toward site / outsiders | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| Known protest / crime / disorder hotspots in AOI | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| Emergency services (accessibility, reliability) | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
Security forces & population assessment: [Synthesis - the overall security-force environment (supportive / neutral / unhelpful / hostile) for the planned operation; whether any security-force element is a threat actor in its own right (corrupt, arbitrary, aligned with a hostile party); the density and coverage of checkpoints affecting movement; and the local population’s likely behaviour during an operation or incident.]
14. Threat / Risk Factors at the Recce Location
Dynamic threat and risk factors specific to the recce location and its immediate surroundings - not a repeat of the broader Country Risk Assessment but the local expression of those threats at this street, neighbourhood, or site. Score each threat for its likelihood and impact at this location during the operational window, using the L×I register where applicable or a categorical severity scale. Include: crime (violent, acquisitive, carjack, express kidnap in the immediate area); terrorism / extremist activity (recent incidents, known cells, target profiles that match this site type); civil unrest / protest / disorder (history, current tensions, known flashpoints within walking distance); conflict spillover / crossfire risk (if near a contested zone or border); natural hazard / seasonal risk (flooding, landslide, extreme heat, storm - affecting access, egress, or site integrity); and health / CBRN / environmental hazard (industrial sites, waste, air quality, disease outbreak). Where a risk is already scored in the Country Risk Assessment or Operational Risk Assessment, cite it and localise it rather than re-deriving.
| Risk Factor | Local Expression at Site / AOI | Likelihood (1–5) | Impact (1–5) | Inherent (L×I) | Existing Mitigation (site-level) | Residual (L×I) | Band | Trend | Confidence | Source Grade |
|---|---|---|---|---|---|---|---|---|---|---|
| Crime (violent/acquisitive in immediate area) | [ ] | [1–5] | [1–5] | [ ] | [ ] | [ ] | [Low/Mod/Elev/High/Crit] | [↑/→/↓] | [H/M/L] | [ ] |
| Terrorism / extremist activity (local targeting) | [ ] | [1–5] | [1–5] | [ ] | [ ] | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| Civil unrest / protest / disorder (proximity to flashpoints) | [ ] | [1–5] | [1–5] | [ ] | [ ] | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| Conflict spillover / crossfire (if near contested zone) | [ ] | [1–5] | [1–5] | [ ] | [ ] | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| Natural hazard / seasonal (flood/storm/heat affecting access) | [ ] | [1–5] | [1–5] | [ ] | [ ] | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| Health / environmental hazard (industrial/CBRN/disease) | [ ] | [1–5] | [1–5] | [ ] | [ ] | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| [Add location-specific risk factor] | [ ] | [1–5] | [1–5] | [ ] | [ ] | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
Location risk assessment: [Synthesis - the dominant local risk factor; whether any scored threat rises to a level that would change the operational plan; and the trend across the operational window. Cross-reference the consumed Country Risk Assessment and Operational Risk Assessment where they provide the baseline.]
15. Consolidated Findings Register & Severity Matrix
Aggregate every significant observation from §6–§14 into one ranked register, ordered by severity (Critical → High → Moderate → Low → Informational) and then by operational significance, so the client sees the whole physical-intelligence picture in a single table. Include the finding, the section it comes from, the location/point, the severity rating with basis, and the operational implication.
| Rank | Finding | § | Location / Point | Severity | Severity Basis | Operational Implication | Confidence | Source Grade |
|---|---|---|---|---|---|---|---|---|
| 1 | [ ] | [§] | [ ] | [Crit/High/Mod/Low/Info] | [ ] | [ ] | [H/M/L] | [ ] |
| 2 | [ ] | [§] | [ ] | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| 3 | [ ] | [§] | [ ] | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
| … | [ ] | [§] | [ ] | [ ] | [ ] | [ ] | [H/M/L] | [ ] |
Severity definitions: Critical - renders the planned operation infeasible or unacceptable risk at the site/route as assessed; requires a materially different approach, alternate site/route, or cancellation. High - a significant vulnerability or threat that requires material mitigation or route/venue change; operationally actionable. Moderate - a notable observation that requires adjustment, monitoring, or inclusion in the security plan. Low - a relevant observation with minor or no material impact on the plan. Informational - descriptive baseline; no direct operational impact.
Register note: [The number and distribution of findings across severity levels; the single Critical observation (if any); the pattern of findings that, taken together, form a composite assessment of the site/route.]
16. Key Findings Summary
Consolidated register of the load-bearing findings behind the assessment, each graded by evidentiary status (Verified / Assessed / Contested / Unresolved) and confidence, so the reader can see what is directly observed vs. inferred vs. uncertain. Materiality flags the findings that most affect the operational plan.
| # | Finding | Status | Confidence | Materiality |
|---|---|---|---|---|
| 1 | [ ] | [Verified / Assessed / Contested / Unresolved] | [H/M/L] | [ ] |
17. Red Flag / Notable Observations
Any observation that warrants immediate attention outside the normal severity ranking - an immediate safety warning (e.g., live ordnance, structural collapse risk, toxic material visible), a direct indicator of hostile activity (e.g., fresh signs of forced entry, unattended suspicious item, person observed photographing the perimeter from a concealed position during the recce), a legal/crime-in-progress observation (e.g., open drug market at the access point, illegal checkpoint, human trafficking indicator), or a data-protection/privacy issue (e.g., exposed personal data visible from the public vantage). Each flag carries a type, severity, and the disposition taken or recommended. These are exceptions, not routine observations.
| # | Flag / Observation | Type | Location | Severity | Evidentiary Basis | Disposition | Status |
|---|---|---|---|---|---|---|---|
| 1 | [ ] | [Safety / Hostile activity / Legal / Data-privacy / Other] | [ ] | [Crit/High/Mod] | [ ] | [ ] | [Open / Closed / Referred] |
18. Analysis of Competing Hypotheses (ACH)
Apply to the central recce question - typically whether the site is operationally viable as planned vs. needs a material change, or whether a specific physical observation (e.g., a security-force pattern, an overwatch position, a locked gate) is normal or indicates hostile intent or preparation. State the competing hypotheses, array the diagnostic evidence for/against each, and identify the most consistent explanation and what evidence would overturn it. Use ACH to discipline the assessment against both alarmism and complacency; do not pad the apparatus where the evidence is one-sided - say so and close.
| Evidence / Indicator | H1: [Site/route viable as planned] | H2: [Site/route requires material change] | H3: [Observation X indicates hostile intent/preparation] |
|---|---|---|---|
| [ ] | [C/I/N] | [C/I/N] | [C/I/N] |
(C = consistent · I = inconsistent · N = neutral.) Most consistent hypothesis: [ ] - [rationale + the diagnostic evidence that would overturn it].
19. Key Assumptions Check (KAC)
The assumptions underpinning the recce’s findings and operational judgments - about the stability of the physical environment (no construction/renovation/seasonal change before the operational date), the accuracy and currency of baseline imagery/maps, the representativeness of the recce pass(es) (single observation vs. pattern), the non-hostile intent of observed activity, the existence or absence of features that could not be verified (interior layout, underground structures, off-hours security posture), and the continued absence of a disclosed threat. Each with its basis, confidence, and the impact on the operational plan if it proves wrong. Linchpin assumptions (those that, if wrong, would change the operational recommendation) are flagged.
| # | Assumption | Basis | Confidence | Impact if Wrong | Linchpin? |
|---|---|---|---|---|---|
| 1 | [e.g., The physical environment observed on the recce date is representative of conditions on the operational date] | [ ] | [H/M/L] | [ ] | [Y/N] |
| 2 | [e.g., The itinerary/operational plan provided as context for the recce is complete and current] | [ ] | [ ] | [ ] | [ ] |
| 3 | [e.g., Interior layout assessed from floorplan/exterior clues is accurate; no significant undisclosed interior features exist] | [ ] | [ ] | [ ] | [ ] |
| 4 | [e.g., No hostile activity has been triggered by the recce itself (the recce was not detected or was not attributed to the client)] | [ ] | [ ] | [ ] | [ ] |
| 5 | [e.g., Security posture observed is routine and not heightened for the recce period] | [ ] | [ ] | [ ] | [ ] |
20. Collection Gaps & RFIs
Where coverage is thin, contested, or entirely absent, the impact on the operational assessment, the collection that would close the gap, and where to escalate. Recce gaps are typically: an area or vantage point that could not be accessed; a route leg not driven; an interior not entered; a time-of-day or day-of-week not sampled; a seasonal or weather condition not captured; a security-force shift change not confirmed; or a specific threat-actor or local-population question that requires HUMINT or a deeper product.
| Gap | § / Location | Impact on Assessment | Recommended Collection | Escalation Target | Priority |
|---|---|---|---|---|---|
| [ ] | [ ] | [ ] | [ ] | [Additional recce pass / Interior-access recce / Night recce / Weekend recce / Seasonal re-rece / Imagery update / HUMINT collection / Country Risk / Operational Risk / Threat-actor assessment / Protective Advance Survey / Hostile Surveillance Vulnerability Assessment] | [H/M/L] |
21. Recommendations
21.1 Operational Assessment
Overall assessment of the site/route against the stated recce objective and operational context - the dominant physical-intelligence findings, the feasibility of the planned operation from a physical-environment perspective, and the most consequential vulnerabilities or risks. State the overall viability determination (VIABLE / CONDITIONAL / NOT VIABLE) and the principal conditions. Be explicit about the coverage gaps and the assumptions that bound the assessment.
[ASSESSMENT]
21.2 Recommendations
- For operational planners / decision-makers: [The viability determination and the physical-environment factors that most support or constrain the plan; the site/route/access recommendations that flow from the observations.]
- For the security / protective team: [The priority vulnerabilities to treat (perimeter gaps, overwatch positions, egress bottlenecks, route chokepoints), the recommended mitigation direction (not the security plan itself - route to the appropriate operational product), and the indicators to monitor for change before the operational date.]
- For recce re-run / gap closure: [Which collection gaps (§20) are material enough to warrant a follow-on recce, and under what conditions (different time of day, interior access, seasonal revisit, different route).]
- For analysts (next intelligence steps): [Which findings warrant a deeper product (Protective Advance Survey, Hostile Surveillance Vulnerability Assessment, Event Threat Assessment, Facility Threat Assessment, Country Risk update) and which indicators should be tracked for change before the operational window.]
- Escalations / downstream products: [Items routed to the Protective Advance Survey & Recce Report, Hostile Surveillance Vulnerability Assessment, Executive Trip Security Package, Travel Emergency & Evacuation Plan, Event & Venue Threat Assessment, Operational Mapping & Advance Support, country/area products (Country Risk Assessment / Country-Entry Risk Assessment).]
- Conditions for reliance / refresh: [The perishability window and the events or indicators that should trigger a re-rece before the operation.]
22. Annex A - Sources & Methodology
*Collection methods and scope; the recce type (overt / discreet / remote / mixed) with dates, times, number of passes, vantage points, and any interior access; the source register graded with the Admiralty two-axis code; the reference scales (below); statement of the likelihood-vs-confidence separation; the OCOKA framework applied and its tailoring; the severity scale used; the threat/risk scoring method; coverage and currency limitations; confirmation that all collection was lawful (no trespass, no privacy intrusion, no surveillance of individuals, all photography from public/permitted vantage points); and the treatment of any local official, media, or third-party sources.
Source reliability (Admiralty, A–F): A Completely reliable · B Usually reliable · C Fairly reliable · D Not usually reliable · E Unreliable · F Reliability cannot be judged.
Information credibility (Admiralty, 1–6): 1 Confirmed by other sources · 2 Probably true · 3 Possibly true · 4 Doubtful · 5 Improbable · 6 Truth cannot be judged. (Each sourced datum carries a two-character grade, e.g., B2.)
Estimative probability / likelihood (ICD 203): almost no chance / remote (01–05%) · very unlikely (05–20%) · unlikely (20–45%) · roughly even chance (45–55%) · likely (55–80%) · very likely (80–95%) · almost certain (95–99%).
Analytic confidence (evidence base - kept separate from likelihood): HIGH (multiple independent reliable sources, primary documentation, no significant contradiction) · MODERATE (some corroboration, gaps, minor unresolved inconsistency) · LOW (single/uncorroborated source, significant gaps, plausible alternatives open). Never combine a likelihood term and a confidence level in the same sentence.
Risk scoring (where used): Likelihood (1–5) × Impact (1–5) = 1–25; band key: 1–5 Low · 6–10 Moderate · 11–15 Elevated · 16–20 High · 21–25 Critical.
Observation severity scale (used throughout this product): Critical - renders the planned operation infeasible or unacceptable risk at the site/route as assessed; requires a materially different approach, alternate site/route, or cancellation. High - a significant vulnerability or threat that requires material mitigation or route/venue change; operationally actionable. Moderate - a notable observation that requires adjustment, monitoring, or inclusion in the security plan. Low - a relevant observation with minor or no material impact on the plan. Informational - descriptive baseline; no direct operational impact.
Coverage confidence (product-level): HIGH (full physical access to all relevant zones and routes, multiple passes at relevant times, current imagery, no significant access barriers) · MODERATE (adequate coverage with gaps - some areas not accessed, single pass only, imagery partially dated) · LOW (significant access/currency barriers, interior not accessed, limited passes, heavy reliance on remote sources only).
OCOKA framework (adapted for urban/built environment): Observation and fields of fire - vantages overlooking the site/route from which observation, surveillance, or fire could be directed. Cover and concealment - physical screening and hiding positions for people and vehicles on approaches and at the site. Obstacles - natural and man-made barriers to movement (walls, fences, water, rail, terrain, construction, traffic). Key terrain - any location whose control gives a decisive advantage to either the client or a hostile actor. Avenues of approach - all routes into and out of the site, and their viability for the planned movement. Applied with the operational context as the lens - OCOKA is assessed against the specific threat and movement scenario, not as abstract terrain analysis.
Searched sources (record source type, provider/title, as-of date, coverage scope, limitations, and any self-interest/reliability caveat): [TABLE]
23. Annex B - Appendices
- Appendix A - Recce Plan & Execution Log: the recce objective, team composition, dates/times, route driven, vantage points occupied, interior-access log, weather conditions, and any incidents or deviations from plan.
- Appendix B - Photographic & Video Baseline: key-frame stills and video clips indexed to observation points and findings - handled as operationally sensitive.
- Appendix C - Route Analysis & Profiles: detailed per-leg OCOKA and viability assessments (§7), with route maps, chokepoint diagrams, and divert-route overlays (where produced).
- Appendix D - Perimeter & Access Point Register: the full §9 inventory with photographs, vulnerability scores, and overwatch mapping.
- Appendix E - Observation / Overwatch Position Register: full §11 inventory with photographs, distances, and visibility arcs.
- Appendix F - Internal Layout Diagrams: floorplan sketches or annotated imagery (where interior access or plans obtained), with zone markings and egress paths.
- Appendix G - Communications Survey Log: signal-strength measurements, visible-network logs, and power-backup observation details (where recorded).
- Appendix H - Security Forces & Local Population Observation Log: timestamped observations of guard rotations, police patrols, checkpoint activity, and local population behaviour.
- Appendix I - Consolidated Findings Register: the full §15 register with all findings, severity ratings, and operational implications.
- Appendix J - Map Overlays & Geospatial Data: AOI/AO boundaries, route traces, observation arcs, perimeter line, chokepoints, and key terrain markers - in geospatial format where produced.
- Appendix K - Full Source Register: every source, Admiralty grade, access date, reference, and any coverage/limitation note.
- Appendix L - Glossary & Abbreviations.
- Appendix M - Revision History.
END OF REPORT.
Verification disclaimer: This Reconnaissance / Recce Report is a point-in-time, site-/route-scoped physical-intelligence assessment based on open, licensed, and lawfully accessed sources current as of the recce date(s). It is not a security plan, a protective-operations plan, a facility vulnerability assessment meeting any regulatory or insurance standard, a structural or safety engineering survey, or a surveillance-detection product. Observations and judgments are the firm’s independent, structured analytic assessments calibrated to the stated scales - a time-bound snapshot of the physical environment as observed, not a guarantee of its current or future state. Physical recce was conducted from public and permitted vantage points only; no entry onto private property without authorisation, no intrusion into any expectation of privacy, and no surveillance of individuals without lawful basis. No classified, unlawfully obtained, or out-of-licence material was used. Operational decisions based on this report require integration with the client’s own security, legal, and operational teams. The physical environment is perishable - re-commission the recce if the operational date is materially later than the recce date or if a significant environmental change is known.
Document control footer: [REF-YYYY-### · Version · Classification/TLP · Prepared/Reviewed/Approved · Distribution].
Model wiring
Generated from cell frontmatter at publish time.