ROUTE ANALYSIS
[ROUTE NAME / SEGMENTS - ENGAGEMENT REF]
The ROUTE ANALYSIS is the standard transit corridor assessment between primary and secondary locations, identifying choke points, bottlenecks, and safe havens. This is a template-driven, repeatable report skeleton. All engagement-specific, venue-specific, or principal-specific values must be recorded as bracketed placeholders (e.g. [VENUE], [YYYY-MM-DD]). Do not assert fictional findings or invent data.
Document Control
| Field | Value |
|---|---|
| Report Reference | [REF-YYYY-###] |
| Date of Report | [YYYY-MM-DD] |
| Reporting Period / As-Of Date | [YYYY-MM-DD] |
| Classification / Handling | [internal / CONFIDENTIAL - CLIENT EYES ONLY] |
| Client | [CLIENT NAME] |
| Requesting Party | [REQUESTER NAME / ID] |
| Prepared By | [ANALYST NAME / ID] |
| Reviewed By | [REVIEWER NAME / ID] |
| Approving Officer | [APPROVER NAME / ID] |
| Version | [0.1.0] |
| Distribution | [NAMED RECIPIENTS] |
Handling & Legal Caveat
Handling: [internal / CONFIDENTIAL]. Disseminate only to authorized recipients. May contain personal data on principals or security staff: store and transmit per data-processing agreement.
Nature of this product: This is a physical security reporting template. It does not deliver legal advice or guarantee prevention of incidents.
Sourcing & verification: Findings derive from physical inspection, local reconnaissance, and open-source intelligence current as of the report date and are graded per Annex A.
Subject / Engagement Snapshot
| Field | Value |
|---|---|
| Primary Route | [ ] |
| Start / End | [ ] |
| Recce Date | [ ] |
| Overall Security Grade | [Low / Moderate / Elevated / High / Critical] |
Table of Contents
- BLUF
- Executive Summary
- Key Judgments
- Priority Intelligence Requirements (PIRs)
- Physical & Tactical Findings
- Verified Findings
- Red Flags
- Analysis of Competing Hypotheses (ACH)
- Key Assumptions Check
- Gaps and RFIs
- Recommendations
- Annex A: Sources & Methodology
- Annex B: Grading Matrices
(Page numbers populate on export to PDF.)
1. BLUF
2-3 sentences. Lead with the overall suitability/safety assessment and the single most critical finding, followed by the recommended security posture. State it so a decision-maker can act on this section alone.
[BLUF]
2. Executive Summary
Triggering requirement and engagement context: what venue, route, or event is being covered, the scope of physical advance or transit analysis, and a narrative of key findings across the security dimensions, written to the ICD 203 floor.
[EXECUTIVE SUMMARY]
3. Key Judgments
Key assessments on safety, vulnerability, and threat exposure. Each judgment must separate likelihood (calibrated estimative vocabulary per ICD 203) and confidence (evidence base).
| Judgment | Likelihood | Confidence | Change Indicator |
|---|---|---|---|
| [e.g. Venue perimeter breach probability] | [almost no chance / remote / very unlikely / unlikely / roughly even chance / likely / very likely / almost certain] | [HIGH / MODERATE / LOW] | [e.g. Failure of access control equipment] |
4. Priority Intelligence Requirements (PIRs)
The collection-management spine. Tailor to the specific report type. Matrix must have exactly 4 columns: PIR, Answer, Confidence, Key Gap.
| PIR | Answer (summary) | Confidence | Key Gap |
|---|---|---|---|
| PIR-1: Are transit highway segments free of construction blockages? | [ ] | [H/M/L] | [ ] |
| PIR-2: Are there alternative routes around identified traffic choke points? | [ ] | [H/M/L] | [ ] |
| PIR-3: Are medical safe havens within a 10-minute drive of all segments? | [ ] | [H/M/L] | [ ] |
5. Physical & Tactical Findings
Instructional tradecraft: Analyze the physical transit corridor geography, routing logic, timing exposure, medical waypoints, and pre-movement dry-run requirements. All values are placeholders.
5.1 Route Legs & Selection Rationale
Instructional tradecraft: Define the primary, alternate, and emergency route legs. Detail the specific segments, distances, Estimated Travel Times (ETT), and the security/operational rationale for selection.
| Leg Type | Segment Description / Bypasses | Distance / ETT | Selection Rationale |
|---|---|---|---|
| Primary Leg | [Start Location] to [End Location] via [Segment/Highway Name] | [N] km / [N] min | Direct route minimizing transit time; high-density multi-lane highway offering multiple lane-change bypass options |
| Alternate Leg | [Start Location] to [End Location] via [Surface Street / Arterial Name] | [N] km / [N] min | Avoids primary highway chokepoints; utilized during primary route blockage or elevated threat posture |
| Emergency Leg | [Start Location] to [Emergency Safe Haven / Hospital] via [Segment Name] | [N] km / [N] min | Direct link to Level 1 trauma center; selected under active attack or medical emergency |
5.2 Chokepoint & Vulnerability Analysis
Instructional tradecraft: Detail specific physical vulnerabilities along each leg that restrict movement or eliminate egress routes. Identify single points of failure.
- Overpasses and Tunnels:
- Location A: [Tunnel Name at Segment Coordinate] | Vulnerability: Complete lateral constraint; zero GPS/cellular signal propagation.
- Location B: [Overpass at Segment Coordinate] | Vulnerability: Vulnerable to dropped-object hazards or elevated monitoring.
- Forced-Stop and Funnel Points:
- Location C: [Toll Plaza / Merge Lane at Segment Coordinate] | Vulnerability: Lane constriction from [N] lanes down to [N] lanes, forcing convoy deceleration to [N] km/h.
- Location D: [Predictable Stop Sign / Signal at Segment Coordinate] | Vulnerability: Predictable stopping point adjacent to blind corners.
- Predictable Slow Points:
- Location E: [Freight Corridor / Rail Crossing at Segment Coordinate] | Vulnerability: Predictable freight delays up to [N] minutes; grade crossing single point of failure.
- Single Points of Failure:
- Location F: [Bridge Span at Segment Coordinate] | Vulnerability: No adjacent surface street bypasses within [N] kilometers; structural blockage traps convoy on bridge.
5.3 Predictive Attack-Site Analysis
Instructional tradecraft: Estimate the locations along the route where a hostile action is statistically most likely or would achieve maximum consequence. Provide tactical reasoning.
- Highest Likelihood Attack Location: [e.g. Interstate off-ramp junction at Segment Coordinate]
- Tactical Reasoning: Convoy speed must decelerate to under [N] km/h; curvature of ramp blocks forward line of sight; lateral guardrails prevent off-road exfiltration.
- Highest Consequence Attack Location: [e.g. Underpass tunnel at Segment Coordinate]
- Tactical Reasoning: Enclosed structure limits thermal/visual signature; blocks radio comms with C2 Post; prevents air medical evacuation; ensures total containment of detail vehicles.
5.4 Timing & Exposure Windows
Instructional tradecraft: Define the timing variables that affect transit vulnerability. Document the time-of-day exposure profile.
- Rush-Hour Vulnerability Windows: Peak traffic congestion occurs between [HH:MM-HH:MM] and [HH:MM-HH:MM] daily. ETT increases by [N]% during these windows.
- Signal Timing and Coordination: Traffic signals along [Arterial Name] are [adaptive / fixed]. Fixed signal cycle is [N] seconds; convoy stopping probability is [N]% without emergency preemption.
- Time-of-Day Exposure Profile: Transit during low-light hours [HH:MM-HH:MM] increases visual acquisition difficulty for drivers and limits covert scout spotting capabilities.
5.5 Medical Waypoints & Safe Havens
Instructional tradecraft: Register all verified safe locations and medical treatment facilities along the transit corridor.
| Route Leg | Safe Haven / Facility Name | Type (Precinct / Hospital / Govt) | Coordinates / Mile Marker | Drive Time (ETT) | Medical Capability / Trauma Level |
|---|---|---|---|---|---|
| Primary | [e.g. Municipal Police Precinct 4] | Precinct | [COORDINATES / MM] | [N] min | Secure holding area, no medical |
| Primary | [e.g. University Trauma Center] | Hospital | [COORDINATES / MM] | [N] min | Level 1 Trauma Center, Burn Unit |
| Alternate | [e.g. Federal Courthouse] | Govt | [COORDINATES / MM] | [N] min | Armed security presence, secure garage |
| Alternate | [e.g. Community Medical Center] | Hospital | [COORDINATES / MM] | [N] min | General Emergency Room, Level 3 Trauma |
5.6 Actions-On Drill Reference Protocols
Instructional tradecraft: Cross-reference tactical reaction plans for emergency contingencies. Do not duplicate the full EAP.
- Vehicle Breakdown Drill:
- Trigger: Mechanical failure or disablement of a detail vehicle.
- Protocol: Execute immediate principal transfer to the backup vehicle within [N] seconds per [EP-004] (Motorcade Movement Plan) Section [N]. Lead vehicle blocks threat lane.
- EAP Link: For security-related breakdowns, hand off to [EP-012] (Emergency Action Plan) Section [N] (Vehicle Ambush / Disablement).
- Route Blockage Drill:
- Trigger: Visual verification of road blockade, demonstration, or major accident.
- Protocol: Execute immediate vehicle U-turn or reverse out of the segment within [N] seconds per [EP-004] Section [N], redirecting the convoy to the pre-planned Alternate Leg (Section 5.1).
- EAP Link: Acknowledge blockage to C2 via Detail Net and hand off to [EP-012] Section [N].
- Convoy Ambush Drill:
- Trigger: Active gunfire, explosive device activation, or forced vehicular stop by hostile forces.
- Protocol: Maintain vehicle movement; drive through the contact zone utilizing vehicle weight to ram obstructions if required.
- EAP Link: Immediately activate digital duress per EP-011 and hand off detail control to [EP-012] Section [N] (Active Assailant drill).
5.7 Pre-Movement Reconnaissance & Dry-Run Protocol
Instructional tradecraft: Establish the mandatory pre-movement timing run and road condition checks.
- Recon Timing: The timing run must be conducted within [N] hours of detail kickoff (nominally at T-24h) by the Lead Driver.
- Verification Checklist:
- Surface Check: Inspect road surface for new potholes, debris, or traction hazards along primary and alternate legs.
- Timing Verification: Record actual ETT at the planned departure time window to calibrate route timing logs.
- Construction Audit: Physically verify that no new temporary work zones or lane closures have been established.
- Safe Haven Check: Visually confirm that safe haven ingress gates and police station access routes are clear and unobstructed.
- Radio Propagation Check: Conduct comms check on Command and Detail Nets at all tunnel entrance and chokepoint locations to confirm signal coverage.
6. Verified Findings
A register of verified findings. Status must be chosen from the allowed vocabulary. Confidence and Materiality must be stated.
| # | Finding | Status | Confidence | Materiality |
|---|---|---|---|---|
| 1 | [e.g. Safe room structural layout verification] | [Verified / Unverified / Contradicted] | [H/M/L] | [L/M/H] |
7. Red Flags
Red Flags or notable risk indicators observed. Severity must map to the defined terms: Critical (disqualifying), High (requires EDD/conditions), Medium, Low.
| # | Red Flag | Severity | Basis | Disposition |
|---|---|---|---|---|
| 1 | [e.g. Blocked exit door in north corridor] | [Crit / High / Med / Low] | [Physical inspection] | [Open / Mitigated] |
8. Analysis of Competing Hypotheses (ACH)
ACH on the central threat or vulnerability judgment. Document evidence for and against each hypothesis.
| Hypothesis | Consistent Evidence | Inconsistent Evidence | Assessment |
|---|---|---|---|
| [Hypothesis, e.g. Access breach occurs via service door] | [Evidence] | [Evidence] | [Assessment] |
9. Key Assumptions Check
Key assumptions that, if wrong, would flip the recommendation. List the assumption, its basis, and the impact if false.
- [Key Assumption, e.g. Local emergency service response remains under 10 minutes] (risk if false: [risk])
10. Gaps and RFIs
Collection gaps and Request for Information (RFIs). Identify missing information and the impact on the assessment.
- [Gap / RFI, e.g. Local utility access key layout is missing] (impact: [impact], priority: [H/M/L])
11. Recommendations
Translate the assessment into concrete recommendations for the stakeholder groups (e.g. TL, Detail Leader, drivers).
- [Recommendation] (owner: [owner])
Annex A: Sources & Methodology
Collection methods and scope. Source register must be graded with the Admiralty two-axis code. Describe where the methods are doctrine-derived.
A.1 Methodology
The Route Analysis is conducted via route reconnaissance (recce) drives, traffic patterns analysis, and satellite terrain mapping. It consumes the ART-region-package to verify regional road configurations, local traffic feeds, and emergency hospital contact details.
A.2 Source Register
| Source / Type | Admiralty Grade | Date Accessed | Relevance |
|---|---|---|---|
| [Source Description] | [A-F/1-6] | [YYYY-MM-DD] | [Description] |
Annex B: 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.
Risk scoring key: Likelihood (1-5) × Impact (1-5) = 1-25; 1-5 Low · 6-10 Moderate · 11-15 Elevated · 16-20 High · 21-25 Critical.
END OF REPORT
Model wiring
Generated from cell frontmatter at publish time.