← GCSE Computer Science

Progress and forecast

Replayed from 186 status changes in 26 sessions since 7 Sep · 189 days to the exam · built from 8 weeks of pace

Today

7% · 20 of 300 steps

6% three weeks ago · 0% on 7 Sep · aimline says 16% today

Pace, last 8 weeks

1.8 steps a week

needs 6 to be 67% by 10 May · weeks ran +1 · +3 · +8 · 0 · +2 · 0 · +1 · 0

Behind aimline. 9 consecutive weeks under the aimline: the rule says change the teaching, not wait.

Stuck topics. Developing and not moving despite repeated work: P05 (10 touches, 5 weeks), P03 (7 touches, 6 weeks), D03 (6 touches, 4 weeks), P17 (5 touches, 5 weeks), P04 (4 touches, 5 weeks).

Sign in to see the forecast cone and the topics in flight.

Where she is, where she's headed

Coverage since 7 Sep with the aimline 0% 25% 50% 75% 100% Oct Nov Dec Jan Feb Mar Apr May everything secure · 67% aimline · 6 steps a week 7% today exam · 10 May
coverage, day by dayaimline: 0% on 7 Sep to 67% on 10 Mayeverything securedays off

Booked days off are shaded: no steps are expected on a day with no GCSE Computer Science block, and the cone routes around them. The cone stops at 100% because the syllabus does; it does not know that later topics may be harder than the ones already taught.

Chart data
Week endingActualAimlineLikely lowMost likelyLikely high
2026-09-132%2%———
2026-09-202%4%———
2026-09-273%6%———
2026-10-046%8%———
2026-10-116%10%———
2026-10-186%11%———
2026-10-256%13%———
2026-11-017%15%———
2026-11-027%16%———

How the colours have moved

Topics by status, week by week 0 25 50 75 100 1 exam-ready 2 secure 13 developing 18 gap 66 not started 6 Sep 20 Sep 4 Oct 18 Oct 1 Nov 2 Nov
exam-readysecuredevelopinggapnot started

Green grows from the bottom. The yellow band is what is in flight: 13 developing now. A flat picture is a stalled week; green shrinking is a regression. 84 topics have not been opened.

Chart data
Week endingNot startedGapDevelopingSecureExam-ready
2026-09-061000000
2026-09-13961120
2026-09-20951220
2026-09-27930520
2026-10-0467181320
2026-10-1167181320
2026-10-1866171520
2026-10-2566181411
2026-11-0166181321
2026-11-0266181321

Week by week

Steps gained each week against the pace needed 0 7 14 +5 W37 +1 W38 +3 W39 +8 W40 0 W41 +2 W42 0 W43 +1 W44 0 W45 upper limit 11.62 needed · 6 a week lower limit 0
WeekBlocksSessionsTouchesOpenedStepsAimlineReading
2026-W377 Sep3455+51 behindP02 ↑, P14 ↑, P08 ↑, P02 ↑ …
2026-W3814 Sep43112+15 behindP03 ↑, P03 ↓, P03 ↑
2026-W3921 Sep35355+38 behindP04 ↑, P04 ↓, P05 ↑, P02 ↓ …
2026-W4028 Sep34358+86 behindA01 ↑, P16 ↑, P28 ↑, S01 ↑ …
2026-W415 Oct33800stalledevidence only
2026-W4212 Oct44212+215 behindA04 ↑, D01 ↑
2026-W4319 Oct331800stalledP08 ↑, D02 ↓
2026-W4426 Oct4010+1nothing loggedD05 ↑
2026-W452 Nov3000027 behind in progress

Touches are status changes where nothing moved: evidence logged against a topic that stayed where it was. Opened counts topics taught for the first time. Natural process limits from 8 weeks: a week above 11.62 or below 0 is a signal, anything between is routine variation.

How this is worked out
  1. The line is coverage replayed from every status change, one point per day, in steps: one topic moving up one level.
  2. The aimline runs from coverage on the first tracked day to the goal (every step on exam day unless the parent set another). Two weeks under it is a warning; four weeks running is the rule to change the teaching.
  3. The cone re-runs the future 5,000 times. Each run first re-draws which of the last 8 weeks count, then gives every future week the pace of one of those, scaled to the blocks the timetable has that week. Days off carry no blocks. The shaded band is where 70% of runs land; the paler band, 90%.
  4. Stalled is a week with blocks and sessions but no steps. Behind is a week that ended under the aimline. Touched, unmoved counts evidence logged against a topic that stayed put.
  5. The cone does not know that later topics may be harder, that exam-ready needs revision-phase work, or about holidays nobody has booked. It narrows as weeks are added.