How to Write a Church Security Plan

Most churches that start thinking about security skip straight to the tools and tactics without writing anything down. That works fine until something actually happens, and the team discovers that nobody agreed on what to do. A written plan is what converts a group of willing people into a coordinated team.

You do not need a security professional to write your plan. You need a clear head, a few hours, and a willingness to think through scenarios before you face them. This guide walks you through what to include.

What a church security plan actually is

A church security plan is a written document that describes who is responsible for safety at your church, what they are expected to do, and how they should respond to specific situations. It covers your team structure, your standard Sunday procedures, and your response protocols for emergencies.

Think of it less as a policy document and more as a shared understanding. The goal is that any member of your team, on any given Sunday, knows what is expected and what to do without having to ask.

The six things every church security plan needs

1. Team structure and roles

Who is on the team, who leads it, and who they report to. List the roles (team lead, floor volunteer, children’s ministry coverage, etc.) and the name currently in each role. This section should be reviewed and updated at least once a year.

2. Volunteer screening standards

What is required before someone can serve: application, background check, training completion, and any role-specific qualifications. Putting this in writing protects the church and sets a clear bar for everyone who serves.

3. Standard Sunday procedures

What your team does on a normal service day. Assignments by position, pre-service walkthrough, communication protocol, and how you hand off at the end. Routine creates muscle memory, and muscle memory matters when something breaks the routine.

4. Response protocols for common scenarios

Walk through the situations your team is most likely to encounter: a disruptive individual, a medical emergency, a suspicious person or vehicle, a fire, a missing child, and an active threat. For each, describe who responds, what the first steps are, and when to involve outside authorities. These do not need to be long. A few clear sentences per scenario is enough.

5. Communication and chain of command

How does your team communicate during a service? Earpieces, radios, a group text, hand signals? What is the chain of command when the team lead is unavailable? Write it down so there is no ambiguity.

6. Review and update cadence

A plan that is never reviewed becomes stale. Build in a schedule: a full review once a year, and a quick check after any incident, even a minor one. Note the date of the last review on the document itself.

A few things to keep out of the plan

Keep tactical details about weapons, codes, or security positions out of any document that is widely distributed. The plan your volunteers read should describe their responsibilities, not provide a roadmap to anyone who gets hold of the document.

Keep it short. A plan that takes thirty minutes to read will not be read. The best church security plans I have seen fit in five to eight pages. If yours is growing past that, break it into a core plan and separate policy documents for specific areas.

Getting the plan used

A plan is only as good as the team’s familiarity with it. Once you have a draft, walk through it with every volunteer before they serve. Have them sign off that they have read it. Then review it together at least once a year as a team, ideally alongside a tabletop exercise where you talk through the scenarios out loud.

The goal is not compliance. The goal is that when something happens, your team acts from memory and training, not from a document they are trying to find on their phone.

If you are starting your team from scratch, write a simple first draft of your plan before your first deployment. It does not need to be perfect. It needs to exist.