JC 2 General Paper GP Tuition | GP Study Plan and Revision Timetable

A good JC2 General Paper timetable does not try to fit more work into every week. It decides what kind of GP work deserves time now, what can wait, what must be repeated, what must be tested under pressure, and what should be removed when the schedule becomes overloaded.

The final A-Level year is not a blank calendar. Students already have lectures, tutorials, school assignments, common tests, preliminary examinations, other H1 and H2 subjects, co-curricular commitments, consultations, travel, sleep, family time and periods where energy is simply lower. A world-class GP study plan has to work inside that reality. If the timetable only works during an ideal week, it is not a timetable. It is a wish list.

This guide owns the calendar and resource-allocation problem inside the SETC JC2 General Paper lane. It does not replace How to Study for GP, which explains the study process itself, or the GP Revision Guide, which explains how to diagnose, retrieve, repair, transfer and retest. This page answers a different question: when should each kind of GP work happen, how much space should it receive, and how should the plan change when school life interrupts it?

The current 2026 Singapore-Cambridge H1 General Paper syllabus remains 8881. Officially, candidates sit Paper 1 and Paper 2 at separate sittings. Paper 1 requires one essay from eight questions and draws on local, regional and global issues across domains such as society, economics, politics, the arts and humanities, science and technology, and the environment. Paper 2 uses multiple prose passages and assesses comprehension, inference, analysis, evaluation, summary, synthesis and application. The timetable in this guide is built around those broad capability demands rather than around a narrow prediction list. See the official SEAB 2026 A-Level syllabus listing and the official 8881 syllabus for the authoritative examination requirements.

The scheduling problem is not time. It is allocation.

Most students already know that they should “study GP regularly.” That advice is too weak to run a final-year programme. Regularity without allocation can produce months of activity with very little change. One learner reads news every day but never practises argument. Another writes essays every weekend but never repairs the same recurring structural errors. Another completes many Paper 2 exercises but does not measure whether semantic precision improves. Another spends so long on GP that Mathematics, Economics, Chemistry or History performance begins to deteriorate, creating a new problem elsewhere.

A serious timetable allocates scarce resources across competing jobs. Those resources include time, attention, mental freshness, teacher feedback, good practice material, current-affairs input, full-paper opportunities and recovery. The question is not “How many hours of GP should I do?” The better question is “What is the highest-return GP job for this week, and what is the smallest amount of time that can move it?”

The seven timetable rules

Schedule by function, not by vague subject blocks. “GP: 2 hours” is weaker than “Paper 1 question selection + one timed plan + error review.”
Protect both papers. A strong Paper 1 month cannot justify letting Paper 2 decay, and vice versa.
Separate input from output. Reading current affairs is not the same as retrieving, arguing, summarising or applying.
Place difficult work when cognitive energy is higher. Deep question interpretation and timed writing should not always be pushed into the most exhausted part of the week.
Build repair between tests. Full papers without repair are measurement without learning.
Use buffers. A timetable with no spare capacity will collapse after one school event.
Reset by evidence. When the plan fails, change the allocation based on what caused the failure, not on guilt.

Start with a timetable baseline, not a timetable template

Before copying any weekly schedule, collect evidence from the last three to five weeks. The baseline should include school timetable, travel time, sleep, other subjects, common recurring deadlines, GP homework, recent Paper 1 and Paper 2 performance, teacher feedback, unfinished tasks and the learner’s best concentration windows.

How many genuinely usable independent study blocks exist on weekdays?
Which weekday is consistently overloaded?
Which weekend block is usually protected?
When does the learner think most clearly?
When does the learner usually procrastinate or become too tired for high-level reasoning?
Is GP currently losing marks through knowledge, interpretation, argument, language, Paper 2 precision, timing or variance?
What assessment is next?
Which other subject currently has the highest urgency?

The result is not yet a schedule. It is a resource map. Only after that map exists should the learner decide how GP fits into the week.

Maren, Iona and Leonie need different timetables

