Skip to content

Deliver tests

Delivering a test in Janison Insights means scheduling a published test as an assessment event and enrolling the test-takers who will sit it. They then take it in test sessions that an invigilator runs. This page walks through that journey in order, explains what happens afterwards, and says who does each part. Each stage has its own guide, linked as you go.

Before any of this, a test author writes the items, builds them into a test and publishes it. A published test is what an assessment event delivers. The author area covers that work.

Note

Janison Insights is highly customisable, so the entities on your site may have been renamed and the menu customised.

You only see the menu items your role has permission to use.

How a test is delivered

Delivery has 3 stages. Sessionless, hybrid and offline delivery vary the pattern, and are covered after the stages.

Create the assessment event

An assessment event links one test to a schedule, a set of delivery options, a marking mode and the test-takers enrolled to sit it. Go to Deliver > Assessment Events to create one.

A new event starts in the Draft workflow state. While it's in Draft, set the timing options, choose the marking mode and enrol the test-takers. Then select Change beside Workflow state and move the event to Delivery. Test sessions can only be created for an event in Delivery.

Some sites link an event to an assessment package of test components instead of a single test. See Assessment events, Assessment packages and Test components.

Create test sessions

A test session is like a virtual classroom. It groups the test-takers one invigilator supervises, so you can run one session per room, group or cohort, or a single session for everyone. Each session has a session code.

Create sessions from the Invigilator Dashboard, or from Create Test Session, both under Deliver. The dashboard also summarises the sessions running in your org unit. See Invigilator dashboard.

Run the session

Test-takers sit the test in Janison Replay or a supported browser. They start it by entering their one time code and, for a session-based event, the session code the invigilator shares. See Janison Replay and Supported browsers and platforms.

The invigilator runs the session from the Test Sessions Administration screen, which shows each test-taker's progress in real time. From it the invigilator starts and finishes the session, pauses and resumes test-takers, and awards or removes time. Where incident reporting is enabled, incidents are recorded there too. See Test session administration and Incident reporting.

Any attempt can also be found and acted on from Deliver > Manage Attempts, across all events. See Manage attempts and Test attempt workflows.

Other ways to deliver

  • Sessionless delivery removes the session stage. Test-takers enter with their one time code alone, and the device must stay online throughout. It suits low-stakes tests. See Sessionless delivery.
  • Hybrid delivery puts the test on paper. You print a question paper and answer sheet for each test-taker, scan the completed sheets back in, and Insights reads the answers. See Hybrid test preparation and delivery.
  • Resilient and offline delivery in Janison Replay keep the test running through internet dropouts, or with no internet at all. Devices that were offline are reconciled after the test so the attempts upload. See Janison Replay.

After the test

Auto-marked items, such as multiple choice, are scored as soon as the attempt is submitted. Items that need a human marker are marked under the event's marking mode, which has 3 options:

  • Standard marking project — results are released once marking is finalised for the whole cohort. See Standard marking.
  • Enrolment based marking project — each test-taker's results are released as soon as their own responses are marked. See Enrolment based marking.
  • Quick marked event — there's no marking project; a marker works through a single list of responses. It suits low-stakes tests with simple scoring. See Quick marking.

Where the event enables results and feedback, test-takers see their results on the candidate dashboard. Reports on results are covered in Reporting.

Who does what

Three default roles cover delivery. Your site may rename them or change their permissions under Settings > Roles, so treat these as the starting point. User roles and key features describes every default role.

  • Delivery Manager — sets up and manages assessment events, enrols test-takers, creates test sessions and oversees invigilators. Delivery managers don't author or mark.
  • Invigilator — runs assigned test sessions and supervises the test-takers in them: starting the session, watching progress, pausing tests and awarding extra time. The Invigilator Dashboard lists the sessions in their org unit. Invigilators can't create or edit assessment events.
  • Test Manager — end-to-end access: authors, delivers, invigilates and marks the tests for their subject.

What's in the deliver area

Settings

No single setting controls delivery as a whole. The settings that affect each screen are listed on that screen's guide. Administrators configure them in 4 groups:

Settings > Assessment Event Settings — the options and defaults for assessment events, such as whether sessionless delivery is offered and whether incident reporting is available.

Settings > Test Delivery Settings — Janison Replay and offline options for your site, such as reliable offline delivery, Replay lockdown and low-bandwidth mode, and what the delivery and test session administration screens show.

Settings > Replay Tenant Settings — the behaviour of installed Replay apps, such as the lockdowns, pushed to devices centrally.

Settings > Roles — which roles can see each Deliver menu item and act on sessions and attempts.