ClassPilot is the public-facing idea of a better computing lesson runtime: a stable learner shell, a visible lesson timeline, a central task stage, persistent notes and work areas, and teacher-controlled progression so the room moves together. Less tab chaos. Less repeated explaining. More live teaching.
A large lesson display remains dominant while learners keep their own notes, progress, and help actions visible in the same frame.
The shell stays familiar, but the centre of the screen becomes an activity workspace for structured tasks, responses, and guided practice.
In a computing room, you are teaching live, troubleshooting, checking understanding, nudging pace, and trying to capture useful evidence without losing the class. Most tools handle one of those jobs well and make the others worse. ClassPilot is aiming for the opposite.
The emerging ClassPilot direction is not “another big scrolling page”. It is a stable lesson shell: header, brief, central work surface, feedback, notes, and a fixed action rail. That geometry matters because it helps learners stay oriented and lets the teacher trust what every screen in the room roughly looks like.
Core zones stay where learners expect them. The task moves forward, but the frame does not keep rearranging itself.
The thing learners are meant to do now stays dominant, whether that is a checkpoint, guided practice, or a bounded code task.
Learners keep useful context close by rather than flipping between instruction, rough work, and response surfaces.
The current step, what is done, and what is next should be obvious without asking the room to guess.
Ready does not mean everyone immediately disappears to different places. The teacher can hold, reteach, then release together.
Readable contrast, visible focus states, clear labels, and predictable controls matter more than flashy motion.
Simple enough to run live. Structured enough to keep the room together. Flexible enough to support support, stretch, and evidence without bolting on more chaos.
Start from the lesson plan, deck, or authored step flow. The public promise is clarity, not “rebuild your department from scratch”.
Advance the room, project the current focus, and see learner state without juggling tabs or swapping mental models.
Each learner sees the current task, the work surface, their notes, and the fixed actions for ready, stuck, and help.
Checkpoints, submissions, status, and notes create a usable trail during the lesson rather than as a separate admin task afterwards.
Not edtech theatre. Practical wins in the middle of a real lesson.
Visible progression and teacher-held release make it easier to keep a mixed-attainment room roughly aligned without losing your stronger learners.
When “what do I do now?” is always on screen, you spend less lesson time restating task setup and more time actually teaching.
Support, hints, and stretch can appear as controlled branches inside the same runtime, instead of becoming separate improvised workflows.
If the system sees the checkpoints, notes, and submissions while the lesson is happening, the record is already half built.
Join the list for pilot updates, clearer demos, and public milestones as the product direction firms up. This is for teachers and departments who want to shape something practical, not a noise-heavy mailing list.
Same backend capture flow, improved front-end experience. Name and email only.