Editing Herzing Issues: Proctoring and Testing (section)

=== HU-182: The reporting student's July 1, 2026 exam started over an hour late due to a ProctorU/Meazure Learning staffing error, which he identified as the seventh or eighth instance of a delayed exam start in the prior six months, citing five specific prior dates ===
{| class="wikitable" style="width:100%"
! style="width:14em" | Severity
| High
! style="width:14em" | Status
| CONFIRMED as to the July 1, 2026 delay and Meazure Learning's own acknowledgment of a scheduling error; the characterization as the seventh or eighth such instance rests on the reporting student's own count and the five listed dates, which are CONFIRMED as dates he reports delays occurred but have not been independently corroborated against a separate proctoring log in this entry
|-
! Issue type
| Chronic ProctorU Staffing and Scheduling Failure Causing Repeated Delayed Exam Starts
! Date added
| 2026-07-17
|-
! Owner
| colspan="3" | ProctorU Inc. d/b/a Meazure Learning / Herzing Testing and Accommodations
|}
'''Finding.''' Meazure Learning Compliance wrote to the reporting student acknowledging that he experienced a delay in being assigned a PRO Proctor and starting his July 1, 2026 exam administration, attributing it to an inadvertent scheduling error that caused an issue with PRO Proctor availability, apologizing for the inconvenience, and stating a commitment to ensuring PRO Proctor availability for future scheduled exams. Forwarding this response to Herzing ADA, Student Affairs, and Academic Operations staff, the reporting student stated that he started the exam over an hour late, that he would normally accept an isolated apology of this kind, but that this was the seventh or eighth time this had happened in the prior six months, and that simply not scheduling sufficient PRO Proctor staff when students schedule their exams is not acceptable. He listed five specific additional dates on which his exam had started late or been delayed: June 5, June 6, June 13, June 2, and May 4, 2026, and asked what Herzing and the vendor needed to do to ensure consistency. The June 6, 2026 date on this list corresponds to the weather-related no-show and reschedule-lock failure already documented in the {{HU|HU-163}} cluster, so at least one of the five listed dates is independently corroborated elsewhere in this tracker; the remaining four dates (May 4, June 2, June 5, June 13, 2026) are not yet separately documented as standalone entries and rest on the reporting student's own account as stated in this email.

'''Evidence.''' Email, Meazure Learning Compliance to the reporting student: acknowledgment of an inadvertent scheduling error causing PRO Proctor unavailability and delay for the July 1, 2026 exam, an apology, and a stated commitment to future availability. Email, the reporting student to Herzing ADA, Student Affairs, and Academic Operations staff: statement that the exam started over an hour late, that this was the seventh or eighth such instance in six months, and a list of five additional dates (2026-06-05, 2026-06-06, 2026-06-13, 2026-06-02, 2026-05-04) on which his exam started late or was delayed. Cross-reference {{HU|HU-163}} (the June 6, 2026 weather-related no-show and reschedule failure, one of the five listed dates).

'''Reported statement.'''
<blockquote>Typically, I wouldn't have a problem with the response like this and would be understanding, but this is the seventh or eighth time this has happened in the last six months. Simply not scheduling people to be on staff when students schedule their exams is not acceptable.</blockquote>

'''Standards.''' 34 C.F.R. Section 668.14 (administrative capability, including effective oversight of a contracted testing vendor) and, given the reporting student's documented testing accommodations, the Americans with Disabilities Act (42 U.S.C. Section 12101 et seq.) and Section 504 of the Rehabilitation Act (29 U.S.C. Section 794), since unreliable proctor staffing has a disproportionate effect on a student who requires a PRO Proctor as part of an approved accommodation. A single delayed exam start, standing alone, would be a minor operational issue; a repeated pattern of seven or eight such instances in six months, if corroborated, would support a finding of a systemic vendor staffing and scheduling reliability failure rather than isolated incidents.

'''Impact.''' Repeated delayed exam starts disrupt testing conditions, consume accommodated testing time, and add to documented cumulative stress and administrative burden already reflected elsewhere in this tracker, including the appeals volume referenced in {{HU|HU-163e}}. If the pattern of seven or eight delayed starts in six months is corroborated, it would indicate the vendor's PRO Proctor staffing problem is ongoing and unresolved despite prior institutional awareness of at least the June 6, 2026 instance documented in {{HU|HU-163}}.

'''Notes.''' Recommend requesting from ProctorU/Meazure Learning or from Herzing a complete log of the reporting student's scheduled exam start times and any delays for the six-month period referenced, to independently corroborate the seven-or-eight-instance count and the four dates (May 4, June 2, June 5, June 13, 2026) not yet separately documented in this tracker.

Student: The reporting student.

Source Group: Email, Meazure Learning Compliance to the reporting student, subject Fw: July 1, 2026 Exam Administration; forwarded by the reporting student to Herzing ADA, Student Affairs, and Academic Operations staff with a list of five additional delay dates; out-of-office auto-replies from Emilie Thompson and Shannon Bishop; provided by the reporting student.

Cross-References: {{HU|HU-163}} and its sub-issues {{HU|HU-163a}} through {{HU|HU-163e}} (the June 6, 2026 weather-related no-show and reschedule-lock failure, one of the five dates listed here), {{HU|HU-163e}} (Notes updated 2026-07-17 to reference this entry); {{HU|HU-187}} (cumulative examination scheduling compression resulting from this pattern of delays and disruptions, added 2026-08-04).

<span id="HU-187"></span>