Closing the Loop: How Program Assessment Data Becomes Accreditation Evidence

Every engineering program collects assessment data all year. Course exams, design project evaluations, capstone reports, peer reviews, self-assessments — the evidence of student learning is generated continuously, assessed by faculty who know the work, and filed away in learning management systems or course portfolios. Then accreditation comes around, and the coordinator starts building evidence from scratch.

The gap between what programs already measure and what they present to CEAB is not a data problem. Programs have the data. It is a connection problem. The assessment results that prove students are meeting learning outcomes exist in one place. The accreditation evidence map lives in another. Bridging them at accreditation time is manual, error-prone, and stressful — the very stress that MapOutcomes was built to eliminate.

This post covers why the assessment-to-accreditation gap exists, what CEAB actually expects under Criterion 3.1, and a practical framework for turning your existing assessment data into accreditation evidence without creating new work for faculty.

1. The Assessment-Evidence Gap

Canadian engineering programs have been assessing graduate attributes for years. In that time, schools have developed rubrics, aligned course outcomes to program-level attributes, and built assessment infrastructures that generate meaningful data every semester.

And yet, when accreditation time arrives, the coordinator still finds themselves asking faculty for evidence that should already exist. The disconnect is structural:

• Assessment lives at the course level. Instructors design exams, assignments, and projects. They assess student work against course learning outcomes. The results go to the instructor, the department, and sometimes the faculty assessment committee.
• Accreditation lives at the program level. CEAB evaluates whether the program as a whole develops the 12 Graduate Attributes [1]. Evidence must show aggregate results across courses, years, and cohorts.
• The bridge between them is narrative. Self-study reports describe the connection in prose: "GA3 is assessed through MECE2304, MECE3402, and MECE4901, with aggregate results showing satisfactory performance." The narrative asserts a connection that the data should demonstrate — but the data rarely travels from the course to the program report in a usable form.

Using the data you collected for improvement and evidence purposes is the step many programs find hardest. Most are still approaching the loop rather than closing it.

2. What CEAB Actually Expects Under Criterion 3.1

CEAB's Criterion 3.1 is the accreditation board's requirement that programs demonstrate systematic assessment of Graduate Attributes. It is not a request. It is a basis for accreditation decisions. The criterion asks the institution to demonstrate that graduates possess twelve attributes [1], and it sets five specific expectations (3.1.1 to 3.1.5): an organization structure with faculty and leadership engagement, documented curriculum maps, indicators for each attribute, assessment tools, and assessment results for all twelve attributes within a period of six years or less [1]. In practice, that translates into four jobs for the coordinator, the last of which sits under Criterion 3.2 (continual improvement):

1. Articulate the attributes. Define what each of the 12 Graduate Attributes means for your specific program. Criterion 3.1.3 calls for a set of measurable, documented indicators for each attribute [1], so your program must translate each attribute into program-specific indicators.
2. Map the curriculum. Criterion 3.1.2 requires documented curriculum maps showing the relationship between learning activities and each attribute, and the semesters in which these take place [1]. Show which courses contribute to each attribute and at what level (for example, introduce, reinforce, assess). This is the evidence map that coordinators build — the one that lives in spreadsheets until tools like MapOutcomes replace them.
3. Collect assessment data. Criterion 3.1.4 calls for documented assessment tools that provide data on student learning for all twelve attributes over a cycle of six years or less [1]. Programs commonly use direct measures (exam questions, design project rubrics, lab reports) and indirect measures (student self-assessments, alumni surveys, employer feedback) to evaluate student performance against each attribute.
4. Use the results. This is the "closing the loop" step, and it is assessed under Criterion 3.2. The program needs processes showing that assessment results are validated, analyzed and applied to the further development of the program (3.2.1), and a demonstration that the process has led to consideration of specific improvement actions (3.2.3) [1]. If students consistently underperform on a particular attribute, the strongest evidence is a record of what the program did about it — and whether the change made a difference.

The last step is where many programs struggle. Collecting data is the easy part. Connecting it to accreditation evidence and showing how it drives improvement is the part that requires structure, not just effort.

3. The Four-Step Loop: From Data to Evidence

The assessment-to-accreditation loop is not a one-time activity. It is a four-step cycle that should run continuously. Programs that close it do not create new processes — they connect existing ones.

Step 1: Measure

Faculty already measure student learning against course outcomes every semester. The assessment data exists in the form of exam results, rubric scores, project evaluations, and other course-level evidence. The key requirement is that each assessment is explicitly linked to a course learning outcome, and each course learning outcome is mapped to a Graduate Attribute.

When this mapping is explicit and maintained, assessment data is already accreditation evidence. The question is not "do we have the data?" — it is "is the data tagged with enough context to travel from the course to the program report?"

Step 2: Aggregate

CEAB evaluates the program, not individual courses. Aggregate results across courses, sections, and cohorts to show program-level performance on each Graduate Attribute. This is where spreadsheets become unwieldy: combining assessment results from 50+ courses into a coherent program-level picture requires consistent mapping, consistent scoring, and consistent reporting.

Programs that do this well use a common rubric or scoring framework so that a "3 out of 4" on GA4 from one course means the same thing as a "3 out of 4" from another. A simple scale with a small number of defined levels, applied identically across courses, makes aggregation much easier.

Step 3: Analyze

Look for patterns. Which attributes consistently meet targets? Which ones show declining performance over time? Are there specific courses where students struggle, suggesting a curriculum gap rather than a student performance issue?

