Church security training should help people make sound decisions before, during, and after an incident—not simply memorize a list of threats. For church leaders in Southern California, the right program starts with the building, congregation, service schedule, and existing response roles. It also makes clear where volunteers’ responsibilities end and when trained professional support may be appropriate.
Request a security consultation
Call (833) 272-7247 to discuss security coverage.
What should church security training accomplish?
A useful program prepares a church community to notice concerns, communicate clearly, and follow a coordinated response. It does not turn every volunteer into a security officer, and it should not encourage people to intervene beyond their training. Its purpose is to reduce confusion and support the safety of people attending services, programs, and events.
Start with outcomes the leadership team can observe. For example, can the people assigned to welcome visitors identify who to notify about a concern? Do staff know which doors are intended to remain controlled during a service? Can the team share a clear location and description over its chosen communication method? Does everyone understand what to do when an emergency requires contacting public safety authorities?
Training should also make room for the church’s welcoming mission. Security procedures need to be practical, respectful, and consistent with the way the congregation uses its space. A procedure that volunteers cannot remember or apply is unlikely to help when stress rises.
Make those outcomes concrete before selecting a course or instructor. A planning team might write three short objectives: volunteers can report a concern using a consistent location name; program leads can account for their groups using the church’s existing process; and the designated contact knows how to communicate with responders. These objectives help leaders distinguish useful instruction from a general presentation that does not connect to the site.
GuideStone’s church safety and security training resources offer a church-focused starting point for leaders who want to review safety with their team. The Texas District & County Attorneys Association also describes church security training as a way to consider risks and prepare a security team. Use outside resources to inform local planning, not as a substitute for assessing your own site and procedures.
Who needs to take part in the planning?
Training works best when the right people help shape it. The pastor or designated senior leader should set priorities and approve procedures. A facilities contact can explain doors, keys, alarms, room uses, and maintenance constraints. A person responsible for children’s programs can identify arrival, pickup, and reunification processes. Ushers, greeters, event coordinators, and other volunteers can describe how people actually move through the property.
Include people with different responsibilities, but do not assume every participant needs the same level of instruction. A small planning group can draft the overall approach, while role-specific practice covers what each person needs to know. Define who can make decisions, who passes information, who meets arriving responders, and who accounts for people in a particular area.
- Leadership: approves the plan, assigns accountable owners, and communicates expectations.
- Facilities: verifies access points, room names, keys, lighting, and any physical constraints.
- Program leads: explain schedules and the needs of children, older adults, and people who may need assistance.
- Volunteer teams: practice simple actions within their assigned roles and know how to summon help.
- Professional security personnel, when used: coordinate post instructions, communications, and escalation with church leadership.
Assign a plan owner rather than leaving updates to an informal group. That person can gather changes, schedule reviews, and make sure new team members receive an orientation. For broader context on professional guard roles and site coverage, review the provider’s security guard services information and decide what questions apply to your facility.
It can help to separate decision-making authority from observation and communication. A greeter may notice an issue and relay a factual description, while a designated leader determines the next step. This separation prevents multiple people from issuing conflicting directions. Name a backup for each important function, and make sure the backup has the same information and access needed to act when the primary contact is unavailable.
How do you assess a church before training?
Walk through the property at the times it is used, not only when it is empty. Observe how members, guests, vendors, and program participants arrive and leave. Note where people gather, where lines form, which rooms are occupied, and how someone could ask for help without creating unnecessary disruption.
Record observations rather than making assumptions about risk. A simple site review can cover:
- Entrances and exits used during services, classes, meetings, and special events.
- Areas that are open to visitors and areas that need staff or volunteer awareness.
- Parking and exterior approaches, including how someone would describe a location to responders.
- Communication options available to the team and places where reception or audibility may be limited.
- Procedures for children’s check-in and pickup, accessibility needs, and accounting for groups.
- Who can access keys, alarm controls, first-aid supplies, and emergency contact information.
Keep sensitive details in a controlled document rather than posting them publicly. The purpose of a walkthrough is to find practical questions for planning and training, not to publish a map of vulnerabilities. If changes are needed, assign an owner and a reasonable review date.
Make the walkthrough representative. If the congregation uses a room differently on weekdays than on weekends, review both patterns. Notice ordinary pinch points, such as a crowded check-in table or a doorway used by several groups at once. Ask the people who regularly work there what tends to slow movement or make instructions hard to hear. The aim is to identify operational details that shape training, not to label ordinary activity as a threat.
Use a simple observation log with columns for location, normal activity, question to resolve, responsible person, and follow-up date. For instance, an observation might note that two programs release at the same time and ask how staff will communicate if the usual meeting area is unavailable. This turns a broad concern into a question with an owner and a way to check whether the plan addresses it.

