Quest Ladder
TeachFORGE.ai
Quest Ladder / Delivery results
Results: release, export and the marking queue
What came back, who it came from, and when to show it to them.
Released is a decision. Make it once the marking is done.
The results table
Results lists what has come back. Its columns are Token, Alias, Item, Marks, Teacher feedback, Status and Attempts, with a late flag where the policy allowed late work.
The token and alias identify a learner without naming them. The alias is the label you chose — a seat number, a colour card — and it is the practical way to tie a row to a person in the room without the platform holding a name.
The attempt line
Above the table a line reads along the lines of {{total}} attempts · {{named}} from your classes · {{anon}} by link.
That split is the honest picture. Named attempts are from learners with personal links and carry a full record; link attempts are counted in the totals and belong to nobody in particular.
A large anonymous count with a small named one usually means the delivery link was shared rather than personal links. It is not wrong — it is just analytics you cannot act on per learner. Personal links is the fix.
Releasing results
Release results to students is what makes marks visible to learners. It is a separate action from marking on purpose: you can mark thirty scripts over two evenings and release them all at once, rather than a class comparing marks as they trickle in.
For anything with hand-marked items — long answer, proof, graph sketch — the sensible order is to clear the marking queue first and release afterwards. Open marking queue is linked from here for exactly that.
Exporting
Export CSV takes the results as they are filtered. It is the route into a spreadsheet, a mark book, or whatever your school actually records grades in.
The export mirrors the view, so filter first and export second. There is no separate export configuration to get wrong.