The On-Site Accreditation Visit: What Really Happens and How to Prepare for It

The self-study is submitted. The gap analysis is done. The 90-day countdown has run its course. Now the visiting team is on their way, and the most visible, highest-stakes part of the accreditation cycle is about to happen: the on-site visit.

For the coordinator, these few days are both the culmination of months of preparation and a completely new kind of challenge. Everything you have built in documents and spreadsheets now has to hold up in person, under direct questioning from people whose job is to find what is missing.

The on-site visit is where accreditation becomes real. Not because the visiting team discovers something you did not already know, but because it is the moment when all your preparation is tested in the one format that matters: face-to-face conversation with the people who will write the report that determines your program's accreditation status.

Here is what actually happens during an on-site accreditation visit, what the visiting team is looking for in each activity, and how to prepare your faculty, your students, and yourself for the interactions that will shape the final report.

What the On-Site Visit Looks Like: The Schedule

An on-site accreditation visit typically lasts a few days; a CEAB visit normally spans three days [1]. The exact schedule is agreed between the visiting team chair and the dean or designated official [1], and the day-by-day pattern below is typical rather than fixed. Understanding the general shape is the first step to preparing for it.

The visit usually follows this pattern:

Day 1: Opening and Faculty Interviews

The visit begins with an introductory meeting between the visiting team, the dean and the department heads, where the schedules for the team members' meetings are confirmed [1]. The dean or designated senior official should be ready to give a brief welcome and overview of the program.

After the opening, team members proceed with their individual assignments, which include interviews with faculty, students, support departments and administrators [1]. Faculty interviews are where the visiting team tests whether the self-study narrative matches what the people actually doing the teaching know and believe about the program.

Faculty interviews can be with individuals or with groups of faculty members [1]. CEAB visiting team members are experienced engineers from both academic and non-academic settings [1]. They know what a strong program looks like, and they know when a faculty member has not been properly briefed on the accreditation process.

Day 2: Students, Support Staff, and Facilities

The middle of the visit often shifts focus to students and support structures. The visiting team will interview individuals and groups of students [1]. They want to hear about the student experience, the quality of instruction, the adequacy of resources, and whether students feel prepared for professional practice.

The team will also tour facilities — laboratories, workshops, libraries, and any specialized spaces used by the program. This is not a superficial walk-through. Visiting team members will look at equipment condition, safety protocols, student workspace, and whether the facilities match what the self-study claims.

Support staff interviews may include academic advisors, lab technicians, IT support, and administrative staff. The visiting team wants to understand whether the program has adequate support infrastructure and whether the people who maintain it are informed and engaged.

Day 3: Closing and Preliminary Feedback

On the final day the visiting team meets in private to agree on its findings. In the afternoon, the team holds a session with the dean (and, if the dean agrees, department heads and others) to communicate its findings verbally; CEAB calls this the exit statement [1]. It is not the final report, but it is an early signal of how the visit went.

The closing session is formal. It should make clear that accreditation decisions are made only by the Accreditation Board and are conveyed to the institution in writing [1]. After this, the program waits. The decision process takes months, not days (see below).

Faculty Interviews: The Most Critical Part of the Visit

Faculty interviews are among the most telling activities of the visit. This is where the self-study document meets the reality of the people who deliver the program.

The visiting team is testing several things in these interviews:

• Faculty understanding of accreditation. Do the people teaching the courses understand what accreditation is and why it matters? If a faculty member cannot explain the indicators their course maps to, that is a red flag.
• Consistency with the self-study. The self-study claims that the program has a coherent curriculum, strong CI processes, and engaged faculty. The visiting team checks whether individual faculty members' responses are consistent with those claims.
• Evidence of closed-loop improvement. Faculty should be able to describe a time when assessment data led to a curriculum change. If no faculty member can give a concrete example, the visiting team will question whether the CI process is real or just documented for accreditation purposes.
• Faculty involvement in program governance. The visiting team wants to see that faculty are engaged in curriculum decisions, not just implementing directives from above. Programs where faculty are passive participants in the accreditation process make a weaker impression.

How to prepare faculty: Do not script their answers. That backfires — visiting team members can tell when someone is reading from a script, and it raises suspicion. Instead, run a preparation session where you walk faculty through the types of questions they will hear, explain what the visiting team is looking for, and give them the key facts they should be able to discuss: the indicators their courses map to, recent assessment results for their courses, and one concrete example of curriculum improvement driven by assessment data.

A twenty-minute preparation session for each faculty member is enough. Most faculty are genuinely willing to help — they just need to know what to expect and what matters. The coordinator's role is to translate the accreditation framework into language that faculty find meaningful.

