One Evidence System for Every Accreditation Your Institution Runs

The Silo Problem

Open your institution's accreditation portfolio and you will likely find something familiar: several accredited programs, each running on its own rhythm. Engineering answers to one accreditor, nursing to another, pharmacy and allied health to others still, and each one has its own coordinator, its own set of spreadsheets, its own evidence folders, and its own review cycle.

None of that is a mistake. The frameworks are genuinely different — different criteria, different visiting teams, different submission systems. But the way most institutions manage them is an accident of history: every new program that earned accreditation brought its own tooling with it, and nobody ever consolidated. So today, one institution can be running three or four parallel accreditation operations that share almost nothing.

The cost is rarely visible in a single program. It shows up in the aggregate — in duplicated tooling, in coordinators who cannot see each other's work, and in institutional knowledge that lives in one person's head and walks out the door when they leave.

The Anatomy of Every Accreditation Is the Same

Strip away the criteria and every accreditation framework asks for the same underlying thing: proof that your program is doing what it says it is doing, and evidence that it is getting better over time. The specific language changes — CEAB calls them graduate attributes [1], CASN's nursing standards include a standard on program outcomes [2], and ACPE's pharmacy standards speak of educational outcomes [3] — but the work of producing the evidence is structurally identical.

Every coordinator, in every framework, is doing the same five things:

• Mapping — connecting each learning outcome or attribute to the courses and assessments that address it.
• Evidence collection — gathering the artefacts (syllabi, rubrics, assessment data, improvement plans) that prove the mapping is real.
• Gap detection — finding the outcomes with thin or missing evidence before the visiting team does.
• Narrative writing — turning the data into a self-study or annual report a human can follow.
• Continuous improvement — showing that the gaps found last cycle were actually closed.

If the work is the same, the tooling could be the same. That is the insight most institutions never act on, because acting on it requires someone to look across frameworks instead of down into one.

What Siloing Actually Costs

The cost of running parallel accreditation operations is not dramatic in any single month. It is a slow leak, and it compounds. Here is where it shows up:

Duplicated tooling and licensing. If each program or framework runs on its own spreadsheet system, its own evidence repository, or its own software seat, you are paying the same cost several times over for the same underlying function. Multiply a per-program cost by eight programs and it is no longer trivial.

Coordinators who cannot see each other. The engineering coordinator and the nursing coordinator at the same institution rarely share a single view. They are solving the same problem — "how do I prove this outcome is addressed?" — with different tools, in different formats, and with no way to compare. The patterns one coordinator has already worked out, a clean evidence template or a repeatable gap-detection routine, never reach the others.

Institutional knowledge that does not survive turnover. This is the cost that hurts most. When a coordinator leaves, their program's accreditation history — the decisions, the workarounds, the "why we did it this way" — often leaves with them, trapped in personal spreadsheets and email threads. The next coordinator starts from scratch. Do that across four frameworks and your institution has no durable memory of its own accreditation. Our post on surviving coordinator turnover covers how to keep one program's record alive — the same problem, at a smaller scale.

No cross-program learning. A strong assessment practice in one program is a ready-made exemplar for another. But if the evidence lives in silos, that transfer never happens. Your institution is leaving its best ideas locked inside a single department.

The Case for One System

Consolidating onto a single evidence platform is not about forcing every program to look the same. The frameworks stay different — CEAB is still CEAB, CASN is still CASN. What consolidation buys is the shared infrastructure underneath: one place to map, one place to store evidence, one place to find gaps, and one place where the institutional record lives.

The concrete benefits:

• One evidence map, many frameworks. Each program keeps its own criteria and outcomes, but they live in the same system. A chair or dean can see the state of every accreditation at once, not one framework at a time.
• Cross-program pattern learning. When the engineering team builds a clean assessment-evidence template, the nursing team can adopt it in an afternoon instead of rebuilding it from zero.
• Institutional memory that outlives any individual. The data belongs to the institution, not to the coordinator. When someone leaves, the next person inherits a complete, searchable record — every mapping, every piece of evidence, every gap closed since the last visit.
• One export, one standard. Visiting teams and self-study reports all want the same thing: a clear, defensible map of outcomes to evidence. A single system produces that format consistently across every program. Our guide to building an evidence map from scratch walks through that map for a single program — here it is the same map, shared.

There is a timing argument too. The institutions that consolidate now are the ones that will walk into their next accreditation visit with a defensible story about continuous improvement across the whole portfolio — not a patchwork assembled in the final four weeks before the team arrives. If you already manage several CEAB cycles at once, our post on managing multiple cycles simultaneously is the single-framework version of this argument.

Where to Start

You do not have to migrate everything at once. A practical sequence:

1. Audit your portfolio. List every accredited program, its framework, its cycle position, and the tool it currently runs on. You will usually find more duplication than you expected.

2. Find the shared evidence. Identify the artefacts that are already common across programs — assessment rubrics, continuous-improvement plans, policy documents. That is your first batch of consolidation.

3. Pilot one framework. Pick the program closest to a visit and move it onto the shared system first. You get the fastest payoff and a real-world test before you scale.

4. Extend framework by framework. Once the pilot works, bring the next program over. The second migration is always faster than the first, because the infrastructure already exists.

The goal is not to make your institution look like one big program. It is to make every accreditation run on the same foundation — so the work gets easier each time, and the record belongs to the institution for as long as it runs.

References

1. 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
2. Canadian Association of Schools of Nursing, "BScN Accreditation Program," CASN. [Online]. Available: https://casn.ca/accreditation/bscn-program
3. Accreditation Council for Pharmacy Education, "Accreditation Standards and Key Elements for the Professional Program in Pharmacy Leading to the Doctor of Pharmacy Degree (Standards 2025)," ACPE, 2025. [Online]. Available: https://www.acpe-accredit.org/wp-content/uploads/ACPEStandards2025.pdf