Preparing Your People With a Mock Site Visit
Hello, everyone! Over the past two blogs, we've been looking at mock site visits as an additional step your program can take when preparing for an ARC-PA site visit. We've talked about rehearsing the process and ensuring the documentation you've carefully assembled can demonstrate what your program does in a way that an outside viewer understands. Now, let’s talk about preparing your people.
Faculty, staff, senior administrators, preceptors, and students may all participate in interviews during the site visit. They know your program from very different perspectives, and they may be asked questions about their roles, experiences, responsibilities, and understanding of how the program operates. While they may know those things very well, that doesn't necessarily mean they're ready to answer questions.
Preparation Comes Before Practice
By the time your program reaches the mock site visit, preparing your people shouldn't be a brand-new idea. During the consulting process, you've likely spent time helping the different groups involved in your program understand that the ARC-PA site visit is coming, what the process involves, and what they should understand about the program and the importance of their own roles within it. This groundwork matters.
But understanding what may be expected of you and experiencing it firsthand are two different things.
You can discuss the kinds of questions someone might encounter. You can remind participants to listen carefully, answer what is actually being asked, and avoid guessing about something they don't know. You can make sure everyone understands the important policies and processes related to their role.
Then someone sits across from them and actually asks the question. Suddenly, eyes are watching, sometimes taking notes, and a perfectly ordinary response can feel enormously consequential.
Whew! That’s a lot of pressure. And that's why practice becomes valuable.
Practice, Not a Script
A mock interview isn't meant to teach participants a set of approved answers. In fact, memorized answers can defeat the purpose. Rather, the goal is to help participants become comfortable listening carefully to the question, thinking about what is actually being asked, and answering accurately from their own knowledge and experience.
Site visit questions don't always sound like compliance questions. A senior administrator might be asked about institutional support or the greatest challenges the program may face in the coming years. Faculty may be asked how they contribute to curriculum improvement, what happens when a student struggles, or how the program incorporates their input. A preceptor may be asked about communication with the program. Students may be asked about policies, resources, or their experiences.
Those questions can sound deceptively simple. But answering them well may require participants to understand not only their own experiences, but how those experiences fit into the program's processes.
A practiced interviewee is less likely to be blindsided. They haven’t rehearsed what to say; they’ve practiced how to respond. Sometimes that means giving a concise answer and stopping; sometimes it means asking the interviewer to clarify the question. Sometimes the correct answer is simply, “I don't know,” rather than guessing about something outside one’s knowledge or responsibility.
Participants can also practice another surprisingly useful skill: recovering when an answer doesn't come out quite the way they intended. One unexpected question needn’t derail an entire interview. Experience makes it easier to pause, clarify, correct yourself if necessary, and move on.
Let the Nerves Happen During the Rehearsal
The actual site visit will still matter. People may still be nervous, and no rehearsal can predict every question they'll encounter. But the real site visit doesn't have to be the first time they've sat across from someone asking accreditation-related questions.
After a mock visit, they've experienced the rhythm of an interview. They've learned that a pause before answering isn't a catastrophe. They've discovered whether they tend to talk too much when they're nervous, or answer so briefly that important information never makes it into the conversation. There’s a reason lawyers prepare their clients before testimony: even knowledgeable people can find formal interviews nerve-wracking.
Most importantly, your people have an opportunity to learn from that experience when nothing is yet riding on the outcome.
Conclusion: Mock Site Visits Are a Distinctive Layer of Preparation
I’m glad that you’ve taken the time to read this series about what a mock site visit can achieve. When the stakes are high, knowing you're ready matters.
Working with Scott Massey PhD, LLC helps your program understand the Standards, evaluate its processes, assemble its evidence, and prepare for review. A mock site visit doesn't replace that work or repeat it.
Instead:
You test your documentation.
You test your logistics.
You test your people’s readiness.
You put the entire site visit plan in motion.
Choosing not to conduct a mock visit doesn't necessarily mean your program is unprepared. But it does mean giving up this distinctive layer of review and protection: an additional opportunity to uncover vulnerabilities, test your preparation, and give your people valuable experience before the actual review.
I hope this series has helped you better understand what a mock site visit can offer your program. As always, our team at Scott Massey PhD, LLC is here to help you prepare for the accreditation challenges ahead.
