Invigilation Centre Guide

Modified on Wed, 21 Aug at 4:10 PM

ISEB suggests bookmarking the link to the Invigilation Centre Guide. It is a live document and is kept updated.


1. Support details 

General enquiries 

Please visit our support page for any general enquiry relating to the ISEB Common Pre-Tests or any non-urgent technical issue.

To contact us for non-urgent support, email [email protected]

To contact us for urgent support during a test, please submit a ticket, selecting 'Technical difficulties during a test'. This prioritises your ticket.

As well as this guide, please read the Guide to Administering the Common Pre-Tests and Troubleshooting for support on how to prepare and what to do on the day.


2. Outline of URL links

Platform name

URL Link

Function of link

When to use this platform?

Walkthrough

https://iseb.eva.tech/walkthrough/

Familiarisation with the structure of the test and accessibility features

Anytime before the tests

InvigilationCentre Portal

https://iseb.eva.tech/invigilation-centre/

View and approve applicant profiles, schedule tests, complete Centre Declaration Forms

From September 5th onwards

Assessment Platform

https://iseb.eva.tech/test

The online platform for pupils to take the ISEB Common Pre-Tests

During the assessment window

Diagnostic tool

https://iseb.eva.tech/debug/


The diagnostics tool checks the required service connections for the tests 

One week before scheduled tests 


3. The Invigilation Centre Portal
To help you navigate the portal, we have created the following video and guides for you. You will also be able to find support articles written on the ISEB Knowledge Base. These will be kept updated with frequently asked questions and answers. If you can’t find your answer there, email us [email protected]

Getting started video

How do I schedule the tests?


4. Preparing for the tests - Checklist

In advance

  • Check the system requirements (see below)
  • Run the diagnostic tool on every laptop/PC (make sure you are logged in as the pupil to ensure the correct access privileges are being diagnosed) 
  • Download and print the Test Codes
  • Check the scheduled test window has not expired
  • Explore the ISEB Test Walkthrough with pupils to familiarise them with the platform

On the day

  • Ensure the pupils have access to pen/pencil and paper for any rough work (for all four tests)
  • Ensure the room meets the invigilation centre requirements (see below)
  • Read the Invigilator Script
  • Brief each invigilator with the invigilation centre requirements and information on malpractice
  • Ensure any SEND access arrangements are met
  • Ensure pupils have their Test Codes and know their dates of birth

After the test

  • Complete the online Centre Declaration Form (please note that all comments are visible to senior schools and guardians)

5. System requirements

The Common Pre-Tests are all online, so an internet connection is required.  

  • The assessment platform will only support a Chrome browser; the minimum version required is 100. However, we recommend you have the latest version for reliability. Please check all computers meet this requirement before the assessment.

  • Due to the nature of Apple devices, there might be issues with the way the questions are presented. Due to this, we recommend only using PCs/laptops.

  • We recommend a 10-15mbps connection speed for each machine for optimum performance when sitting the assessment.

  • There is no offline version of the test.


Diagnostic Tool

The diagnostic tool should be used two weeks ahead of the test on all IT equipment that will be used. This tool will identify if there are any issues (e.g., firewall systems) that may prevent the tests from running.

Instructions

This diagnostics tool checks the required service connections for the session you are about to host.

You should run this check one week ahead of your scheduled session date to ensure that any issues identified can be dealt with ahead of time.

If there are any errors in the report, please download your report and contact ISEB by completing the following form.

Please note that the URLs listed in the report must be whitelisted at your school to ensure the functions all work as expected.


6. Invigilation Centre Requirements

Prior to the testing taking place

  • a senior member of staff will be appointed to be responsible for the administration of the tests
  • the senior member of staff and any test invigilator/s understand what constitutes malpractice and agree to report any suspected incidents to ISEB
  • a suitable testing environment will be provided, and every effort will be made to eliminate disturbances or interruptions
  • applicants will have access to pen/pencil and paper for their rough work during the tests
  • any textbooks, calculators, mobile devices, wall displays or other materials that might assist an applicant are removed from the room
  • the test invigilator will ensure that all applicants are logged in with the correct applicant’s name displayed and they are ready to commence the test