Maren is a writing-first learner. She enjoys ideas and essays and can accidentally turn every GP session into long-form writing. Her timetable must force variety: question selection, short plans, evidence retrieval, paragraph surgery and Paper 2 maintenance. She needs limits on overbuilding.

Iona is a reading-first learner. She can spend a great deal of time understanding passages, articles and current affairs. Her timetable must convert input into visible output: closed-note retrieval, summary compression, inference explanation, connection mapping and application. She needs proof that reading changes performance.

Leonie is an execution-first learner. She may understand GP well but become unstable when the week is crowded or a test approaches. Her timetable must include fixed start routines, short recoverable tasks, realistic timed exposure, buffer capacity and rules for what to do when the plan slips.

The timetable has four layers

Year architecture: what the broad phases of JC2 are trying to achieve.
Block architecture: what the next 24, 12, 6 or 3 weeks prioritise.
Weekly architecture: how Paper 1, Paper 2, input, repair and simulation share the week.
Session architecture: what actually happens inside a 20-, 40-, 60- or 90-minute block.

Weak timetables usually jump straight to layer four: “Monday 7–8 pm, GP.” Strong timetables begin with the phase and make each session serve it.

The annual JC2 architecture

Phase 1 — Stabilise and diagnose

Early JC2 should identify which JC1 weaknesses still matter. Use recent school work, one or two representative timed tasks, marked scripts and closed-note issue retrieval. The goal is to define no more than three active risks. The schedule should favour targeted repair over high simulation volume.

Phase 2 — Build transfer under time

Once the main repair targets are clear, increase unseen work. Paper 1 plans should come from unfamiliar question sets. Paper 2 practice should use passages where the topic is not already comfortable. Timed segments become more common, but full papers still appear only when they answer a diagnostic question.

Phase 3 — School assessment and prelim integration

When common tests or prelims approach, the timetable becomes more examination-shaped. This does not mean abandoning repair. It means integrating repair into paper-level performance: question selection, pacing, completion, recovery, checking and variance. School assessment evidence should feed the next block rather than simply generating a grade.

Phase 4 — Final runway and taper

Late JC2 shifts from expansion toward retrieval, consolidation, representative simulation and execution. Current-affairs input becomes more selective. New techniques face a stricter adoption gate. The goal is not maximum workload. The goal is maximum availability of known skills on examination day.

The 24-week GP plan

A 24-week plan is useful when there is enough runway to repair foundations without losing sight of final performance. Divide it into six four-week cycles. Each cycle has one dominant aim and one maintenance aim.

Weeks 1–4: Diagnostic compression. Build the active-risk dashboard, prune issue notes, establish Paper 1 and Paper 2 baselines, and identify repeated language or timing errors.
Weeks 5–8: Paper 1 architecture. Emphasise question interpretation, selection, thesis, paragraph roles, evidence economy and evaluation. Maintain Paper 2 with one precision block each week.
Weeks 9–12: Paper 2 meaning control. Emphasise passage claim tracking, paraphrase, inference, summary, connections and application. Maintain Paper 1 with one unseen planning set and one paragraph or essay block each week.
Weeks 13–16: Integrated timing. Add more timed sections, finishability decisions, checking and skip-return routines. Current-affairs retrieval becomes question-linked rather than topic-linked.
Weeks 17–20: Simulation and variance. Use carefully spaced full or near-full papers. Every simulation produces a repair block and a delayed transfer test.
Weeks 21–24: Consolidation. Reduce disruptive novelty, revisit active risks, retrieve issue models, rehearse exam routines and stabilise sleep and workload.

Do not interpret these weeks rigidly. If school prelims fall inside Week 14, the simulation phase may start earlier. If a learner has a severe Paper 2 deficit, that block may need six weeks instead of four. The architecture is a decision framework, not a calendar prison.

The 12-week GP plan

Twelve weeks is enough time for meaningful change if the plan is selective. The biggest danger is trying to reproduce a full-year programme at double speed. Do less, but choose better.

