Emergency Response Plan
SUBJECT: Emergency Response Plan
EFFECTIVE DATE: March 09, 2021; October XX, 2022
BOARD POLICY REFERENCE: CGC
Purpose
The Blinn College District Emergency Response Plan (ERP) is designed to protect lives, preserve property, and ensure the resumption of essential services and normal activities as soon as possible. The ERP provides processes for responding to active threats, acts of violence, severe weather, and other emergencies affecting campus operations and activities. This plan applies to all College District sponsored events and activities on College District property.
The College District adopts the National Incident Management System (NIMS) for consistent emergency management across all campuses and facilities. NIMS enables interoperability among government, private sector, non-governmental organizations (NGOs), and College District entities during emergency responses to critical incidents.
Procedures/Guidelines
See attached Blinn College District ERP.
Blinn College District Emergency Response Plan (ERP)
September 2022, V.1
Blinn College District Emergency Management
Blinn College District Safety and Risk Management
Unified Campus Safety Program (UCSP)
Promulgation Statement
This Emergency Response Plan (ERP) provides guidance on how Blinn College District conducts emergency response across all campuses and facilities. It supports and supplements the Washington County Emergency Operations Plan (EOP), serving as an interactive support document. For campuses in Brazos, Fayette, and Austin Counties, the ERP serves as the primary response plan for critical incidents with significant operational impacts.
Approval and Implementation
The Board of Trustees has officially adopted NIMS as the emergency management framework, guiding the ERP. The Emergency Management Coordinator (EMC) is responsible for ERP oversight and stakeholder coordination. The ERP is flexible and may be fully activated based on specific emergencies and senior leadership decisions. This ERP supersedes previous versions and the Emergency Procedures Manual.
Table of Contents
- Promulgation, Approval and Implementation
- Acronyms Used in the ERP
- Purpose, Scope and Legal Authority
- General Considerations
- Direction, Guidance and Activation
- Concept of Operations – Overall Approach
- Hazard Analysis
- Capabilities Assessment
- Planning Assumptions
- Operational Guidance – NIMS
- Blinn College District ICS Use and Structure
- Incident Command Roles Summary
- Specific ICS Organizational Chart
- Roles and Responsibilities within ICS Structure
- Concept of Operations Under ICS Framework
- Preparedness
- Plans and Procedures
- COOP Concept
- Vital Records Retention
- Essential Facilities Infrastructure Protection
- Special Legal Emergency Planning Considerations
- District Emergency Teams
- Response
- Activation of District ICS Operations
- Continuing Response
- Recovery
- Mitigation
- Prevention
- Program Maintenance
- Record of Distribution
- Plan Development and Maintenance
- Record of Changes
- Annexes (Active Threat, Active Shooter, Severe Weather, etc.)
Acronyms Used in the Emergency Response Plan (ERP)
- AAR
- After Action Report
- AED
- Automated External Defibrillator
- ADA
- Americans with Disabilities Act
- BCD
- Blinn College District
- BCDPD
- Blinn College District Police Department
- BIT
- Behavior Incident Team
- CIRT
- Critical Incident Response Team
- COOP
- Continuity of Operations Plan
- CPR
- Cardiopulmonary Resuscitation
- DHS
- Department of Homeland Security
- DPS
- Texas Department of Public Safety
- EMS
- Emergency Medical Services
- EOC
- Emergency Operations Center
- EOP
- Emergency Operations Plan
- EPG
- Executive Policy Group
- ERP
- Emergency Response Plan
- ERT
- Emergency Response Team
- FBI
- Federal Bureau of Investigation
- FEMA
- Federal Emergency Management Agency
- FERPA
- Family Educational Rights and Privacy Act
- HAZMAT
- Hazardous Material
- HIPAA
- Health Insurance Portability and Accountability Act
- HR
- Human Resources
- HSPD
- Homeland Security Presidential Directive
- IAP
- Incident Action Plan
- ICP
- Incident Command Post
- ICS
- Incident Command System
- IMT
- Incident Management Team
- IT
- Information Technology
- JIS
- Joint Information System
- LO
- Liaison Officer
- MACS
- Multi-Agency Coordination Center
- MOU
- Memorandum of Understanding
- NGO
- Non-Governmental Organization
- NIMS
- National Incident Management System
- PIO
- Public Information Officer
- PPE
- Personal Protective Equipment
- SDS
- Safety Data Sheets
- SITREP
- Situation Report
- SO
- Safety Officer
- SOP
- Standard Operating Procedure
Purpose, Scope, and Legal Authority
This Emergency Response Plan provides operational concepts and procedures for all Blinn College District campuses and facilities. If an emergency exceeds Blinn's capabilities or boundaries, the Washington County EOP takes precedence. For other counties, mutual-aid agreements apply.
The ERP offers all-hazards guidance for emergency management, mitigation, preparedness, response, and recovery. It describes the emergency response organization and assigns responsibilities. The ERP applies to all Blinn officials, departments, agencies, and relevant stakeholders.
The ultimate priority is the safety and well-being of students, guests, faculty, and staff during critical incidents or disruptions, ensuring rapid restoration of services critical to Blinn’s mission.
General Considerations
Threats from violence are significant, but the ERP also addresses other man-made and natural hazards. Such incidents require targeted action to stop attacks, minimize casualties, and begin recovery efforts.
Direction, Guidance, and Activation
Emergency operations require the coordinated efforts of multiple departments and groups. The Emergency Management Coordinator (EMC), usually the Chief of Police, has authority to activate the ERP. In their absence, the Assistant Chief of Police or Safety and Risk Management Director may activate the plan.
The EMC:
- Advises the Chancellor on emergency management
- Keeps the Executive Policy Group informed on preparedness and response
- Coordinates planning with emergency partners
- Oversees the Emergency Operations Center (EOC) during activation
- Takes staff roles as needed during multi-jurisdictional response
The Chancellor, or designee:
- Retains authority over emergency response management
- Manages the Executive Policy Group (EPG)
- Can initiate the Continuity of Operations Plan (COOP)
- Ensures key stakeholders are informed
- Coordinates public information with the PIO
Concept of Operations – Overall Approach
Active threats include but are not limited to active shooter, explosives, barricades, biological agents, hazardous materials, cybersecurity threats, fires, utility outages, extreme weather, pandemics, and food-borne illness. The Blinn College District Police Department is the primary law enforcement agency for response.
When incidents overcome Blinn's capacity, relevant county EOPs and protocols take precedence, with mutual-aid enacted for facilities outside Washington County. NIMS provides the framework for all operations, enabling standardized, interoperable responses.
Hazard Analysis
Blinn College District campuses face both natural and man-made hazards. Past incidents have included severe weather and pandemics, with lesser incidents including food-borne illnesses and external threat responses. Below is a summary of primary hazards:
| Hazard Type | Likelihood | Impact on Health/Public Safety | Impact on Property |
|---|---|---|---|
| Acts of Violence | Low | High | Medium |
| Biological Release | Low | High | Low |
| HazMat Release | Low | High | Low |
| Cyber Threat | High | Low | Low |
| Structural Fire | Medium | Medium | High |
| Terrorism | Low | High | Medium |
| Utility Disruption | Medium | Medium | Medium |
| Flood | Medium | Medium | Medium |
| Tornado | Low | Medium | High |
| Winter Storm | Low | Low | Medium |
| Infectious Disease | Medium | Medium | Low |
| Food Borne Illness | Low | Medium | Low |
Capabilities Assessment
Emergency services are provided primarily by Blinn College District Police and Facilities Maintenance, with external support as necessary. Emergency response agency assignments by county are outlined, with mutual aid and coordination with external partners as key elements.
Planning Assumptions
- District faces ongoing and new hazards
- Emergencies may occur at any time, sometimes with little warning
- Local jurisdictions provide immediate responses at Schulenburg and Sealy campuses
- Proper planning and drills improve readiness and effectiveness
- Officials must recognize and fulfill their emergency responsibilities
- Special needs populations require additional assistance
- Physical and mental health is a post-incident priority
- ERP implementation reduces/prevents disaster losses
Operational Guidance – NIMS
- Preparedness: Planning, training, equipping, exercising, evaluating, and corrective actions to ensure readiness.
- Prevention: Actions to prevent hazards, e.g., security, environmental planning.
- Response: Resource coordination and tactical action to protect life, property, and environment.
- Recovery: Activities to restore critical functions and stabilize the community post-emergency.
- Mitigation: Efforts to lessen disaster impacts (structural/non-structural measures).
Blinn College District ICS Use and Structure
The District uses the Incident Command System (ICS), aligned with NIMS, for all emergencies, critical incidents, and major events, with roles assigned based on expertise and needs rather than day-to-day hierarchy. ICS supports scalable, flexible, and unified response.
- ICS may differ from normal organizational structure; assignments may change as incidents evolve.
- The Chancellor has final authority for all emergency operations and may serve as Area Commander during multi-campus incidents.
- The Executive Policy Group (EPG) oversees district-wide policy, support, and resource allocation during emergencies.
Incident Command System General Roles Summary
Key roles include Incident Commander, Emergency Management Coordinator, Executive Policy Group, Public Information Officer, Safety Officer, Liaison Officer, and section chiefs for Operations, Planning, Logistics, and Finance/Administration. Full ICS chart and details provided in plan appendices.
Roles and Responsibilities within ICS Structure
- Incident Commander (IC): Leads on-scene response, coordinates with EMC, establishes objectives, manages resources, communicates with executive staff.
- Emergency Management Coordinator (EMC): Manages EOC, sets priorities, supports tactical response, coordinates communications, informs EPG.
- Command Staff:
- PIO: Handles public/media information and rumor control through the Joint Information System (JIS).
- Safety Officer: Monitors and advises on operational safety.
- Liaison Officer: Coordinates with external agencies and NGOs.
- General Staff:
- Operations: Tactical response, possibly via support branches for rescue, EMS, law, etc.
- Planning: Information/intelligence gathering, IAPs, resource tracking, documentation.
- Logistics: Resource orders, facilities, security, transport, food, IT, medical services.
- Finance/Admin: Personnel time, contracts, compensation, costs, procurement, record keeping.
Information Collection, Analysis, and Dissemination
Efficient information gathering, evaluation, relevance analysis, categorization, and mission-oriented intelligence sharing is vital for effective response and recovery. Critical information is continuously documented for legal, regulatory, and after-action reporting.
Concept of Operations under ICS Framework
- Standardized structures, plans, and procedures
- Training, exercises, equipment readiness
- Interoperable communications and information management
- Preparedness for identified threats and hazards
- Regular review and documentation of all emergency operations
Preparedness and Planning
- ERP and SOPs developed and maintained for all departments and special teams.
- Continuity of Operations Plan (COOP) ensures essential functions continue.
- Vital records retention, alternate operating locations, and infrastructure protections in place.
- Legal compliance with Clery Act, FERPA, HIPAA, ADA, and psychological first aid addressed.
Emergency Teams and Training
- Teams: IMT, ERT, CIRT, BIT, and EPG with defined roles, training, and participation requirements.
- Annual drills/exercises required for all team members and executive staff.
- Equipment and facilities maintained and assigned as needed, with external formal agreements approved through the Chancellor.
Response
- Immediate action to save lives and protect property
- District-wide emergency declarations as appropriate
- Activation protocols based on threat level and impact ("trigger chart")
- Pre-response readiness includes situational awareness, up-to-date plans, supply checks, and team communication.
- CIRT leaders coordinate with first responders for protective actions (evacuation, shelter, lockdown)
- Information and communications protocols set for interoperability and accuracy
Incident Levels
- Type 1: National-level, most complex (e.g., >1,000 responders)
- Type 2: Regional response, multi-operational period, expanded command
- Type 3: Multiple resources, extended duration, increased structure
- Type 4: Single period, several resources, functional briefings
- Type 5: Handled with 1-2 resources, short duration, simple incidents
Demobilization and Deactivation
- ICS structure adapts to incident needs; teams stand down as situations stabilize
- Priorities established for the orderly release of personnel and transfer of responsibilities
Recovery
- Goal: Restore normal operation and recover critical infrastructure
- Prioritize welfare of people, physical site restoration, and mental health resources
- Continuity of Operations Plan used throughout recovery
- Document all costs and decisions for reimbursement and improvement
- After Action Report generated for all major incidents
Mitigation and Prevention
- Long-term, permanent measures to reduce risk (e.g., infrastructure upgrades, security, building codes, hazard assessments)
- Prevention through policies, inspections, outreach, data analysis, and threat-specific planning
- Community partnerships to promote safety beyond campus boundaries
Program Maintenance
- Regular ERP review and update (at least annually, or after significant events/change)
- Distribution tracking for ERP and related materials
- Ongoing training, exercises, and evaluation of emergency programs and teams
- Controlled public availability of ERP (excluding details for sensitive operations)
Record of Distribution
| Version Number | Date of Distribution | Distribution Groups | Distributed By |
|---|---|---|---|
| V.1 | October 3, 2022 | BCDPD, EPG, ERT, IMT, CIRT, Washington County EMC, RELLIS EMC | A.B. Carlisle |
| V.1 (Public) | October 3, 2022 | BCD Webpage – Emergency Management | A.B. Carlisle, R. Bray |
Plan Development and Maintenance
- ERP reviewed/updated at least annually, after-action reviews, legislative changes, or at Chancellor/Board request.
- All changes recorded in the “Record of Change” section, with date, description, version, and distribution update.
Record of Change
| Change Number | Date of Change | Description of Change | Change Made By |
|---|---|---|---|
| 1 | September 27, 2022 | Creation of new Emergency Response Plan to satisfy requirements of TEC 37.108 and TSSC guidance. This ERP replaces both BCD ERP of 11/4/14 and BCD EPM of 10/21/14. | A.B. Carlisle |
End of Blinn College District Emergency Response Plan