Skip to content

What a candidate actually sees during the exam

The paper, and nothing in the way of it

StudyDrome Exam Manager runs the exam in three columns: a question navigator, a case-vignette context panel, and the question itself. Candidates flag items, keep private notes, and raise feedback on a specific question. Answers are saved on their own schedule per question type. An essay saves every 30 seconds as well as after typing stops.

Book a pilot

How does a candidate get from login to the exam?

  1. 1

    The candidate signs in and lands on the Tests page. The student app ships two menu items: My Courses and Tests. Every other address sends them back to the tests list.

  2. 2

    The list shows what they are eligible to sit. Each row carries a single primary action, whose label and enabled state follow where that attempt has got to.

  3. 3

    Where a hold applies, the reason sits inline next to a disabled button. The candidate reads why rather than guessing.

  4. 4

    Opening a test shows the intro screen with your instructions. There is no attempt yet, so reading the rules costs nothing.

  5. 5

    Starting the attempt opens the player in full screen. There is no menu around it — the paper is the whole surface.

  6. 6

    Submitting ends the attempt and takes them to the results page first, if the exam turns it on.

What does the exam screen give a candidate?

The exam runs in three columns. The navigator sits on the left and the question on the right. A case vignette fills the middle for the questions that have one.

Column

What it carries

Navigator

Every question in the paper. Each badge shows whether it is answered or unanswered, and whether it is flagged.

Context panel

The shared case vignette for questions that use one. It can be magnified if the exam allows.

Question

The item itself, with flag, feedback, and messages within reach.

On a phone, the navigator becomes a dropdown, and the context panel becomes an accordion. The paper is the same paper. Nothing is dropped to make it fit.

Four things sit next to the question, and each is one action:

  • Flag for review, tooltipped "Flag for review" and "Remove flag".
  • Feedback, tooltipped "Report issue with question" — a ticket against that specific item, raised while the candidate is looking at it.
  • Messages, tooltipped "View Messages", with an unread badge when a proctor has written.
  • Notes: a draggable popup that holds up to 1000 characters, shown only when the exam allows notes.

The navigator is built for a screen reader, not just for a mouse. Each badge announces itself as "Question 4, Heart failure, answered, flagged for review". A candidate who cannot see the color still gets the state.

Clicking a question saves the one you leave last. The move waits for that flush before it navigates. StudyDrome also tells the server which question is being viewed, so time spent per item is recorded rather than inferred.

When does an answer get saved?

Each question has its own saving pipeline. Typing in one item never cancels the save of another. That is the failure a single shared queue produces on a long paper.

The cadence differs by question type, because the typing does. A candidate finishes picking an option the moment they click. A candidate writing an essay is not.

Question type

When the answer is sent

Multiple choice, checkboxes, true/false, and the other selection types

Immediately on the click

Fill in the blank

One second after typing stops

Short answer

Three seconds after typing stops

Essay

Three seconds after typing stops, and every 30 seconds regardless

The essay pair is the one that matters. A debounce alone protects somebody who stops to think. The interval protects somebody who does not. Long answers are written by people who do not.

The screen says "Saving..." while a call is out. It confirms with "Answer saved successfully". A pending answer clears only when the server genuinely accepts it. An answer that failed stays queued, rather than looking saved.

What happens when the connection itself goes is a different mechanism with its own answers, covered in losing internet mid-exam.

Which settings decide what a candidate gets?

StudyDrome Exam Manager says this out loud in the product, on the screen where these choices are made:

Important Note — These settings help prevent cheating but may affect user experience. Test thoroughly before deploying to students.

That is the whole trade-off in two sentences, and it is worth reading as an instruction. Three settings determine what the candidate sees during the paper.

Setting

What it gives the candidate

Ships as

Review page

A screen before submission listing every question, answered and flagged

Off

Question text in review

Full question text on that screen rather than titles alone

Off

Marks

The point value of each question, during the sitting

Off

All three arrive off, and that is a decision somebody should make on purpose. A candidate gets the review page because the exam office enabled it. Never because a default happened to be generous. The same holds in reverse, which is why the note says to test it first.

All three are captured into the exam at the moment you publish it. They sit alongside everything else that has to stay fixed for the sitting. The mechanism is set out in what freezes at publish.

What happens when a candidate submits?

