Also from the developer: Travel Vista

Evaluation slot booking

The part of the semester where group chats melt down — solved with a simple grid of slots and one database rule.

Last updated: October 2026 · nuSkor is an independent student-built project — not affiliated with any university.

The problem

Evaluations, vivas and demos all need the same scarce resource: ten minutes of a teaching assistant’s time, multiplied by a whole class. The usual mechanism — a message thread where people claim times — produces collisions, silent double-bookings and an afternoon of manual reconciliation. Students refresh a chat instead of preparing for the evaluation.

How it works

Course staff define an evaluation period and open a set of time slots. Students see the grid and book an open slot with one tap. The critical part is what happens next: the booking is written to the database with a uniqueness rule — one student, one booking per evaluation; one slot, one booking, period. If two people tap the same slot within the same second, exactly one succeeds; the other politely gets an error and picks another. No race conditions, no “I thought I had 4 o’clock”.

What staff and students get

  • Students: a live grid of slots with their own booking visibly confirmed, and the ability to see the date, time and location the course set for each slot.
  • Teaching assistants: a roster view of who booked what, in order — ready for the evaluation session, with no spreadsheet to rebuild.
  • The course: a full audit trail. Bookings are tied to accounts, not to messages, so “did I book?” has one authoritative answer.

The design decisions behind it

Two choices matter most. First, the uniqueness enforcement lives in the database, not in the interface — hiding a button is not a guarantee; a constraint is. Second, the flow is deliberately minimal: students do not need to exchange messages, confirmations or screenshots, because the system state itself is the confirmation. Anything the course needs to change — opening more slots, moving a session — happens on the staff side and is visible to everyone instantly.

Rescheduling follows the course’s own rules: how late bookings are allowed, whether cancellations reopen a slot, and what happens in exceptional cases are configured by the course staff, since they differ from course to course.

Evaluation slots — Course YSample data

10:00

Taken

10:15

Open

10:30

Booked — you

10:45

Open

11:00

Taken

11:15

Open

11:30

Taken

11:45

Open

12:00

Open

Your booking: 10:30 — confirmed. One booking per student; slots lock the instant they are taken.

Frequently asked questions

Can I book two slots to be safe?
No — one booking per student per evaluation period. That rule is what keeps the grid honest, and it is enforced by the database, not by trust.
What happens if I need to change my slot?
It depends on the rules the course staff set. Some courses allow cancelling and re-booking while slots remain; others lock bookings near the session. Ask your course staff — they control it.
Is the booking official?
It is the course's own scheduling record inside nuSkor. Whether it doubles as an official attendance document is up to your course and institution.

Track your real marks and book evaluation slots on nuSkor.

The portal is free for students: the marks your instructors publish, class statistics, a privacy-conscious ranking and evaluation slot booking — all in one place.

Login as Student