Students occasionally report problems with a viva or disagree with the outcome. The platform keeps a record of what happened in each session and provides actions for adjusting an attempt or its outcome. This article describes what is available and points to the existing articles where each action is covered in detail.
What students typically report
Three categories cover most of what comes in:
- A technical issue during a session. A microphone that did not pick up sound, a network drop that ended the session, a frozen page that required a refresh.
- A technical issue after a session. A result that has not appeared, a button that does not respond, a confirmation email that did not arrive.
- A dispute over an outcome. The student feels the report does not reflect their performance, that a question was misread, or that the score is inconsistent with their submission.
The first two relate to whether the session ran as intended. The third relates to whether the report is right.
Where the evidence lives
The student's report holds a record of each attempt. Two of the sections are present for every viva, and two are present only when proctoring was enabled.
- Student answers. The question by question view, with the transcript on each row.
- Score analysis. Per criterion scores with the reasoning behind each.
- Incident logs (proctored vivas). Events flagged during the session, alongside the timestamp and current status of each.
- Session Replay (proctored vivas). Playback of the recorded session. Selecting an incident in the log opens the replay at the relevant timestamp.
Read together, these provide a record of how the session ran and how the report was arrived at. For vivas without proctoring, the answers and the scoring carry the full record.
What is available in response
The platform provides a number of actions on the report and in the students table. Each is covered in detail in the relevant article:
- Editing the summary changes what the student sees on release. Inline edits flow through to the released report. See Reviewing Student Attempts.
- Granting another attempt raises the maximum on the Attempts column, and the student can re attempt the viva. See Managing Student Attempts.
- Standing by the draft is a reply through your usual channel, with reference to the relevant parts of the report.
- Dismissing an incident marks it as reviewed without further action. The change is recorded in the activity feed.
- Deleting an attempt removes it from the student's record entirely, including the score, transcript, and replay. The action cannot be reversed.
Editing the summary and granting an attempt are the responses chosen most often. Deletion is comparatively rare, and while a dispute or appeal is open, the original attempt forms the evidence record.
Where Integrevise support helps
The Integrevise support team can help with three kinds of issue:
- A bug. A page that does not load, an unresponsive control, or an error several students have reported.
- A pattern across the cohort, suggesting a configuration or platform problem rather than something specific to one student.
- An action only the support team can take, such as restoring a deleted attempt or extracting evidence in an unusual format.
The contact form on Help & Support or contact@integrevise.com are equivalent routes; see Getting Help.
Where institutional process applies
Two situations sit outside what the platform decides:
- A formal academic appeal. Once an appeal is open, the original attempt forms the evidence record (transcript and scores, plus replay and incidents where proctoring was enabled), available for the duration of the appeal.
- A misconduct concern. Patterns that suggest an integrity breach are flagged for review rather than adjudicated by the platform; the outcome follows your institution's process.
The platform records remain available throughout in both cases.
Audit
Every adjustment is recorded in the module's activity feed: grants, reductions, deletions, dismissals, and edits. The feed provides a chronological record, available for later reference.