How should a church turn observations into procedures?
Turn the site review into a short set of written instructions that people can find and understand. The document does not need to describe every possible event. It should identify the people responsible for decisions, the way concerns are reported, and the first steps the team is expected to take. Use plain language and consistent names for rooms and entrances so people can communicate without translating unfamiliar terms during a stressful moment.
For each procedure, identify an owner and a backup. A plan that names only one person can fail when that person is absent. Likewise, a phone list should indicate which contact is appropriate for routine questions and which situations require emergency services. Confirm that designated contacts know their responsibilities and have agreed to serve in those roles.
Make the written instructions usable without exposing details unnecessarily. Keep a controlled copy for the people who need it, establish how updates are distributed, and remove superseded versions from circulation. A public-facing summary can explain broad expectations, such as where visitors should enter or how to ask for assistance, without sharing sensitive operational details.
Procedures should also address how leaders will account for people after a disruption. Decide who checks whether staff and program groups have reached the agreed location, how information is passed to leadership, and how the church will communicate with families or attendees. Keep the process aligned with the congregation’s existing child-protection, accessibility, and emergency policies rather than creating conflicting instructions.
Finally, test the language with the people expected to use it. Ask a volunteer to explain the steps back in their own words. If an instruction is hard to remember, overly broad, or unclear about who acts next, revise it before training. That small review can reveal whether a plan is workable more quickly than simply distributing a long document.
A useful procedure can follow a repeatable pattern: who notices or receives information, who is notified, what facts should be shared, who decides on the response, and how the team confirms the next step. Keep instructions focused on decisions people can make. For example, ask a reporter to state the location, what they observed, and whether anyone needs immediate assistance, rather than speculate about a person’s intent.
Set a simple version-control practice. Put a review date and plan owner on the controlled copy, tell staff where the current version is kept, and remove outdated copies from shared folders or printed binders when changes are made. If a contact, room name, or process changes, communicate that specific update to everyone whose role depends on it. This helps prevent a correct plan from becoming unreliable through small, unnoticed changes.

