Church Security Is Not a Volunteer Afterthought
Most churches have no real security plan. They have a guy named Dale who volunteers to stand near the door on Sunday mornings because he used to work in construction and has a nice talking stick. That is not a strategy. It is a liability. I spent about eight years running security programs for a network of mid-size churches, mostly in the 200 to 800 attendance range. I watched more than one congregation learn hard lessons the way they always do: after something bad happened. The single most effective thing any church can do before that point is put together a Free Church Security Manual that actually gets used, not just filed away in a Dropbox folder nobody checks.
Free Church Security Manual: What It Actually Should Contain
A proper manual for a church setting needs several sections, and they need to be written for people who will never have handled a crisis before. Volunteerness is your workforce. Your manual should reflect that reality. The core sections are: 1. Roles and Chain of Command — Define who is in charge during an incident. Most churches fail here. You cannot have three deacons all thinking they are calling the shots while an active threat is unfolding. Name a Security Director. Name a deputy. Write down exactly who makes which call, including the decision to lock doors, call 911, and the congregation. This usually takes about 30 minutes of meeting time to get right.
2. Threat-Specific Response Protocols — Write separate procedures for the scenarios that actually happen. I am not talking about zombie apocalypses. I am talking about: an unruly visitor causing a disturbance, a domestic violence situation spilling into the narthex, a medical emergency in the nursery, and yes, an active shooter. Each gets its own one-page flowchart. One page. If it is longer than that, nobody will read it when adrenaline hits. 3. Communication Templates — Pre-write the scripts. "Evacuate to Parking Lot C" is easier to say when you have it on a laminated card. Include the exact phrases to use when calling 911. Dispatchers ask specific questions. If your volunteer is fumbling through "uh, there is a guy with a gun at the church," you are losing critical seconds. I usually provide my teams with a script card that covers location, nature of emergency, number of threats, and whether people are trapped. 4. Facility Hardening Checklist — This is the boring part that prevents most problems. Map every exterior door. Know which ones have locks that actually work. Identify blind spots in your parking lot. Check whether your CCTV cameras have night vision or if they are producing grainy footage from 2014. During my work with a suburban church in Ohio, we found that the motion-sensor lights on the back entrance had been disabled by a contractor three years earlier and nobody noticed. The Free Church Security Manual should include a facility audit you update quarterly. Budget about two hours per quarter for this.
Get the Full Details
5. Volunteer Training Schedule — A manual that sits on a shelf is worthless. You need a recurring training rhythm. I recommended a 15-minute tabletop exercise once per month and a full drill once per quarter. Tabletop exercises are just the team sitting in a room and walking through "what would you do if..." scenarios. They take 15 minutes and are dramatically more effective than nothing. Full drills, where you actually practice lockdown procedures, take about 45 minutes and should include your worship team and childcare workers, not just the security volunteers. 6. Post-Incident Protocol — This section gets ignored constantly. After an incident, you need a debrief procedure within 48 hours, a counseling referral list, and a media response plan. Churches are small communities. Rumors spread faster than facts. Having a designated spokesperson and a holding statement ready to go prevents the pastor's wife from giving an unplanned interview to the local news that contradicts the official account.
Where Churches Mess This Up
I have reviewed dozens of church security plans. The same mistakes appear repeatedly. The biggest mistake is writing the manual like a legal document. It should be readable by a 17-year-old youth group volunteer on a Sunday morning at 8:45 AM, three minutes before they report to their post. Short sentences. Clear verbs. No jargon. "Secure the area" means nothing to a new volunteer. "Go to the north door. Close it. Lock it. Stay behind the wall until you hear the all-clear" means everything. The second mistake is ignoring the nursery and children's ministry. Churches overwhelmingly design security around the sanctuary and lobby. But children's wings are often in separate buildings or interior rooms with multiple exits and no exterior visibility. I once worked with a church that had a detailed sanctuary lockdown plan and absolutely nothing for the nursery. When I asked about it, the security lead said, "The nursery is on the ground floor. We'd just run out." That is not a plan. That is hope. We spent a Saturday rewriting the children's wing procedures, and it took less than three hours to make them operational.
The third mistake is not accounting for non-Sunday operations. Weekday night groups, food pantry distribution, community classes — these often run with zero security coverage. If your manual only addresses Sunday services, it covers roughly 20 percent of your actual operating hours. Add a section for weekday operations. It is mostly a question of who is currently on-site and how they communicate.
A Specific Problem I Faced and How I Solved It
Three years ago, a church in my network had a genuine crisis. A man with a history of stalking one of their volunteers showed up at the children's ministry entrance during Wednesday night youth group. He was not armed, but he was agitated and had already bypassed the front office receptionist. The security team's existing protocol was designed for Sunday scenarios, where the lobby is the primary access point. The children's wing had no intercom, no phone, and one door that stuck halfway open because the hydraulic closer had failed six months earlier and nobody had scheduled the repair. The incident lasted nine minutes before the man left on his own. Nobody was hurt. But in those nine minutes, three security volunteers were giving conflicting instructions over a group text thread because there was no voice communication system in the children's wing. The church had spent $4,000 on badge readers for the main entrance and nothing on interior comms. The workaround was simple and cheap. I had the church buy three Android tablets mounted on the walls in the children's ministry and main sanctuary, loaded with a free push-to-talk app. Total cost was about $180. The tablets also ran a shared Google Doc with the current security protocols so volunteers could pull them up instantly. We also got the hydraulic closer fixed. After that, the real fix was updating the manual to include the children's wing as a secured zone with its own lock-down procedure. The tablet system allowed the Security Director to issue a single voice command that reached every volunteer simultaneously. Before that, it was five different text messages bouncing around with no confirmation anyone had seen them.
I have since replicated that tablet-and-push-to-talk setup for seven other churches in the region. It works. The limitation is that the tablets need to be charged and the Wi-Fi needs to be stable. In a church with aging infrastructure, that is not guaranteed. As a backup, every volunteer still carries a $15 two-way radio. The radios are for the initial moments. The tablets are for sustained coordination. You need both until the Wi-Fi proves reliable under stress, and it rarely does on the first try.
Getting a Free Church Security Manual
There are several reputable sources for a Free Church Security Manual at no cost. The National Church Safety Institute publishes a solid template. The Church Law and Tax Report has a customizable one. The Federation of Protestant Welfare Agencies also has free resource materials. None of these will be perfect for your specific building or denomination, and that is the point — treat any free template as a starting framework, not a finished product. What I usually recommend is taking any free template and spending a full afternoon walking your actual facility with a flashlight and a notebook. Walk every entry point. Test every lock. Sit in the security volunteer's actual position and see what they can and cannot observe. You will find things the template never mentions because the template was written for a building you do not have. That is normal. Fill in the gaps with your own procedures.
What These Manuals Cannot Do
A Free Church Security Manual will not prevent an incident. It will not replace trained personnel. It will not stop a determined threat from entering your building. What it does is reduce confusion, save seconds during critical moments, and ensure that when something goes wrong, the people responding are doing the same thing rather than figuring it out as they go. In my experience, that distinction is the difference between a manageable incident and a tragedy. There is also a legal dimension worth noting. In several states, churches can be held liable for inadequate security measures when an incident occurs on their property. A documented, regularly updated security manual is the strongest evidence you can produce that you took reasonable steps. Not having one is, frankly, negligent in a way that has nothing to do with whether an attack actually happens and everything to do with whether you are prepared to handle it if one does. The manual is a living document. Update it every quarter. Run a drill after every major update. If your congregation size changes by more than 25 percent, revise the evacuation and lockdown procedures. If you add a new building or wing, update the facility audit immediately. Churches that treat their security manual as a set-it-and-forget-it document are the same churches that learn their mistakes in the worst possible way.
