Trinity Safety Training Group LLC | Life Safety Ministry Brief
Picture this. It's Sunday morning, worship has ended, and a visitor strikes up a conversation with one of the church's greeters. He compliments the service, asks how long the pastor has been there, and mentions how difficult it must be to coordinate everything that goes on during a typical Sunday.
The greeter enjoys the conversation. After all, being friendly and helpful is part of the job. Before long, they're discussing the pastor's schedule, when he typically leaves the building, and which staff members are usually around during the week.
Nothing about the conversation seemed threatening. The visitor was polite, the questions sounded reasonable, and the greeter had no reason to believe anything was wrong.
But consider what just happened. A complete stranger walked into the church and, through an ordinary conversation, learned details about the pastor's routine and the church's staffing. Information that may not have been provided if someone had simply walked up and asked for it directly.
Was the visitor genuinely curious? Maybe. Could he have been deliberately gathering information? Absolutely.
And that's why Life Safety Ministry Teams need to understand elicitation.
What Exactly Is Elicitation?
Elicitation is the deliberate use of conversation to obtain information from another person, often without making that person feel as though they're being formally questioned. It's a recognized technique in intelligence and counterintelligence work, but the underlying principles show up in everyday conversations more often than most people realize.
Unlike an interrogation, where someone generally knows they're being questioned, elicitation can blend into a perfectly normal discussion. The individual sharing information may think they're simply helping someone, correcting a misunderstanding, or talking about a subject they know well.
Now, that doesn't automatically make elicitation dishonest or dangerous. People use similar conversational techniques in journalism, business, negotiations, and ordinary social interactions. But the same methods can be used to obtain information that someone might otherwise choose not to share.
For church safety personnel, understanding the difference matters. We want our people to be approachable and capable of having productive conversations. We also want them to recognize when a seemingly harmless exchange begins drifting into information that should probably remain private.
And sometimes, that line isn't nearly as obvious as we'd like.
Feigned Ignorance: Let Me Explain That to You
One of the more recognizable elicitation techniques is feigned ignorance. Someone presents themselves as unfamiliar with a subject, knowing that people often enjoy explaining things they understand.
Think about how naturally we respond when someone says, "I'm not really sure how that works."
Most of us immediately begin explaining.
In a church setting, this might involve a visitor who appears confused about how the building operates or how different ministries are organized. A well-meaning volunteer begins helping, which is exactly what we want volunteers to do. The problem develops when that explanation moves beyond directions or general information and starts revealing internal procedures, staffing arrangements, or access restrictions.
There's nothing wrong with telling someone where the children's check-in desk is located. Explaining how the children's ministry controls access, which doors are monitored, or when those doors might be unattended is another matter entirely.
The lesson isn't to stop helping people. It's to recognize that being helpful doesn't require explaining everything we know.
Assumed Knowledge: When Familiarity Creates Trust
Another technique involves assumed knowledge. Someone introduces a subject in a way that suggests they already know something about it, and the other person naturally confirms or expands on the information.
This can be particularly effective in churches because familiarity often creates a sense of connection.
Someone who knows the pastor's name, mentions a ministry leader, or refers to an event from the previous week may immediately seem less like a stranger. The volunteer begins thinking, "Well, they must know somebody here."
Maybe they do.
But knowing someone's name doesn't establish a relationship, and familiarity with church activities doesn't automatically provide authorization to access restricted areas or obtain private information.
A visitor might know quite a bit about a church simply from its website, livestreams, social media pages, or conversations with other people. None of that is necessarily concerning. It does mean, however, that LSMT members should avoid confusing knowledge with trustworthiness.
Access decisions should be based on established procedures, not on how familiar someone sounds.
Deliberate False Statements: Our Need to Correct People
Here's an interesting one. People really don't like hearing something they know is wrong, particularly when it's a subject they understand well.
A deliberate false statement can take advantage of that tendency.
Imagine a volunteer hears someone make an inaccurate statement about the church's security arrangements. The volunteer knows the statement is incorrect and immediately wants to set the record straight.
Before long, they've explained how the security team actually operates.
The original statement may have been completely innocent. It could also have been intended to encourage that very correction.
This is where a little restraint becomes important. Not every incorrect statement requires a detailed explanation, especially when correcting it would reveal nonpublic information.
A simple response such as, "We have procedures in place to help keep everyone safe, but we don't discuss the specifics," is perfectly reasonable.
You can be courteous without giving someone a tour of your security plan.
Bracketing: Getting More Specific Than You Intended
Bracketing involves introducing a range or estimate that encourages someone to provide a more precise answer. People often correct numbers when they believe they know the actual figure.
We do it in ordinary conversation all the time.
Someone makes an estimate, and another person says, "Actually, it's closer to..."
There's nothing inherently suspicious about that exchange. But when the subject involves staffing levels, operational schedules, or security resources, an unnecessary correction can disclose information the church never intended to make public.
Not all numbers are sensitive. Average attendance, for example, may already be published on a church website. The number of safety personnel assigned to a particular area during a specific service is a different kind of information.
LSMT members need to understand the difference, and so do the people who serve alongside them.
Word Repetition: Sometimes People Just Keep Talking
Word repetition is a simple conversational technique that encourages someone to expand on what they've said. It can be part of ordinary active listening, and when used appropriately, it's especially useful during emotionally charged conversations.
Suppose someone approaches a team member and says, "Nobody at this church will listen to me."
The team member responds, "You feel like nobody's listening?"
That acknowledgment may encourage the person to explain what happened, who they've been trying to reach, or why they're upset. Perhaps the issue is a misunderstanding that pastoral staff can resolve. Perhaps the individual is experiencing a personal crisis and needs assistance.
Or perhaps the conversation reveals statements that warrant additional attention.
The point isn't to manipulate someone into revealing personal information. It's to listen carefully enough that we understand what they're actually trying to communicate.
One of the mistakes safety personnel sometimes make is deciding what a situation means before allowing the other person to explain it.
Good listening helps prevent that.
Mutual Interest and Reciprocity: The Friendly Conversation
People tend to be more comfortable with someone who shares their interests, experiences, or opinions. And when someone tells us something about themselves, we often feel inclined to share something in return.
That's normal human behavior.
It's also one reason apparently friendly conversations can produce more information than either person initially intended to exchange.
For an LSMT, the concern isn't that people are making friends. Churches should encourage relationships and hospitality. The concern is whether those conversations begin revealing information about leadership routines, restricted areas, security assignments, or other matters that don't need to be discussed publicly.
A visitor can be genuinely friendly and still ask questions that are inappropriate to answer. Likewise, a team member can establish rapport without pretending to have experiences or beliefs they don't actually hold.
There is no need for church volunteers to become undercover investigators.
From General Conversation to Specific Information
Some elicitation approaches begin with broad subjects and gradually move toward more specific information. What starts as a conversation about church growth, for example, may eventually involve questions about staffing, leadership availability, or building operations.
Of course, ordinary conversations develop this way too. That's what makes the distinction difficult.
We shouldn't assume malicious intent simply because someone asks several related questions. Instead, team members should consider the nature of the information being requested, whether the individual has a reasonable need for it, and whether other concerning behaviors are present.
A person asking how to schedule an appointment with the pastor is doing something perfectly normal.
Someone who repeatedly seeks private details about the pastor's movements, despite being offered the appropriate contact information, presents a different situation. That behavior may deserve additional attention, particularly when combined with other observations.
Context matters. It always does.
So How Can an LSMT Use These Principles?
This is where understanding elicitation becomes useful beyond simply protecting information.
LSMT members frequently encounter situations in which they need to understand someone's intentions, needs, or concerns. Sometimes the person is frustrated. Sometimes they're confused. Occasionally, they may be exhibiting behavior that raises a legitimate safety concern.
A good conversational approach can help clarify what's happening without making the situation worse.
Imagine an individual arrives at the church office visibly upset and insists on speaking with the senior pastor. Rather than immediately treating the person as a security problem, a team member can acknowledge the concern and invite the person to explain what assistance they need.
As the conversation develops, careful listening and neutral follow-up questions may reveal whether the person has a legitimate pastoral concern, a grievance involving church leadership, or an issue that requires a more immediate response.
The team member doesn't need to deceive the individual or conceal their role. In fact, doing so can create unnecessary ethical and legal problems.
The objective is to gather enough relevant information to make an informed decision while preserving the person's dignity.
And there is an important limit. If the individual makes a credible threat or circumstances indicate imminent danger, the team should stop treating the interaction as an information-gathering opportunity and follow its emergency procedures.
A conversation is not worth prolonging when doing so puts people at risk.
The Other Side of Elicitation: Protecting Church Information
Perhaps the greatest practical value of elicitation awareness is helping church personnel recognize when they may be sharing more than they should.
Consider how many people within a typical congregation possess information about its daily operations. Administrative assistants know staff schedules. Greeters know where visitors enter. Children's ministry volunteers understand check-in procedures. Custodial personnel know building access arrangements. Safety team members understand emergency response procedures and staffing assignments.
Most of these individuals are naturally helpful. That's a good thing.
But helpful people can unintentionally disclose information that, when combined with other details, provides an unnecessarily clear picture of the church's operations.
This is why information protection shouldn't be treated as the exclusive responsibility of the LSMT.
Church leadership should establish clear expectations about what information may be shared publicly and what should remain limited to authorized personnel. Volunteers don't need to memorize complicated intelligence concepts, but they should understand why certain questions are better referred to the church office or safety director.
And they need to know that declining to provide sensitive information isn't rude.
It's responsible.
Practical Response Guide: Recognizing and Responding to Elicitation
Recognizing an elicitation attempt is one thing. Knowing how to respond without appearing suspicious, becoming confrontational, or making a visitor feel unwelcome is another.
Life Safety Ministry Team members should understand that not every unusual question requires an investigation. Often, the appropriate response is simply to provide general information, maintain appropriate boundaries, and continue observing the interaction. However, when someone repeatedly seeks sensitive information or exhibits additional concerning behavior, the team needs to recognize when a routine conversation warrants further attention.
The following examples illustrate how an LSMT member or church volunteer might respond.
Questions About the Pastor's Schedule
Visitor: "Does Pastor usually leave right after the service, or does he stay around for a while?"
Recommended response: "His schedule varies, but I'd be happy to help you contact the church office or arrange a time to speak with him."
The volunteer remains helpful without disclosing predictable movements or private scheduling details. If the individual repeatedly presses for specific times or locations, that pattern may warrant discreet notification to the LSMT.
Questions About Security Personnel
Visitor: "You guys have a pretty good security team here, don't you? How many people do you normally have working on Sundays?"
Recommended response: "We're fortunate to have people who help keep things running safely. Is there something specific you're concerned about?"
The response avoids revealing staffing levels while giving the visitor an opportunity to explain a legitimate concern. The question itself isn't proof of suspicious intent, but repeated requests for operational details deserve attention.
Correcting False Assumptions
Visitor: "I heard you don't have anyone watching the building during the week."
Recommended response: "We have procedures for taking care of the property throughout the week, but we don't share the details of those arrangements."
The volunteer neither confirms nor corrects specific security arrangements. There is no need to prove that the visitor's information is inaccurate.
Questions About Restricted Areas
Visitor: "I'm trying to find the children's classrooms. Is there another way into that part of the building?"
Recommended response: "I can take you to the children's check-in desk. They'll be glad to help you."
The volunteer provides legitimate assistance without discussing alternate entrances or access-control procedures. If the individual refuses assistance and continues attempting to enter restricted areas, the behavior should be reported.
Apparent Familiarity With Church Leadership
Visitor: "I know Pastor pretty well. He told me I could stop by his office whenever I wanted."
Recommended response: "I'd be glad to contact the office and let them know you're here."
The response is courteous without accepting a claimed relationship as authorization. The appropriate staff member can verify whether the visitor is expected.
Questions That Become Increasingly Specific
Visitor: "How many services do you have? Does everyone leave afterward? Is there usually anybody still here later in the afternoon?"
Recommended response: "Our public service times are available on the website. If you're hoping to visit or meet with someone, I can help you make arrangements."
The volunteer recognizes that the conversation is moving from general public information toward staffing and occupancy details. Rather than answering every question, the response redirects the visitor toward a legitimate purpose.
An Upset Individual Seeking a Church Leader
Visitor: "I've tried talking to your pastor, and nobody will tell me where he is. Somebody needs to answer for what's happened."
Recommended response: "I can see you're upset, and I'd like to understand what's happened so we can get the right person to help. When you say somebody needs to answer for it, what do you mean?"
The response acknowledges the person's frustration while clarifying an ambiguous statement. The team member should listen for specific threats or indications of imminent harm, maintain appropriate distance, and request assistance when warranted.
If the individual communicates a credible threat or presents an immediate danger, the team should stop relying on conversation alone and activate its emergency procedures.
When the Individual Refuses to Accept the Answer
Visitor: "Why won't you just tell me how many security people are here? What are you hiding?"
Recommended response: "I understand you're asking, but we don't share those details. If you have a safety concern, I can connect you with someone who can address it."
The volunteer maintains the boundary without arguing or becoming defensive. Repeating the same explanation calmly is generally more productive than trying to justify every security policy.
When Should the LSMT Become Involved?
A single question about church operations rarely establishes a security concern. However, an interaction may warrant further assessment when the individual repeatedly seeks nonpublic information, attempts to bypass established procedures, makes threatening statements, or engages in concerning behavior that cannot reasonably be explained by the stated purpose of the visit.
Team members should avoid labeling the individual as dangerous based solely on curiosity, nervousness, appearance, or an unfamiliar communication style.
When reporting an interaction, communicate the actual questions asked, the answers provided, and any observable behavior that raised concern. Avoid embellishment or speculation about the person's motives.
For example, reporting that "the visitor asked three times about the pastor's departure time after being offered assistance contacting the church office" is more useful than reporting that "someone was casing the pastor."
If the circumstances suggest a credible threat, the team leader should determine the appropriate protective measures and law enforcement notification. An immediate threat requires an immediate emergency response.
A Simple Response Model: Acknowledge, Redirect, Assess, Report
LSMT members can use four principles to guide these interactions.
Acknowledge. Respond respectfully to the person and recognize the question or concern without automatically assuming malicious intent.
Redirect. Provide appropriate public information or offer a legitimate way to obtain assistance without disclosing sensitive operational details.
Assess. Consider the entire interaction. Is the person accepting assistance? Are the questions becoming more intrusive? Is there a pattern of behavior that warrants attention?
Report. When the interaction raises a legitimate safety concern, communicate the relevant facts through the church's established reporting procedures.
These principles should be practiced during team training rather than simply handed out as a written policy. Members need to become comfortable setting boundaries without sounding accusatory, particularly when interacting with frustrated or persistent individuals.
The objective is not to win the conversation or outsmart the visitor. It is to remain welcoming, protect sensitive information, and recognize when additional action is appropriate.
Train for Conversations, Not Just Confrontations
Church safety training often emphasizes physical security, emergency response, and use-of-force considerations. Those subjects are important, but they don't address every situation team members will encounter.
In reality, most LSMT interactions involve ordinary people and ordinary conversations.
That's precisely why conversational awareness deserves training time.
An instructor could present a fictional exchange between a visitor and a receptionist, then ask the team to identify which information was appropriate to share and where the conversation began moving into sensitive territory. Another exercise might involve a frustrated visitor seeking access to a staff member, allowing participants to practice listening, clarifying concerns, and maintaining appropriate boundaries.
These exercises don't need to become elaborate productions. A few minutes of realistic role-play, followed by a thoughtful discussion, can reveal weaknesses that might never surface during a lecture.
And while online instruction can introduce elicitation concepts, there's real value in practicing conversations face-to-face. Tone, timing, listening, and judgment are difficult to evaluate through a multiple-choice test.
Team members should receive constructive feedback on how they communicate, not simply whether they remembered the correct terminology.
Don't Turn Elicitation Awareness Into Paranoia
There is one caution that deserves particular emphasis.
Once people learn about elicitation techniques, they may begin noticing them everywhere. A visitor asks about the pastor. Someone makes an incorrect statement. Another person asks how many people attend the church.
Suddenly, every conversation looks suspicious.
That's not the objective.
Most people asking questions about a church have perfectly legitimate reasons for doing so. They may be looking for help, considering membership, trying to contact someone, or simply making conversation.
The presence of a recognizable elicitation technique does not establish malicious intent. Many of these conversational behaviors occur naturally, without any deliberate effort to obtain sensitive information.
LSMT members should therefore focus on patterns, context, and the nature of the information being requested rather than treating individual questions as warning signs.
We want teams that are observant and thoughtful, not teams that make visitors uncomfortable because they've decided everyone is hiding something.
Leadership Takeaway: What Should Your Church Do Now?
Church leaders should recognize that protecting sensitive information is not solely the responsibility of the Life Safety Ministry Team. Greeters, receptionists, children's ministry volunteers, administrative staff, and even well-meaning congregation members may unintentionally disclose information that could compromise church safety.
Start by identifying what information should remain confidential, particularly details involving security procedures, staffing assignments, restricted access, and the private routines of church leadership. Make sure volunteers understand those boundaries and know how to respond when someone asks questions they aren't authorized to answer.
Then practice. Incorporate short, realistic conversational scenarios into LSMT training and include other ministry volunteers whenever possible. Teach them to recognize elicitation techniques, maintain a welcoming attitude, and report concerning patterns without jumping to conclusions.
Here's the question leadership needs to answer: If someone walked into your church this Sunday and began casually gathering information about your security arrangements, would your volunteers recognize what was happening—or would they unknowingly help?
That's a conversation worth having before Sunday morning.
Final Thoughts
Church safety isn't limited to what happens during an emergency. Much of it involves the small decisions people make during an ordinary Sunday morning, including what they notice, what they communicate, and what information they choose to share.
Elicitation is worth understanding because it reveals something important about human behavior: people often provide information more freely during a comfortable conversation than they would in response to a direct request.
That can be useful when a team member is trying to understand someone's concern. It can also create vulnerabilities when sensitive church information is shared without considering who needs it or why.
The solution isn't to discourage conversation. Quite the opposite. LSMT members should become better communicators, more attentive listeners, and more thoughtful observers.
They should also recognize that friendliness and discretion are not mutually exclusive.
Not every question is suspicious. Not every friendly conversation is harmless. And being helpful doesn't mean telling someone everything you know.
Sometimes protecting the congregation begins long before an emergency, with nothing more complicated than recognizing where a conversation is going and knowing when enough information has been shared.
If this guide would help your pastor, ministry leaders, or Life Safety Ministry Team, please share it with them. Visit trinitysafetygrp.com for more practical guidance and training resources to help your church prepare.