Test session administration¶
A test session is like a virtual classroom. Invigilators use it to manage test-takers as they complete an assessment. An administrator or invigilator sets it up once the assessment event has been switched to Delivery mode.
Test-takers complete the assessment in Janison Replay or a browser. Their progress appears in real time on the Test Sessions Administration dashboard. From there you start and finish the session, and manage individual test-takers — for example, pausing a test or granting extra time.
Important
Janison Insights is highly customisable. Depending on your site's configuration and your role's permissions, your screens may differ from the images on this page.
Practise running a test session¶
Test session simulation
Practise running a test session, with a guide beside each step. You create a session, start it and admit a late arrival. Then you handle a disruption and 2 device problems, award extra time and finalise. Done it before? Skip straight to free practice.
Test-day scenarios
The simulation shows you how. These ask what you'd do when something goes wrong on test day, and every choice shows what happens next.
Test-day scenarios
These scenarios put you in the invigilator's seat when something goes wrong during a test session. Each one sets the scene and asks what you'd do. Every choice tells you what happens next, so try the ones you wouldn't pick too.
Every scenario is set in Room 12 at Bligh High. You're the invigilator, and 10 test-takers are sitting 2026 Y9 Numeracy, a 40-minute test, in Janison Replay. Your site's settings can change some of what happens; see Settings.
A laptop freezes mid-test
Ten minutes into the test, Bao Nguyen puts his hand up. His laptop froze a couple of minutes ago, and nothing on screen responds to the mouse or keyboard.
What do you do first?
A restart is usually all a frozen laptop needs. You hold the power button until the laptop turns off, then start it again. Bao opens Replay and enters his one-time code and the session code.
His screen says his test is locked to another computer or device, and asks him to speak to his test administrator. On your dashboard, a lock icon has appeared in his Actions column.
What do you do?
Bao moves to the spare laptop and enters his codes. A lock icon appears in his Actions column, you accept, and he carries on. It works, and it's the move to make when a laptop won't restart. It just isn't the first thing to try.
A restart is usually all a frozen laptop needs, and it keeps Bao on the laptop he started on. If the session can run offline, that laptop may hold answers that haven't reached Insights yet. Whenever you do swap laptops, set the frozen one aside, and don't reset or reinstall Replay on it.
You tick Bao's row, but Pause Test-taker is unavailable. You can pause only test-takers who are online, and a frozen laptop stops checking in with Insights. Within about a minute, the dashboard counts him as offline.
Bao's clock is still running. It runs on the Insights server, not on his laptop, so every minute the laptop is frozen comes off his time. Pause session would stop it, but it would stop the whole room too. Note the time instead, so you know how much to give back, and get him working again.
Submitting doesn't give Bao a fresh start. It hands in his test with only the answers he'd saved, and ends his attempt.
To undo it, you'd tick him on the Submitted tab and select Reopen test-taker, which works only while the session is running. When a test-taker's device fails, keep their attempt open and get them back into it.
Bao's test opens where he left off. The lock icon appeared because Insights locks each attempt to the sign-in that started it, not to the laptop. A new sign-in waits for you, even on the same laptop, so no-one can pick up his test without you knowing.
Some events skip this step. Where Allow re-entry to a test without needing to be unlocked is turned on for the event, a new sign-in takes over the test straight away, and no lock icon appears.
His answers are all there, apart from any change he was making to the item on screen when it froze. Insights saves an answer each time he moves to another item.
All up, Bao has been without a working laptop for 7 minutes. What do you do about his time?
Reject turns away Bao's new sign-in. His screen now says his session has expired or been closed by the test administrator, and his test is still locked to the frozen sign-in.
He has to enter his codes again so you can accept them, and his clock runs the whole time. Reject is for a sign-in you don't expect, such as someone using another test-taker's codes.
The lock doesn't clear on its own. Bao's laptop checks about every 20 seconds whether you've let him in, and keeps waiting until you do. His clock is running all the while.
Tick Bao's row, select Award more time, enter 7 in Time to add and say why in Details. His test now ends 7 minutes later. If your site uses incident reporting, report a Technical incident too, recording 7 minutes as both time lost and time awarded.
What to take away from this one:
- A test-taker's clock keeps running when their device fails, and nothing pauses it automatically.
- Insights saves an answer each time a test-taker moves to another item, so a restart loses only unsaved changes to the item on screen.
- A new sign-in waits for you to accept it, even on the same laptop, unless the event allows re-entry without unlocking.
- Only Award more time gives a test-taker time back.
Bao loses 7 minutes. His clock runs on the Insights server, not on his laptop. It kept going while the laptop was frozen, and while he waited for you to let him back in. Nothing gives that time back unless you award it.
Bao still loses 7 minutes. Time awarded on an incident report is a record of what you did. It doesn't change his test. Only Award more time on the dashboard gives him the time back.
That's fair to Bao, but not to the rest of the room. He now has 8 minutes more than everyone else. Give back the time a test-taker lost, and no more.
If you've given too much, tick his row and select Award less time to take back the extra.
Create a test session¶
You create test sessions from the Delivery Dashboard. For the steps, see the test centre dashboard.
You can create several sessions for one event — for example, one per room — so each invigilator sees only the test-takers in their room. Or use a single session so invigilators can monitor everyone at once.
The session dashboard¶
The Test Sessions Administration dashboard is where you manage the session and its test-takers.
Select each plus (+) marker on the screenshot to see what that part of the dashboard does. Use the arrows on a label to step through all 10 in order.
- Manage the session Use these buttons to pause, resume, finalise or abandon the whole session.
- Session code The code test-takers enter to join this test session.
- Download session details Downloads the Invigilator Session Details Excel report. It shows the assessment event details, the disability adjustment codes and each test-taker's details, including their start and end times.
- Allow unrestricted entry When ticked, test-takers who join after the session has started can enter without you having to allow them in.
- Pause proctored sessions When ticked, a proctored test pauses if it loses its connection to the proctoring software.
- Number of test-takers How many test-takers have accessed the test session.
- Manage test-takers Search for a test-taker, then use these buttons on the ones you've ticked. Which buttons appear depends on the tab you're on and the session's state.
- Status filters Filter the list of test-takers by status: All, Not started, Started, Paused, Submitted, Waiting entry or Other. Waiting entry is hidden while Allow unrestricted entry is ticked.
- Test-taker details and progress Each test-taker in the session, with their one-time code, status and progress.
- Test attempt information Select this icon in the Actions column to see a test-taker's test attempt information.
The icon in the Actions column opens the Test Attempt Information window for that test-taker.
Depending on your site, the dashboard can also show:
- an incident count, with Report incident and View timeline — see incident reporting
- a Scan check-in button below the test-taker count
- the time the session will be finalised automatically, if it has a maximum duration — see auto-finalise test sessions
- a warning that the session may be running offline, as a reminder to reconcile every Replay device before you finalise
Important
Test-takers who complete the test offline may not appear on the dashboard until their attempt has been reconciled.
Confirm an action¶
Most actions on this page open a dialog before they take effect. It can contain:
- Test-takers selected, showing how many test-takers the action applies to
- a time field, for actions that add or remove time
- Reason, a list of reasons your site has set up — it appears only if reasons are configured
- Details, for a note about why you took the action — it's optional unless your site requires it when the reason is Other
Complete the fields, then select Confirm. Select Cancel to back out.
Some actions show a final message after the dialog, such as "Are you sure?" or a confirmation that the action worked. Select Yes or Ok to close it.
Start a session¶
Before the session starts, the dashboard shows short prompts: write the session code on the board, wait for test-takers to join, then start the session. Test-takers appear on the dashboard as they join, but they can't start their tests until you start the session.
To start the session:
- Select Start session.
- A message asks you to confirm. It also tells you whether test-takers who join later will be admitted automatically or will need you to admit them. Select Yes.
Cancel a session¶
If a session isn't needed, you can cancel it before it starts. Cancelling releases the test-takers from the session so they can join a new one straight away. The session can't be used again.
- Select Cancel session.
- Select Yes to confirm.
- If your site uses reasons, complete the dialog and select Confirm.
Pause and resume a session¶
You may need to pause the whole session — for example, when test-takers leave the room for a fire drill. Pausing stops every test-taker's time and locks them out of their items. When you resume, they continue with the time they had left.
Pause a session¶
- Select Pause session.
- In the Pause session dialog, enter any details and select Confirm.
Resume a session¶
The Resume session button replaces Pause session while the session is paused.
- Select Resume session.
- In the Resume session dialog, enter any details and select Confirm.
- A message warns that this resumes the test for everyone in the session and starts their timers. Select Yes.
Award or remove time¶
You can add or remove time for test-takers in a timed test. These buttons appear only when at least one test in the session is timed.
Both are unavailable while any test-taker you've ticked is offline. If a device has frozen or lost its connection, award the time once the test-taker is back in their test.
Award more time¶
- Tick the checkbox next to each test-taker.
- Select Award more time.
- Enter the number of minutes in Time to add, add any details, and select Confirm.
Award less time¶
Award less time appears once someone in the session has been awarded extra time. It's unavailable if any test-taker you've ticked wasn't awarded extra time.
- Tick the checkbox next to each test-taker.
- Select Award less time.
- Enter the number of minutes in Time to reduce, add any details, and select Confirm.
Pause and resume test-takers¶
You can pause an individual test-taker — for example, if they need to leave the room. Pausing stops their time and locks them out of their items.
Pause a test-taker¶
You can pause only test-takers whose test has started and who are online.
- Tick the checkbox next to each test-taker.
- Select Pause Test-taker.
- Enter any details and select Confirm.
Resume a test-taker¶
Paused test-takers appear on the All and Paused tabs.
- Tick the checkbox next to each paused test-taker.
- Select Resume test-taker.
- Enter any details and select Confirm.
Resume test-taker is unavailable if any test-taker you've ticked isn't paused.
Admit waiting test-takers¶
Test-takers who join after the session starts wait to be admitted. You can admit or reject them one at a time, or admit everyone at once. These buttons appear once the session has started.
Note
If Allow unrestricted entry is ticked, test-takers who join late enter without waiting, and the Waiting entry tab is hidden.
Until they're admitted, test-takers see a Wait to begin screen.
Admit or reject individual test-takers¶
- Select the Waiting entry tab.
- Tick the checkbox next to each test-taker. Tick the checkbox in the header row to select everyone.
- Select Allow Start or Reject Entry.
The Allow Start attempt or Reject Entry attempt dialog opens. Enter any details and select Confirm.
Admit all test-takers¶
To admit everyone who's waiting, select Start All. It appears on the All and Waiting entry tabs.
Allow entry on a different device¶
Each attempt is locked to one sign-in, not to a device. Once a test-taker has started their test, entering their codes again means you must admit them before they can continue. That includes moving to a different device, and signing in again on the same device after a restart. A lock icon appears in their Actions column, and their screen asks them to speak to their test administrator.
- Select the lock icon.
- Select Accept to let them carry on, or Reject to turn the new sign-in away. After Reject, the attempt stays locked to the earlier sign-in.
The test-taker's time keeps running while they wait, so admit them as soon as you can.
If the event has Allow re-entry to a test without needing to be unlocked turned on, you don't need to admit anyone. A test-taker who signs in again takes over their attempt, and no lock icon appears. That includes signing in on another device or browser, in a private window or in a second tab. The setting is in the event's delivery settings.
Submit a test-taker's attempt¶
You may need to submit an attempt for a test-taker — for example, if they left the room without submitting.
- Tick the checkbox next to each test-taker.
- Select Submit test-taker.
- Enter any details and select Confirm.
- A message confirms how many attempts were submitted. Select Ok.
Submit test-taker isn't shown on the Submitted or Waiting entry tabs.
Reopen a submitted attempt¶
You may need to reopen a submitted attempt — for example, if it was submitted by mistake. You can add time when you reopen it.
- Select the Submitted tab. Reopen test-taker appears only on this tab, and only while the session is running.
- Tick the checkbox next to each test-taker.
- Select Reopen test-taker.
- Optionally enter minutes in Time to add, add any details, and select Confirm.
Postpone or abandon a test-taker's attempt¶
These buttons appear on the All, Not started, Started and Paused tabs while the session is running. They're unavailable if any test-taker you've ticked has already submitted.
- Postpone candidate stops the attempt part-way and takes it out of the session, so it can be picked up later.
-
Abandon candidate stops the attempt for good. It can't be resumed.
-
Tick the checkbox next to each test-taker.
- Select Postpone candidate or Abandon candidate.
- Enter any details and select Confirm.
Warning
Postponing, abandoning or submitting an attempt that's being completed offline makes that attempt unusable. If you can, take the device online and synchronise the attempt instead.
For what each status means and what can happen next, see test attempt workflows.
Finalise a session¶
Finalising closes the session so no-one else can join. Finalise when testing is complete. You can finalise only when:
- every attempt has been submitted or abandoned
- the session isn't paused
To finalise the session:
- Select Finalise session.
- A message asks whether you really want to close the session. Select Yes.
- Enter any details and select Confirm.
- A message confirms the session has been finalised. Select Ok.
Your site can also show a prompt when every test-taker has finished, as a reminder to finalise. Sessions with a maximum duration can be finalised automatically — see auto-finalise test sessions.
Abandon a session¶
Abandoning ends a running session for good. You can't reopen an abandoned session. You can't abandon a session when every attempt has been submitted (finalise it instead) or while anyone is waiting to enter.
- Select Abandon session.
- A message asks whether you really want to abandon the session. Select Yes.
- Enter any details and select Confirm.
Every attempt in the session that hasn't been submitted becomes Abandoned, whether it was in progress, paused or not yet started. The time each test-taker had used is recorded, and the details you entered are saved against each attempt. The test-takers can't continue, and their attempts can't be resumed. Attempts that were already submitted keep their status.
Settings¶
Each button on this dashboard is an action your role must be allowed to use. Administrators grant them per role at Settings > Roles. If a button described here doesn't appear, your role may not include it.
Administrators can configure the following at Settings > Assessment Event Settings.
Enable Unrestricted Entry — adds the Allow unrestricted entry checkbox to the dashboard. Choose Not allowed, Allowed and off by default or Allowed and on by default.
Enabled Allow Re-entry to a Test Without Needing to be Unlocked — adds the Allow re-entry to a test without needing to be unlocked checkbox to each event.
Enable Proctored Test Delivery Option — lets events use proctoring, which adds the Pause Proctored Sessions checkbox to their sessions.
Show prompt when all students are finished — shows a message when every test-taker has finished. Choose No, Panel only or Pop-up and Panel.
Reasons Setup — sets the reasons offered in each dialog's Reason list, and whether Details is required when the reason is Other.
Enable Incident reporting functionality for session invigilation — adds the incident count, Report incident and View timeline to the dashboard. See incident reporting.
Administrators can configure the following at Settings > Test Delivery Settings.
Enable Offline Reliable Delivery — lets attempts run offline. The dashboard then warns that the session may be running offline, and offline attempts may not appear until they're reconciled.
Maintain Remaining Time for Offline Test Attempts — stops a test-taker losing time when they leave a test that's being taken offline and come back to it. A test running online keeps counting down on the Insights server while a test-taker's device is down.
Administrators can configure the following at Settings > Test Designer Settings.
Auto save interval — also saves the item on screen every so many seconds, from 20 to 600. Without it, Insights saves an item only when the test-taker moves to another one, so a frozen device can lose more.