Weeks 1–2: baseline, marked-script review, issue-bank audit, timing map and three active risks.
Weeks 3–4: repair the highest-cost Paper 1 or Paper 2 constraint with isolated drills plus unseen transfer.
Weeks 5–6: repair the second major constraint while maintaining the first under short timed conditions.
Weeks 7–8: integrate both papers; add one realistic simulation or two half-paper simulations with full review.
Weeks 9–10: focus on variance: difficult topics, unfamiliar passages, late-paper fatigue, timing and recovery.
Weeks 11–12: taper new input, retrieve established knowledge, revisit active feedback, run representative practice and protect freshness.

The 12-week plan works best when every week has one sentence of intent. Examples: “This week tests whether I can choose a Paper 1 question without chasing familiarity.” “This week tests whether summary accuracy survives time pressure.” “This week reduces late-paper language deterioration.” Intent prevents schedule drift.

The 6-week GP plan

Six weeks requires aggressive prioritisation. Do not rebuild everything. Use current evidence to select one Paper 1 risk, one Paper 2 risk and one execution risk.

Week 1: diagnose and choose the three risks. Remove low-value tasks from the schedule.
Week 2: intensive repair of the highest-cost risk using short repetitions.
Week 3: transfer the repair to unseen tasks and begin the second risk.
Week 4: integrate under moderate time; refresh issue-bank retrieval and checking routines.
Week 5: one high-quality simulation followed by deep review and targeted repair.
Week 6: representative practice, retrieval, confidence in known routines, lower novelty and stronger sleep protection.

If a student is still doing four full GP papers in Week 6 while carrying unresolved recurring errors, the schedule is measuring too much and teaching too little.

The final 3-week GP plan

Week 3 before the examination

Run the final major diagnostic. Check whether Paper 1 question selection is stable, whether examples are retrievable, whether Paper 2 meaning control survives time, and whether completion is reliable. Repair only live risks. Do not reopen solved topics because they feel familiar.

Week 2 before the examination

Reduce simulation volume. Use shorter timed tasks, active retrieval, summary compression, application bridges, issue-model recall, question ranking and checking routines. Confirm logistics and sleep rhythm.

Final week

Protect the operating system. New material must pass a strict relevance test. Use brief representative tasks and closed-note retrieval. Keep Paper 1 and Paper 2 both active without exhausting either. The learner should finish the week feeling procedurally familiar, not cognitively flooded.

The default weekly architecture

There is no universal number of GP hours. A useful default for many students is to distribute GP across four different jobs rather than one large weekend block.

Input and issue maintenance: one short block to update one or two existing issue models.
Paper 1 output: one block for question selection, planning, paragraph work or a full essay depending on the current phase.
Paper 2 output: one block for interpretation, paraphrase, summary, synthesis or application.
Feedback and repair: one block that turns marked work into a new decision rule and transfer test.
Simulation: added selectively, not automatically every week.

In a crowded week, reduce duration before deleting entire functions. A 20-minute Paper 2 precision drill can preserve a skill better than abandoning Paper 2 for seven days because there was no time for a full paper.

A sample moderate-load week

Monday — 25 minutes: closed-note current-affairs retrieval. Reconstruct one issue model and verify only what is missing.
Wednesday — 45 minutes: Paper 2 precision block. One passage segment, paraphrase/inference questions, error classification and one transfer item.
Friday — 35 minutes: Paper 1 selection and planning. Rank an unseen question set, choose one, produce thesis and paragraph architecture.
Sunday — 75 minutes: one larger output task: timed essay, half Paper 2, or a feedback-to-transfer repair session depending on the current active risk.

This is not a prescription. It demonstrates distribution. Four different cognitive jobs across the week usually create better retention and transfer than one four-hour GP marathon.

A sample high-pressure school week

When other subjects peak, GP can temporarily move into maintenance mode rather than disappearing.

15 minutes: one issue retrieval card.
20 minutes: one Paper 1 question-ranking set.
20 minutes: one Paper 2 semantic-precision drill.
20 minutes: review the most important feedback rule from recent marked work.

