Why Cameras and Binders Are No Longer Enough
I didn't build ChurchSecurityPlanner as a contractor for some security firm. I built it because my father — Pastor Clint Reagan at Calvary Chapel Knoxville, a congregation of more than 5,000 — called me and said he couldn't find anything that actually worked for managing his security teams. He was jumping between six different platforms just to run one ministry, including group texts to coordinate volunteers, Excel to track certifications, Google Calendar for scheduling, and Telegram for team communication. And the emergency response plan was printed and bound, not in the hands of a single volunteer when it actually mattered.
I spent years in ministry as a youth pastor and served on church security teams. Along the way I was trained in church protection protocols by law enforcement and military professionals. I knew exactly what the gap looked like: what a church leader needs administratively and what a security professional needs tactically. So I built what he needed.
That background shapes what follows. It comes from serving on church security teams, not from selling cameras.
The four pillars are Prevention, Recognition, Response, and Recovery. They apply whether your congregation is 50 or 5,000, and none of them require a large budget.
The Plan in Brief
If you want the short version, a church security plan has seven parts. This is an example to adapt to your church.
- Assess your risks. Walk the building and list where problems are most likely. The church security plan template gives you the fields.
- Form the team and set roles. Decide who leads and who holds each post. See church security team roles.
- Write your procedures. Put medical emergencies, disputes and severe weather on paper, in short steps.
- Schedule coverage. Build a rotation so no one covers every service. Start with the church security team schedule template.
- Agree how the team communicates. Pick one channel and make sure every volunteer is on it.
- Report and review. Write up every incident, even small ones, using a church incident report template.
- Train and drill. Practice the procedures at least once a year and after any incident.
The rest of this guide takes these in turn.
Pillar 1: Prevention, Church Safety Starts With Scheduling and Screening
Prevention doesn't begin on Sunday morning. It begins much earlier, with the people you recruit, how you vet them, and whether they show up faithfully.
Build Your Church Security Team on Documentation, Not Good Intentions
Many churches ask every security volunteer to complete a background check before their first shift, including the person who has attended for twenty years and whom everyone loves. Keep a record of how you screen and train your volunteers, and keep it somewhere better than a group text thread. Talk to an attorney licensed in your state about what screening is right for your church.
Beyond background checks, your church security team needs centralized records for the items below. This is an example to adapt to your church.
- CPR and first aid training (with expiration dates)
- De-escalation training completions
- Role assignments by service and zone
- Background check dates and renewal schedules
If these records live in a spreadsheet on one volunteer coordinator's laptop, they'll be gone the moment that person changes churches. In ChurchSecurityPlanner, admins record each volunteer's trainings and certifications as accolades, and a role on a shift can require one.
Build a Rotation That Doesn't Burn Out Volunteers
In my experience, volunteer burnout is the biggest threat to a church security program's longevity, and it usually comes from one thing: no rotation system. When the same three reliable people cover every service because the group text went unanswered, those three people will eventually quit. When they do, you have no security team.
A functional church security scheduling system gives every volunteer visibility into their upcoming shifts, makes it easy to swap coverage without creating confusion, and provides clear accountability so no shift goes unstaffed because someone assumed someone else would cover it.
If your team runs its rotation across a calendar, a group text and a spreadsheet, our guide to church security team software walks through what breaks and what one place for the whole team changes.
The goal is a team where no single person is indispensable and no service is one "sorry, can't make it" text away from a coverage gap.
Pillar 2: Recognition, Noticing Trouble Early
Recognition is the trained capacity to notice that something is wrong before it becomes a crisis. In my law enforcement training for church environments, this was called pre-incident indicators: the behavioral and environmental signals that come before an escalation. You don't need SWAT training to develop this skill, but you do need a system that gives your volunteers the structure to practice it consistently.
Zone-Based Coverage Gives Every Area an Owner
In my experience, the problem usually isn't a shortage of volunteers. It's a lack of clarity about who is responsible for what. When everyone is on "general security duty," everyone assumes someone else is watching the children's wing.
Zone-based coverage fixes this. Divide your facility into defined zones (parking lot, main entrance, sanctuary, children's wing, fellowship hall, overflow areas) and assign each zone a designated volunteer who owns situational awareness for that space. When something happens in Zone 3, there's no ambiguity about who responds first and who provides backup.
This structure also makes training more effective. A volunteer who knows their specific zone can mentally walk through response scenarios for that space, and that kind of mental rehearsal matters when real seconds count.
The Cameras-Plus-People Model
Camera systems are valuable tools for recording and monitoring. But a camera cannot intervene. It cannot make a judgment call about whether the agitated man in the parking lot is a distressed parent or a threat that needs to be escalated. It cannot route the right person to the right location in real time.
The most effective approach pairs physical observation tools with trained human volunteers who have a communication channel that's faster and more discreet than a radio call. The camera gives you a record. Your team gives you a response.
Pillar 3: Response, Turning a Written Plan Into Action
This is where most church security programs break down. The Emergency Operations Plan exists. It was carefully developed. It may even follow FEMA's guide. And it's sitting in a binder in the church office that nobody has opened since last year's safety committee meeting.
When an actual incident occurs, such as a medical emergency, an active threat or a custody dispute that turns physical, people don't freeze because they lack courage. They freeze because they lack clarity. The EOP is inaccessible in the moment it matters most.
Keep Your Emergency Operations Plan Where Volunteers Can Open It
The FEMA Guide for Developing High-Quality Emergency Operations Plans for Houses of Worship is a free, widely used federal guide to writing an emergency operations plan. It sets no requirements, but it covers a range of threats and hazards with guidance written for houses of worship. If you haven't read it, it is a good place to start.
But then break it down. Instead of one 40-page PDF, write short role-specific checklists and keep them in your resource library, where volunteers can open them on their phones. When a medical emergency is triggered, the medical response volunteer should see their checklist, not the lockdown protocol written for the access control team. When an incident is unfolding, role-specific checklists are the difference between a coordinated response and three volunteers doing three different things. In ChurchSecurityPlanner, those checklists sit in your team's resource library, so a volunteer can open them on their phone.
Communicating Without Radios
Two-way radios have their place in large-venue security operations. But in a church, with background music, children's programming and a worship service in full swing, radios create problems as often as they solve them. A radio call that carries across the sanctuary announcing "we have an issue near the main entrance" can cause exactly the kind of congregational panic that complicates your response.
Team messaging with push notifications lets your team coordinate without broadcasting to the room. Your team can coordinate quietly, for example to send a medical responder to the right wing, without a radio call. Practice your lockdown procedure separately; no app replaces it. A photo of a license plate or a suspicious item can be attached to an incident report, which a radio call can't do.
For most churches, moving away from radios as the main way to communicate is a practical improvement.
Pillar 4: Recovery, Documentation, Debriefs and Review
Every incident, including the minor ones that resolve without much happening, is worth documenting. The churches that do this consistently are the ones that actually get better over time.
Why Document Every Incident
Post-incident documentation serves three purposes for your leadership team:
Your own records. A timestamped incident report with the names of responders is easier to find and read later than handwritten notes completed three days after the fact. Talk to your insurer and to an attorney licensed in your state about what to keep and for how long. In ChurchSecurityPlanner, an incident report carries attachments, comments, a status and a follow-up trail.
Insurance. Talk to your insurer.
Team improvement. The debrief is where real training happens. What did the first responder do well? Where did communication break down? What would you change? These conversations, structured around real events, are more valuable than any tabletop exercise.
A good target: every incident logged within 24 hours, with timestamps, responder names, actions taken, and how it resolved. The discipline of logging minor incidents is what prepares your team to document the serious ones accurately.
Operational Protection: Everyday Church Safety and Security
A security plan is more than a response to the worst day. Most of a safety team's work is operational protection: the routine practices that keep a church's normal life running safely week after week.
- Service-time coverage. Know who is on duty for each service and event, where they are posted, and who is in charge if something happens.
- Access during the week. Decide which doors are open, when, and who checks them, including for midweek groups, children's ministry and rentals.
- Communication. Give the team one agreed way to reach each other and the person in charge, and practice using it.
- Incident reporting. Write down every incident, however small, so patterns show up before they become emergencies.
- Continuity. Plan how services, childcare and communication continue if a building, system or key volunteer is unavailable.
Reviewed once a year and after any incident, these routines turn a written plan into daily practice.
For the routines week by week, with a sheet your team can adapt, see church operational protection: the everyday routines.
A Note for Small Churches
If your congregation is under 200, you may be reading this and thinking that formal church security planning is for bigger churches with dedicated staff and real budgets. It isn't, and you may need it more.
Smaller congregations are less likely to have trained security personnel on-site. They're more likely to rely on informal, ad-hoc responses when something goes wrong. And they're not exempt from the incidents that make headlines at larger churches. Threats don't sort by attendance numbers.
The good news is that a small church security plan doesn't require a six-figure camera system or a dedicated security director. It requires five reliable volunteers with clear, documented roles. A communication tool faster than a group text. An emergency protocol everyone has actually read and rehearsed at least once.
The gap between having no plan and having a solid one is smaller than it looks. The coordination and clarity that come from a simple, well-organized team cost almost nothing. The alternative is figuring it out in the middle of something you weren't prepared for.
Trenton J. Reagan is the founder of ChurchSecurityPlanner, a former youth pastor and church security team member. He was trained in church protection protocols by law enforcement and military professionals and has a lifelong background in firearms training and tactical preparedness. ChurchSecurityPlanner was built in response to a direct request from his father, Pastor Clint Reagan of Calvary Chapel Knoxville — a congregation of 5,000 — who needed a comprehensive tool to manage his security teams.