Platform
Looking at one student
Everything one child did, the code they actually wrote, and the three things you can do about it — feedback, a score override, and more attempts.
The dashboard gives you a name. This page is what to do once you have it.
Open a class → Progress → click the student’s name in the grid. (Or their name in any dashboard panel’s big view.)
What is on the page
Four bands, top to bottom. The first is a preview; the other three are real.
Everything below that band is real.
The learning curve
A line of their scores in the order they earned them. It appears once they have completed two things, and it answers a question no single score can: are they getting better?
A curve that climbs is productive struggle — leave them alone, they are learning. A curve that is flat or falling across many attempts is wheel-spinning, and that is the moment to step in. A child on their seventh attempt scoring the same as their first is not being persistent; they are stuck and have not realised it.
The mission attempts table
Every flight, newest first: the mission, the score, the status, when they started, whether it was LATE, and a small speech-bubble icon where you have already given feedback.
Statuses mean:
| Status | What happened |
|---|---|
| completed | They finished it. |
| failed | They flew it and did not meet the objectives. |
| in_progress | Still going, or they closed the tab mid-flight. |
| abandoned | Started and never finished. |
| reset | You gave the attempt back (see below). It no longer counts against their limit. |
Click any row.
Inside one attempt
This is where you can actually do something.
Three scores, not one
| Where it comes from | |
|---|---|
| System | The mission’s own scoring rules — did they achieve the objectives, in time, within the constraints. This is the score everything else counts. |
| Observer | A separate watcher that measures the quality of the flight itself: how efficient the path was, how many collisions, how steady the hover. It answers “did they fly it well”, not “did they pass”. Not every mission produces one. |
| Teacher | Yours, if you gave one. It overrides nothing automatically — it sits alongside as your judgement, and it appears in the exported CSV in its own column. |
A student who passes with a high System score and a poor Observer score has got the drone to the right place by brute force. That is worth a conversation and it is invisible on a gradebook.
The code they wrote
Two tabs: Generated Code and Blocks.
Blocks shows the actual arrangement of coloured blocks they assembled. This is what to look at. You do not need to be able to read code to see that a child has put the “land” block before the “fly forward” block, or that a loop is wrapped around the wrong thing. It is usually obvious in about five seconds, and it is very often the whole explanation for four failed attempts.
Generated Code is the text version of the same thing. Read it if you like code; ignore it if you do not. It says nothing the blocks do not.
If a student worked before this feature existed, you may see “No code snapshot”. That is a gap in the record, not something they did wrong.
Writing feedback
Underneath, a box marked Feedback, with a line under it that matters: “Visible to the student.”
They will read this. It arrives as a notification and is attached to the specific attempt, so they see it in the context of the flight it is about — which is far more use than a comment on a grade sheet a week later.
Two hundred characters of “the takeoff is fine, but look at the order of your last two blocks” is worth more than any number you could give them.
Overriding the score
Beside the feedback box, Score override (0–100). Use it when the platform’s number does not reflect what happened — a clever solution the scoring rules did not anticipate, an effort you want to recognise, a mission that mis-scored.
Your number goes into the Teacher Score column of the CSV export, next to the system score rather than replacing it. Both are kept, so the record shows what the machine thought and what you thought.
Giving a student more attempts
The Reset Attempts button. It asks first:
Reset all attempts for this student on this mission? This lets them resubmit.
It marks their existing completed and failed attempts on that mission as reset. The attempts are not deleted — the rows stay, and you can still see them — but they stop counting towards the submission limit, so the student gets their tries back.
This is the fix for a student the dashboard flagged as at cap, below pass. That child cannot do anything about it themselves; this is the only way through.
The quiz results table
Above the flights, if the lesson had a quiz: the lesson, the percentage, how many questions they got right, how long they spent, and when.
Click a row and you get their answers question by question, marked right or wrong, with the correct answer shown — plus how their score and time compare with the class average, and whether they were rushed, on pace or took extra time.
Rushed with a good score is fine. Rushed with a bad one usually means guessing, and it is a better thing to raise with a child than the mark itself.
What is not on this page
You cannot see anything they wrote privately. Students can highlight and annotate lesson text as they read, and none of it — not the text, not who wrote it — reaches you. You see counts of where a class marked something confusing, and only in aggregate. What you cannot see, and why covers the full boundary.
Next
→ Running a lesson — what happens on the students’ screens while all this is being recorded.