Seventy-five minutes spread across the week can preserve the system until capacity returns. The schedule should explicitly mark the week as maintenance so the learner does not interpret reduced volume as failure.

A sample GP-intensive repair week

After a diagnostic reveals a serious recurring weakness, GP may need a temporary concentration block.

Day 1: inspect marked scripts and isolate the first weak link.
Day 2: complete three short drills targeting that link.
Day 3: attempt a new task with the same underlying demand.
Day 4: receive or conduct feedback and refine the replacement rule.
Day 5 or 6: test under time.
Day 7: record recurrence and decide whether to maintain, escalate or retire the risk.

The week should end with a decision. “Do more GP” is not a decision. “Question-scope error did not recur in three unseen plans; move it to maintenance and promote evidence evaluation” is a decision.

Session design: 20 minutes

Rank five Paper 1 questions by finishability.
Retrieve one issue model from memory.
Paraphrase five difficult claims while preserving certainty and causality.
Compress one short passage into summary points.
Review one feedback rule and complete two transfer examples.
Rehearse one application bridge from passage idea to context.

Session design: 40 minutes

Unseen Paper 1 question set: shortlist, choose, plan, stress-test thesis and review.
One Paper 2 passage segment: answer, mark, classify errors, redo one weak item and test transfer.
Issue-bank audit: retrieve, verify, prune and connect examples to possible question families.
Marked-script repair: classify comments, write decision rules, partial rewrite and unseen test.

Session design: 60–90 minutes

Timed essay plus immediate process notes.
Large Paper 2 segment plus detailed error review.
Mock review and repair design.
Two linked cycles: short diagnostic → repair drill → unseen transfer.

Long sessions should not become unbroken endurance. Use clear phases. A 90-minute block can contain 45 minutes of output, 20 minutes of feedback, 15 minutes of repair and 10 minutes of planning the next transfer test.

How to balance Paper 1 and Paper 2

Equal time is not always fair time. If Paper 1 is stable and Paper 2 is the binding constraint, Paper 2 should receive more repair time. But the stronger paper still needs maintenance because skills decay.

A useful allocation rule is maintenance floor + repair premium. Give each paper a minimum weekly touch. Then assign the extra block to the weaker or more urgent mechanism. This prevents a common JC2 pattern where the stronger paper is abandoned for six weeks and becomes the new weakness.

How to schedule current affairs

Current-affairs work has three different jobs: discovery, verification and retrieval. They should not be confused.

Discovery: notice important developments that may change an existing issue model.
Verification: confirm date, actors, mechanism, scale and limitation using reliable sources.
Retrieval: recall the issue later without the article in front of you and connect it to a question.

A student who spends five hours discovering and zero minutes retrieving has created a research archive, not an examination resource. Schedule current affairs in small bounded blocks. Use the GP Current Affairs and Examples guide for the evidence discipline behind this process.

How to schedule mock papers

A mock has a cost. It consumes time, energy, marking and review capacity. Therefore every mock must have a purpose statement before it is scheduled.

Test whether Paper 1 question choice is now stable.
Test whether Paper 2 accuracy survives the second half of the paper.
Test whether completion remains reliable when the topic is unfamiliar.
Test whether a repaired feedback error returns under fatigue.
Test examination-day pacing and recovery.

Do not schedule the next full mock until the previous mock has produced at least one repair action and one transfer check. See GP Practice Papers and Mock Exams for the full simulation system.

How to schedule feedback and marked scripts

Feedback is time-sensitive. A script returned three weeks ago loses diagnostic value if the learner cannot remember the decision process that produced it. Build a small feedback block within 24 to 72 hours where possible.

Capture the comment.
Classify the error family.
Identify the likely cause.
Write a replacement decision rule.
Schedule one short repair drill.
Schedule one unseen transfer task later in the week.

Use How to Use Feedback and Marked Scripts when the challenge is turning annotations into future performance.

How to integrate school tests and prelims

School assessment weeks already provide heavy GP measurement. Do not automatically add extra full papers around them. Use the school paper as the simulation and reserve independent study for preparation beforehand and repair afterwards.

