8.2 Interviewing Techniques (Not Interrogation)

Interviewing Techniques (Not Interrogation)

Quick Answer: A security officer conducts interviews, not interrogations. An interview is a calm, non-accusatory conversation aimed at gathering facts from a witness, victim, or involved party after an incident. An interrogation is accusatory, presumes the person's guilt, and is generally a law enforcement function outside a Class D officer's role. Good interviewing depends on rapport, a private and calm setting, open-ended questions, and careful listening — not pressure, accusation, or reading body language as proof of lying, since so-called 'deceptive cues' are not reliable indicators of deception and should never be treated as evidence.

Interview vs. Interrogation: A Critical Distinction

These two terms are often confused, and the exam tests the distinction directly:

A Class D security officer's post-incident role is almost always an interview role: talking with witnesses, victims, and other involved parties to build an accurate, factual account of what happened. Officers are not trained interrogators, have no authority to compel a statement, and create serious liability exposure — for themselves and their employer — by pressuring, threatening, or attempting to coerce a confession out of anyone. If a matter clearly calls for interrogation-level questioning of a suspect, the correct step is to secure the scene, protect everyone's safety, and hand the matter to law enforcement or a trained investigator rather than attempting it personally.

Preparing for the Interview

Before starting, an officer should know, as much as possible, what happened, who was involved or present, and what specific facts still need to be established. Interviews go better in a private, calm, and reasonably comfortable setting, away from onlookers, noise, and other distractions that make people self-conscious or guarded. Conducting an interview immediately after an incident, while memory is fresh, produces more accurate and detailed information than waiting — but only if the person is calm enough to speak coherently; a person still in shock or visibly distressed may need a few minutes before a useful interview can begin.

Building Rapport

People share more, and more accurate, information with someone they perceive as fair, calm, and genuinely listening. Rapport starts with basic professionalism: introducing yourself and your role, explaining briefly why you need to talk with them, and using a calm, non-judgmental tone regardless of what the person may have done or witnessed. Active listening — making eye contact, not interrupting, and occasionally paraphrasing back what was said to confirm understanding — signals genuine attention and encourages the person to keep talking. Rapport is not the same as being a pushover; an officer stays professionally neutral and does not take sides, express personal opinions about guilt, or make promises about outcomes the officer cannot control.

The Approach and Question Structure

Most effective interviews follow a general funnel: start broad, then narrow. Begin with open-ended questions that invite a free narrative — "Tell me what happened" or "Walk me through what you saw" — rather than questions that can be answered with a single word. Open-ended questions let the person's own account and word choice come through, which is more reliable and more useful later than answers shaped by the interviewer's assumptions. Once the general account is on the table, narrower closed questions ("What time did that happen?" "Which door did they use?") fill in specific gaps.

A critical technique failure to avoid is the leading question — one that suggests the answer the interviewer expects or wants ("He grabbed the bag with his right hand, correct?"). Leading questions can implant a false detail into a witness's memory or make a statement appear coached or unreliable if challenged later. Skilled interviewers ask neutral versions of the same question ("Which hand did he use?") and let the witness supply the detail.

The Caution on 'Deceptive Cues'

Popular training material and older security curricula sometimes teach that specific body-language signs — avoiding eye contact, crossing arms, fidgeting, touching one's face, or pausing before answering — reliably indicate that someone is lying. This is not supported by reliable research and is a significant exam trap. Nervousness, cultural differences in eye contact norms, anxiety about being questioned at all, and simple personality differences all produce the exact same behaviors in people who are being completely truthful. A well-trained officer treats behavioral observations as, at most, a reason to ask a clarifying follow-up question — never as proof of deception, and never as a basis to accuse someone or escalate the encounter. Basing an accusation on body language alone is both unreliable and a serious liability exposure if the person later claims defamation or wrongful accusation.

Ending the Interview and Documenting It

An interview should end as professionally as it began: thank the person for their time, explain what happens next if appropriate, and provide contact information if follow-up is expected. Whenever practical, have the person review and sign a written statement in their own words, or take detailed contemporaneous notes if a formal statement is not feasible — memory degrades quickly, and a statement taken immediately after an incident is far more valuable later (in a report, a hearing, or a court proceeding) than a recollection reconstructed days afterward. The officer's own incident report should record who was interviewed, when, where, and a factual summary of what was said, without adding personal opinions about who was truthful or at fault. Even an interview that yields little useful information should be documented professionally, because a gap in the record is itself a problem if the incident is later reviewed.