This Guideline document is provided to you and your organization as a starting point or maturity checkpoint for existing procedures. It is brought to you on behalf of Jim McConnell, Principal Owner, and Ask McConnell, LLC — A Converged Security Services Provider. The content is not meant to cover every circumstance, industry, law, regulation, contractual requirement, threat, environment, or risk, but it provides a starting point for any organization. Please consult with your legal counsel and insurance provider about added requirements. We are not legally protecting these documents; we just ask for credit, shout-outs, and referrals if you find them helpful.
Jim McConnell | info@askmcconnell.com | askmcconnell.com
Church Service Disruption Response Guide
Updated: 18 June 2026
One person’s perspective — weigh it against your law, insurance, culture, and context.
Every organization that gathers people — especially faith communities — will eventually face a disruption. Some are attention-seeking: an exuberant worshipper drawing eyes away from the service, or an organized group with a message they intend to deliver. Others are non-attention-seeking: a medical incident, a behavioral health crisis, or an environmental emergency. The response is different in each case, but the preparation is not. Have the plan before you need it.
General Principles — Before Anything Happens
- Establish in advance what cue the pastor or speaker will give the security team when they want action taken — a nod, a hand signal, or a verbal phrase. Do not leave this to improvisation during a live incident.
- Designate a single incident commander for each service — one person whose job it is to coordinate the team’s response. Everyone else supports; one person decides. This eliminates the paralysis of two team members waiting for the other to move first.
- Initial engagement with any disruptive individual should involve two people: one security-trained team member and one pastoral staff member. A unified, calm response reduces escalation risk.
- Whoever makes initial contact must be trained in and comfortable with de-escalation as the primary tool. Going hands-on is a last resort — not a first move.
- Before every service, confirm where your nearest law enforcement presence is. A calm, visible officer standing nearby is often enough to change the dynamic without a word spoken.
- Train a second team member to watch the rest of the room during any confrontation. The person making contact should not also be the only one watching for secondary reactions.
- Always assess before engaging: the individual causing a disruption may be deaf, blind, non-English speaking, or experiencing a medical or special needs event. Do not assume intent without a moment to evaluate.
Team Communication During an Incident
- Establish your communication method before the service: earpieces, two-way radios, or a designated hand-signal system. Cell phone calls and texts during an active incident are slow and visible — have a faster channel ready.
- All team members should know the incident commander’s call sign or location so they can report to and receive direction from one source during a disruption.
- Keep communication brief and calm on the channel. Other team members and nearby attendees may be listening or watching your body language. Your composure is part of the response.
- After the incident, do a full team debrief — what the incident commander observed, what the contact team observed, and what bystanders reported. Build that into your next pre-service briefing.
Attention-Seeking Disruptions
Note: Attention-seeking disruptions range from enthusiastic but distracting worship expression to organized protest activity. The response escalates with the severity of the disruption — but always starts at the lowest effective intervention. If you are dealing with an organized group, assume they have a plan. Have yours already running before they execute theirs.
Flag-Waver / Enthusiastic Expression Level
- Designate a section of your venue in advance — a balcony, side section, or rear area — where more expressive worship styles are welcome. Establish this before an incident, not after one.
- After a first disruption, a staff member should approach the individual warmly, not confrontationally: “Hey — we love your heart for worship. We have a section in the balcony where that style of expression is completely at home. Would you be willing to move there so we can serve you better?”
- Offer an alternative, not just a correction. A monthly night of worship, a more expressive service format, or a specific area of the venue gives them somewhere to go — and shows you mean it.
- If a gentle ask is met with offense, move from a request to a clear, calm direction. Match the tone you want the room to keep.
- If the behavior continues after a clear direction, involve the security team. At that point, asking has become telling.
Protester / Organized Disruption Level
- The presence of security personnel and law enforcement — calm, visible, positioned near the disruption — is your most powerful first tool. You do not need to touch anyone to change the dynamic of a room.
- Assume coordination. Organized groups frequently split up and disrupt from multiple points simultaneously. When one person stands up, your incident commander should immediately scan the rest of the room for secondary actors before focusing entirely on the first.
- Be aware that protesters may be recording or livestreaming the interaction. Your team’s behavior is potentially public the moment it starts. Calm, professional, and proportionate — always.
- Continue the service as normally as possible unless law enforcement advises otherwise. Stopping the service rewards the disruption and signals the tactic worked.
- Use de-escalation language and in-kind requests: “We would be glad to have a pastor speak with you privately in the office.” or “For the safety of our attendees, would you be willing to take this conversation to the parking lot?”
- Silence and calm presence are sometimes the most effective response. Not every disruption requires a verbal reaction from the stage or the team.
- Move nearby attendees approximately seven to ten feet from the individual or group. If it is safe to do so, have security team members, deacons, or ushers form a calm, outward-facing perimeter — visible containment without physical contact.
- If an individual is removed and returns, consult your legal counsel about issuing a formal trespass notice. A documented, signed notice served in the presence of a witness gives law enforcement clear legal standing to act on a return visit — and signals to the individual that your organization is prepared to enforce its boundaries.
- If there is any immediate threat to the safety of attendees or staff, move directly to law enforcement. Do not hesitate. Document everything and prepare a follow-up plan — removal does not always end the situation.
Non-Attention-Seeking Disruptions — Medical and Behavioral Incidents
- Move nearby attendees away from the incident quickly and calmly. Your goal is to create space — not panic. How the team moves sets the tone for how the room responds.
- Form a perimeter of team members around the individual — but face outward, not inward. The two or three people actively assisting need working space, and the person on the ground does not need fifteen people staring down at them. Privacy and calm are part of the response.
- Maintain the perimeter until EMS or trained medical volunteers have the situation under control. Your job is crowd management, not medical intervention — unless you are trained and designated for it.
- If the service can continue without drawing further attention to the incident, allow it to — at the pastor’s discretion. A calm service helps keep the room calm.
Documentation — After Every Incident
- Log every disruption, regardless of severity: date, service, type of incident, individuals involved (description if name is unknown), response taken, and outcome. What feels minor in the moment may become part of a pattern over time.
- If the same individual appears repeatedly, that log is your record — for pastoral follow-up, legal action, or law enforcement reference.
- Share incident summaries with your security team lead and, where appropriate, your senior leadership team. Patterns in your incident log are the best early warning system you have.
Related Resources
🖶 To save or print this guide, use your browser’s Print function (Ctrl+P / Cmd+P) and select “Save as PDF” if needed.