A useful assessment cycle is:

Two weeks before: identify likely performance risks, not predicted topics.
One week before: representative timed segments, retrieval and checking routines.
Assessment week: reduce extra GP volume and protect execution.
Within 72 hours after return: classify the most expensive errors.
Following week: repair the first weak link.
Two to three weeks later: delayed unseen retest.

The Prelim to A-Level Strategy owns the deeper conversion of preliminary-examination evidence into final-runway decisions.

How GP should coexist with other A-Level subjects

GP cannot be planned in isolation. The final-year timetable must account for the marginal return of the next hour across subjects. A learner with a Chemistry practical test tomorrow should not force a full GP essay tonight merely because Sunday was labelled “GP essay day.” The plan should bend without breaking.

Use three load states:

Build state: ordinary week; GP receives full planned training.
Maintenance state: other-subject pressure is high; GP keeps minimum Paper 1, Paper 2 and retrieval touches.
Recovery state: illness, severe fatigue or major school disruption; the priority is restoring capacity, then restarting through the smallest stable routine.

This removes the false choice between “follow the timetable perfectly” and “give up completely.”

The buffer rule

Do not allocate every available hour. Keep at least one flexible weekly block or leave deliberate slack inside larger study periods. Buffers absorb school events, extra consultations, fatigue and unfinished work without forcing every subsequent task to move.

A timetable without a buffer assumes perfect forecasting. JC2 is not perfectly forecastable.

The reset protocol when the timetable slips

Stop carrying everything forward. Missed tasks do not all become tomorrow’s tasks.
Identify why the slip happened. Bad estimate, unexpected school demand, avoidance, fatigue, illness or overplanning?
Protect the next high-value job. Choose one task that keeps the system alive.
Delete or defer low-value work. A schedule reset requires subtraction.
Return through a small win. Use a 20- to 40-minute bounded task before rebuilding a full week.
Change the timetable if the same failure repeats. Repeated slippage is evidence that the design is wrong.

Leonie’s key rule is simple: a missed Tuesday should not be allowed to destroy Wednesday, Thursday and the weekend. Recovery is part of the timetable, not an exception to it.

When to increase GP time

The same high-cost error has survived several weeks of low-dose practice.
School assessment evidence shows GP is the largest current risk.
The student cannot complete representative tasks within expected time.
Paper 1 or Paper 2 has been under-maintained for several weeks.
A major assessment is approaching and GP-specific transfer has not been tested.

When to reduce GP time

Extra hours are producing fatigue but not new learning.
Full papers are repeating the same errors without repair.
Current-affairs collection has expanded beyond retrieval capacity.
Other subjects have acute high-return needs.
The learner is near examination week and freshness is becoming more valuable than volume.

The anti-procrastination design

Some GP tasks are cognitively ambiguous. “Study current affairs” and “improve essays” are easy to delay because the start action is unclear. Convert every block into an executable first move.

Not “Essay practice” but “Open unseen set, rank top three questions in eight minutes.”
Not “Read news” but “Update the technology-regulation issue card with one verified development.”
Not “Paper 2” but “Complete two inference questions and explain evidence-to-answer reasoning.”
Not “Review mistakes” but “Take the last marked essay and classify the three most expensive comments.”

The timetable should contain verbs.

The weekly review meeting with yourself

Spend ten minutes at the end of the week answering five questions:

What GP capability actually improved this week?
Which planned task did not happen, and why?
Which error repeated?
What is the highest-return GP job next week?
Does next week require build, maintenance or recovery state?

A timetable becomes intelligent only when it learns from execution.

Four student timetable archetypes

Archetype 1 — Strong content, weak Paper 1 structure

Reduce news collection. Maintain one current-affairs block per week. Add two Paper 1 architecture blocks: question ranking and timed planning, plus one paragraph-to-essay transfer. Paper 2 remains on maintenance.

Archetype 2 — Strong essay, weak Paper 2 precision

