Also from the developer: Travel Vista

For teaching assistants

You already know the workflow: checkers, spreadsheets, a group chat on fire. nuSkor is what happens when all three become one quiet system.

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

Teaching assistants run the academic supply chain: quizzes get graded, totals get computed, evaluations get scheduled, and questions get answered — usually across Microsoft Excel, a messaging app and memory. nuSkor replaces that arrangement with a structured workflow, without adding bureaucracy. Set the course up once, and every routine that follows becomes a two-minute operation instead of an evening.

The TA workflow, start to finish

  1. Structure once. Create the assessments with their names, totals and weightages the first week. Every total downstream computes itself.
  2. Enter marks your way. Small checkers go in by hand; anything that already lives in a spreadsheet comes through CSV import, where every row is validated against the roster before a single mark is saved. Typos surface as flagged rows, not as students with missing marks.
  3. Publish when ready. Marks stay invisible to students until you publish. Verify in private, release in public, correct calmly.
  4. Open evaluation slots. Define the period and the slots; students claim them; the roster assembles itself on the booking grid. No double-bookings, no claim threads.
  5. Announce once. Deadline changes and schedule shifts go into the course feed, where the whole course sees the same current version.

What this saves you

  • Arithmetic. Weighted totals, percentages and standings compute themselves from what you entered. You check numbers; you do not maintain them.
  • Message traffic. “Where do I stand?” and “did I book?” have visible answers, which removes a surprising share of your inbox.
  • Reconciliation. One record, one source of truth: the spreadsheet, the notebook and the chat history stop competing to be believed.
  • Rooms full of speculation. The anonymised leaderboard and class statistics let students read their own situation without asking you to confirm it line by line.

You stay in control

Nothing publishes without your action. Access is scoped to the sections you run — you cannot see, and are not responsible for, data outside your scope. Corrections flow through your own entries: fix the mark, republish, and everyone downstream sees the corrected version. The portal records who can do what at the database level, which means your rights and your responsibilities are aligned, not merely assumed.

And when the semester ends, there is no great spreadsheet cleanup — the record already looks the way you would have wanted it to look. If your course is considering the portal, the TA guide walks through running a full course week with it, and the how it works page shows the student-side view you will be feeding.

Frequently asked questions

Do I need special training to run a course?
No. The workflow follows the semester's natural shape — assessments, marks, evaluations, announcements. If you can run a course on a spreadsheet, you will find this lighter, not heavier.
Can I fix a mark after publishing?
Yes. Correct the entry and republish; students see the current version, and the change is recorded against your account.
What can I see as a TA?
The courses and sections you run, and the marks and bookings that belong to them. Nothing outside that scope — enforced by database rules.
How do I get started?
Sign in through the TA login with the Google account your course expects. If your course is not set up on nuSkor yet, contact us through the contact page.

Ready to run your course without the spreadsheet chaos?

Sign in as a TA to reach your sections, or read the TA guide for a walkthrough of the full workflow.

Login as Student