Why Staff and Volunteer Interviews Find What Walkthroughs Miss

The building shows the specs. The people show the program.

A walkthrough tells you what a facility has. Interviews tell you how it actually operates. Both are part of a real audit, and the interviews are often the more valuable half.

Staff and volunteers see things every day that leadership does not see. They know the rhythms of the building in ways that a one-day visit cannot surface. They also know the places where the written policy and the real practice have drifted apart, the hallways where something feels off, and the protocols that got quietly dropped when the volunteer who used to enforce them stopped showing up.

An audit that does not talk to the people who work the space is missing half the picture.

Why the walkthrough alone is not enough.

A walkthrough is a snapshot. An auditor walks the building at a specific moment. They see what is happening that day, with those people, at those times. They do not see:

• What happens when the regular usher is out sick and a newer volunteer covers
• Which doors get propped open on a busy Wednesday evening
• The child who was accidentally released to the wrong adult last month, and how the team handled it
• The volunteer whose behavior around children has raised concerns nobody has formally escalated
• The vendor who shows up unannounced and is always waved through

All of those are program-level realities. They live in the memory and experience of the people who work the program, not in the physical structure of the building. The only way to learn them is to ask.

What we ask, and why.

Interview questions are structured to work even when the interviewee is cautious. We do not start with “is anything wrong?” We start with the easier questions and move toward the harder ones as the conversation builds trust.

The easier questions first

• Walk me through your typical week here. When are you present? What is your role?
• What does a normal Sunday (or Monday morning, or typical shift) look like for you?
• Who else is usually in the building when you are?
• What parts of your job involve keeping people or property safe?

These questions are not fishing for problems. They are establishing how the interviewee actually uses the space, which gives everything they say next its proper context.

The middle questions

• Has anything surprised you since you started here? Anything that worked differently than you expected?
• Are there any routines that made sense when you started but feel different now?
• What happens when a new volunteer starts? Who shows them what?
• If there was a medical emergency right now, walk me through what you would do.

These open space for interviewees to name drift, gaps, or discomfort without having to frame anything as a complaint. Often they will describe the program drift we were looking for without ever calling it that.

The direct questions

• Is there a part of your work, or the building, or a time of day, that gives you pause?
• If you could change one thing about security here, what would it be?
• Have you ever seen something and thought "I should say something about that" and then not said it? What was it?
• Is there anyone here whose behavior you would describe as unusual or concerning?

The last question is the hardest one to ask and the most important. Asked well, privately, with confidentiality clearly established, it is the question that has, in our experience, surfaced the most consequential findings.

The conditions that make interviews work.

Interviews only produce useful information when the person being interviewed believes the conversation is safe. That belief is engineered, not assumed.

Confidentiality, named and explained

Before any interview, we state clearly how the conversation will be handled. Names are not attributed in the report. Specific quotes are only used with explicit permission. Patterns across multiple interviews are summarized in a way that does not expose individual sources.

A setting that signals discretion

Interviews happen in a quiet room with the door closed. Not the main office. Not a space where other staff walk past every two minutes. The setting sends the message as clearly as any spoken word.

The right interviewer

The interviewer matters. A team member of the organization cannot reliably run these interviews. A uniformed presence, an imposing persona, or an obviously rushed auditor will all shut down candor. The goal is an interviewer who is calm, unhurried, attentive, and clearly on the interviewee’s side for the duration of the conversation.

No one is skipped lightly

If an interview is requested and the person declines, that is noted and respected. But we generally aim to offer the conversation to anyone whose role gives them meaningful exposure to the space. The person we almost did not interview is often the one whose perspective turned out to matter most.

What gets done with the findings.

Interview findings appear in the audit report as patterns, not as attributed quotes. The report names the gap, the risk, and the recommended action. It does not name the source.

Some findings require immediate handling. If an interview surfaces an allegation of misconduct, a threat to a specific person, or any situation that triggers a mandatory reporting obligation under Florida law, we act on it immediately according to the engagement agreement. Leadership is informed. Appropriate authorities are involved where required. The interviewee’s identity is protected to the extent legally possible.

Most findings are not of that severity. They are drift findings, communication gaps, protocol inconsistencies, or the quieter concerns that deserve attention but not crisis response.

The lessons from Hurricane Ian.

After Hurricane Ian in 2022, we re-interviewed staff at several Southwest Florida clients as part of an after-action review. What those interviews surfaced was consistent. The people closest to the program knew, before the storm, where the plan had gaps. Some of them had mentioned those gaps informally. In most cases, their observations had not made it into any written process.

The lesson is broader than hurricane response. Staff and volunteer observations are a leading indicator of where incidents are going to happen. A periodic interview rhythm is one of the most reliable ways to surface those observations before an event forces the issue.

The proverb is about the multiplication of insight. An organization that only hears from leadership is making decisions with limited counsel. An organization that structures a way to hear from everyone, periodically and safely, is practicing the wisdom the proverb describes.

Running this on your own.

If you cannot run a full interview round right now, a lighter version is still useful:

• Pick three people from different roles: a greeter or usher, a back-office staff member, and a long-tenured volunteer.
• Schedule 30 minutes with each, separately, in a quiet room.
• Ask the four direct questions listed above. Take notes. Do not interrupt.
• Compare notes across the three conversations. Look for patterns.
• Act on whatever emerges, starting with the concerns named by more than one person.

The exercise takes an afternoon. It will tell you more about your program than any survey.

The quiet value of being asked.

A final note on what interviews do beyond producing findings. They tell the people who do the day-in work of your organization that their observations matter. That you wanted to know. That the program is paying attention to what they see.

That signal, received by a committed staff or volunteer, tends to strengthen the very culture the audit is trying to protect. People who feel heard stay engaged. People who feel ignored drift. A security audit that includes good interviews is not just a diagnostic tool. It is a small act of organizational care that pays back well beyond its cost.

If your organization in Fort Myers, Cape Coral, Naples, or Port Charlotte is ready for an audit that takes its people as seriously as its buildings, we would be glad to talk.