This analysis is the input to two outputs: the self-study narrative (which describes the program's performance to the visiting team) and the continuous improvement plan (which describes what the program will do about any gaps). Both should be grounded in the data, not impressions.

Step 4: Document and Act

This is the closing-the-loop step. Every piece of assessment data should have a destination: either it meets the target and is documented as evidence of satisfactory performance, or it does not meet the target and triggers a documented improvement action.

The documentation is the accreditation evidence. The action is the continuous improvement that CEAB expects to see. Programs that skip either half — documenting without acting, or acting without documenting — will find the visiting team asking the same question: "Show me the connection."

4. Why Many Programs Struggle to Close the Loop

Several structural barriers commonly keep programs from closing the loop. They are worth naming because they are not failures of will — they are failures of tooling:

• Assessment data lives in silos. Course-level results are stored in learning management systems, departmental drives, or individual faculty files. There is no central repository that connects course outcomes to program attributes to assessment results.
• Mapping is a snapshot, not a living document. The course-to-attribute map is built for the self-study report and then sits idle for years. Curriculum changes — new courses, revised outcomes, dropped prerequisites — happen without updating the map. By accreditation time, the map is outdated.
• Faculty are asked to produce evidence, not use evidence. Coordinators send requests asking faculty to "provide evidence for GA5." Faculty respond with confusion because they assessed students against course outcomes, not against GA5. The mapping layer is invisible to them.
• No automated aggregation. Combining results from dozens of courses into program-level reports requires manual data entry, copy-pasting between spreadsheets, and reconciliation of inconsistent formats. The time cost is prohibitive, so programs settle for summaries that are too coarse to be useful.

These barriers are solvable. They are not solved by working harder — they are solved by building the connections that currently require manual labour.

5. Practical Steps to Close the Loop This Year

You do not need a new assessment system or a semester-long project to start closing the loop. Here are five concrete steps, ordered by impact:

1. Audit Your Existing Assessment Data

Start with what you already have. Pull assessment results from the past two years. For each data point, ask three questions: What course outcome was assessed? What Graduate Attribute does that outcome map to? What was the aggregate result? If you cannot answer all three, that is a gap to close.

2. Build a Living Evidence Map

Replace the static spreadsheet with a system that updates when the curriculum changes. Every course should show its learning outcomes, each outcome should map to one or more Graduate Attributes, and each mapping should link to the assessment data that supports it. When a course is revised, the map updates. When new assessment results come in, they attach to the existing mapping.

This is exactly what connected evidence mapping does. Tools like MapOutcomes automate the link between syllabus outcomes, Graduate Attributes, and assessment results — so the map stays current without coordinator intervention.

3. Standardize Your Scoring Rubric

Adopt a common scale across all courses. A four-level scale is a common choice — for example, developing, proficient, advanced, exemplary. When every course uses the same scale, aggregation is straightforward and the visiting team can read the results without translating between different faculty grading conventions.

4. Create a Continuous Improvement Log

Every time assessment data triggers a curriculum change, document it: what the data showed, what action was taken, and what the result was. This log becomes a core section of your self-study report. It shows the visiting team that your program does not just collect data — it uses it.

5. Run a Semesterly Checkpoint

Set a recurring meeting — 30 minutes, once per semester — where the coordinator and department chair review the evidence map, check for gaps, and flag attributes that need attention. This replaces the six-month pre-visit scramble with steady, manageable maintenance.

6. What a Closed Loop Looks Like in Practice

Here is what the difference looks like when a program closes the loop versus one that does not:

Without a closed loop: Assessment results are collected each semester and filed. At accreditation time, the coordinator builds a spreadsheet mapping courses to attributes, asks faculty for evidence, and writes a narrative describing program performance from memory and fragmented data. The self-study report makes claims that are difficult to trace to specific results. The visiting team asks for evidence that takes weeks to produce.

With a closed loop: Assessment results are collected each semester and automatically linked to course outcomes and Graduate Attributes. The evidence map updates in real time. The coordinator runs a program-level report showing aggregate performance on each attribute, trend lines across cohorts, and documented improvement actions. The self-study narrative is drafted from the data, not about it. The visiting team asks for evidence and receives a traceable, one-click export.

The difference is not more work. It is connected work.

7. The Coordinator's Role: From Evidence Collector to Program Analyst

Closing the loop changes the coordinator's role in a way that most coordinators welcome. Instead of being the person who chases evidence every six years, the coordinator becomes the person who understands program-level learning outcomes at any moment.

That shift matters beyond accreditation. Department chairs use this data for curriculum reviews. Deans use it for resource allocation. Faculty use it to justify course changes. External stakeholders — employers, professional bodies, accreditation agencies — all want to see the same thing: that the program knows what its students can do and has evidence to prove it.

When assessment data becomes accreditation evidence automatically, the coordinator stops being a data janitor and starts being a program analyst. That is the role the position should have been from the start.

Closing Thoughts

The data already exists. The assessments are already running. The gap is not in what you measure — it is in how those measurements travel from the course to the program report. Closing the loop does not require new assessments or more faculty work. It requires a system that connects what faculty already do to what accreditation requires.

Programs that build that connection can turn accreditation preparation from a last-minute scramble into a routine report review. The evidence is already there. It just needs to be connected.

References

1. Engineers Canada, "2024 Accreditation Criteria and Procedures," Canadian Engineering Accreditation Board, Engineers Canada, Nov. 2024. [Online]. Available: https://engineerscanada.ca/sites/default/files/2024-11/Accreditation_Criteria_Procedures_2024.pdf