Qualifying English Test

     

    QUALIFYING ENGLISH TEST (QET)

    Students admitted to undergraduate courses of study in NTU are required to take the Qualifying English Test (QET) unless they meet the exemption criteria. Students who fail the QET will be required to take Introduction to Academic Communication (HW0001) as a subject of study.

    Students (unless exempted from QET) will not be eligible to register for all language elective and selected Communication Skills courses, or to graduate from NTU if they do not pass QET or HW0001.

     

    TEST DATE

    The QET for AY2019-20 will be held on Monday, 5 August 2019. Please be present at your test venue at least 15 minutes before the commencement of the test.

     

    Students admitted after the above QET date will be arranged to sit for the next QET conducted.

     

    TEST DURATION

    The duration of the test is 1 hour 15 minutes.


    QET ATTENDANCE SLIP

    Students are required to present both their QET Attendance Slip and identification document (i.e. matric card, identity card, passport, ez-link card, driving licence, student pass) when attending the test for attendance marking.

    Please click here from Friday, 12 July 2019 (10.00 a.m. onwards) to Monday, 5 August  2019 to check whether you are required to take the QET and to retrieve your QET Attendance Slip.  Details on the time and venue of the test will be reflected in the attendance slip.  It is crucial that you check the details before you go for the test. 

    Please print the QET Attendance Slip and bring it along for the Qualifying English Test. Screen shots from your mobile devices will not be accepted. Please click here to view the detailed venue allocation for all programmes.

     

    ADDITIONAL INFORMATION

     

    RELEASE OF QET RESULTS

    The QET results will be released in the third week of August 2019.  More details will be updated nearer the release date.

    Use the following login methods to view the QET results:


    Note: If you encounter problems logging in via SSO, please try to login using PIN.

     

    Updated on 23 Aug 2019.

    Share Article