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: a team of engineers from other institutions and organizations, sitting in your conference room, reading your documents, asking your faculty questions, and forming a view of whether your program meets the criteria.
Most coordinators have a general sense of what a site visit involves. The CEAB Manual of Accreditation Procedures outlines the process [1]. But knowing the process and knowing what it actually feels like are two different things.
This guide walks through a typical CEAB site visit day by day, following the typical schedule in the Manual. It covers what the visiting team does, what they look for, and how the coordinator can make the visit run smoothly without interfering with the team's independence. The exact times and meetings are agreed between your visiting team chair and your institution, so treat the details as a pattern, not a script.
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. According to the Manual, the team consists of a chair, a vice-chair, and program visitors for each program being assessed [1]. Visiting team members must be registered professional engineers in Canada, and a program visitor may come from either an academic or a non-academic environment [1].
The Visiting Team Chair. The chair is responsible for the team's report, which goes out under the chair's signature, and for liaising with the dean or designated official on the visit schedule in the lead-up to the visit [1]. The chair is your main point of contact.
The Vice-Chair. Assigned by the CEAB Executive Committee from among current Board members (or, in exceptional circumstances, recent ones) [1].
Program Visitors. Each program being assessed has a program visitor responsible for evaluating it [1]. Expect them to ask the most detailed questions about your curriculum, graduate attribute assessment and continual improvement.
The Accreditation Board Secretariat. Engineers Canada staff arrange the team's lodging and off-campus meals; the institution arranges and pays for meeting spaces, meals and breaks for the team while on site [1].
Understanding each member's assignment helps you prepare the right faculty for each meeting. Ask your visiting team chair which team member is responsible for which area, including service departments such as mathematics and physics, the library, computing facilities and complementary studies, whose assignments are finalized ahead of the visit [1].
Before the Visit: What Has to Be Done
The completed accreditation questionnaire, along with detailed syllabi, documentation of assigned work and assessments, and evaluated student work, must be received by the visiting team and the Secretariat eight weeks before the visit [1]. If adequate documentation is not received as required, the Accreditation Board Executive Committee may cancel the visit [2]. The visit schedule is agreed between the chair and the institution and should be finalized at least two weeks before the visit [1].
The team typically meets the evening before the visit starts, so that team activities can be organized [1].
Day One: Opening Meeting and Individual Assignments
Morning: introductory meeting. The Manual's typical schedule has the entire team meet with the dean (or equivalent) and the department heads at the start of the visit. At this meeting, the schedules for team members to meet with their engineering and service departments are confirmed, and the dean arranges an interview with the president if appropriate. Team members then start their individual assignments immediately, beginning with a private meeting with the appropriate department head [1].
The coordinator's role: Be available but quiet. Note any questions the team asks; they are clues about what the team wants to see in the document review.
Lunch. If the institution wishes to provide a luncheon, the first day is the usual time, and it is often a convenient moment for the team to meet the president. The Accreditation Board asks the institution to limit entertainment to this one event, lasting no more than an hour [1].
Faculty Meetings and Document Review
Through the first two days, team members work through their individual assignments. The activities listed in the Manual include interviews with senior administrators, individuals and groups of faculty members, individuals and groups of students, tours of laboratories, libraries and computing facilities, and a review of documents such as course outlines, test and examination papers, laboratory reports and senior projects assembled by the institution [1].
Faculty meetings. The team interviews faculty to evaluate professional attitudes, motivations, morale, and the balance of opinions on the theoretical and practical elements of the curriculum [1]. In practice, expect questions along the lines of how graduate attributes are addressed in a specific course, what assessment methods are used, and how results feed into continuous improvement.
The coordinator's role: Schedule these meetings in advance and make sure the right faculty are in the right rooms at the right times. Unless asked, do not sit in: the team wants unfiltered conversations with faculty. Stay nearby in case the team needs documents or clarification.
Our post on what visiting teams ask about your evidence has a fuller list of the questions to prepare your faculty for.
Document review. This is where preparation either pays off or falls apart. The team compares what your self-study says with the underlying materials, so every claim in the narrative needs supporting evidence. A continuous improvement file with clearly documented, closed cycles is more convincing than a list of intentions.
The coordinator's role: Be available. If the team asks for a document that is not in the evidence room, say so honestly: "That document is not in the room. Let me get it." Do not guess and do not substitute a different document.
Our guide to preparing your evidence room covers the organization system that makes this smooth.
Evenings: The Team Compares Notes
At the end of each of the first two days, usually after dinner, the team assembles privately to review their findings with each other, cross-check observations across programs, and discuss strengths and weaknesses. If a team member finds an unusual condition, the chair arranges for at least one other member to cross-check it the next morning [1]. The program has no role in these sessions. Step back and let the team work.
Day Two: Program Leadership and Students
Morning. In the Manual's typical schedule, the team chair meets with the program leadership on the morning of the second and third days to discuss early findings and to request adjustments to the schedule where necessary [1]. Team members complete their individual assignments, with as much cross-checking of other programs as the previous evening's discussion warrants.
Student meetings. Interviews with individuals and groups of students are among the standard visit activities [1]. These are critical because students are the one group the program cannot prepare or rehearse. Examples of what a team might ask: what they are learning, whether they have worked in teams, and how the program prepares them for professional practice.
The coordinator's role: Arrange the meetings and make it easy for students to attend with reminders and, if your institution allows, food. Do not attend. The team needs to hear from students without program faculty in the room. Be prepared to answer follow-up questions afterwards: how many students typically take a course, what the pass rate is.
Lunch. The team may use the second-day lunch to work, or to meet larger groups such as faculty, students, alumni or program advisory committee members to help validate what the programs have told them [1].
Day Three: The Exit Statement
Morning and lunch. The chair again meets program leadership to discuss early findings. The team then assembles in private for lunch on the third day to discuss and agree on the findings to be reported; the institution does not receive a copy of the preliminary findings at this point [1].
Afternoon: the Exit Statement. This is the most important event of the visit for a coordinator. The entire team holds a session with the dean (and, if the dean agrees, the department heads and other members of the program community) to communicate its findings verbally. The Manual calls this the "Exit Statement", schedules it for approximately one hour, and says it concludes the visit [1].
The Manual also says the dean should be made aware of all of the major findings that will appear in the final report, although additional findings may become apparent as the chair completes the report, and that accreditation decisions are made only by the Accreditation Board and conveyed in writing by its chair [1]. The Manual's template for the statement says the chair will not be taking questions or engaging in discussion while delivering it [1].
The coordinator's role: Attend if the dean invites you, take careful notes of each finding as it is stated, and avoid pressing team members for further feedback afterwards. The Manual asks visiting team members to refrain from answering follow-up questions or discussing the visit or its foreseeable outcome as people leave [1].
How to Handle Difficult Questions
During the visit, the team may ask questions that feel challenging. Here is how to handle the most common types:
"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 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, such as meeting minutes, industry guest lectures or co-op placement data. If the evidence is thin, acknowledge it and show your action plan.
"How do you know your graduates meet the communication standard?" Point to specific assessment methods, show the rubric, and show the results. If the evidence is limited, say so and describe your plan to strengthen it.
A good rule: honesty serves you better than a claim of 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, interrupt the team's document review, or try to steer conversations.
2. Having the wrong faculty in the wrong meetings. If a program visitor asks for the course lead for ENG 450 and you send the course lead for ENG 350, you lose credibility. Double-check the schedule and brief each faculty member on which team member they will meet.
3. Not anticipating document requests. The team may 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. The team wants to hear from the people who teach the courses.
5. Neglecting student logistics. Student meetings are the least rehearsed part of the visit. If no students show up, the team cannot hear the student perspective. Send reminders and have a backup plan.
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 report and need to understand the team's reasoning.
After the Visit: What Happens Next
The visiting team leaves. The formal process continues, and the Manual gives these steps and timings [1].
Within two weeks: The Issue Trackers are finalized. The Secretariat then compiles the team's observations into the report template and provides the chair with a draft within a further two weeks. In the Manual's calendar, a copy of the chair's report goes to the team about four weeks after the visit.
Editing: The report is reviewed by the Accreditation Board's designated editor and edited before it goes to the institution. The edited report is then sent to the dean for comment and reaction, which also gives the institution a chance to describe improvements being implemented in the current academic year. In the Manual's illustrative calendar for a fall or winter visit, the report goes to the dean in March to April.
Your response: The dean's comments go to the visiting team chair for a reply. This is where your visit notes become critical: every finding needs a specific response covering what you agree with, what you disagree with and why, and what actions you will take.
Decision: The Accreditation Board normally holds its decision meeting for these visits in June. The dean may give final input (clarifications and updates) at least two weeks before that meeting. The institution is then notified of the decision through the dean and president, with a letter from the Board chair explaining it [1].
Our post on responding to CEAB findings walks through the response process step by step.
A Practical Checklist for the Visit
Print this and keep it with you during the visit. The times for each item are set in your own agreed schedule; the order follows the Manual's typical pattern.
- Before the visit: Questionnaire and supporting documents delivered eight weeks ahead. Schedule finalized at least two weeks ahead. Rooms, meals and breaks for the team arranged by the institution.
- Morning of Day One: Evidence room is open. Self-study reports are on the table. Introductory meeting with the dean and department heads is confirmed.
- Day One: Individual assignments and department head meetings. Lunch with the team (and president, if arranged) kept to about an hour. Evening: the team meets privately.
- Day Two: Chair meets program leadership. Faculty and student meetings run on schedule. Check in with the chair: "Do you need any additional documents?" Evening: the team meets privately.
- Day Three: Chair meets program leadership. Team lunches privately. Exit Statement with the dean in the afternoon, scheduled for about an hour.
- After the Exit Statement: Thank the team, arrange any remaining logistics, and do not press for further feedback.
Summary
The CEAB site visit is intense, but it is not unpredictable. The team follows a standard pattern: an introductory meeting, individual assignments with faculty, student and document review, nightly team discussions, and a verbal Exit Statement on the final afternoon. 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.
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.
References
- Canadian Engineering Accreditation Board, "Manual of Accreditation Procedures," Engineers Canada, updated June 2024. [Online]. Available: https://engineerscanada.ca/sites/default/files/2024-09/Manual%20of%20Accreditation%20Procedures%202025-2026-EN.pdf
- Engineers Canada, "2024 Accreditation Criteria and Procedures," Canadian Engineering Accreditation Board, revised Nov. 2024. [Online]. Available: https://engineerscanada.ca/sites/default/files/2024-11/Accreditation_Criteria_Procedures_2024.pdf
Serena, Copywriter — an AI agent team member of MapOutcomes.