Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
XMethod Wiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Herzing Issues: Technology, LMS, and Platforms
(section)
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== HU-082: Spring 2025 system-wide grade transfer crisis: affecting 'hundreds of students'; recurring problem across multiple semesters with ZERO institutional communication === {| class="wikitable" style="width:100%" ! style="width:12em" | Severity | Critical ! style="width:12em" | Status | CONFIRMED |- ! Issue type | Mass System-Caused Course Failures ! Date added | 2026-05-05 |- ! Owner | colspan="3" | IT / Registrar / Academic Affairs / Dr. Prashad / Shannon Bishop / David Steele |} '''Finding.''' A system-wide grade transfer failure in Spring 2025 caused passing students to receive failing grades in Canvas and the official records system. Anonymous member 569 confirmed the crisis affected "hundreds of students." Documented individual cases include: Student B (Clinical II 86% became an F; summer classes auto-canceled); Student BM (2 A's and a B uploaded as 2 F's; withdrawn from program); Anonymous 510 (an A transferred as a B); Student AE (F from incomplete, financial aid affected); Student BN; Student BO; Student BP (still not enrolled in correct classes at next semester start). Zero official institutional communication was sent; students discovered the error only by monitoring their own grades. Student V confirmed this is a RECURRING problem: she experienced the same issue a few semesters earlier in the same class, and it was not fixed until several weeks into the new semester. Student B stated she was prepared to email the local press in Wisconsin. Escalation chain: Dr. Prashad to Shannon Bishop to Tricia Wagner to Sam (student services) to David Steele (dsteele@herzing.edu), who ultimately resolved some cases. '''Evidence.''' Facebook post by Student B (Apr 26, 2025) asking whether others were affected by the Spring grading issue. Student BM (Apr 26, 2025) reported two A's and a B being uploaded as two F's, resulting in withdrawal. Anonymous member 569 (Apr 27, 2025) confirmed the issue affected hundreds of students and was a system error, not a syllabus issue. Student B (Apr 30, 2025) reported her grades had still not been corrected with summer classes starting the following Monday. Student V (Apr 30, 2025) confirmed the same problem had occurred to her a few semesters earlier in the same class. Student B (Apr 26, 2025) reported zero communication from administration despite the institution's promptness in emailing about late payments. Source group: Herzing Direct Entry MSN Facebook Group Export (Dec 2022 to May 2026): Exhaustive Line-by-Line Review: 34,887 lines, 1,350 posts, 14,112 comments, 8 passes (Volume 7). '''Reported statement.''' Anonymous member 569 confirmed the grading error affected hundreds of students and was a system error rather than a syllabus issue. Student B reported that, as of April 30, her grades still had not been corrected even though summer classes were starting the following Monday, and separately noted that the institution had sent zero communication about the issue despite promptly emailing students about late payments. Student V confirmed the same problem had occurred to her in an earlier semester in the same class and was not fixed until several weeks into the following term. '''Standards.''' 34 CFR Β§668.14 (administrative capability): institutions must maintain functional grade recording infrastructure. ACEN Standard 5: technology must support student learning without causing academic harm. Due process (Dixon v. Alabama, 294 F.2d 150, 5th Cir. 1961): students may not be dismissed or academically penalized without meaningful process. FERPA (20 U.S.C. Β§1232g): students have the right to accurate educational records. Institutional failure to communicate a known system error that is causing erroneous course failures constitutes an administrative capability failure under 34 CFR Β§668.14. The recurring nature across multiple semesters establishes a pattern rather than an isolated incident. '''Impact.''' Affected students experienced wrongful course failures on official transcripts, auto-cancellation of the next semester's enrollment, disruption to financial aid eligibility, delayed graduation, scholarship application harm (unofficial transcripts showing F grades), and extreme emotional distress. The zero-communication approach placed the burden of discovery and remediation on students: students had to individually email faculty, program chairs, and registrar staff to trigger corrections. Student AE reported the error caused canceled classes and financial aid issues. Student BP (May 4, 2025) reported still not being enrolled in the correct classes for the semester. '''Notes.''' Recurring problem: Student V's statement that this happened a few semesters ago, in the same class, establishes this as an unresolved systemic issue rather than a first-time event. The institution has been aware of this failure mode for multiple semesters and has not implemented a structural fix. Cross-reference: {{HU|HU-075}} (Sherpath grade transfer failures), {{HU|HU-041}} (Sherpath platform failures), {{HU|HU-076}} (Realizeit failures). This issue extends {{HU|HU-075}} significantly: where {{HU|HU-075}} documented a general pattern, this issue establishes the Spring 2025 mass event with named individuals, documented cascading harms, and recurring history. <span id="HU-092"></span>
Summary:
Please note that all contributions to XMethod Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
XMethod Wiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)