Student Interviews: The Wild Card

Student interviews are the most unpredictable part of the on-site visit. Unlike faculty, students have no incentive to be careful with their answers. They will be honest, sometimes brutally so, and the visiting team values that honesty because it gives them an unfiltered view of the program.

Visiting teams use student interviews to assess:

• Student experience and satisfaction. Are students engaged? Do they feel supported? Do they believe the program is preparing them for professional practice?
• Access to resources. Can students actually use the labs, workshops, and facilities described in the self-study? Or do those resources exist on paper but are booked solid or poorly maintained?
• Transparency of learning outcomes. Do students know what is expected of them? Can they articulate the learning outcomes of their courses? Programs that communicate outcomes clearly to students make a stronger impression here.
• Advising and support. Do students have access to academic advising? Do they know who to talk to when they are struggling? The visiting team sees this as a proxy for institutional commitment to student success.

How to prepare students: You cannot, and should not, coach students on what to say. The visiting team knows when students have been coached, and it undermines the program's credibility. What you can do is ensure that students are informed about the visit, understand why accreditation matters for their degree, and know where to find information about learning outcomes and program expectations.

A brief email to all students in the program explaining the purpose of the visit and encouraging honest, constructive responses is appropriate. Do not stage-manage which students the visiting team speaks to. If the team asks for a random selection, provide one.

Facility Tours: What the Visiting Team Actually Looks For

The facility tour is not an architecture review. The visiting team is not evaluating whether your building is beautiful or your labs have the latest equipment. They are checking whether the facilities support the program as described in the self-study.

Three things matter most:

• Adequacy. Does the program have enough lab space, equipment, and workspace for the number of students enrolled? If the self-study claims robust hands-on learning but the labs are overcrowded or shared with other programs, the visiting team will notice.
• Condition and safety. Is the equipment functional? Are safety protocols visible and followed? A lab with broken equipment and no safety signage is a negative signal, even if the curriculum is strong.
• Investment and maintenance. The visiting team looks for evidence that the institution invests in the program. New equipment, maintained facilities, and visible upgrades suggest institutional commitment. Peeling paint and broken furniture suggest neglect.

How to prepare: Walk the facility tour route yourself before the visit. Fix what you can — clear clutter, ensure safety signage is visible, make sure equipment is turned on and functional. Brief whoever is leading the tour so they can explain what each space is used for and how it supports specific program outcomes. Do not show off; show evidence.

The Coordinator's Role During the Visit

The on-site visit is not a hands-off event for the coordinator. You are the program's guide, resource person, and damage controller. Here is what you should be doing during each phase:

Before the Visit Arrives

• Have the self-study ready. The visiting team will ask for specific sections. Have printed copies and digital access available. Know where every piece of evidence is located.
• Prepare the visiting team's workspace. A quiet, well-lit room with power outlets, reliable internet, and copies of the self-study. Small logistics matter — a visiting team that is comfortable is a visiting team that can focus on evaluation, not hunting for a working outlet.
• Brief the point person. The dean or designated official should know the schedule, the visiting team members' backgrounds, and the key messages from the self-study. They will be the face of the program during the opening and closing sessions.

During the Visit

• Be available, not intrusive. The visiting team will need you — to clarify a document, arrange an interview, or locate evidence. Be nearby and responsive, but do not hover during interviews. Faculty and students are more candid when the coordinator is not in the room.
• Listen. Pay attention to what the visiting team asks. Their questions tell you what they are focused on. If they spend extra time on a particular indicator or keep circling back to CI documentation, that is a signal that this is an area of concern.
• Handle logistics smoothly. Schedule conflicts, room changes, and missing documents are the coordinator's responsibility. Anticipate problems before they happen. A visit that runs smoothly reflects well on the program's organizational capacity.

After Each Day

• Debrief with the point person. Share what you observed: which questions the team focused on, which faculty interviews seemed to go well, and any areas where the team seemed unsatisfied. This real-time feedback allows you to adjust the next day's preparation if needed.
• Address gaps immediately. If the visiting team asked for a document you did not have readily available, find it overnight. If a faculty member struggled with a question, brief them on the relevant facts before the next day's interviews.

Common Mistakes Coordinators Make During the Visit

These are common pitfalls that can undermine even well-prepared programs:

Mistake 1: Over-Preparing Faculty

Running a full rehearsal with scripted answers makes faculty sound rehearsed. The visiting team can spot a scripted response from a mile away, and it raises suspicion about the authenticity of the entire program. Brief faculty on the types of questions and the key facts, then trust them to answer naturally.

Mistake 2: Defensive Responses

