The day-to-day management and oversight of all anti-terrorism and emergency management issues for the SC HQ facility rests with the facility's designated Anti-Terrorism Officer (ATO), who reports through the senior commander to the installation or headquarters commander. The ATO coordinates a supporting team: the security force, the emergency management coordinator, the fire and emergency services chief, and the operations directorate. Executive authority and legal accountability remain with the commanding officer, who signs the facility's anti-terrorism plan and holds final approval over force protection posture decisions.
How the Responsibility Chain Is Constructed
Anti-terrorism and emergency management at a headquarters facility are not a single job. The work splits into four functional lanes, and the person named in the question is the officer who owns one of those lanes. Doctrine across US defense and federal facilities assigns anti-terrorism program management to a designated officer at each command echelon. That officer normally reports directly to the commander, not to a mid-level security manager, so that threat information reaches decision authority without filtering.
The ATO's first mechanism is the threat and vulnerability assessment cycle. The officer convenes a working group, collects intelligence and law enforcement threat reporting, walks the physical perimeter and controlled spaces, and scores vulnerabilities against a standing matrix. The output is a prioritized list of protective measures with cost and timeline attached. The commander approves or rejects each measure. Without commander signature, no countermeasure obligation exists.
The second mechanism is the emergency management plan cycle. The emergency management coordinator maintains hazard-specific annexes for fire, severe weather, active assailant, hazardous material release, and medical mass casualty. Each annex names a primary and alternate duty officer, a notification tree, a rally point, and a decision trigger. The ATO and the coordinator crosswalk these annexes against the anti-terrorism plan so that a single event does not produce two conflicting responses.
The third mechanism is exercise and drill governance. An annual exercise schedule binds the plan to reality. Drills test communication paths, not just tactics. A failed notification tree discovered in a tabletop exercise is cheaper to fix than the same failure discovered during an actual lockout.
The fourth mechanism is the inspection and audit trail. Higher-echelon inspectors review anti-terrorism programs on a recurring cycle. Findings convert into a corrective action tracker. The ATO owns the tracker, but the commander owns the closure deadline. This is the structural reason the question points upward as well as sideways: the ATO manages, but the commander is accountable.
Quantified Context: Staffing, Cycles, and Thresholds
Facility anti-terrorism programs run on defined calendar intervals rather than continuous vigilance alone. A typical headquarters program conducts a full vulnerability assessment biennially, refreshes the threat assessment annually, runs at least one command-level tabletop exercise per year, and executes a physical security survey before any major construction project breaks ground. Emergency management adds a separate cadence: shelter-in-place drills, evacuation drills, and notification tests on intervals set by the governing regulation.
Staffing scales with facility population and mission sensitivity. A headquarters building housing several hundred personnel typically carries one full-time ATO, a deputy, and a small emergency management cell of two to four people. Larger installations push the security force, fire services, and emergency operations center into standing organizations of dozens. The ratio matters because the ATO's span of control determines how much of the assessment cycle is delegated to tenant commands.
Cost figures follow the same pattern. Physical hardening measures range from near-zero-cost procedural changes to six-figure capital projects. A bollard line at a main gate, blast-film window retrofit, or standoff distance reconfiguration each carries a distinct price band and procurement timeline. The ATO's job is to sequence these against the threat ranking rather than spread spending evenly.
Comparison of Oversight Models
Different facilities divide the same duties in different ways, and the confusion in the question usually traces to which model the facility follows.
| Oversight model | Who manages day to day | Who holds final authority | Typical facility type | Trade-off |
|---|---|---|---|---|
| Designated ATO under commander | Anti-Terrorism Officer | Commanding officer | Defense headquarters, federal campus | Clear accountability, single point of failure if ATO departs |
| Dual-hat security and emergency manager | One officer wears both portfolios | Commander or senior civilian director | Smaller headquarters, tenant-heavy buildings | Efficiency in lean staffing, thin bench during absence |
| Emergency management office separate from security | Emergency management coordinator | Director of operations | Civilian agency headquarters | Strong continuity planning, weaker threat intelligence integration |
| Contracted security with government oversight | Contractor program manager | Government contracting officer's representative | Leased commercial space | Cost flexibility, slower decision cycle on classified threat data |
| Regional or enterprise program office | Program office staff | Regional director | Multi-site organizations | Consistent standards, weaker local situational awareness |
The counterintuitive detail: the most common failure mode in headquarters anti-terrorism programs is not a weak ATO. It is an unclear delegation of authority during the ATO's absence. Programs that name a trained alternate in writing and rehearse the handoff outperform programs with a stronger primary officer but no deputy.
Edge Cases That Redistribute Responsibility
Tenant organizations break the clean chain. When a headquarters building houses multiple commands or agencies, each tenant may run its own anti-terrorism program while the host facility controls the perimeter, utilities, and emergency notification system. Responsibility then splits by geography and by function. The host owns the gate; the tenant owns its internal spaces and its personnel accountability. A memorandum of agreement should name who declares a building-wide emergency and who controls the public address system during that declaration.
Leased space adds another layer. In commercial leases, the landlord controls building systems and the government tenant controls its suite. Emergency evacuation coordination crosses that boundary, so the lease should specify notification responsibilities, exercise participation, and access for security surveys.
Remote and alternate work arrangements change headcount assumptions. Attendance data feeds the facility's mass casualty planning and shelter capacity calculations. A plan built on full occupancy misallocates resources on days when only a fraction of personnel are present.
Command transitions are a distinct edge case. During a change of command, anti-terrorism program authority passes with the command, not with the ATO. Programs that fail to brief the incoming commander on open corrective actions lose continuity at exactly the moment accountability resets.
Red-flag warnings worth watching:
An ATO position vacant for more than one assessment cycle without a written acting designation. Emergency annexes that have not been crosswalked against the anti-terrorism plan since the last reorganization. A notification tree that has never been tested outside business hours. Tenant organizations with no documented interface to the host emergency operations center. Corrective action items past their commander-approved closure date with no revalidation.
Timeline of the Annual Oversight Cycle
Responsibility for day-to-day management expresses itself as a calendar. The table below shows a representative headquarters cycle; exact dates are set by governing regulation and command policy, not by a universal standard.
| Period | Activity | Accountable party | Output |
|---|---|---|---|
| First quarter | Annual threat assessment refresh | ATO with intelligence support | Updated threat baseline for commander review |
| First quarter | Emergency contact and notification tree validation | Emergency management coordinator | Verified call-down roster |
| Second quarter | Tabletop exercise, command level | ATO convenes, commander presides | After-action report with corrective actions |
| Midyear | Physical security survey of controlled spaces | Security force with ATO oversight | Deficiency list with risk rankings |
| Third quarter | Full-scale or functional drill, one hazard per year | Emergency management coordinator | Measured response times and gaps |
| Third quarter | Corrective action tracker review | Commander approves closures | Signed status report |
| Fourth quarter | Biennial vulnerability assessment (even years) | ATO leads working group | Prioritized protective measure package |
| Fourth quarter | Budget submission for next fiscal year countermeasures | ATO prepares, commander endorses | Funded and unfunded requirement list |
The timeline is the accountability instrument. A program with a current calendar and signed reviews is demonstrably managed. A program with a plan document and no exercise record is not.
Misconceptions and Professional Caveats
The most persistent misconception is that the anti-terrorism officer personally performs all anti-terrorism work. In practice the ATO is a program manager. The security force executes access control. Fire and emergency services execute rescue. Communications runs notification systems. The ATO integrates, assesses, and reports.
A second misconception treats emergency management as a subset of security. The two disciplines share a facility and a commander but rest on different authorities. Emergency management derives from preparedness statutes and standards; anti-terrorism derives from force protection and threat response policy. One plan cannot simply absorb the other without losing legal basis for both.
A third misconception assumes classified threat reporting flows automatically to the officer who needs it. Access to threat information depends on clearance level, need-to-know determination, and the facility's information sharing agreements. An ATO without the right access cannot manage what cannot be seen. This is a personnel and access problem, not a diligence problem.
The professional caveat: written position descriptions rarely match actual duty assignments. Facilities under strain routinely dual-hat the ATO with physical security, operations security, or even information technology duties. When that happens, the assessment cycle stretches and the drill schedule slips first. Auditors look for exactly this pattern.
Plain-language version: the person in charge of the paperwork and the calendar is the ATO, but the person who answers for the results is the commander.
Practical Actions to Confirm or Fix Responsibility
Verification beats assumption. The steps below let a staff officer, inspector, or new commander confirm who actually holds the duty.
Request the current appointment letter designating the Anti-Terrorism Officer and the emergency management coordinator, including effective dates and any acting designations. A duty that exists only in a position description is not an assigned duty. Pull the commander-signed anti-terrorism plan and emergency management plan. Check the signature dates against the required review interval. Ask for the last two exercise after-action reports and the corrective action tracker. Confirm that closure items carry commander signatures, not just staff initials. Walk the notification tree with a test message outside normal duty hours. Measure the time to reach 90 percent of the roster. Confirm that every tenant organization has a named point of contact and a documented interface to the host emergency operations center. Review the lease or support agreement for leased space to confirm who controls notification and evacuation during a building-wide event.
Threshold guidance for triage: treat any corrective action open beyond two review cycles as a command-level issue, any notification test below the facility's established reach standard as a plan failure rather than a communications failure, and any ATO vacancy exceeding one full assessment interval as a program gap requiring written mitigation.
Limitations
Public doctrine describes the responsibility structure generically because facility-specific appointment letters, command policies, and lease terms are not public documents. Specific titles, reporting lines, and calendar intervals vary by command, agency, and facility. The principles above describe stable mechanisms; the exact answer for a named facility lives in that facility's appointment letters and signed plans. Where a facility has not published or provided those documents, no external source can confirm the assignment with certainty.
This article is general educational information about organizational responsibility for facility anti-terrorism and emergency management programs. It is not a security assessment, legal opinion, or official determination of duty for any specific facility. For facility-specific questions, contact the installation or headquarters security office, and for an immediate threat or emergency, contact local emergency services.