Level 1 — Starting From Zero

Security hasn't been formally addressed. There may be an usher or two keeping an eye on things, but there's no designated team, no written plan, and no communication system.

Your immediate priority is people — identify 2–3 willing volunteers to form the nucleus of a team. Start with the most critical coverage area first: the children's wing. Establish a basic communication method — even a simple phone tree is better than nothing while you build. Download the free Safely Gathered Church Security Risk Assessment Worksheet to identify your biggest gaps. Go to Part 2 of this guide to build your team structure from the ground up.

Level 2 — In Progress But Unorganized

You have a security team and genuine effort behind it — but coordination happens through group texts, verbal check-ins, and some events get missed.

Your immediate priority is structure — move from informal coordination to defined roles and assigned posts. Document who is responsible for what. Every volunteer should have a written role description. Replace your group text with a dedicated team communication channel. Establish a standard event checklist — the same questions answered before every service. Go to Part 2 of this guide to formalize your existing team's structure.

Level 3 — Organized But Fragmented

You have solid protocols and a committed team — but they're using a patchwork of tools. Information lives in too many places, and coordination still requires manual effort.

Your immediate priority is consolidation — bring your tools, policies, and communication into one place. Audit your current toolset: what can be eliminated? What is creating unnecessary friction for volunteers? Ensure your policies are documented, current, and formally acknowledged by every volunteer in writing. Evaluate whether your current system scales — would it hold up if your team doubled in size? Go to Part 2 to review your team structure against established best practices.

Site Security Coordinator / Administrator

Owns the overall security program — policies, training, scheduling, and team performance. Serves as Incident Commander during an emergency: gives orders, coordinates response, liaises with law enforcement. Conducts pre-service briefings and post-service debriefs. Reviews incident logs after every service and follows up on any reported concerns. Maintains the relationship with local law enforcement. Reviews and updates the security plan at least every 6–12 months.

Access Control

Covers all designated entry points during services. Monitors for individuals displaying unusual or concerning behavior. Controls entry to restricted areas including the children's wing. Greets arrivals with a warm, watchful posture — hospitality and security are not opposites. Knows exactly who to notify and how if a concern arises at their post.

Best practice: Only one exterior door should remain unlocked from the outside during a service. Every other exit remains accessible from inside. Source: FBI Law Enforcement Bulletin.

Patrol / Perimeter

Covers the parking lot, building exterior, and interior hallways. Follows a varied circuit — never the same route twice, to avoid predictability. Serves as the team's earliest warning system — the first to observe a threat approaching the property. Checks in with Access Control at regular intervals. Monitors for vehicles or individuals behaving unusually in the parking lot.

Note: Many serious incidents begin in the parking lot. A visible volunteer presence is one of the most effective deterrents available to a church with no budget for security equipment.

Medical Responder

Serves as the team's first medical response. Ideally holds current CPR/AED certification and basic first aid training. Knows the location of all AED units and first aid supplies on the campus. Responds to medical emergencies during services: fainting, cardiac events, injuries. Documents all medical responses in the team's incident log.

Ideal candidates: congregation members who are nurses, EMTs, paramedics, doctors, or who hold current first aid certifications. Cross-training with the security team on communication protocols is strongly recommended.

Who to Look For

• •Individuals with backgrounds in law enforcement, military service, emergency medical services, or professional security.
• •People who are calm under pressure, situationally aware, and not looking for authority — but willing to exercise it when necessary.
• •Congregation members who are known, trusted, and "above reproach" — the standard cited in 1 Timothy 3:2-7.
• •Individuals who understand that the goal is order and protection, not control, authority, or confrontation.

Note: If your team is comprised entirely of volunteers, make sure to have a headcount high enough so that each individual's church attendance is not significantly affected.

Non-Negotiable Requirements Before Any Volunteer Serves

• •Written acknowledgment of your security policy and code of conduct — not a verbal agreement.
• •Basic orientation training — role responsibilities, emergency procedures, communication protocols, and the chain of command.