Keep one short Paper 1 maintenance task weekly. Allocate two or three shorter Paper 2 precision blocks across the week instead of one large practice. Target paraphrase, inference, summary or application according to evidence.

Archetype 3 — Knowledgeable, inconsistent under time

Reduce passive study. Increase timed starts, closure rules, section checkpoints, skip-return and checking. Use full simulations sparingly; most training should isolate the execution mechanism that collapses.

Archetype 4 — Overloaded high-achiever

GP often receives either too much perfectionist time or none at all. Use small high-quality blocks, strong maintenance floors, clear stop rules and weekly prioritisation across subjects. The goal is sustainable excellence, not maximal daily effort.

60 timetable failure scenarios and repairs

Every GP session becomes current affairs. Cap input and require an output task before more reading.
Every GP session becomes essay writing. Schedule Paper 2 precision and question-selection work explicitly.
Paper 2 is postponed because it feels harder. Move it to an earlier, shorter weekday block.
Paper 1 is postponed because it feels too large. Replace full essays with plans and paragraphs until execution restarts.
The learner plans seven GP hours and completes two. Rebuild from actual capacity, not aspiration.
The learner completes everything but sleeps too little. Reduce workload; sleep loss is part of the system cost.
A school test interrupts the week. Switch GP to maintenance rather than carrying every missed task forward.
One missed day causes guilt. Use the reset protocol and protect the next high-value block.
Weekend GP expands indefinitely. Give the block an end condition and stop rule.
Weekdays are too exhausted for essays. Use short retrieval and precision tasks on weekdays; place deeper writing in a fresher block.
Current-affairs notes keep growing. Add a pruning week and retrieval test before new input.
Examples cannot be recalled under time. Schedule closed-note recall after unrelated work to create interference.
Essay marks are flat despite weekly essays. Replace one essay with diagnosis and targeted paragraph repair.
Paper 2 marks are flat despite many practices. Track the error family rather than total volume.
The learner does a mock every Sunday. Insert repair and delayed retest before the next mock.
The learner avoids mocks completely. Start with half-paper or timed-section simulations.
School prelims are treated as a verdict. Schedule a post-prelim diagnostic week.
School prelims are ignored after marking. Convert the top two recurring errors into the next block’s priorities.
The plan uses exact hours for every day. Replace some fixed hours with flexible weekly targets and buffers.
The plan is too flexible and nothing starts. Fix one or two anchor sessions each week.
Feedback arrives but the timetable is full. Treat feedback review as higher priority than another generic practice.
Consultations are booked but not prepared. Schedule a ten-minute pre-consultation diagnosis block.
Consultation advice is forgotten. Schedule a transfer task within the next week.
Paper 1 improves while Paper 2 declines. Reinstate the Paper 2 maintenance floor.
Paper 2 improves while examples go stale. Reinstate issue retrieval and light current-affairs maintenance.
The learner spends too long choosing examples. Schedule example-retrieval drills by mechanism.
The learner spends too long planning essays. Add a planning ceiling and multiple short timed plans.
The learner starts essays too quickly and drifts. Add a planning floor and interpretation checklist.
Summary practice always happens when fresh. Occasionally place it after a reading block to test fatigue resilience.
Application is weak because context knowledge is shallow. Add one local-context card session, not a large new notes project.
The learner revises favourite issues only. Use a rotation that includes uncomfortable but high-value domains.
The learner revises every issue equally. Weight retrieval by usefulness, weakness and recency.
The plan changes every week. Keep the architecture stable and change only the active-risk block.
The plan never changes despite evidence. Use weekly review data to reallocate time.
The student cannot explain the purpose of a task. Remove or redesign it.
The schedule is copied from a top student. Rebuild around this learner’s school load and error profile.
The schedule contains no review. Add a weekly ten-minute control meeting.
The schedule contains no buffer. Free one small block before adding anything else.
The buffer becomes wasted time every week. Use it for optional maintenance only after core tasks are secure.
A student is sick for four days. Enter recovery state; do not compress five days of work into the weekend.
The learner returns from illness and overcompensates. Restart with minimum viable GP before full build state.
Other subjects are neglected before GP prelims. Use representative GP work rather than unlimited volume.
GP is neglected before other-subject prelims. Preserve minimal Paper 1, Paper 2 and retrieval touches.
Final month is filled with new resources. Apply the novelty filter and keep only active-risk additions.
Final month contains no new information at all. Maintain light updates to major evolving issues.
The learner stops writing full essays too early. Keep occasional integrated practice until taper.
The learner keeps doing full essays too late. Shift toward short representative tasks and freshness.
Timetable performance is judged by completion rate alone. Track whether the intended capability changed.
A task is completed badly just to tick the box. Use a quality gate and redo only the key mechanism.
The learner studies whenever motivated. Create fixed anchors so GP does not depend on mood.
The learner follows the timetable even when the diagnosis changes. Promote the new binding constraint.
Paper 1 examples are fresh but argument is weak. Reallocate from input to structure.
Argument is strong but examples are vague. Reallocate one block to evidence retrieval and verification.
Paper 2 understanding is good but answers are wordy. Schedule compression drills rather than more reading.
Paper 2 answers are concise but inaccurate. Schedule semantic-preservation work rather than speed.
Examination week triggers panic studying. Use the prewritten final-week taper rather than inventing a new schedule.
The student does not know what to do the day after a bad paper. Use recovery: rest, classify only what is useful, protect preparation for the next sitting.
The student studies GP until the last possible minute before bed. Protect shutdown time and sleep.
The learner cannot restart after a holiday or break. Begin with one short diagnostic and one easy retrieval win.
The learner reaches the exam with many unfinished resources. Accept incompleteness; prioritise retrievable competence over archive completion.