Which skills should training cover?
Build the curriculum around the tasks people are expected to perform. Basic awareness and communication are often more useful for a broad volunteer group than detailed tactical instruction. A smaller group with assigned responsibilities may need additional practice under qualified instruction.
| Training area | Who may need it | Practice or preparation |
|---|---|---|
| Observation and reporting | Greeters, ushers, program staff, designated team members | Describe a concern factually, identify its location, and notify the designated contact. |
| Communication and escalation | People assigned to communicate or coordinate | Use agreed language and contact paths; know when to call emergency services. |
| Access and visitor flow | Facilities staff, service leads, assigned volunteers | Review which entrances are in use, how people are directed, and who can authorize a change. |
| Emergency procedures | All staff and volunteers, with role-specific instruction | Learn the church’s approved actions, meeting points, and accountability process. |
| Scenario discussion | Planning group and relevant team members | Talk through a realistic situation, decisions, communications, and after-action improvements. |
| Post and site orientation | Professional guards and church contacts | Review responsibilities, site instructions, reporting, and coordination with church leadership. |
Make boundaries explicit. Volunteers can be trained to observe, communicate, guide people according to the plan, and request help. Do not assign them tasks that require specialist qualifications or exceed what the church has approved. For more on the value of clear duties and written instructions, use the security services FAQ as one source of questions to raise with a provider.
Training can be layered so that people receive information suited to their role. A general orientation might cover how to report an issue, who leads the response, and how to reach help. Ushers could practice clear directions and passing a message to a lead. Children’s program staff may need to rehearse their existing attendance and family communication procedures. A facilities contact may review access and building-specific information with the people responsible for it.
Ask the trainer to distinguish what can be covered in a shared session from what needs a separate role briefing. A mixed audience can learn a common vocabulary, but participants should leave knowing their own responsibilities. Avoid adding techniques simply because they sound advanced; an activity belongs in the program only if it supports a defined responsibility and can be taught safely by an appropriate instructor.
How should a church practice scenarios?
Begin with a tabletop discussion. A facilitator presents a situation in stages and asks participants what they would do, whom they would contact, and what information they need. This allows leaders to test decision-making and communication without creating a surprise for the congregation.
Choose scenarios that reflect actual operations. Examples include a medical emergency during a service, a separated child, a person who needs assistance evacuating, an unexpected building-access issue, or a disruptive interaction at a public event. The purpose is not to predict every event. It is to rehearse how people will communicate, use their assigned roles, and seek appropriate help.
Before any live exercise, set the scope and notify the people who could be affected. Decide whether the activity is a discussion, a walk-through, or a more involved drill. Protect children and congregants from unnecessary alarm, and coordinate with relevant authorities when the exercise requires it. Do not stage realistic weapons, threats, or other elements that could be mistaken for a real emergency.
After practice, ask participants what was clear and what was confusing. Note where a contact list was outdated, instructions conflicted, or a decision had no named owner. Update the plan, then explain the changes to the people who need them. A short, useful review is better than recording an exercise and never acting on its lessons.
To keep a tabletop focused, give participants a one-page scenario and assign a facilitator, note-taker, and decision lead. Introduce only enough detail to prompt decisions; the goal is to test the process, not to surprise or trick people. For each decision point, ask: Who owns this action? What information is needed? Who needs to hear it? What would make the team move to the next step? Record unanswered questions separately from decisions already covered by policy.
Consider one straightforward scenario: a child is not at the expected pickup point after a program ends. Participants can walk through who checks the normal process, who informs the program lead, what information should be shared with family, and how the rest of the group remains supervised. This exposes gaps in role assignment and communication without requiring a dramatic simulation. A different scenario can examine how a person who needs mobility assistance receives help during an evacuation, using the church’s established accessibility procedures.
Close each exercise with a short after-action review. Ask what participants expected to happen, what actually happened in the discussion, what was unclear, and what change would make the next response easier. Sort findings into immediate corrections, items requiring leadership approval, and topics needing qualified outside guidance. Give each action an owner and deadline, then check it at the next planning meeting.
Call (833) 272-7247 to discuss on-site guard support.
How often should training be reviewed?
Set a recurring review schedule and revisit the plan whenever something important changes. A new entrance procedure, renovation, program, service time, or change in leadership can affect how people move and who has responsibility. New volunteers should receive role-specific orientation before they are expected to use the procedures.
Use a simple record to make the process manageable. Track the date, participants or roles covered, topics reviewed, questions raised, and follow-up owner. Store the record with the church’s controlled planning documents. Avoid recording sensitive personal information that is not needed to improve readiness.
Training records are not proof that every situation is covered. They help leaders see whether core instructions have been communicated and whether open issues were addressed. A regular check-in can ask whether contact details still work, whether designated people understand their duties, and whether the plan matches current facility use.
Review after a change as well as on a calendar. If a room is repurposed, a program adds a new session, or the usual point person steps away, ask which instructions and contact paths are affected. A short targeted briefing may be more useful than waiting for the next full training date. Keep the review proportionate: confirm the change, update the procedure, notify the affected roles, and record what remains unresolved.
What should buyers ask a training or security provider?
Church leaders comparing outside support should seek clear answers about scope, roles, and coordination. A training session and an on-site guard assignment are different services. Ask what is included, who will participate, what preparation is expected, and how recommendations will be translated into the church’s own procedures.
- How will the provider learn the building layout, schedule, visitor flow, and church priorities?
- Which topics are included, and which require a separate qualified instructor or public agency?
- How will volunteer roles be kept within appropriate boundaries?
- What information will the church receive after a walkthrough, class, or exercise?
- How would a guard assignment coordinate with the church’s designated contact and written instructions?
- What reporting and communication process is available during coverage?
- What are the proposed schedule, responsibilities, assumptions, and costs?
Ask for a proposal that distinguishes training, consultation, and physical guard coverage rather than treating them as interchangeable. A professional guard service can provide an on-site presence, but the church still owns its internal procedures and decisions. ASAP Security Guards provides manned security services in Southern California and offers a free security consultation; a conversation can clarify whether the request is for guard coverage or planning support. The price quote and consultation page is a useful next step for discussing a facility’s requirements.
Compare proposals against the same questions so the decision is not based on different assumptions. One provider may be describing a training session, while another is proposing scheduled guard coverage; compare the actual deliverables, staffing responsibilities, and follow-up rather than the labels. Ask how the provider will learn the church’s operating schedule, how changes will be communicated, and who on the church side will approve site instructions. Request clarity on what is excluded, too. This helps leadership identify when another instructor, public agency, or internal policy owner needs to be involved.
Before a meeting, gather a basic schedule, facility-use summary, known communication procedures, and the questions raised during the walkthrough. Do not send sensitive building details through an unsecured channel or include information that is not needed for an initial discussion. A provider can use the broad outline to understand the request, while the church decides what site-specific information should be shared and with whom.

