CEAB accreditation terms run up to six years [1]. Too many programs spend most of that time doing nothing and the last stretch panicking. If you are an accreditation coordinator, you probably know the rhythm: a site visit arrives, you deliver the self-study, the team leaves, and then silence follows for months. Sometimes years.
Then, as the next visit approaches, the phone rings. Engineers Canada describes the accreditation process as an 18-month one [2]. The Dean wants to know how ready you are. You open your spreadsheets. You realize you have no idea.
The problem is not that the cycle is long. It is that most programs treat the years between visits as dead time. The accreditation cycle is not a visit followed by a break. It is a continuous process with distinct phases, each with work that should be done while you are calm, not while you are in crisis mode.
Here is what the accreditation cycle actually looks like — and what you should be doing in each phase.
The Six-Year Cycle: Four Phases
The CEAB grants accreditation for a term of up to six years. A shorter term may be granted, for example to align programs at the same institution or where the Board has areas of concern, and a term can be conditional on meeting specific requirements [1]. The exact timeline depends on the Board's decision and any conditions attached to it. But the structure is consistent.
You can think of the cycle as four phases. Each one has a different purpose, a different emotional tone, and a different set of tasks that should be completed before the next phase starts.
Phase 1: Post-Visit Resolution (Months 1–6)
The visiting team has left. You have received the preliminary feedback. Now you need to do three things while the memory of the visit is still fresh.
- Document the findings. The official report will take time to arrive. Write down what the team said — formal comments, informal hallway conversations, even the questions they asked but never got answers to. Those questions are signals of where your evidence was weak.
- Process the conditions. If the team placed conditions on your accreditation — specific items you must address before the next visit — create a tracking system for them. Every condition should have an owner, a deadline, and a definition of done.
- Capture institutional knowledge. The people who helped prepare for the visit — faculty leads, administrative support, department chairs — have context that will not be obvious to anyone six months from now. Record it.
This is the phase most programs neglect. The visit is over, the stress is gone, and everyone goes back to their normal work. The result: six months later, nobody remembers exactly what the team found or what they promised to fix.
Phase 2: Continuous Improvement (Most of the Term)
This is the longest phase and the most important one. Your accreditor does not expect your program to be frozen in time between visits. They expect it to evolve — and to document that evolution. The CEAB expects programs to continually improve (Criterion 3.2), and expects assessment results for all twelve graduate attributes to be gathered over a cycle of six years or less (Criterion 3.1.5) [1]. This is where most programs struggle to produce meaningful evidence.
Continuous improvement is not a section you write for the self-study. It is a process that runs year-round. Here is what it looks like in practice:
- Assessment data collection. Every course should generate outcome assessment data each term. Grades, rubric scores, project evaluations — the evidence that students are achieving the learning outcomes mapped to your accreditor's outcome indicators.
- Analysis and action. When assessment data shows an outcome is not meeting targets, the program responds. Curriculum changes, teaching adjustments, resource allocation — and then documents the change and its effect.
- Closure. The improvement cycle closes when you can show that an action was taken, the result was measured, and the outcome improved (or a new action was triggered if it did not).
The visiting team will look for this evidence in your next self-study. Not a single story of improvement from three years ago — a pattern of assessment, action, and closure that runs through the program's normal operations. If your evidence is only collected in the six months before the visit, the team will see it. The gap in the timeline will be obvious.
Phase 3: Follow-Up Reports (Varies by Program)
Not every program has this phase. The CEAB may grant a limited-term accreditation that can be extended once it receives a report showing that the matters giving rise to its concerns have been resolved adequately [1]. If that is your situation, the report is a shorter document than the full self-study, but it serves the same purpose: demonstrate that the concerns have been addressed.
Follow-up reports cover the specific concerns or conditions the Board identified. Depending on your decision, they might touch on topics such as:
- Updates on faculty qualifications or hiring
- Evidence of curriculum changes that were recommended
- Progress on facility or resource improvements
- Closure of specific outcome indicator coverage gaps
Programs that maintain evidence year-round treat follow-up reports as a matter of pulling together what is already organized. Programs that wait until the report is due start from scratch — and put the extension of their accreditation term at risk.
Phase 4: Self-Study Preparation (The Run-Up to the Next Visit)
This is the phase everyone knows. The formal process starts when the institution submits a Request for Accreditation, which the Secretariat must receive by July 1 of the calendar year before the visit cycle begins [3], and the completed questionnaire is due to the visiting team eight weeks before the visit [3]. Engineers Canada frames the whole thing as an 18-month process [2]. You form committees, assign sections, collect evidence, write the report, and prepare the campus for the visiting team.
How smoothly this phase goes depends entirely on what happened during Phases 1, 2, and 3. If you have been collecting assessment data, tracking improvements, and maintaining mapped evidence, the self-study is a matter of organizing and writing up what you already have. If you have not, you are reverse-engineering years of evidence from incomplete records and fading memories.
Self-study preparation is far less painful when evidence is maintained continuously. When it is not, the preparation turns into months of frantic data collection, and the result is still thinner than it could have been.
The Readiness Gap
There is a pattern that shows up in almost every program that treats accreditation as a cyclical event rather than a continuous process. Coordinators call it the readiness gap, though it does not have an official name.
The readiness gap is the difference between what you can prove to a visiting team on any given Tuesday and what you could prove if you had six months to prepare. In programs with strong year-round evidence management, the gap is small — you can demonstrate compliance at any time. In programs that only collect evidence for the self-study, the gap is enormous — and the visiting team can see it.
Visiting teams know the difference between a program that is genuinely ready and one that has spent the last six months building a case for readiness. The evidence tells. Continuous assessment data, documented improvement cycles, and traceable mappings are things you cannot fake at the last minute. Their absence is just as visible.
What Changes When You Close the Gap
Closing the readiness gap is not about working more. It is about working differently. Instead of collecting evidence once per accreditation cycle, you collect it as part of the normal course review process. Instead of writing the self-study from memory, you write it from a living evidence map that has been updated every semester.
The practical result:
- Self-study preparation takes far less effort. Most of the data is already organized and mapped.
- Follow-up reports are easier to assemble. Evidence for every condition is tracked and current.
- Unexpected review requests are not a crisis. If your accreditor or your institution asks for a status report, you can produce one in a week.
- The coordinator is not the only person who knows where everything is. Evidence is institutional, not personal.
This is what connected evidence mapping gives you. Not a dashboard for the Dean — though that is a by-product. The real value is the ability to look at your program at any point in the accreditation cycle and know, with specificity, where you stand on every outcome indicator.
The Practical Takeaway
The accreditation cycle is not a visit with a long break between. It is a continuous process with four distinct phases. The work that separates a smooth self-study from a frantic one is done in the years between visits — not in the months before.
If your program is currently in Phase 2 (the continuous improvement years), now is the time to build the habits that will make the next self-study manageable. Map your evidence. Collect assessment data each term. Track improvement actions and close the loops. Document while it is fresh, not while it is overdue.
The visiting team will not know whether you spent the whole term building evidence or six months scrambling for it. But the quality of your self-study will reflect the difference — and so will your accreditation outcome.
References
- Engineers Canada (Canadian Engineering Accreditation Board), "Accreditation Criteria and Procedures 2025," Engineers Canada, 2025 (revised November 2025). [Online]. Available: https://engineerscanada.ca/sites/default/files/2025-12/2025-Accreditation_Criteria_Procedures-EN.pdf
- Engineers Canada, "Accreditation resources," Engineers Canada. [Online]. Available: https://engineerscanada.ca/accreditation/accreditation-resources
- Engineers Canada (Canadian Engineering Accreditation Board), "Manual of Accreditation Procedures," Engineers Canada, 2025 (updated December 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.