Case Study: A Complete Closing-the-Loop Cycle, Step by Step
What this is. A fully worked assessment-to-improvement cycle built on our open sample dataset (a certification course at a fictional technical college, with synthetic student records). Every number below comes from the downloadable dataset, so you can check the math yourself. It is published as a demonstration of the method, not as a customer testimonial. Real institutional case studies will be added here as pilot partners complete cycles and approve publication.
The setup
A technical college runs a Security+ certification course. For Module 8 (Network Security), the instructor defines three course-level outcomes, each mapped to a CompTIA SY0-701 exam domain:
| Code | Outcome | Framework alignment |
|---|---|---|
| SLO-001 | Students identify network security threats and vulnerabilities | SY0-701 Domain 1.1 |
| SLO-002 | Students recommend mitigation strategies for identified threats | SY0-701 Domain 1.2 |
| SLO-003 | Students analyze and defend against attack vectors | SY0-701 Domain 1.3 |
The evidence source is an assessment the course already uses: a hands-on test at the end of the module. No new assignments were created. Twenty students each receive a rubric score (4 = Proficient, 3 = Developing, 2 = Beginning, 1 = Insufficient) on each of the three outcomes: sixty direct-evidence data points from one class session.
The results
Proficiency here means the percentage of students scoring 3 or higher. Aggregating the sixty rubric scores:
| Outcome | Proficient (4) | Developing (3) | Beginning (2) | Insufficient (1) | Proficiency |
|---|---|---|---|---|---|
| SLO-001 Threat identification | 9 | 8 | 3 | 0 | 85% |
| SLO-002 Mitigation strategies | 4 | 8 | 7 | 1 | 60% |
| SLO-003 Attack vector defense | 6 | 9 | 4 | 1 | 75% |
The pattern is the finding. Students recognize threats (85 percent) but a large group cannot yet recommend what to do about them (60 percent). Grades alone would never have shown this: most of these students passed the module. The outcome-level data shows exactly where the curriculum is thin.
Closing the loop
This is the record accreditors look for and institutions most often skip. All five required parts, exactly as they appear in the dataset:
- Finding
- Students demonstrated strong threat identification skills (85 percent proficiency on SLO-001) but struggled with mitigation strategies (60 percent proficiency on SLO-002). The curriculum provides solid foundational knowledge but lacks depth in defensive techniques.
- Change implemented
- Add two detailed case studies on network defense strategies to the study guide. Increase hands-on practice time for mitigation scenario labs. Integrate real-world defense case studies from recent security incidents.
- Responsible person
- The course instructor.
- Target date
- July 15, 2026 (before the next cohort begins).
- Verification plan
- Re-assess SLO-002 with the Fall 2026 cohort using the same rubric on the same hands-on test. Target: move proficiency from 60 percent to at least 75 percent.
Note what makes this record complete: the change is specific (not "we will monitor the situation"), a named person owns it, it has a date, and the verification plan commits to re-measuring the same outcome with the same instrument. When the Fall data comes in, the comparison is one chart: 60 percent before, whatever the new number is after. That trend line is the evidence of improvement accreditors ask for, and it is also the moment faculty see the process pay off.
Why this cycle is worth copying
- It used an existing assessment. Zero new grading burden; the rubric structured scoring the instructor was already doing.
- It produced direct evidence. Rubric-scored student performance, not survey opinions or course grades.
- The finding was actionable. One specific weak outcome, not a vague sense that "students struggle."
- The loop actually closes. A change, an owner, a date, and a re-measurement commitment: the four things that separate documentation of activity from intentional improvement.
The full method behind this cycle is covered in the practitioner's guide to outcomes assessment, and the 4-week faculty adoption process that gets instructors to run cycles like this willingly is in the Faculty Onboarding Playbook.
Real institutional case studies
In progress. A pilot of this exact cycle is currently running with real course data at a technical college. When the verification cycle completes and the institution approves publication, the documented before-and-after results will be published here. Any customer institution gets the same treatment: run a cycle, and with your approval we will write it up.
Want to run this cycle on one of your own courses?
Download the sample data and templates, or ask for a guided demo and we will walk your team through the same steps with your own program.
Try It With Sample Data