The visiting team asks a simple question: “Show us how you develop Graduate Attribute 4 through your third-year courses.” You pause. The spreadsheet has a cell for it, but the evidence was uploaded in 2022, the course code changed last year, and you cannot find the current rubric. The team notes the gap. You feel the moment.
This is the scenario that keeps accreditation coordinators awake at night. Not the big, obvious deficiencies — those are visible months in advance. It is the quiet gaps: the stale evidence, the unmapped course, the indicator that nobody thought to check. The ones that surface only when a visiting team member asks a question you did not prepare for.
Every CEAB visiting team finds gaps. Every self-study report has areas of concern. The question is not whether gaps will exist — they always do — but how many, how severe, and how quickly you can recover from them. This post covers the full lifecycle of accreditation risk: how gaps arise, what happens when visiting teams find them, how to respond in the moment, and how to build a system that catches gaps before they reach the site visit.
How Gaps Arise: The Five Failure Points
Gaps do not appear at random. They follow predictable patterns. Understanding these patterns is the first step to preventing them.
Failure Point 1: Evidence goes stale
A rubric from 2021 is not evidence of 2026 teaching practice. Courses change. Faculty leave. Assessment methods evolve. Evidence that was strong at the time of submission becomes outdated simply through the passage of time. The gap is not that evidence does not exist — it is that the evidence on file does not represent current practice.
This is the most common gap type. We covered it in our post on the evidence review — the four-step process for validating evidence recency is the primary defense against stale evidence.
Failure Point 2: Curriculum changes outpace the evidence map
You add a new course to the program. You remove an old one. You renumber everything because the faculty senate asked for a consistent coding scheme. The evidence map still reflects the curriculum that existed eighteen months ago. The visiting team asks about a course that no longer exists, or cannot find evidence for a course that is now central to the program.
This gap is entirely preventable. Our post on managing curriculum changes covers the update process: log the change, update the map, verify Graduate Attribute coverage, and close the new evidence gaps within the same term.
Failure Point 3: The coordinator leaves
The accreditation coordinator moves to another department, retires, or takes a sabbatical. The new coordinator inherits a set of spreadsheets, a shared drive with inconsistent folder names, and a partial understanding of which indicators are covered and which are not. Six months pass before the gaps become visible.
This is the institutional knowledge risk. We explored it in our post on building an accreditation evidence repository — when the evidence is connected, mapped, and traceable in a system rather than a person’s head, the coordinator transition is a handoff, not a reconstruction.
Failure Point 4: Faculty do not submit
The course exists. The indicator is mapped. The request was sent. The evidence never arrived. This is the human gap — not a structural problem, but a workflow failure. Faculty members are busy. Evidence requests compete with grading, research deadlines, and service commitments. Without a clear, low-friction submission process, the evidence never gets collected.
Our post on getting faculty to submit evidence has five strategies that address this gap directly: embed requests in the teaching calendar, scope them specifically, show faculty the value, reduce friction to zero, and get the department chair involved.
Failure Point 5: The criteria change
Engineers Canada updates the accreditation criteria. A new Graduate Attribute appears. An existing indicator is reworded. The evidence map that was complete yesterday now has a gap that did not exist last cycle. Programs that do not track criteria changes proactively find themselves scrambling to map evidence to requirements they did not have to address before.
We covered the faculty licensure changes in our post on CEAB’s faculty licensure changes — the preparation steps are the same for any criteria update: audit the changes, identify new evidence requirements, and build a gap closure timeline before the next self-study deadline.
What the Visiting Team Does When They Find a Gap
Understanding the visiting team’s process reduces anxiety. The team is not looking to fail your program. They are looking to verify that your program meets the accreditation criteria. When they find a gap, their next steps follow a predictable pattern.
They probe deeper
A missing piece of evidence does not immediately become a finding. The visiting team member will ask follow-up questions: “Can you show us an alternative?” “Has this assessment method changed recently?” “Can we see the course outline that covers this?” They are giving you a chance to provide evidence from a different angle.
How you respond matters. A confident answer — “That particular assessment changed last year, but here is the current syllabus section that covers the same attribute” — defuses the gap. A flustered search through folders signals a deeper problem.
They cross-reference
Visiting teams rarely look at one piece of evidence in isolation. They will cross-reference your self-study narrative against the evidence you submitted, the curriculum map you provided, and the faculty interviews they conducted. If your narrative claims strong coverage of GA4 through design courses, but the evidence map shows only one design course with a rubric from three years ago, the gap is flagged.
This is why the self-study narrative must be evidence-backed. Our post on the self-study narrative covers the evidence-first writing method: every claim is cross-referenced to a specific piece of evidence, so the narrative and the map tell the same story.
They document it
Every gap becomes a line item in the visiting team’s internal notes. Not every gap becomes a public finding. The team distinguishes between:
- Minor gaps — easily resolved during the visit. The team notes the issue, gives you a chance to provide alternative evidence, and may not include it in the final report.
- Areas of concern — significant gaps that the team believes reflect a systemic weakness. These appear in the final report with specific recommendations for improvement.
- Critical findings — rare but serious. A complete absence of evidence for a required attribute, or evidence that does not support the program’s own claims. These can result in conditional accreditation or a shortened review cycle.
They discuss it with your program
On the final day of the site visit, the team presents preliminary findings. This is your chance to respond. If they flag a gap, you can provide additional context, offer to submit supplementary evidence, or acknowledge the issue and commit to a remediation timeline.
How you respond to the preliminary findings shapes the final report. Programs that acknowledge gaps honestly, propose concrete remediation steps, and demonstrate self-awareness receive more constructive — and less severe — final findings than programs that defend, deflect, or dispute.
The Aftermath: What Happens After the Visit
The visiting team departs. The CEAB committee reviews their report. A final decision is issued. Here is what happens next, depending on the severity of the findings.
Scenario A: No findings or minor recommendations
Your program retains full accreditation. The recommendations are advisory — they do not require formal follow-up, but ignoring them is risky. The next visiting team will check whether you addressed them. A recommendation from Cycle 3 that remains unaddressed in Cycle 4 becomes an area of concern.
Scenario B: Areas of concern with a formal action plan
Your program retains accreditation but must submit a formal action plan within three to six months. The action plan must address each finding with specific steps, responsible parties, and deadlines. CEAB reviews the plan and may request interim progress reports.
This is the most common outcome when gaps are found. It is not a failure. It is a structured opportunity to improve. The key is to treat the action plan as a real commitment, not a box-checking exercise.
Scenario C: Conditional accreditation
Your program retains accreditation with conditions. The conditions specify exactly what must be improved and by when. A follow-up review may be scheduled within 12 to 24 months — well before the normal seven-year cycle. If conditions are not met, the program risks losing accreditation.
Conditional accreditation is rare but not uncommon. It typically results from multiple systemic gaps rather than a single missing piece of evidence. The programs that recover most effectively are the ones that treat the conditions as a catalyst for building systematic evidence management, not just a compliance checklist.
Scenario D: Accreditation withdrawn
This is the outcome no coordinator wants. It happens when a program cannot demonstrate that it meets the minimum accreditation criteria, and the visiting team finds the evidence gaps to be fundamental and unremediable within a reasonable timeframe.
Withdrawal is exceptional. Programs that are actively managing their accreditation process — even imperfectly — rarely face this outcome. The programs at risk are the ones that treated accreditation as a periodic event rather than an ongoing practice.
How to Prevent Gaps Before They Become Findings
The post-visit response is important. But the real work is prevention. Here is a practical framework for catching gaps before a visiting team does.
Step 1: Run a gap analysis on a regular cadence
Do not wait for the self-study cycle to discover what evidence you have and what you are missing. Run a gap analysis annually, or at least every other year. Our post on the accreditation gap analysis provides a five-area audit framework and a green-amber-red scoring method that takes one afternoon to execute.
What to check:
- Coverage — does every Graduate Attribute have at least two courses providing evidence at the Mastery level?
- Recency — is the evidence from the current or previous academic year?
- Quality — does the evidence actually demonstrate the attribute it claims to support? Our post on evidence quality covers the criteria visiting teams use.
- Traceability — can you trace every claim in the self-study narrative to specific evidence?
- Continuity — does the I-R-M (Introduction-Reinforcement-Mastery) progression hold across the program?
Step 2: Build a maintenance rhythm
Gaps appear between cycles, not during them. A maintenance rhythm ensures that evidence is refreshed, curriculum changes are logged, and the map stays current without requiring a full cycle-level effort.
The rhythm we recommend:
- Each term — collect evidence for offered courses. Validate that submissions are current and sufficient.
- Annually — review curriculum changes, update the evidence map, run the gap analysis, refresh stale evidence.
- Bi-annually — review the self-study narrative draft against the current evidence map. Identify narrative claims that are no longer supportable.
Step 3: Automate gap detection
Manual gap detection is slow and error-prone. A connected evidence map automates the process: the system flags indicators with insufficient evidence, highlights stale evidence, and shows coverage gaps in real time. You do not need to wait for an annual audit to know where your weaknesses are.
This is the core advantage of moving from spreadsheets to a connected system. We covered the migration in our post on building an evidence map from scratch — the six-step process takes one week for a program that has already mapped its curriculum.
Step 4: Prepare for the visit with a mock review
In the 90 days before the visit, run an internal mock review. Assign a faculty member who has not been involved in the evidence collection to play the role of a visiting team member. Give them the self-study narrative and ask them to request evidence for every claim. Time how long it takes to find and produce each piece.
The gaps that surface in a mock review are the ones that would surface in the real visit. Addressing them before the team arrives turns potential findings into confident answers. Our post on the 90-day preparation plan has the full countdown framework, including the mock review phase.
Step 5: Build a culture of evidence ownership
Gaps persist when evidence collection is seen as the coordinator’s job. In programs where gaps are rare, evidence ownership is distributed: faculty members understand which attributes their courses support, department chairs ensure evidence is submitted as part of the course review cycle, and the coordinator’s role is review and synthesis, not evidence hunting.
Our post on the faculty evidence submission playbook has the five strategies for building this culture. Implement them early, not three months before the visit.
Summary
Every visiting team finds gaps. The difference between a strong outcome and a concerning one is not whether gaps exist — it is how many, how severe, and how well-prepared you are to respond.
The five failure points are predictable: stale evidence, curriculum changes, coordinator transitions, faculty non-submission, and criteria updates. The prevention framework is practical: run annual gap analyses, build a maintenance rhythm, automate detection with a connected evidence map, run a mock review before the visit, and distribute evidence ownership across the program.
The tool you use matters. A spreadsheet cannot automate gap detection, track evidence recency, or connect curriculum changes to evidence requirements. A connected evidence map does all of this in real time. It does not eliminate gaps — no system can. But it catches them early, gives you time to fix them, and ensures that nothing surprises the visiting team.
MapOutcomes builds that connected evidence map for your program. Every indicator linked to its courses, every course to its assessments, every assessment to the evidence that supports it. Gaps are flagged automatically. Evidence recency is tracked. Curriculum changes propagate through the map instantly. Book a demo to see how the gap detection works in practice.