How to Start a Church Security Team: A Step-by-Step Guide

More churches are formalizing safety. What used to be a couple of ushers keeping an eye on the door is becoming a dedicated safety ministry with screened volunteers, defined roles, written plans, and real training. Standing one up well takes more than recruiting willing people — it takes a clear mandate, the right team, consistent procedures, and a way to stay organized. This is a practical, step-by-step guide for a church building a security team from the ground up.

This is an operations-and-management guide — how to structure, staff, train, and run the team. It is not a tactical manual.

Step 1: Secure leadership buy-in and a clear mandate

A safety ministry needs an explicit mandate from your pastor, board, or elders — covering its purpose, authority, budget, and how it reports. Document who the team protects, who authorizes what, and how decisions get made. A written mandate keeps the ministry supported through leadership changes and gives volunteers clear authority to act. It also signals to the congregation that safety is a thoughtful, sanctioned part of church life, not a fringe activity.

Step 2: Define your mission and scope

Decide what the team is responsible for. Common scope includes greeting and observing at entrances, monitoring the parking lot, supporting secure children's check-in, responding to medical incidents, handling disruptions calmly, managing severe-weather and evacuation procedures, and coordinating coverage for special events. Clear scope drives everything that follows — how many people you need, what training matters, and what your plan must cover.

Step 3: Recruit and screen the right people

Select for temperament first: calm, observant, dependable, good with people. Off-duty or retired law enforcement, military, EMS, and nurses are valuable, but so are level-headed members who take it seriously. Screen everyone — background checks, references, and an interview — and require the same child-protection screening your church uses for children's ministry. The goal is a trustworthy, hospitable team, not the largest team.

Step 4: Define roles and structure

Even a small team works better with defined roles: a team leader who owns each service or event, members assigned to entrances, the parking lot, the worship space, and children's areas, plus someone watching communications. As you grow, add shift leaders and a coordinator. (See church security team roles and structure for a full breakdown.)

Step 5: Decide your posture — armed or unarmed

Decide early whether the team will be armed, because it shapes recruiting, training, insurance, and policy. There's no universal answer — it depends on your state's laws, your insurer, your congregation's culture, and your team's experience. Make it a deliberate leadership decision and document the policy. (See armed vs. unarmed church security.)

Step 6: Write a security and emergency plan

Put your procedures in writing so the team responds consistently instead of improvising. A church security plan should cover roles, communication, and responses to the most common situations — medical emergencies, severe weather, lost children, disruptive individuals, and evacuation — plus how you coordinate with local police and EMS. (See how to write a church security plan.)

Step 7: Train the team

Train before you deploy, and keep training. Core competencies are situational awareness, communication, de-escalation, basic medical/first-aid and CPR, child-safety procedures, and knowing the plan cold. Run periodic drills and tabletop scenarios so the team is calm and coordinated when something real happens. (See church security team training and best practices.)

Step 8: Build relationships with local responders

Introduce your team to your local police department and EMS before you ever need them. Share your plan, learn their response expectations, and agree on points of contact. For larger events, invite them to weigh in. These relationships turn an emergency from improvised to coordinated.

Step 9: Set up coordination and documentation

From day one, decide how you'll schedule volunteers, assign positions, communicate during services, and log incidents. Many teams start on group chats and paper sign-up sheets, which works until it doesn't — multiple services, campuses, and events quickly outgrow it. A shared system keeps schedules, assignments, event plans, and incident records in one organized, reviewable place, which also supports leadership reporting and insurance documentation.

Step 10: Review and improve

Treat every service and event as a chance to learn. Debrief regularly, capture what happened, and refine the plan. A documented record also supports oversight and continuity as volunteers come and go.

Common pitfalls to avoid

• No written mandate — leaves the team unclear on authority and vulnerable when leadership changes.
• Recruiting for size over temperament — the right few outperform a large, untrained group.
• Skipping screening — every member should clear the same checks as children's ministry volunteers.
• No written plan — improvised responses are inconsistent and hard to improve.
• Coordination living in people's heads and group chats — knowledge is lost every time someone steps away.

Tools that keep a safety ministry organized

Once the mandate, team, and plan are in place, the day-to-day challenge is running it consistently. AdvanceWork gives church safety teams one place to schedule and assign volunteers, plan coverage and event advances, log incidents, and produce the records leadership and insurers ask for. Small and volunteer-run teams can start with AdvanceWork Fast; larger or multi-campus ministries can use the full platform — request a demo. (New to the topic? Start with our complete guide to church security.)

Frequently asked questions

How do you start a church security team?

Secure a leadership mandate, define your mission and scope, recruit and screen the right volunteers, set roles, decide your armed/unarmed posture, write a security and emergency plan, train the team, build relationships with local responders, and set up a way to schedule and document the work.

How many people do you need on a church security team?

It depends on your size and layout, but many churches start with enough to cover entrances, the parking lot, the worship space, and children's areas during each service — often a handful of trained volunteers per service, scaled up for larger congregations and events.

Do church security volunteers need background checks?

Yes. Every team member should clear the same background and child-protection screening your church requires for children's ministry, plus references and an interview. Screening protects the congregation and the church.

What training does a church security team need?

Situational awareness, communication, de-escalation, basic first aid/CPR, child-safety procedures, and thorough familiarity with the church's security and emergency plan — refreshed with regular drills.