The Friday After the Visiting Team Packs Up
The visiting team leaves Friday afternoon. They've shared some informal impressions over dinner — maybe positive, maybe concerning, maybe both. You shake hands, thank them for their time, and walk them to the door. Then you take a breath and face the next eight to twelve weeks.
For most accreditation coordinators, the next phase of the process looks like this: wait. The official CEAB report is weeks away. There is nothing to do but hope the team saw what you intended and that the draft report reflects a fair reading of your program.
But the coordinators who get the best outcomes know something the others don't: the period between the visiting team leaving and the official report arriving is not empty time. It is the last window where you can influence the findings. Not through lobbying or pressure — but through documentation, preparation, and a clear understanding of what happens behind the scenes.
Our day-by-day guide to the CEAB site visit covers what happens during the visit itself. This post picks up where that one leaves off.
The Timeline You're Facing
The post-visit timeline is not published in detail by CEAB, but based on the experience of coordinators across Canadian engineering programs, here is what typically happens:
| Phase | Timing | What happens |
|---|---|---|
| Team debrief | Within 48 hours of visit end | The visiting team holds a private debrief meeting. They discuss initial impressions, align on findings, and assign individual report-writing responsibilities. |
| Individual report drafting | Weeks 1–4 post-visit | Each team member writes their section. The team lead consolidates and reconciles inconsistencies. This is where informal impressions become formal findings. |
| Draft report circulation | Weeks 4–8 post-visit | The draft report reaches CEAB for internal review, then is shared with your program. This is the version you will respond to. |
| Program response window | 4–6 weeks after receiving draft | Your program has a fixed period to review the draft, provide clarifications, and formally respond to findings. This is your most important action window. |
| Final report and council decision | Weeks 10–14 post-visit | CEAB reviews the program's response, the visiting team may revise findings, and the council makes the final accreditation decision. |
The exact timing varies depending on the team's schedule, travel logistics, and the complexity of the report. Some programs receive a draft in five weeks. Others wait ten. You cannot control the timeline, but you can control your preparation.
Our post on the accreditation cycle timeline covers the full six-year cycle, including what happens between visits.
What the Visiting Team Does Next
Most coordinators have a vague idea of what happens after the visit. The team goes home, writes a report, sends it to CEAB, and eventually you get it. The reality is more structured — and more actionable for you than you might think.
The team debrief (within 48 hours). The visiting team does not go straight home and write their sections independently. They hold a structured debrief meeting — usually via video call — within two days of the visit ending. This is where they align on findings, resolve disagreements between team members, and assign who writes what. The debrief sets the tone for the entire report. If three team members saw something differently, the debrief is where they converge on a single interpretation.
Individual report writing (weeks 1–4). Each team member writes their section based on their observations, the evidence they reviewed, and the faculty interviews they conducted. The team lead consolidates the sections, checks for consistency, and adds the executive summary and overall recommendation. This is where informal impressions from the debrief become formal findings.
Internal CEAB review (weeks 4–6). Before the draft reaches your program, CEAB reviews it for completeness, fairness, and alignment with the criteria. This step catches factual errors, ensures the report addresses all applicable criteria, and flags any findings that may need additional context. Your program does not see this review — but it shapes the draft you receive.
Draft report to program (weeks 6–8). The draft report is sent to your program's designated contact — usually the coordinator or department chair. This is not the final report. It is a working document that your program has the right to respond to. The response is not optional, and it is not a formality. It is a substantive part of the accreditation process.
Understanding this timeline matters because it tells you when to act. You cannot influence the team debrief (it happens without you), but you can influence the draft report through the quality of the evidence you provided during the visit. And once the draft arrives, your response is the single most important thing you will do between the visit and the final decision.
The Informal Feedback You Already Have
Before the formal report arrives, you already have data. The visiting team shared impressions on-site. They may have mentioned strengths they noticed, areas they found thin, or questions they plan to raise. Some teams are open about their initial read. Others are carefully neutral. Either way, you heard something.
Here is what to do with that informal feedback:
Write it down while it's fresh. Within 24 hours of the visit ending, document everything the team said — verbatim if possible. Include the context (over dinner? in the corridor? during the closing meeting?). Distinguish between what they said explicitly and what you inferred. This document becomes the foundation of your preparation for the formal response.
Note which evidence the team found strong versus thin. If the team specifically praised a particular course's assessment evidence or flagged a criterion as under-documented, record which criterion and which course. These are your confirmed strengths and your confirmed risks. When the draft report arrives, you'll already know where to focus.
Record the faculty questions that came up. The team may have asked faculty about a particular practice, policy, or change during the interview. Those questions often foreshadow formal findings. If the team asked three different faculty members about the same topic, that topic will likely appear in the draft report.
Separate signal from noise. Not everything a visiting team member says over dinner is a finding. They are human — they make observations, joke, and speculate. The formal report is written under a different standard. Do not treat casual conversation as a verdict. But do treat repeated themes across multiple team members as early indicators.
Our guide to organizing your evidence room covers how to make sure the team can find what they need during the visit — which directly shapes the feedback they give.
Four Actions You Can Take in This Window
The period between the visit and the draft report is not idle time. It is a preparation window. Here are four actions that the most effective coordinators take:
Action 1: Document the debrief
As described above, write down everything you remember about the team's informal feedback. Include:
- Specific strengths they mentioned
- Areas of concern or questions they raised
- Evidence they found strong or thin
- Faculty interview follow-ups they implied they would pursue
- Any comments about program changes, curriculum updates, or institutional support
Share this document with the department chair. It becomes the shared reference point for the formal response.
Action 2: Audit the evidence you provided
Go through your evidence room — physical or digital — and note anything that was requested but not provided, or provided but may be incomplete. If the team asked for a document that you had to scramble to find during the visit, make sure a clean, current version is ready for the formal response. If a course file was missing a section, update it now. The formal response is not just a rebuttal — it is an opportunity to provide clarifying evidence that was not available during the visit.
Our post on course files that double as accreditation evidence shows how to maintain this evidence year-round so you are never scrambling.
Action 3: Brief the department chair and faculty
Send a brief email to the department chair summarizing the visit, the team's informal feedback, and the expected timeline for the draft report. This is not a detailed report — it is a one-page summary that keeps leadership informed and engaged. Include:
- Overall tone (positive, mixed, concerning)
- Top three strengths identified
- Top three areas of concern
- Expected draft report arrival date
- Proposed response timeline
When the department chair knows what to expect, they can support you when the draft report arrives. If they are surprised, the response window shrinks because you have to spend time explaining instead of acting.
Action 4: Start drafting the response structure
You do not need to write the full response yet — you can't, because you haven't seen the draft report. But you can prepare the structure. Create a document with one section per criterion. Under each criterion, note the informal feedback you received. This skeleton will save you days when the draft report arrives. Instead of starting from scratch, you'll be filling in a framework that already captures the team's initial read.
Responding to the Draft Report
When the draft report arrives, the clock starts. You typically have four to six weeks to respond. Here is how to use that time effectively:
Read the full report before reacting. The first read-through should be silent and complete. Do not annotate. Do not argue with individual findings. Just read. You will read the report at least three times — once to understand the overall narrative, once to fact-check each finding, and once to draft the response. Mixing these passes creates a reactive, defensive document.
Fact-check before you argue. If a finding contains an factual error — wrong dates, incorrect course names, mischaracterized evidence — correct it immediately. Factual corrections are the easiest part of the response. CEAB takes factual accuracy seriously, and a finding based on a factual error may be withdrawn entirely.
Provide evidence, not opinions. The response is not a place for argument or emotion. It is a place for evidence. If the report says a criterion is "partially met" because evidence is thin, provide the evidence. If it says a process is unclear, provide documentation that clarifies it. If it says a policy exists but is not implemented, provide implementation records. Every paragraph of the response should be anchored to a specific piece of evidence.
Involve the faculty who generated the evidence. If a finding relates to a specific course or program area, involve the faculty member who owns that area. They can provide context, clarify evidence, and ensure the response reflects reality. The coordinator writes the response, but the evidence comes from across the program.
Submit before the deadline. The response deadline is firm. Submitting late signals disorganization and undermines the credibility of your response. Aim to submit five business days before the deadline. This gives you a buffer for unexpected issues and shows CEAB that your program operates with discipline.
Our post on writing the self-study data summary covers the same principle: evidence, not narrative, is what moves the process forward.
What Happens If the Report Has Findings
Not every post-visit outcome is a clean pass. Some programs receive findings that require action — conditions to maintain accreditation, recommendations to address, or areas of non-compliance. Here is how to handle each:
Conditions. A condition is a formal requirement that must be met to maintain accreditation. Conditions are serious but not fatal. They require a documented action plan, a timeline, and follow-up evidence. The key is speed: start the action plan the week the report arrives, not the month. Every week of delay makes the condition harder to resolve.
Recommendations. Recommendations are advisory — they do not threaten accreditation status. But they do signal areas where the visiting team saw room for improvement. Treat recommendations as early warning indicators. If a recommendation is not addressed, it becomes a condition in the next cycle. Addressing recommendations proactively is the best way to keep the next visit smooth.
Non-compliance. A finding of non-compliance with a specific criterion is the most serious outcome. It requires immediate action, a formal remediation plan, and evidence of resolution within a defined period. Non-compliance findings are rare in Canadian engineering programs, but when they occur, they require department-level attention and institutional support. The coordinator should escalate to the department chair and dean immediately.
Regardless of the outcome, the post-visit period is not the end of the accreditation cycle. It is the beginning of the next phase. The CEAB cycle is six years. The visit is three days. Everything else — the evidence management, the continuous improvement, the faculty engagement — happens in the space between.
Our guide to building continuous improvement cycles covers how to turn post-visit findings into ongoing program improvement.
Summary
The period between the visiting team leaving and the official report arriving is the most under-utilized window in the accreditation cycle. Most coordinators treat it as waiting time. The best ones treat it as preparation time.
You cannot control the visiting team's findings. But you can control how well you document their informal feedback, how thoroughly you audit the evidence you provided, how effectively you brief your leadership team, and how quickly you respond to the draft report. These four actions — documentation, evidence audit, leadership briefing, and response preparation — separate a reactive coordinator from a proactive one.
The accreditation cycle is six years long. The visit is three days. The post-visit window is eight to twelve weeks. Use those weeks wisely, and the next cycle will start with clarity instead of anxiety.
Ready to see how MapOutcomes keeps your evidence current and accessible between visits? Request a demo and we will show you how a connected evidence map eliminates the post-visit scramble.