Respuesta
A Revision Timetable That Gets Used
Colour-coded hour grids fail by Wednesday, because one missed evening makes every later cell wrong. Count topics per week instead, and tick only after a retest.
Respuesta breve
How do you make a revision timetable that you will actually use?
Do not schedule hours. Write a list of six or so named topics for the week and tick each only when it survives a retest. A disrupted week then costs you two topics, not the whole timetable.
La respuesta corta
A timetable that gets used counts topics, not hours. Set a week's list of about six named topics and tick each one only when the student can answer unseen questions on it without notes. Hour grids fail because a single missed evening makes every later cell wrong, and a wrong grid gets abandoned rather than edited.
Qué cambia la respuesta
- In the last three weeks before a paper the unit stops being topics and becomes whole timed papers, and the format changes shape with it.
- A student with eight subjects needs the topic count split between them explicitly, or maths silently takes all of the week or none of it.
- Students who genuinely will not begin without external structure need a fixed start time as well as a topic list — the appointment then has exactly one job, which is starting.
- If a student cannot name their own weak topics, the timetable is not yet the problem and a marked diagnostic paper comes first.
Why the colour-coded grid fails by Wednesday
It is a schedule of appointments with no slack in it. Ordinary life supplies about one disrupted evening a week, and after that every later cell is wrong. Correcting it means redrawing the grid, which nobody does, so the whole thing is quietly abandoned and the abandonment gets read as a character flaw.
Making it is also pleasant. An afternoon with coloured pens produces a strong sensation of having got somewhere and no retention whatsoever, which is a poor trade for a Sunday in April.
The deepest problem is that it allocates hours rather than outcomes. A student can comply with it perfectly — two hours of maths on Tuesday, done — and learn nothing at all, because 'two hours of maths' does not say what has to be true at the end of them.
The format that survives a bad week
One page, handwritten, on the wall. Each week is a list of named topics plus one line for timed practice. That is the whole system, and its virtue is that a bad week reduces the number of ticks rather than invalidating the document.
An example week reads: surds; bounds; similar shapes and area scale factors; box plots; iteration; direct and inverse proportion. Timed: Paper 2, first 45 minutes. Six topics and one paper section — specific enough to start and short enough to finish.
- Count topics, not hours.
- Set the number you would manage in a bad week rather than a good one. A list you beat is a list you keep using.
- A topic is ticked when three unseen exam questions on it come out right without notes — not when it has been read or watched.
- Every topic goes back on the list once, a week later. The second pass is where it becomes permanent.
- One line of timed practice a week from the beginning, rising to two in the final month.
Three dates go on the calendar, and nothing else
The date of the first paper. The date new learning stops — about three weeks before, and sooner for a student with many subjects. The date the work switches to whole papers. Those three.
Everything else lives on the weekly list. A calendar carrying ninety entries is a calendar nobody opens, and the effort of maintaining it comes directly out of the time it was supposed to organise.
Where the topics come from
Not from the contents page of a revision guide. That page is ordered by the specification and treats every topic as equally worth your time, which is exactly what a student trying to prioritise cannot afford.
The list should come from the student's own dropped marks on a marked paper, ranked by how many marks each topic cost. The timetable is then nothing more than that ranked list cut into weeks — which is why it takes ten minutes to write rather than an afternoon.
What to do when a week goes wrong
Nothing. Carry the untouched topics into next week and do not lengthen the list to compensate.
The single behaviour that kills revision plans is trying to make up a lost week by doubling the next one. It fails, because the reason last week failed has not gone away, and the failure of the doubled week is then read as proof that the student cannot revise. A plan that absorbs a bad week without comment is worth more than a plan that is optimal on paper.
Preguntas frecuentes
How many topics a week is realistic for GCSE Maths?
Four to six alongside other subjects, if a topic means learn-and-then-test rather than read. Students who set twelve are counting reading, and the difference shows up in March when the retests start failing. Count what you managed last week and set that number, not the number you wish you had managed.
Should I make the timetable or should my child?
The child writes it, though you can sit with them for the first one. A timetable written by a parent is a set of instructions, and instructions get complied with rather than used. The point of the document is that the student consults it without being asked.
Does it need to include other subjects?
Yes, on the same page. Otherwise maths either crowds out everything else or gets crowded out entirely, and neither is noticed until a mock lands. One page, all subjects, topics counted separately per subject, so the week's total is visible at a glance and obviously too large before it fails rather than afterwards.
What about the last week before the exam?
No new topics at all. Two things only: whole timed papers, and the list of topics that failed their retest. A student meeting a topic for the first time in the last week is spending the highest-value hours of the year on the lowest-yield work available.
Última actualización
¿Sigues con dudas?
Cuéntanos la situación y te diremos con claridad qué haríamos, incluso si la respuesta es que no nos necesitas.