How to Start a Church Security Team: A Practical Guide

Most church security teams do not start with a plan. They start with a few people who already keep an eye on the doors: the usher who notices a stranger in the parking lot, the deacon who used to be a police officer, the greeter who knows every family by name. That instinct is valuable, but instinct alone is not a team.

An organized safety team knows who is responsible for what, how to communicate during a service without alarming the congregation, and what to do in the first sixty seconds of an emergency. This guide walks through how to build that team, step by step, whether your church has fifty members or five thousand.

1. Get leadership on board first

A security team without the pastor's support will struggle from day one. Before you recruit anyone, sit down with your senior pastor and church board and agree on a few things in writing:

• Why the team exists. Protecting people, not policing them. Most of what a safety team handles is medical calls, lost children, and disruptive visitors.
• Who leads it. One team leader who reports directly to the pastor or an elder.
• What authority the team has. Can members ask someone to leave? Who makes the call to lock doors or stop a service?
• Whether members will be armed. This is a decision for church leadership, your insurance carrier, and an attorney who knows your state's laws. Do not let it happen by default.

A short written charter approved by your board protects the church, the team, and the volunteers who serve on it.

2. Assess your campus before you recruit

You cannot staff a plan you have not written, and you cannot write a plan until you know your weak points. Walk your campus on a Sunday morning and again on a weeknight. Look at:

• Every entrance, and which ones are unlocked during services
• The children's ministry area, including check in, check out, and restrooms
• Parking lots, lighting, and where people gather before and after services
• How the offering is collected, counted, and moved
• Times when the building is open but lightly staffed, like weekday office hours and youth nights

Write down what you find. That list becomes the foundation of your security plan and tells you how many people you need on each shift.

3. Recruit for character, not just experience

Law enforcement and military backgrounds are helpful, but they are not the most important qualification. The best team members are calm under pressure, observant, discreet, and dependable. They show up when scheduled, and they know how to talk a frustrated visitor down without making a scene.

Build a team with a mix of skills:

• Medical. Nurses, EMTs, and doctors in your congregation are invaluable. Medical emergencies are the most common incident most teams will ever handle.
• Observers. Greeters and ushers who know the regulars and notice who does not belong.
• Responders. People with law enforcement, military, or security training who can step in if a situation escalates.

Run a background check on every team member, especially anyone who will be near the children's area. Have each person sign an agreement that covers confidentiality and the team's policies.

4. Write a simple security plan

Your plan does not need to be a binder nobody reads. It needs to answer a few clear questions that every team member can recite:

• Where is each person posted during a service?
• How do team members communicate with each other?
• Who calls 911, and who meets first responders at the door?
• What happens during a medical emergency, a missing child, a disruptive person, a lockdown, and an active threat?
• Where are the AED, first aid kits, and bleeding control kits?

Keep a one page summary for each type of emergency. Long plans get skimmed. Short plans get followed.

5. Train, then train again

In my years with the U.S. Secret Service, one lesson was constant: people do not rise to the occasion, they fall back on their training. A plan that has never been practiced will fall apart the first time it is needed.

Start with the basics every member should have:

• CPR, AED, and first aid certification
• Stop the Bleed or similar bleeding control training
• Verbal deescalation
• Your church's specific procedures for each type of emergency

Then run short tabletop exercises and walkthroughs during team meetings. Ask "what would you do if" questions. Practice a missing child response before you ever need one. Keep a record of who completed which training and when, because your insurance carrier may ask.

6. Solve communication before Sunday

When something happens during a service, your team needs to reach each other instantly and quietly. Shouting across the sanctuary or sending group texts that sit unread does not work.

Most teams use some combination of radios, earpieces, and phones. Whatever you choose, it should let a team member send an alert with one tap, tell everyone what kind of emergency it is and where, and work even when phones are locked in a pocket. Test it every week before service starts.

7. Document every incident

Every medical call, disruptive visitor, suspicious vehicle, and unlocked door should be written down, even when nothing bad happened. Good records protect the church if an incident leads to a claim or lawsuit. They also show patterns: the same car circling the lot on Wednesday nights, or a side door that keeps getting propped open.

Record the date, time, location, who was involved, what happened, and what the team did. Have the team leader review each report.

8. Schedule so nobody burns out

Volunteer teams fail most often because the same five people cover every service until they quit. Build a rotation so each member serves a predictable number of services a month, and make sure every shift has enough coverage for your plan. As your team grows, add a second leader who can run the team when the primary leader is out.

Common mistakes to avoid

• Starting without leadership approval. It creates confusion about authority the first time something happens.
• Focusing only on the worst case. Active threats get the attention, but medical emergencies and lost children are what your team will handle most.
• Skipping documentation. If it is not written down, it did not happen as far as your insurer is concerned.
• Training once and stopping. Skills fade. Schedule refreshers at least quarterly.