The Gap Between Preparation and Reality
You have spent months preparing. The self-study report is polished. The evidence room is organized. The faculty are briefed. The countdown is over.
Then the visiting team arrives.
And suddenly the abstract concept of "the visit" becomes very concrete: four or five senior academics from other institutions, sitting in your conference room, reading your documents, asking your faculty questions, and forming opinions about whether your program meets the standard.
Most coordinators have a general sense of what a site visit involves. The CEAB Manual of Accreditation Procedures outlines the process. But knowing the process and knowing what it actually feels like are two different things.
This guide walks through a typical two-day CEAB site visit hour by hour. It covers what the visiting team does, what they ask, what they look for, and how the coordinator can make the visit run smoothly without interfering with the team's independence.
Our 90-day visit preparation plan covers the months leading up to this moment. This post covers the visit itself.
Who Is on the Visiting Team?
Before the team arrives, understand who you are hosting. A typical CEAB visiting team has four to six members:
The Team Chair. Usually a senior academic from another Canadian engineering program. They lead the team's deliberations, coordinate the schedule, and sign the draft report. The chair is your main point of contact during the visit.
Discipline Representatives. One or two faculty members who have specific expertise in your program's discipline (civil, mechanical, software, etc.). They will ask the most technical questions about curriculum content, graduate outcomes, and assessment methods.
The Basic Sciences Representative. A faculty member from a math, physics, or chemistry department. They review how your program integrates foundational sciences and whether the mathematical and scientific preparation is sufficient.
The Industry Representative (optional but common). A practicing engineer who provides perspective on whether your graduates are prepared for professional practice. They will focus on the program's connection to the profession, co-op placements, and whether the curriculum reflects current industry needs.
Understanding each member's role helps you prepare the right faculty for each meeting. The discipline representatives need to speak with your course leads. The basic sciences representative needs math and physics faculty. The industry representative wants to hear from career development staff and recent graduates.
Day One Morning: Arrival and Opening Meeting
8:00 AM — The team arrives. The coordinator greets the team at the department office. This is a brief, courteous introduction. The coordinator offers coffee, shows the team to the evidence room, and gives them the self-study report (if not already provided digitally). The team usually wants time to settle in and begin reading before any formal meetings.
8:30 AM — Opening meeting with the department. The team meets with the full department: department chair, associate/deputy chairs, program director, coordinator, and senior faculty. This meeting lasts 30–45 minutes.
What happens: The department chair gives a brief overview of the program: enrollment trends, recent curriculum changes, notable achievements, and any challenges. The team chair may ask clarifying questions. The coordinator is not expected to present — this is the chair's moment.
What the team is listening for: Does the chair understand the accreditation process? Can they articulate the program's strengths without over-selling? Are they honest about weaknesses? A chair who says "everything is perfect" raises more suspicion than one who says "we are working on strengthening our communication outcomes in the second-year design course."
The coordinator's role: Sit quietly. Take notes on any questions the team asks — these become clues about what they want to see in the evidence review later.
Day One Mid-Morning: Faculty Meetings
9:30 AM — 11:30 AM — Structured faculty meetings. The visiting team will typically hold two to three separate meetings with faculty groups. These are the most important conversations of the visit.
Meeting 1: Course leads and upper-year faculty. The discipline representatives will meet with the faculty who teach the core upper-year courses. They want to understand how graduate attributes are addressed in specific courses, what assessment methods are used, and how the results feed into continuous improvement.
What they ask: "How do you assess critical thinking in your design course?" "Can you show me an example of a student project that demonstrates this learning outcome?" "How have you changed the course based on assessment results?" "What evidence do you keep to show that students are meeting these outcomes?"
Meeting 2: Basic sciences faculty. The basic sciences representative meets with math, physics, and chemistry faculty. They want to verify that the foundational preparation is rigorous and sufficient.
Meeting 3: Career development and industry liaisons. If there is an industry representative on the team, they may meet separately with career development staff, co-op coordinators, and faculty who have industry connections.
The coordinator's role: Schedule these meetings in advance. Ensure the right faculty are in the right rooms at the right times. Do not attend unless asked — the team wants unfiltered conversations with faculty. However, stay nearby in case the team needs documents or clarification.
Our post on what visiting teams ask about your evidence has a full list of the questions to prepare your faculty for.
Day One Afternoon: Evidence Review
1:30 PM — 4:30 PM — The evidence review. This is where preparation either pays off or falls apart. The visiting team spends the afternoon reviewing the documents you have organized in the evidence room.
What they review first: The self-study report. They will read it cover to cover, checking for internal consistency, completeness, and alignment with the CEAB criteria. Any claim in the narrative needs supporting evidence in the appendices.
What they review next: Course outlines. They will pull random courses from the curriculum map and check whether the outline matches what the self-study report says the course covers. If the report claims that GA 5 (Communication) is addressed in ENG 350, they will open the ENG 350 outline and look for communication learning outcomes and assessment tasks.
What they review after that: Assessment evidence. Exam papers, assignment rubrics, student work samples, capstone project reports. They are looking for evidence that the assessment methods actually measure the claimed learning outcomes.
The continuous improvement file. This is often the most revealing document. The team will look at your CI actions: what was identified, what was changed, and what evidence shows the change worked. A program with three to five fully closed CI cycles looks very different from one with a list of intentions and no follow-through.
The coordinator's role: Be available. The team will call you when they need a document. If you have organized the evidence room well, you should be able to produce any requested document within two minutes. If you cannot find something quickly, say so honestly: "That document is not in the room. Let me get it." Do not guess, do not substitute a different document, and do not panic. The team understands that not everything will be instantly retrievable.
Our guide to preparing your evidence room covers the organization system that makes this afternoon smooth.
Day Two Morning: Student Meetings
9:00 AM — 11:00 AM — Student meetings. The visiting team will hold at least two meetings with students: one with upper-year students (third and fourth year) and one with first- and second-year students. These meetings are critical because students are the one group the program cannot prepare or rehearse.
What the team asks students: "What are you learning in your courses?" "Can you give an example of an assignment that made you think critically?" "Have you had opportunities to work in teams?" "How does the program prepare you for professional practice?" "Are you aware of the graduate attributes your program claims to develop?"
What the team is listening for: Consistency. If the self-study report claims that teamwork is developed throughout the program, but students say "we never work in groups," that is a red flag. If the report emphasizes communication outcomes but students cannot describe a single communication assignment, that is another gap.
The coordinator's role: Arrange the meetings. Ensure good attendance — send reminders, offer course credit or food, make it easy for students to show up. Do not attend the meetings. The team needs to hear from students without program faculty in the room. However, be prepared to answer follow-up questions after the meeting: "How many students typically take this course?" "What is the pass rate?"
Day Two Late Morning: Closing Meeting and Private Deliberation
11:00 AM — 11:30 AM — Closing meeting. The team meets briefly with the department chair and coordinator. This is not the findings meeting — the team does not share their assessment yet. The closing meeting is a courtesy: the team chair thanks the department, confirms that they have everything they need, and outlines the timeline for the report.
What the team says: "We have completed our scheduled meetings. We will now deliberate privately and produce a draft report. You should expect to receive preliminary findings within [X] weeks. The formal CEAB report will follow the standard timeline."
11:30 AM onwards — Private deliberation. The team retreats to a private space (usually their hotel conference room) to discuss their findings, draft the report, and reach consensus. This deliberation may continue into the afternoon or evening. The program has no access to this process.
The coordinator's role: Thank the team for their time. Offer to arrange transportation, dinner, or any final logistics. Then step back. The team needs privacy to deliberate, and pressing for early feedback is counterproductive.
How to Handle Difficult Questions
During the visit, the team may ask questions that feel challenging. Here is how to handle the most common ones:
"We notice that this course outline is from 2022. Has the course changed since then?" Answer honestly. If the course has changed, explain what changed and why. If the outline in the evidence room is not current, acknowledge it: "That is an older version. The current outline reflects [changes]. I can pull the current version."
"Your self-study report claims strong industry engagement, but we only see one advisory board member. How active is this engagement?" Do not defend or argue. Provide additional evidence if you have it: meeting minutes, industry guest lectures, co-op placement data. If the evidence is thin, acknowledge it: "You are right that our advisory board is small. We are working to expand it. Here is our action plan for the coming year."
"How do you know your graduates meet the communication standard?" Point to specific assessment methods: technical reports, presentations, peer reviews. Show the rubric. Show the results. If the evidence is limited, say so and describe your plan to strengthen it.
The key principle: visiting teams respect honesty more than perfection. A coordinator who acknowledges a gap and shows a plan to fix it leaves a better impression than one who claims everything is fine when it is not. Our post on proactive risk management covers how to identify and address gaps before the team arrives.
Common Mistakes Coordinators Make During the Visit
1. Over-managing the schedule. The coordinator's job is to facilitate, not control. Do not hover in faculty meetings. Do not interrupt the team's evidence review. Do not try to steer conversations. The team needs independence to form their own judgment.
2. Having the wrong faculty in the wrong meetings. If the discipline representative asks for the course lead for ENG 450 and you send the course lead for ENG 350, you lose credibility. Double-check the schedule. Brief each faculty member on which team member they will meet.
3. Not anticipating document requests. The team will ask for documents you did not expect: a specific exam paper, a capstone project report, an assessment rubric from two years ago. Organize the evidence room by graduate attribute and by course so that any document can be found quickly.
4. Trying to pre-answer the team's questions. When a team member asks a faculty member a question, let the faculty member answer. Do not jump in with the "correct" answer. The team wants to hear from the people who teach the courses, not from the coordinator.
5. Neglecting student logistics. Student meetings are the least rehearsed part of the visit. If no students show up, the team cannot assess student learning from the student perspective. Send reminders, offer incentives, and have a backup plan (recorded student interviews, if in-person attendance is low).
6. Not documenting the visit. Take notes on every question the team asks, every document they request, and every observation they make. These notes become invaluable when you receive the findings report and need to understand the team's reasoning.
After the Visit: What Happens Next
The visiting team leaves. The formal process continues:
Week 1–2: The team finalizes their draft report. The coordinator should send a thank-you email to the team chair and confirm the expected timeline for receiving findings.
Week 3–6: The program receives preliminary findings from CEAB. This is not the final decision — it is the team's assessment, which the program can respond to.
Week 6–12: The program submits a response to the findings. This is where your visit notes become critical. Every finding needs a specific response: what you agree with, what you disagree with (and why), and what actions you will take.
Our post on responding to CEAB findings walks through the response process step by step.
A Practical Checklist for Visit Day
Print this and keep it in your pocket during the visit:
- Before 8:00 AM: Evidence room is open. Self-study reports are on the table. Coffee and water are available. Parking passes are ready.
- 8:00 AM: Greet the team. Introduce yourself. Show them to the evidence room. Give them 30 minutes of quiet reading time.
- 8:30 AM: Opening meeting. Chair presents. Coordinator takes notes.
- 9:30 AM: Faculty Meeting 1 (course leads). Coordinator is outside, available.
- 10:30 AM: Faculty Meeting 2 (basic sciences). Verify room setup.
- 11:00 AM: Faculty Meeting 3 (industry/career). Confirm attendees.
- 12:00 PM: Lunch. Offer to arrange catering. The team may want to eat together or separately — ask their preference.
- 1:30 PM: Evidence review begins. Coordinator is in the evidence room or immediately adjacent.
- 3:00 PM: Check in with the team chair: "Do you need any additional documents?"
- 4:30 PM: Evidence review wraps. Confirm Day 2 schedule.
- Next morning 9:00 AM: Student Meeting 1 (upper-year). Verify attendance.
- 10:00 AM: Student Meeting 2 (first/second-year).
- 11:00 AM: Closing meeting. Thank the team. Arrange logistics.
- 11:30 AM: Team deliberates privately. Coordinator steps back.
Summary
The CEAB site visit is intense, but it is not unpredictable. The team follows a standard process: arrival, opening meeting, faculty meetings, evidence review, student meetings, closing meeting, private deliberation. Your job as coordinator is to make each step run smoothly without interfering with the team's independence.
The three things that separate a smooth visit from a stressful one are: organized evidence, prepared faculty, and a coordinator who knows when to step in and when to step back.
If you have spent the last 90 days preparing, the visit itself is just the execution. Trust your preparation. Stay calm. Be honest. And remember: the visiting team wants your program to succeed. Their job is to verify, not to trap.
The self-study report is the document the team will reference throughout the visit. Our section-by-section guide to what to include in your accreditation self-study report will help you ensure every claim is backed by evidence before the team arrives.