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: Proctoring and Testing
(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-163b: The exam was marked a no-show despite the student's documented contemporaneous contact about the weather and internet outage before the window closed, and the no-show then triggered the reschedule lock === {| class="wikitable" style="width:100%" ! style="width:14em" | Severity | High ! style="width:14em" | Status | CONFIRMED |- ! Issue type | No-Show Miscategorization Despite Prior Contact ! Date added | 2026-06-06 |- ! Owner | colspan="3" | ProctorU Inc. d/b/a Meazure Learning |} '''Finding.''' ProctorU stated the exam had been marked a no-show and that, as a result, it could not process scheduling within its restriction window. The reporting student documented that he had contacted ProctorU via chat from his phone before the exam, reporting that his internet was out due to the weather, so the appointment should have been set for reschedule rather than recorded as a no-show. The no-show designation then triggered the lock that prevented any in-window reschedule. '''Evidence.''' ProctorU/Meazure email (Rahul Pradhan) stating the exam has now been marked as a no-show and scheduling cannot be processed within 72 hours; the reporting student reply asking why it was marked a no-show when he contacted ProctorU prior to the exam via chat about the internet outage; ProctorU live chat (June 6, 2026, 1:46 PM CDT). '''Reported statement.''' <blockquote>Why was it marked as a no show? I contacted you prior to the exam in chat to let you know via my phone that my internet was out due to bad weather so it should have been set for reschedule rather than marked as a no-show.</blockquote> '''Standards.''' 34 C.F.R. 668.14 (administrative capability and accurate records, including over a testing vendor). Recording a weather-and-connectivity interruption (reported in real time) as a no-show, and then using that designation to deny an in-window reschedule, is a records-accuracy and fair-process concern. Lead: {{HU|HU-163}}. '''Impact.''' The no-show entry, rather than a reschedule flag, is what locked the student out of his remaining in-window date and routed him into a makeup and appeals process. '''Notes.''' Sub-issue of {{HU|HU-163}} (lead). Documented 2026-06-06. Student: The reporting student. Source Group: ProctorU/Meazure support thread (ticket 8041745); ProctorU live chat, June 6, 2026. <span id="HU-163c"></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)