Internal and semester exams
Objective, written and coding questions, each in a timed phase of its own. Objective answers are marked the moment a paper is submitted; your faculty mark the rest in the console.
For colleges and universities
Every exam on the calendar.
One place to run it.
Internal assessments, semester exams, entrance tests and placement drives: written, scheduled, marked and published from one console, with proctoring your students read about before they start.
A whole lab at once.
One hall link.
Up to 3,000 sitting at onceLab exams of 500 seats, testedFree while Pro is on its way
From the first internal
to the final placement round.
One question bank for the department, and a test for every point in the year.
Entrance and admission tests
Open the test for a window, or in fixed slots with a seat limit that applicants book after accepting their invitation. Every applicant gets the same paper, and it stays the same if they reload.
Placement preparation
Aptitude, reasoning, written and coding rounds shaped like the ones recruiters set, so students meet the format before it counts.
Exams in your computer labs
Every machine in a lab shares one internet connection, which most platforms read as one visitor. A hall link sizes the limits to the room, and a hall of 500 has signed in and sat a test together without trouble.
How a sitting goes
for a student.
- 1
An invitation arrives
Students sign in with the email address you invited. Nobody signs up, and nobody else can see the test.
- 2
They read the rules
What is checked, in plain words, before the paper opens: camera, screen, fullscreen, and what switching tabs costs.
- 3
They sit the paper
Phase by phase, each with its own timer. Answers save as they go, and the clock keeps the server’s time, not the laptop’s.
- 4
Results when you say
You publish results when marking is done, with or without the answer key.
What your exam cell
gets with it.
Proctoring
Camera, microphone, screen sharing and fullscreen, as your policy sets them. A person reviews every flag.
Coding tests
Python, Java, C++, C and JavaScript, run in the browser and graded against hidden test cases.
Exam halls
Lab exams where every machine shares one connection, sized to the seats in the room.
Question bank and marking
A shared, versioned bank for the department, with marking split between the server and your faculty.
Roles for your staff
Administrators, authors, reviewers, schedulers, evaluators and proctors, each seeing what their job needs.
Re-tests
A student who lost their attempt can ask for another, and you approve or decline it with a reason.
Good questions.
Straight answers.
Something else? Ask us.
Can we run an exam in our computer lab?+
Yes. Exam halls are switched on for your institution by Medhank, so ask us first. Then you mark a test as sat in a hall, enter its seats and open the hall link on every machine. A hall of 500 has been tested end to end.
Do students need to create an account?+
No. Each student signs in with the email address their invitation went to. Only the people you invite can see a test.
Who marks written answers?+
Your faculty, in the console. Objective answers are marked by the server as soon as a paper is submitted, and programming answers are graded against their test cases.
What does it cost?+
Medhank is free today. Pro is coming; its pricing will be announced before anything is charged.