How to Write a Church Security Plan (with Template Outline)

A church security team is only as consistent as its plan. Without one, every situation gets handled differently depending on who's on duty. A written security and emergency action plan turns good intentions into a repeatable, trainable response. This guide outlines the sections your church safety plan should include so you can build one that fits your congregation.

This is a planning-and-documentation guide focused on what to put in writing. It does not prescribe tactical methods, and you should review your final plan with local law enforcement, your insurer, and legal counsel.

Why your church needs a written plan

A written plan does three things: it makes responses consistent regardless of who's on duty, it gives you something concrete to train against and drill, and it documents diligence for leadership and insurers. It also forces useful conversations — about roles, communication, and worst-case situations — before an emergency rather than during one.

Section 1: Purpose, scope, and roles

Open with the plan's purpose, what it covers, and who does what. Define the team structure, the per-service leader, and each position's responsibilities. (See church security team roles.) Anyone reading the plan should immediately understand who is in charge and who covers what.

Section 2: Communication

Spell out how the team communicates during services and events — radios or a group channel, call signs or names, how to discreetly signal a problem, and who contacts church staff and outside responders. Include key phone numbers and the chain of contact.

Section 3: Medical emergencies

Medical events are the most common emergency a church team handles. Document how to respond — who your designated medical members are, where AEDs and first-aid kits are located, how to call EMS and direct them to the right entrance, and how to manage the area until they arrive.

Section 4: Severe weather

Cover tornado, severe storm, and other weather procedures appropriate to your region — shelter locations, who monitors alerts, how you communicate to the congregation, and how the team assists. Include power-loss and facility considerations.

Section 5: Lost or missing child

A missing-child procedure is essential and reassuring to parents. Document how check-in/check-out security works, what happens the moment a child is reported missing, who coordinates the search, how exits are managed, and when to involve police.

Section 6: Disruptive or distressed individuals

Most disruptions are non-violent — a distressed visitor, a domestic situation, an unwelcome guest. Document a calm, de-escalation-first approach, who responds, how to involve the team leader, and when to call police. The emphasis is on protecting people while preserving the church's welcoming spirit.

Section 7: Evacuation and reunification

Document evacuation routes and assembly points, how the team directs and assists (including for children and people with mobility needs), how you account for everyone, and how families reunite afterward.

Section 8: Coordination with law enforcement and EMS

Record your local police and EMS contacts, what you've agreed on with them, how you summon and direct them, and what information the team should be ready to provide. Build these relationships before you need them. (See how to start a church security team.)

Section 9: Special events

Large gatherings, holidays, concerts, and guest speakers need their own annex — extra staffing, parking and entrance plans, medical and responder coordination, and a pre-event walkthrough (an "advance"). Plan these the way professional protection teams plan an event.

Section 10: Training, drills, and review

Close with how often the team trains and drills the plan, who maintains it, and how you update it after incidents and exercises. A plan that isn't trained and revised is just a document. (See church security team training.)

Keeping the plan, drills, and incidents together

A plan works best when it lives alongside your schedules, event advances, and incident logs — not in a binder no one opens. AdvanceWork keeps your plan, assignments, event advances, and incident records in one place your team actually uses. Small and volunteer teams can start with AdvanceWork Fast; larger ministries can request a demo. (New here? Start with the complete guide to church security.)

Frequently asked questions

What should a church security plan include?

Purpose and roles, communication procedures, and response plans for medical emergencies, severe weather, lost or missing children, disruptive individuals, and evacuation — plus coordination with police and EMS, special-event planning, and a training and review schedule.

Is there a church security plan template?

Use the ten sections in this guide as your outline, then tailor each to your facility, congregation, and local responders. Review the finished plan with local law enforcement, your insurer, and legal counsel.

How often should a church update its security plan?

Review it at least annually and after any incident or drill that reveals a gap. Treat it as a living document that improves as the team learns.