40 timetable-building drills

Map every fixed weekly commitment before adding GP.
Identify the three freshest cognitive windows in the week.
Identify the two most overloaded periods and protect them from high-demand GP.
Convert four vague GP tasks into executable verbs.
Create a maintenance-floor version of the week using no more than four short blocks.
Create a build-state version of the same week.
Create a recovery-state version.
Choose one fixed GP anchor session.
Add one flexible buffer block.
Assign one Paper 1 and one Paper 2 minimum weekly touch.
Choose the current repair premium.
Write one sentence explaining the purpose of the next mock.
Schedule its review before scheduling another mock.
Place one feedback-to-transfer session within 72 hours of marked work.
Schedule one delayed transfer test seven days later.
Design a 20-minute current-affairs block with a hard stop.
Design a 20-minute Paper 1 planning block.
Design a 20-minute Paper 2 precision block.
Design a 40-minute marked-script repair block.
Design a 60-minute integrated output-and-review block.
Choose one task to delete from an overloaded week.
Choose one task to defer rather than delete.
Choose one task that must remain even during other-subject pressure.
Review the last four weeks and calculate how often planned GP sessions actually started.
Identify the most common reason for non-start.
Change the timetable to remove that trigger.
Identify one GP task that creates little visible return.
Replace it with a targeted alternative.
Run a one-week experiment with shorter but more frequent Paper 2 work.
Run a one-week experiment with fewer but deeper Paper 1 blocks.
Compare which design improves execution.
Write the exact reset rule for a missed weekday session.
Write the exact reset rule for a missed weekend block.
Build a prelim week with reduced extra simulation.
Build the post-prelim repair week.
Build the final three-week taper now, before panic arrives.
Write a novelty filter for the final week.
Write a minimum-sleep rule that the timetable cannot violate.
At week’s end, name one capability that improved and one that did not.
Use that evidence to allocate the next week’s repair premium.

The 100-question GP timetable audit

Use this audit when a timetable looks busy but performance is not moving.

Purpose and diagnosis

What is the main GP problem this month?
What evidence proves it?
Is it Paper 1, Paper 2, knowledge, language or execution?
What is the current binding constraint?
What is the second constraint?
Which old weakness is now stable?
Has it been removed from the active schedule?
What is the next assessment?
What does that assessment actually need from the learner?
Can the timetable state its purpose in one sentence?

