Your VP of Academic Affairs asks a simple question at the start of the fiscal year: "Are our engineering programs in good shape for accreditation?" You know the answer should be straightforward. But the only person who can tell you is a coordinator buried in spreadsheets three levels down, and she doesn't have time for a meeting this week.
This is accreditation unreadability. The information exists. But it is locked in a format, a file structure, and a working memory that belongs to one person. The picture is there — but it is not readable to the people who need to govern it.
Accreditation unreadability is not a coordinator problem. It is a governance problem. And it is one that sits squarely in the Dean's domain, whether the Dean realises it or not.
This post is for Deans and Associate Deans who oversee CEAB–accredited engineering programs. It covers why accreditation readiness is a leadership metric, not an administrative one — what happens when the data is only readable by one person, and what a different approach looks like.
Accreditation Is a Risk Management Function
CEAB accreditation is not optional for professional engineering programs in Canada. It is the mechanism that determines whether your graduates are eligible for the P.Eng. designation, whether your program appears on Engineers Canada's public register, and whether your institution retains its standing with provincial regulators and professional bodies.
Engineers Canada publishes an annual Accountability in Accreditation report that tracks outcomes across the Canadian system. Programs can receive full accreditation, conditional accreditation, or — in the most serious cases — lose accredited status entirely. The consequences of losing accreditation are immediate and severe: you cannot enrol new students into a recognised program, existing graduates lose their pathway to licensure, and the reputational damage extends beyond the faculty to the institution's research partnerships, government funding, and student recruitment.
Yet in most faculties, accreditation readiness is not treated as a board–level risk. It is treated as an administrative task. The coordinator manages it. The chair is informed when problems arise. The Dean hears about it when the visiting team is scheduled — or worse, when something has gone wrong.
This is the accreditation readability problem. The risk is real. The data is real. But the data is not structured in a way that makes the risk visible to the people who manage risk for a living.
What Deans Actually Need to See
A Dean does not need to know which course delivers which Graduate Attribute indicator. That is the coordinator's job. What the Dean needs is a summary that answers four questions:
1. How many programs are in scope, and where are they in the cycle?
CEAB visits occur on a roughly six–year cycle. A faculty with three or four accredited programs may have programs at different stages of that cycle. The Dean needs to know which programs are in self–study mode, which are due for a visit in the next 18 months, and which are in the quieter period between cycles. This is not just calendar management. It is resource planning. The programs entering self–study need coordinator capacity, faculty engagement, and sometimes budget. The programs that are not in self–study need maintenance.
2. What is the overall evidence health across programs?
Not every indicator in every program is equally well–supported. Some have strong, current evidence. Others have gaps — thin evidence, outdated exemplars, or courses that have changed their content without updating their accreditation mappings. The Dean does not need the granular list. They need a summary: "Of the 12 Graduate Attributes across three programs, X are fully supported, Y have moderate evidence, and Z have gaps requiring attention."
This is not a question that can be answered quickly from a spreadsheet. Spreadsheets are designed for data entry, not for executive summaries. The coordinator can produce the summary, but it takes time to compile. By the time it reaches the Dean's desk, it is a static snapshot that may already be out of date.
3. Is the coordinator position sustainable?
This is the question that keeps Deans up at night, because it is the one they cannot answer with data. The accreditation coordinator is a single point of failure. In many faculties, the coordinator role is part–time, adjunct, or absorbed into someone's other responsibilities. When that person leaves — for retirement, for another role, for burnout — the institutional knowledge of the accreditation process leaves with them.
Engineers Canada's AU Task Force report recommended stronger institutional support for accreditation coordination, recognising that the role carries more responsibility than most titles suggest. A Dean who can see that the coordinator is carrying the entire accreditation picture in their head — with no backup system — has a resourcing decision to make.
4. Are we investing in accreditation, or just reacting to it?
Continuous evidence collection costs money. Upgraded assessment tools, faculty development on outcome–based education, summer students to help compile data — these are line items in a faculty budget. When accreditation is reactive, the spending is crisis–driven and inefficient. When it is proactive, the spending is predictable and planned. But you cannot budget for what you cannot see.
This is the core of accreditation readability. If the Dean cannot answer these four questions without a three–week project to compile them, the faculty is not managing accreditation risk. It is hoping.
The Cost of Unreadability
Accreditation unreadability has costs that do not appear in any budget spreadsheet. They show up in other ways:
The coordination tax
When the Dean or chair needs an accreditation status update, the coordinator has to stop what they are doing and compile it. In a busy faculty, these requests compound. The coordinator spends increasing time translating spreadsheet data into summaries for different audiences. This is not the coordinator's fault. It is a structural cost of a tool that was never designed to serve multiple readers.
The blind spot effect
When evidence gaps exist in a course or program, they remain invisible until someone looks for them. In the spreadsheet model, someone only looks when the coordinator has time. Gaps that sit quietly for months become crises in the eight weeks before a visit. The blind spot is not in the evidence. It is in the reporting structure.
The succession risk
This is the cost that materialises most suddenly. A coordinator leaves. The incoming coordinator inherits a set of files that they did not create, in a format that was designed by someone who is no longer there, containing conventions and shortcuts that only the previous owner understood. The transition period can take six months or more — time that may not align with the accreditation cycle.
We have heard from faculties where a coordinator departure coincided with the start of self–study preparation. The result was a six–month delay in evidence compilation, compressed timelines for faculty submissions, and a level of stress that affected morale across the department. This is a risk that the Dean could have mitigated — if the accreditation picture had been readable to someone other than the person who left.
What Readability Looks Like
A readable accreditation system gives the Dean three things:
A live compliance overview
Not a report that is generated once per term. A view that is current. The Dean logs in, sees a summary of evidence health across programs, and can drill down if something looks off. The data is live because the system captures evidence continuously, not just during self–study. Red flags are visible before they become visit–day problems.
Shared visibility, not shared responsibility
The coordinator still does the coordinator's work. The difference is that the evidence map is a shared workspace, not a private file. The chair can see their department's picture. The Dean can see the program–level picture. Faculty can see what they are contributing to. Nobody needs to learn the whole system to see their part of it.
Institutional memory that outlasts people
When the coordinator leaves, the evidence stays. The mappings, the exemplars, the assessment conclusions — they are in a system that the incoming coordinator can open and understand. The transition is not a months–long discovery process. It is a handover of access credentials and a conversation about current priorities.
This is not a luxury. It is basic risk management. Any other function in the faculty — finances, human resources, research compliance — would be considered reckless if the data lived in one person's head. Accreditation deserves the same standard.
Questions to Ask Your Coordinator
If you are a Dean and you want to assess your faculty's accreditation readiness right now, here are five questions to ask. You do not need to schedule a formal review. A 20–minute conversation is enough.
1. "If you left tomorrow, how long would it take your replacement to understand where we stand?"
The answer tells you about your succession risk. "A few days" means the evidence is documented in a shared system. "Several weeks" means it is in files that need orientation. "Months" means you have a single point of failure.
2. "Can you show me the current evidence picture in under five minutes?"
This is the readability test. If the answer requires a meeting next week and a prepared report, the data is not readable. If the coordinator can pull up a view and walk you through it in real time, you are in a better position.
3. "Where are the biggest gaps right now?"
A coordinator working from a connected system should be able to name the top two or three gaps by name. If they need to open a file and look, the gaps are not front–of–mind. That is the blind spot effect in action.
4. "Are we collecting evidence continuously, or only during self–study?"
Continuous collection is the only model that supports the four Dean–level questions above. If the answer is "only during self–study," the faculty is running on a reactive cycle. The evidence exists for six weeks and goes dark for five years.
5. "What tools would make your job easier?"
This is an open question, but the most common answer we hear from coordinators is: "A system that lets me share the picture without having to rebuild it for every audience." If that is the answer in your faculty, the readability problem is the same one we see everywhere else. And it is solvable.
The Dean's Decision
Accreditation readiness is not a binary state. It is a spectrum. At one end, the Dean can answer the four governance questions in real time because the evidence is live, shared, and readable. At the other end, the information exists but is locked in one person's working memory and a set of spreadsheets that only they can navigate.
The decision is not about replacing the coordinator. It is about replacing the constraint. The constraint is the tool. And the tool was designed for a different era — one where one person managed the whole process, where spreadsheets were the best option available, where the cost of unreadability was accepted as the price of accreditation.
That era is over. A connected evidence map exists. It costs less than most faculty budget line items. It takes an afternoon to go live, not a semester to implement. And it gives the Dean, the chair, and the coordinator a shared view of the same data — at the level of detail each of them needs.
MapOutcomes is that system. It was built by someone who has sat in the coordinator's seat and the chair's seat, and who saw the readability gap between them. We built it because every faculty deserves a view of accreditation that is as live and readable as their financial or HR dashboards.
If you would like to see what a Dean–level accreditation view looks like, we will gladly walk you through it. No sales pitch. A 30–minute conversation about your faculty's current accreditation picture and whether a connected evidence map would change how you govern it.
Request a demo, or try the demo playground to explore the interface on your own time.
This post was written for Deans and Associate Deans overseeing CEAB–accredited engineering programs in Canada. For the department chair perspective, see What Department Chairs Need to Know About Engineering Accreditation. For the coordinator's perspective on tooling, see 5 Signs Your Accreditation Process Needs Modernizing.