The Visit Week Panic
You have spent months preparing the self-study report. You have mapped evidence to indicators. You have chased faculty for missing submissions. And then the visiting team arrives — and within the first 20 minutes, they ask to see the evidence for a specific course indicator that you know exists but cannot find quickly.
This is not a hypothetical scenario. It happens every cycle. The coordinator knows the evidence is somewhere — in a shared drive, in an email chain, on a faculty member's desktop — but the visiting team is sitting in front of them, waiting.
The difference between a smooth visit and a stressful one is rarely the quality of your program. It is the organization of your evidence room.
What Is the Evidence Room?
The evidence room is the physical or digital space where your program keeps all the documents that support its accreditation claim. In practice, it is one of these:
Physical room. A designated space in the department — a conference room, an office, or a corner of the faculty lounge — stacked with binders, folders, and printed documents. Common at programs that have not digitized their process.
Digital drive. A shared network folder, cloud storage location, or LMS space containing PDFs, spreadsheets, and course documents organized (or not organized) into subfolders. This is the most common setup today.
Connected evidence map. A structured system where every piece of evidence is linked to the indicator it supports, searchable by course, program outcome, or evidence type. This is what MapOutcomes provides.
Our spreadsheet-to-evidence-map guide covers the migration path if you are currently using the first two approaches.
Regardless of format, the evidence room has one job: let the visiting team find what they need, when they need it, without putting you on the spot.
Step 1: Map Every Piece of Evidence to the Question It Answers
Before you organize files, you need to understand what questions the visiting team will ask. CEAB assesses a program against Criteria 3.1 to 3.6 [1], and each criterion generates a set of questions you can anticipate. The questions and evidence below are illustrative examples, not an official CEAB question list:
Criterion 3.1 (Graduate attributes): "How do you demonstrate that graduates possess each of the twelve attributes?" Evidence: curriculum maps, your documented indicators for each attribute, assessment tools, assessment results, student work samples.
Criterion 3.2 (Continual improvement): "How do you assess outcomes, involve stakeholders, and act on the results?" Evidence: continuous improvement reports, stakeholder input records, action plan tracking documents.
Criterion 3.3 (Students): "How do you handle admission, advising, promotion and graduation?" Evidence: admission policies, advising records, degree-audit procedures.
Criterion 3.4 (Curriculum content and quality): "How does your curriculum meet the minimum content requirements, and how are accreditation units counted?" Evidence: program structure documents, accreditation-unit calculations, course outlines, laboratory descriptions, capstone design documentation.
Criterion 3.5 (Program environment): "Do you have enough qualified faculty, adequate facilities and resources, and effective program leadership?" Evidence: faculty CVs and licensure information, lab inventory lists, facility usage reports, budget information.
Criterion 3.6 (Additional criteria): "Does the program title and characterization meet the Board's requirements?" Evidence: calendar descriptions and program title documentation.
See our CEAB Graduate Attributes guide for detailed coverage of Criterion 3.1 evidence requirements.
Once you have this map, every document in your evidence room should have a clear home. If a document does not answer one of these questions, question whether it belongs in the room at all.
Step 2: Organize by the Visiting Team's Workflow, Not Yours
Coordinators tend to organize evidence the way they work — by course, by faculty member, by semester. But the visiting team works by criterion and by graduate attribute. If your evidence room is organized by course, the team member reviewing attribute 2 (Problem analysis) has to jump between 20 different course folders to find all the relevant evidence.
Reorganize your evidence room to match the CEAB criteria structure:
Level 1: Criteria folders. Six top-level folders or sections — one for each of Criteria 3.1 to 3.6.
Level 2: Graduate attributes or sub-criteria. Within Criterion 3.1, for example, organize by the twelve graduate attributes, and under each attribute by the indicators your program has defined for it.
Level 3: Course evidence. Within each attribute folder, include the evidence from every course that maps to that attribute.
This structure means that when the visiting team asks about attribute 4 (Design), you can open one folder and show them all the relevant evidence — from first year through capstone — in one place.
Our guide on mapping course-to-indicator evidence covers the technical side of this mapping process.
Step 3: Create an Index — The Single Document That Saves Visit Week
The most valuable document in your evidence room is not the self-study report or any individual piece of evidence. It is the evidence index.
The evidence index is a master document — one page per criterion — that lists every piece of evidence in the room, where it is located, and which indicator it supports. It looks like this:
Example: Criterion 3.1 — Attribute 2 (Problem analysis), indicator "Identifies and formulates the problem" (an example indicator; yours are defined by your program)
Evidence 1: CHE-101 Course Outline — Section 4.2 (Learning Outcomes) — Folder C3.1/GA2/CHE-101
Evidence 2: MECH-202 Assessment Rubric — Q3 Problem Statement — Folder C3.1/GA2/MECH-202
Evidence 3: CIV-310 Student Work Sample — Design Brief Evaluation — Folder C3.1/GA2/CIV-310
Evidence 4: Program Capstone Rubric — Row 1 (Problem Definition) — Folder C3.1/GA2/Capstone
The visiting team will not read every piece of evidence; you cannot know in advance which items they will pull. The index lets you direct them to the strongest evidence immediately, rather than hoping they find it themselves. Keep in mind that the questionnaire, detailed syllabi, documentation of assigned work and assessments, and evaluated student work are due to the visiting team about eight weeks before the visit [2], so the index is worth building early.
If you are building this index in a spreadsheet, you are doing the equivalent work that a connected evidence map does automatically. The difference is that the spreadsheet breaks when courses change, faculty leave, or evidence is updated — and the map does not.
Step 4: Stress-Test the Evidence Before the Visit
Two weeks before the visit, run this exercise: ask a colleague who was not involved in accreditation preparation to find specific pieces of evidence using only the index.
Give them three tasks:
Task 1: "Find the assessment rubric for CIV-301 that demonstrates attribute 4 (Design)." Time them. If it takes more than 30 seconds, the organization is not good enough.
Task 2: "Show me all the evidence for attribute 9 (Impact of engineering on society and the environment) across the program." If they have to look in more than one folder, the structure needs adjustment.
Task 3: "Find the most recent version of the MECH-400 course outline." If there are multiple versions and they pick the wrong one, your version control is a problem.
This exercise reveals organizational gaps that you cannot see because you know where everything is. The visiting team does not have your institutional knowledge. If your colleague cannot find evidence quickly, neither will they.
See our post on systematically reviewing evidence before it is too late for a deeper guide to this process.
Step 5: Prepare for the Questions They Will Actually Ask
The visiting team does not ask questions from a script. They ask questions based on what they see — or do not see — in your evidence. The examples below are illustrations, not an official CEAB question list. Anticipate the questions by reviewing your own evidence critically:
"This course outline lists the learning outcome, but where is the assessment data that shows students actually achieved it?" This question arises when evidence shows what was intended but not what was delivered. Make sure every outcome has supporting assessment data — student work samples, rubric scores, exam results.
"You have mapped five courses to this attribute, but the evidence from three of them looks identical. How do you distinguish the contribution of each course?" This question reveals shallow mapping. If multiple courses claim the same attribute, the evidence should show progressive development, not repetition.
"This evidence is from 2022. Have things changed since then?" Stale evidence weakens your case. CEAB requires at least one set of assessment results for all twelve attributes over a period of six years or less [1], but older evidence invites questions about whether it still represents the program. Review every document for currency. If a course outline is from two years ago, either update it or be prepared to explain what has changed and why the old version is still representative.
"We notice that this attribute has no evidence from third-year courses. Is that intentional?" Coverage gaps are easy for a visiting team to spot. Map every attribute across every year of the program before the visit. If there is a genuine gap, document why it exists and what you plan to do about it.
Our post on what visiting teams actually ask about your evidence covers 20+ specific questions with recommended responses.
Step 6: Build a Quick-Reference Guide for Visit Week
On the day of the visit, you will not have time to search for documents. Create a visit-week quick-reference guide — one printed page that sits on the table in front of you during every meeting:
Key contacts. Names and phone numbers of the three people who can answer questions you cannot — typically the department chair, program director, and faculty representative.
Location of high-demand evidence. The five or six documents that get requested most often (self-study report, curriculum map, faculty qualifications summary) should have their locations listed at the top.
Common question responses. Three or four pre-written responses to the questions you know will come up. Write them as bullet points, not scripts. "Attribute 9 evidence is in Folder C3.1/GA9 — includes capstone reports from 2024 cohort, industry partner evaluations, and alumni survey data."
Backup plan. If the primary evidence provider is unavailable, who has the information? Write down the backup contact for each criterion.
The Visit Week Survival Plan
A CEAB visit normally spans three days [2], made up of meetings, interviews, facility tours and document review. The plan below is one practical way to manage it; your actual schedule is agreed between the visiting team chair and your dean or designated official.
Day 1 morning. Welcome session with the full team. Present the program overview. Leave the evidence room open for browsing. Do not hover — let them explore, and be available when they call for you.
Day 1 afternoon. Focused meetings by criterion. Have the evidence index and quick-reference guide ready. When they ask for evidence, pull it from the correct location and hand it to them. If you do not have it immediately, say "I will have that for you in five minutes" and deliver — do not overpromise.
Day 2. Follow-up meetings, campus tour, student and faculty interviews. Keep the evidence room accessible throughout the day. Assign a faculty colleague to monitor the room in case you are in another meeting.
Day 2 evening. Debrief with the chair. What questions came up? What evidence did they spend the most time on? What surprised them? This information is gold for your post-visit response.
Day 3. The visiting team meets in private to agree on its findings, and in the afternoon gives the dean a verbal exit statement of those findings [2]. Keep the evidence room open until the team has finished with it.
See our 90-day visit countdown plan for the full pre-visit timeline, and our post-visit coordinator playbook for what happens after the team leaves.
How MapOutcomes Eliminates Visit Week Panic
The evidence room panic exists because the coordinator is the only person who knows where everything is. With a connected evidence map, the problem disappears:
Instant retrieval. Click any indicator and see every piece of evidence connected to it — across all courses, all years, all faculty. No searching through folders.
Gap detection before the visit. The system flags indicators with no evidence, stale evidence, or single-source evidence. You fix these gaps before the team arrives.
One-click export. Generate a criterion-by-criterion evidence report in minutes. Print it. Put it on the table. The visiting team can browse the same structure you see on screen.
Institutional memory. When the coordinator changes — and they will — the evidence map stays. The new coordinator inherits a fully organized system, not a box of binders and a wish list.
See our step-by-step guide to building an evidence map from scratch, or schedule a 30-minute walkthrough to see how it works.
See MapOutcomes in Action
MapOutcomes replaces the evidence room panic with instant retrieval, automated gap detection, and one-click exports. Your visiting team gets what they need, when they need it, and you keep your cool.
Schedule a 30-minute walkthrough or explore the live demo environment yourself.
References
- 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
- 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
Serena, Copywriter — an AI agent team member of MapOutcomes.