During the testing period

The invigilator should read the following script before the start of each test:

  This the [insert test name] test. 

You have [see table below for length of test] minutes. 

You may use a pen or pencil and paper for your rough work, this will not be marked.

You should work through the questions carefully, you will not be able to skip any questions and you cannot go back to change your answers.

Don’t worry if you think you have made a mistake, answer the next question carefully.

If you finish the test before the time is completed, please sit quietly to allow other pupils to finish.

The test will automatically stop when the time is finished.


Test Name

Standard Test Time

25% Extra Time Tests

English

40 minutes

50 minutes

Mathematics

40 minutes

50 minutes

Non-Verbal Reasoning

30 minutes

37.5 minutes

Verbal Reasoning

25 minutes

31.25 minutes


  • all applicants will be instructed to begin the test at the same time by selecting the appropriate test and to work in silence
  • the invigilator will monitor the test to ensure that applicants are focused on their own screens
  • the invigilator will ensure that no members of staff or pupils other than those involved in the test are able to access the questions
  • no notes relating to the content of the tests will be taken, and no information about the content will be passed on to other members of staff, parents, pupils or any other individuals
  • applicants who finished early should not be allowed to disturb others
  • the invigilator will remind applicants when 5 minutes of the test remains
  • the invigilator will confirm that each applicant’s screen has returned to the home screen, which will show the test has been completed

If there are any issues during the test, refer to the Guide to Administering the Common Pre-Tests and Troubleshooting first.  

To contact us for urgent support during a test, please submit a ticket, selecting 'Technical difficulties during a test'.  This prioritises your ticket.


Following the testing period

• any problems with the administration of the tests should be brought to the immediate attention of the senior member of staff and, where appropriate, to ISEB. 

General Issues 

• any issues that occur during the administration of the tests will be specified in the Centre Declaration Form, which can be found in the Invigilation Centre Portal. Issues to be reported could be those that may have affected a child’s (or more than one child's) test completion (eg, medical issues or unavoidable disturbances, such as a fire alarm). Anything reported on the Centre Declaration Form will be visible to senior schools and the parents or guardians of the child.

Completing the Centre Declaration Form at the end of the test

Malpractice concerns 

• issues concerning suspected malpractice (see Appendix below) must be reported immediately using the following form.


Appendix

Malpractice

Malpractice means any incident which:

  • Gives an unfair advantage to any applicant
  • Compromises the integrity of the test or the result
  • Compromises confidence in the ISEB Common Pre-Tests

Malpractice incidents can be intentional and aim to give an unfair advantage (either immediately or in the future) to applicants, or unintentional incidents. These occur due to a lack of awareness or carelessness during the process.

Malpractice could involve:

  • Applicants
  • Teachers, tutors, invigilators, or those facilitating access arrangements (eg, readers)
  • Assessment personnel such as the senior member of staff responsible for the administration
  • Other third parties (e.g., parents/guardians)

Reporting Malpractice

Anyone suspecting malpractice should immediately contact the senior member of staff. Any incidents should then be reported to ISEB. If anyone does not feel comfortable reporting to the senior member of staff, then this should immediately be reported directly to ISEB. ISEB will then investigate and respond to any allegations. Examples of malpractice can be found below. To report malpractice, click here.


Examples of Malpractice

1.     Breach of security – including, but not limited to:

a.     Failure to keep examination material confidential

b.     Recording (by any means) of test material

c.     Revealing information via internet forums/social media

d.     Failure to adequately supervise applicants

2.     Deception – including, but not limited to:

a.     Substituting applicants

3.     Improper assistance – including, but not limited to:

a.     Assisting or prompting applicants by answering questions

b.     Prompting applicants with signs, verbal or written prompts

c.     Use of internet or unauthorised devices during the test

4.     Candidate malpractice

a.     Unauthorised use of internet or devices during the test

b.     Being in possession of unauthorised confidential material about the tests

c.     Bringing in notes to aid answering the questions

Behaving in any manner which undermines the integrity of the tests is considered malpractice.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article