Portal  /  Standards  /  Assessment Closing the Loop ← Action Plan Item 5
MSCHE ASSESSMENT EXHIBIT · DRAFT

Assessment Closing the Loop — Moodle to CampusOS

Assessment results driving a real institutional action — one of the strongest exhibit types under MSCHE's assessment standard, once the underlying data is attached.
Draft — data needed
Standard
3 — Design, Delivery & Assessment
Exhibit No.
Pending assignment
Owner
TBD
Status
Outline only — awaiting real data
Target
Before September 1
Source
Practice-interview debrief

1The Story, As Told in the Practice Interview

This is the outline given in the debrief — accurate as a summary, but not yet backed by cited evidence.

💬
Student Complaints
About the Moodle platform
→
🔍
Review
Complaints assessed
→
✅
Decision
Switch to CampusOS
→
🚀
Outcome
CampusOS in full use today

The evaluator specifically called this out as strong evidence and asked that more than one person — not just the original respondent — be ready to tell it consistently.

2Why This Example Matters

"Closing the loop" — assessment or feedback data leading to a documented, real institutional action — is exactly what MSCHE Standard 3 (Design, Delivery & Assessment) wants to see. Most institutions can describe their assessment process; fewer can point to a concrete decision it actually produced. This story is a genuine example of that, which is why the evaluator flagged it — but a verbal answer isn't a citable exhibit. It needs to be written down with dates, data, and a record of the decision.

3What Still Needs to Be Documented

Every row below needs a real answer from institutional records — nothing here is filled in with a guess.

QuestionWhat's Needed
When was the problem identified?Term/date the Moodle complaints were first raised or noticed
What data showed the problem?Survey results, support-ticket counts, complaint emails, or meeting minutes discussing it
How many students / what themes?Approximate volume and the specific issues raised (e.g., usability, reliability, mobile access)
Who reviewed it, and how?Was it a formal assessment committee review, a leadership meeting, or an informal escalation? Name the body/process
Were alternatives considered?Other LMS platforms evaluated, if any, and why CampusOS was selected
When was the decision made?Approximate date or term of the decision to switch
Migration timelineWhen the switch happened and how long it took
Outcome / did it work?Any post-migration survey or feedback data showing improvement

4Evidence We Already Have

  • HaveCourse Management — the CampusOS tooling now in place (shows the outcome, not the origin decision)
  • HaveHow to Set Up Your Classroom — full CampusOS walkthrough
  • HaveVideos Library — CampusOS training videos
  • HaveMeeting Briefing — May 9, 2026 — a later technical review/refinement of CampusOS (student status fields, reporting) with the system developer; useful as evidence CampusOS was actively being operated and improved, but does not document the original switch decision
  • NeedAny record (survey, tickets, minutes) capturing the original Moodle complaints and the decision to switch — not yet found on the portal

5Who Should Be Ready to Tell This Story

The evaluator asked that multiple people — not only the original respondent — be able to share this example consistently. Identify 2–3 additional staff (e.g., whoever led the CampusOS evaluation, a faculty member who taught through the transition, IT/LMS administrator) and brief them on the same facts once this page is complete.

6Action Plan

#StepOwnerStatus
1Locate the original Moodle complaint data (survey results, tickets, emails, or meeting minutes)TBDNot Started
2Identify who reviewed the complaints and how the decision was madeTBDNot Started
3Confirm the decision date and migration timelineTBDNot Started
4Gather any post-migration data showing the outcome improvedTBDNot Started
5Fill in Section 3 above with the real answers and cite sourcesTBDNot Started
6Assign a formal exhibit number and brief 2–3 additional staff to tell the storyTBDNot Started
MSCHE Assessment Exhibit — Draft · Standard 3 (Design, Delivery & Assessment) · Target: September 1 · Prepared by iCyber Enterprises LLC — Your Education Consultant.