The visiting team will find things they do not like. That is their job. When they raise a concern, the best response is acknowledgment and a brief explanation. "You are right — that area has been a challenge for us. Here is what we are doing to address it." The worst response is defensiveness. "That is not accurate" or "We have always done it that way" signals a program that cannot see its own weaknesses.

Mistake 3: The Evidence Scramble

The visiting team asks for a document. You know you have it somewhere. It takes forty-five minutes to find. In that forty-five minutes, the visiting team is sitting, waiting, forming an impression that the program is disorganized. Every piece of evidence the self-study references should be instantly accessible — printed, indexed, and ready to hand over.

This is one area where a connected evidence map makes a measurable difference. When evidence is linked to the criteria it supports in a single system, the coordinator can locate and export any piece of evidence in seconds, not minutes.

Mistake 4: Ignoring the Informal Moments

The formal interviews and scheduled activities are only part of the visit. The visiting team also observes the program in the margins — the hallway conversations, the lunch room, the way students interact with faculty. These informal moments often shape the team's impression as much as the formal schedule.

Encourage a welcoming atmosphere. Make sure faculty are approachable, students are visible on campus, and the program's spaces feel lived-in and active. The visiting team is not looking for a performance. They are looking for a program that functions well, and the best evidence of that is a program that looks and feels normal.

What Happens After the Visit

The on-site visit is not the end of the accreditation process. It is the end of the program's active involvement, but the visiting team still has work to do. They will retreat to deliberate, discuss their findings, and draft their report. The report does not arrive within days. After the visit, the visiting team's report is compiled with CEAB Secretariat support, edited, and then sent to the dean for comment. In the Manual's sample calendar for a December visit, the report reaches the dean in March or April, and the Accreditation Board's decision letter follows on June 30 [1].

The report will include:

• Strengths. The perceived strengths of the program, reported alongside areas of conformance to and deviation from the Accreditation Board criteria [1]. These are important — they validate the work you and your faculty have done.
• Areas of concern. Areas where the program deviates from the criteria. These are not necessarily fatal. Under CEAB, if the Accreditation Board judges that there are areas of concern, accreditation may be granted for a term of less than six years, and a limited-term accreditation can be extended once a report shows that the concerns have been resolved adequately [2].
• Suggestions for improvement. The report also includes suggestions for improvement, if any [1]. Addressing them demonstrates a commitment to continuous improvement.

When the report arrives, process it systematically. Document the findings, share them with faculty and leadership, and develop a response plan.

How This Connects to the Rest of the Accreditation Process

The on-site visit is the visible tip of a much larger preparation effort. Every document, every interview, and every facility tour is only as strong as the evidence and processes that support it.

The gap analysis you ran before the visit tells you what evidence the visiting team will test. The 90-day countdown plan ensures that evidence is organized and accessible. The self-study narrative gives the visiting team the story they will cross-reference against faculty and student interviews.

If your preparation was thorough, the on-site visit will confirm what you already know. If your preparation was incomplete, the visit will expose the gaps. The goal is not to present a perfect program — no program is perfect. The goal is to present a program that understands its own strengths and weaknesses, has evidence to support its claims, and has a plan for addressing its areas of concern.

You can read more about the broader preparation process in these posts:

• The Accreditation Visit Countdown: Your 90-Day Preparation Plan — the structured countdown to the visit date
• Writing Your Self-Study Narrative — what visiting teams actually look for in the self-study document

The Bottom Line

The on-site accreditation visit is not something that happens to your program. It is something your program has already prepared for — or has not. Those few days of interviews, tours, and observations are simply the moment when months of preparation are tested in the format that matters most: direct conversation with the people who decide your accreditation status.

The coordinator who enters the visit with organized evidence, prepared faculty, and a clear understanding of what the visiting team is looking for is not entering it with an advantage. They are entering it with what the visiting team expects to find. The surprise — for the program and for the team — comes when the evidence does not match the narrative, when faculty cannot explain their role in the accreditation process, or when the coordinator cannot locate a document that the self-study references.

Avoid those surprises. Build the system that makes them impossible. The visit is only a few days. The preparation is everything.

References

1. Canadian Engineering Accreditation Board, "Manual of Accreditation Procedures (updated December 2025)," Engineers Canada, 2025. [Online]. Available: https://engineerscanada.ca/sites/default/files/2025-10/2025-Manual_of_Accreditation_Procedures-EN.pdf
2. Canadian Engineering Accreditation Board, "2025 Accreditation Criteria and Procedures (revised November 2025)," Engineers Canada, 2025. [Online]. Available: https://engineerscanada.ca/sites/default/files/2025-12/2025-Accreditation_Criteria_Procedures-EN.pdf