Capacity

How many independent study blocks are realistically available?
How many did the learner actually use last week?
Which days are chronically overloaded?
Which blocks have high cognitive freshness?
Which blocks are suitable only for light maintenance?
Is travel time usable for reading or retrieval?
Is the weekend overcommitted?
Is the learner sleeping enough?
Is GP displacing a more urgent subject?
Does the plan contain buffer capacity?

Paper 1 allocation

Is Paper 1 touched every week?
Is question selection practised separately?
Is planning practised without always writing the essay?
Is thesis work visible?
Are paragraph roles practised?
Is evidence retrieval scheduled?
Is evaluation scheduled?
Are full essays used for a reason?
Is essay review built in?
Does the timetable respond to the latest marked essay?

Paper 2 allocation

Is Paper 2 touched every week?
Are paraphrase and semantic precision isolated?
Are inference errors tracked?
Is summary selection separated from compression?
Are cross-passage relationships practised?
Is application explicitly scheduled?
Are timed sections used?
Are full-paper simulations spaced?
Is Paper 2 review deep enough?
Does the plan target the actual error family?

Current affairs and knowledge

How much time is spent discovering new material?
How much is spent verifying it?
How much is spent retrieving it?
Can the learner reconstruct issue models from memory?
Are examples tagged by mechanism?
Are stale examples pruned?
Is recent news displacing established knowledge?
Are uncomfortable domains ignored?
Are favourite topics over-revised?
Does every knowledge block have an output test?

Feedback and repair

How soon is marked work reviewed?
Are comments classified?
Are causes identified?
Are replacement rules written?
Are short repair drills scheduled?
Are unseen transfer tests scheduled?
Is recurrence tracked?
Are solved errors retired?
Are consultations prepared?
Does consultation advice change the next task?

Simulation

Why is the next mock scheduled?
What variable is it testing?
Was the previous mock repaired?
Was transfer retested?
Are mocks too frequent?
Are they too rare?
Is fatigue being measured?
Is timing being segmented?
Is recovery practised?
Does each simulation produce a training decision?

Execution and sustainability

Does each session have a clear first action?
Does each session have a stop condition?
Are difficult tasks placed in better energy windows?
Are short tasks available for overloaded days?
Is there a recovery-state plan?
Is there a maintenance-state plan?
Is there a build-state plan?
Is sleep protected?
Is exercise or recovery disappearing?
Can the plan survive one disrupted day?

Final runway

When will new-resource intake reduce?
When will full mocks reduce?
When will retrieval become dominant?
Are Paper 1 and Paper 2 both maintained?
Is the issue bank compact?
Are active risks few and clear?
Are checking routines familiar?
Is exam-day strategy rehearsed?
Is the final week already designed?
Does the learner know what not to do?

Control and adaptation

What percentage of planned sessions actually start?
Why do the failed sessions fail?
Is the plan too ambitious?
Is it too vague?
Is it too rigid?
Is it too easy?
What evidence would justify reallocating time?
What should be deleted next week?
What should receive the repair premium?
Can the learner run the timetable without constant adult management?

How the timetable connects to the rest of the JC2 system

Use the A-Level Exam Preparation guide for the complete final-year runway. Use How to Study for GP for the day-to-day learning process. Use the GP Revision Guide when deciding what to retrieve and repair. Use How to Improve GP Grades to identify the current binding constraint. Use Last-Minute GP Revision for the final taper and A-Level GP Exam Day Strategy for examination execution.

The final timetable principle

The best JC2 GP timetable is not the busiest. It is the one that keeps the right capabilities alive, gives the weakest high-value skill enough concentrated repair, uses school assessments as evidence, protects both papers, allows other subjects to breathe, and becomes simpler as the examination approaches.

When the calendar becomes difficult, do not ask how to squeeze everything in. Ask what still matters most, what can be maintained with a smaller dose, what should be removed, and what evidence will tell you that the next allocation was better.

Return to the JC2 General Paper hub for the complete final-year route.