How can leaders tell whether training was useful?
Evaluate whether participants can use the procedure, not whether they enjoyed a presentation or received a certificate. At the end of a session, ask people to explain who they would contact, what information they would share, and which decisions belong to leadership. Use a brief scenario or teach-back exercise to check whether instructions are understandable across different roles.
Look for practical signs of readiness: the current contact path is known, the assigned lead and backup are clear, and participants can describe what is within their role. Record unresolved questions rather than expecting a single session to solve every issue. Give each follow-up item an owner and due date, then bring open items to the next leadership review.
Ask for feedback from people who use the building in different ways. A weekday staff member may notice a different challenge than a weekend greeter or children’s program coordinator. Compare the feedback with the written plan and revise instructions where people report confusion. The goal is not to score individuals; it is to find and correct weak links in the process.
When a provider delivers instruction or support, request a clear description of what was covered and what remains outside scope. Confirm whether the provider recommends additional specialist instruction, facility changes, or coordination with local authorities. A transparent summary helps the church decide what to do next and prevents a training session from being mistaken for a complete security program.
A practical review can use three checks. First, ask a participant in each role to describe the next step in a familiar situation. Second, verify that the contact list, room names, and instructions match current practice. Third, look at the action log from the last walkthrough or exercise and confirm whether high-priority items were completed. If people give different answers about who decides or whom to notify, treat that as a plan issue to resolve rather than a personal failure.
When might on-site guard coverage make sense?
Training can clarify what a congregation can handle through its own procedures, but it may also show that a site needs a dedicated professional presence during certain hours or events. Consider the actual operating pattern: how many people attend, which entrances are active, whether there are multiple simultaneous programs, and what level of visible coverage leadership believes is appropriate.
There is no single staffing choice that fits every church. Some organizations may focus on consistent volunteer preparation and clear reporting. Others may want to discuss scheduled guard coverage for services, events, or periods when the property is especially busy. A provider should understand the facility and the requested duties before recommending an approach.
Technology such as cameras can support awareness and review, but it does not replace people who can assess a situation and communicate on site. If considering a camera system, clarify who monitors it, who receives alerts, and how it fits the response plan. ASAP’s 24/7 CCTV monitoring information can help frame those questions; evaluate it as a separate support option, not a substitute for training or a physical guard.
For an initial discussion about a church or other facility in Southern California, use the security services contact page to share the site, schedule, and type of support being considered. Clear details help keep the conversation focused on the facility’s needs.
Discuss your church’s security needs
Call (833) 272-7247 to request a security consultation.
Frequently asked questions
Can volunteers provide all church security?
That depends on the church’s site, schedule, and assigned responsibilities. Volunteers can help with awareness and communication when they have clear, appropriate roles. Leaders should not ask volunteers to perform duties beyond their preparation, and they can consider professional guard coverage when an on-site presence is needed.
Should training include a live drill?
Not every training session needs a live drill. A tabletop discussion or guided walk-through can reveal gaps with less disruption. If leaders choose a drill, define its scope, notify affected people, and take steps to prevent the exercise from being mistaken for a real emergency.
What should a church do first?
Name a planning lead, gather the people who understand the facility and programs, and walk through normal operations. Identify communication and responsibility gaps, then prioritize a short list of practical improvements before choosing training or outside support.
Does camera monitoring replace an on-site guard?
No. Cameras and monitoring may support awareness, but they do not provide the same physical presence or on-site judgment as a guard. A church should decide how each option fits its plan and who is responsible for acting on information.
Make training match the church
Effective church security training is specific to the people, building, and activities it is meant to support. Start with a site review, define realistic roles, practice communication, and follow up on what the team learns. When professional coverage may help, discuss the scope and schedule with a provider so the proposed support fits the church’s actual needs.