Submitting from the review page flushes any pending items. It then warns about unanswered questions or blocks them, depending on how you configured the exam. The candidate reads "Review all questions before submitting", with "{n} of {total}" answered and "{n} flagged for review". They choose between "Back to Test" and "Submit Test".

Afterward, the candidate lands on a results page. It shows the score or an explicit panel stating the server's own reason that the results are not yet ready. A stated reason, rather than an empty screen.

How much detail that page carries is a live setting. The exam office widens or narrows it after the fact, with no republish. Their view of it is on Exam Manager for examinations offices.

The exam screen, in plain terms

Question navigator
The list of every question in the paper, down the left of the screen. Each badge shows whether that question is answered and whether it is flagged.
Flag for review
A marker a candidate puts on a question to come back to it. It changes nothing about the answer or the score, and it is visible on the navigator and the review page.
Context panel
A middle column holding a shared case vignette, shown only for questions that have one. Several questions can draw on the same case without repeating it.
Review page
A dedicated screen before submission listing every question with its answered and flagged state. It is off unless the exam turns it on.
Pending answer
An answer the candidate has given that has not yet been confirmed and saved by the server. It clears only on a genuine success.
Image magnification
Let's have a candidate enlarge an image in the context panel. It is a per-exam setting rather than something the candidate turns on.

What does the exam player guarantee?

The friction the interface creates gets scored as though it were ignorance. These are the properties that keep it out of the way.

  • Leaving a question saves it first. The move waits for the flush, so navigation can never cost an answer.

  • Every question saves on its own pipeline, so a long essay and a quick click never queue behind each other.

  • A pending answer clears only when the server accepts it. An answer that failed stays queued rather than looking saved.

  • The navigator announces the answered, unanswered, and flagged states to a screen reader, not only through color.

  • The phone layout carries the same paper. The navigator becomes a dropdown, and the case panel an accordion.

  • Feedback is raised on a single question while the candidate is on it, so the item is identified precisely.

  • Time is recorded for each question on the screen itself, rather than inferred from when answers arrived.

Who should care about the candidate experience?

  • Exam offices:The review page, marks, and question text are your decisions, and candidates inherit whatever you leave them.

  • Teaching staff:Question feedback arrives tied to a specific item, which is how a bad item gets found on the day rather than at the board.

  • Assessment leads:Per-question timing and flag data describe how the paper was actually sat, not just how it was scored.

  • Disability and support teams:The navigator is built to be heard as well as seen, and notes and magnification are settings you can require.

Frequently asked questions

Can candidates move freely between questions in a StudyDrome exam?

Yes. The navigator lists every question in the paper, and a candidate can jump to any of them. Clicking one saves the question they are leaving before the move happens, so navigating never costs an answer. Each badge shows whether that question is answered and whether it carries a flag.

How often are answers saved during an exam?

It depends on the question type, because typing does. Selection questions send the answer on the click. Fill-in-the-blank waits one second after typing stops; short answer: three seconds. An essay waits three seconds after typing stops and again every 30 seconds, which covers a candidate who writes without pausing.

Can candidates make notes during an exam?

Yes, when the exam allows it. Notes open in a draggable popup that holds up to 1000 characters and stay private to that candidate. Because the popup can be moved, a candidate can keep working out an answer while still reading the question. It is a per-exam setting rather than something they switch on.

How do candidates report a problem with a question mid-exam?

There is a feedback action beside the question itself, tooltipped "Report issue with question". It raises a ticket against that specific item while the candidate is looking at it, so nobody has to work out afterward which question they meant. Proctor messages arrive in the same area and show an unread badge.

Do candidates get a chance to review answers before submitting?

When the exam turns the review page on, it lists every question with its answered and flagged state, summarised as "{n} of {total}" answered and "{n} flagged for review". Submitting from there flushes anything still pending and then warns or blocks on unanswered questions, depending on how you configured it.

Does the exam work properly on a phone or tablet?

Yes, and it carries the same paper. The question navigator collapses into a dropdown, and the case-vignette panel becomes an accordion, so the layout reorganizes on smaller screens rather than dropping anything. Flagging, notes, feedback and messages are all still within reach.

Book a pilot

Sit one of your own papers as a candidate. We will run it on a laptop and a phone and show you the settings behind every screen you meet.

Book a pilot

Related