JC 2 General Paper GP Tuition | Last-Minute GP Revision

Last-minute GP revision should make the learner’s system smaller, faster and more available. It is not a final attempt to learn the whole world. It is the period when broad preparation is compressed into a retrievable issue bank, a stable Paper 1 selection-and-argument routine, a precise Paper 2 meaning-control routine, a small set of checking cues and a recovery process that remains usable under pressure.

This page owns the final-days revision window inside the SETC JC2 General Paper lane. It is narrower than A-Level Exam Preparation, which owns the full runway, and narrower than the GP Revision Guide, which owns revision architecture across a longer period. Here the question is specific: what should a JC2 student do when the examination is close enough that novelty itself becomes a risk?

The first rule: the closer the exam, the more expensive unnecessary novelty becomes

Early in the year, experimenting with new resources, essay structures and note systems can be useful. Near the examination, every major change competes with consolidation. A new method must not only be theoretically better; it must become reliable quickly enough to justify displacing a procedure the learner already owns.

This is why last-minute revision uses a novelty gate. New material enters only when it solves a documented active risk, is clearly better than the current resource and can become usable within the remaining time.

Maren, Iona and Leonie in the final stretch

Maren wants to add more examples because every missing case feels dangerous. Her final revision must prune. Iona wants to verify every ambiguity and can overwork details that are already strong. Her final revision must calibrate “sufficient”. Leonie wants reassurance through repeated full papers. Her final revision must distinguish useful measurement from anxiety-driven simulation.

All three need the same final shift: from expansion to availability.

The five goals of last-minute GP revision

1. Retrieve: make core knowledge available without notes.
2. Maintain: keep stable Paper 1 and Paper 2 procedures active.
3. Repair selectively: address only high-leverage unresolved weaknesses.
4. Rehearse recovery: preserve the paper when difficulty appears.
5. Taper: reduce cognitive clutter and protect exam-ready performance.

Goal 1: retrieve, do not merely reread

Closed-note reconstruction should dominate issue revision. Before opening a topic map, write the central tension, two or three mechanisms, key examples, limitations and one serious counter-position. Then compare and repair only what was missing or inaccurate.

Rereading everything feels comprehensive but hides availability. The examination will not show the notes first.

Goal 2: maintain both papers

Even if one paper is stronger, keep a minimum maintenance dose. Paper 1 maintenance can be one unseen question set, a thesis-and-role plan and a short paragraph. Paper 2 maintenance can be one passage map, several semantic paraphrases and a compact summary or application segment.

The point is not volume. It is keeping the procedures accessible.

Goal 3: repair only what still matters

Keep no more than three active risks. A late repair should be specific: question-choice latency, summary target selection, modality drift, completion, one repeated language error, skip-return or checking. Do not open a new broad “improve evaluation” programme days before the exam unless the weakness is clear and trainable.

Goal 4: rehearse recovery

The final examination will contain uncertainty. Last-minute revision should not create the expectation of a smooth paper. Practise one difficult item inside a representative segment and execute the bounded-attempt, move, reset and return routine.

Goal 5: taper

Tapering means reducing the ratio of acquisition to retrieval and reducing the ratio of exhaustive simulation to representative maintenance. It does not mean stopping work. It means protecting the capabilities that now matter more than novelty.

The final fourteen days: compress the knowledge system

Two weeks out, audit the active issue bank. Retain cases that are accurate, mechanism-rich, distinct and portable. Remove redundant examples from active rotation. Identify volatile cases requiring one final freshness check. Reconstruct core concept families without notes.

At this stage, the student should see fewer active pages, not more. Background archives can remain available, but they should not dictate daily revision.

The final fourteen days: stabilise Paper 1

Practise question-set ranking, interpretation, thesis calibration and role planning. Use full essays only when they answer a specific unresolved question about integration or timing. Maintain evidence retrieval through concepts rather than memorised topic essays.

The final fourteen days: stabilise Paper 2

Maintain claim tracking, paraphrase fidelity, summary target control, cross-passage relationship language and application anchoring. Use short timed segments to keep semantic precision fast. If the learner has a known late-paper time leak, test the relevant sequence.

The final fourteen days: stop collecting predictions

Predicted-topic lists can create false scarcity: the student begins to believe only a handful of issues matter and interprets every new headline as confirmation. Use predictions, if encountered, as optional practice prompts only. Never narrow the entire bank around them.

The final ten days: shift from breadth to retrieval speed

Time how quickly the learner can reconstruct a core issue, generate a viable thesis and retrieve two distinct examples. Do not rush accuracy; simply observe latency. Slow retrieval on a core issue may justify one focused refresh.

The final ten days: verify volatile current affairs

Use the Current Affairs and Examples system to recheck active examples whose status can change quickly. Update dates, policy status or major outcomes only where material. Do not turn verification into a new research project.

The final ten days: resolve administrative uncertainty

Confirm the official examination arrangements relevant to the learner’s cohort and institution through authoritative sources. Remove avoidable uncertainty about venue, permitted materials and reporting requirements. Administrative clarity protects cognitive bandwidth.

The final seven days: use a maintenance-first timetable

Each day can contain one compact knowledge retrieval block, one Paper 1 or Paper 2 maintenance block, one active-risk repair or transfer task and a short review. The exact order should match the learner’s profile. Avoid filling every hour simply because the calendar says “one week left”.

The final seven days: reduce full-paper simulation

If integrated performance is already stable, full-paper volume should fall. Use representative segments, question-choice sets and semantic drills. A full mock still has value if it tests an unresolved high-cost hypothesis and leaves enough time for repair, but reassurance-seeking simulation has poor expected value.

The final seven days: rehearse the exam operating card

The card should be tiny. Paper 1: wording → shortlist → finishability → thesis → roles → evidence → completion. Paper 2: claim → command → semantic fidelity → target → relationship → context → time. Recovery: bounded attempt → mark → move → reset → return. Checking: personal high-probability risks first.

The final seven days: protect sleep consistency

Reading comprehension, working memory, judgement and language control all depend on cognitive function. Last-minute revision that repeatedly replaces sleep with low-quality late-night activity can undermine the very capacities GP measures. Preserve a routine that is realistically compatible with examination timing.

The final five days: retire broad error lists

Convert the error log into a small personal risk card. Maren might retain “scope, duplication, completion”. Iona might retain “source voice, modality, late timing”. Leonie might retain “skip-return, reset, change justification”. Historic errors belong in the archive, not in working memory.

The final five days: use confidence from evidence

Confidence should come from stable procedures, not motivational slogans. Review evidence of successful changed-task retests, improved completion, reduced semantic errors or better recovery. The learner does not need to feel certain that the paper will be easy. They need evidence that they know what to do when it is not.

The final three days: stop major repairs

Only a narrow, well-understood correction should enter now. Major architectural change is unlikely to receive enough repetitions to become automatic. Use retrieval, light representative output, volatile-example verification if genuinely necessary and operating-card rehearsal.

The final three days: reduce note volume

Use condensed issue maps and personal cues. Do not reopen the full archive unless a specific retrieval gap needs checking. The final system should fit cognitively into a small surface.

The final forty-eight hours

Use short blocks. Reconstruct major concept families. Review a few representative examples. Interpret several unseen questions without writing full essays. Complete one compact Paper 2 meaning set. Rehearse recovery and checking. Resolve logistics. Stop before cognitive quality collapses.

What not to do in the final forty-eight hours

• Do not read an enormous new notes pack.
• Do not memorise a new universal essay template.
• Do not attempt to learn every predicted topic.
• Do not take a full mock purely for reassurance.
• Do not replace a proven timing plan without evidence.
• Do not compare revision volume competitively with peers.
• Do not turn one forgotten example into proof that nothing is known.

The final twenty-four hours

Keep revision light and familiar. Review the operating card, key issue tensions, a small number of examples and personal risk cues. If a fact feels uncertain, either verify it quickly through a reliable source or choose a better-known example. Avoid late attempts to become expert in a new domain.

The night before

Prepare materials and logistics early enough that the final hours are not consumed by administrative decisions. The academic work should already be tapering. The objective is to arrive with accessible knowledge and functioning judgement, not with the feeling that every page has been reread.

The morning before the paper

Use familiar routines. A very short retrieval warm-up is reasonable if it helps the learner feel oriented, but avoid competitive last-minute content exchange. The final exam-day execution layer belongs in A-Level GP Exam Day Strategy once that page is published.

Last-minute Paper 1: what to keep active

• Read the wording before recalling content.
• Shortlist before committing.
• Compare finishability, not favourite topic.
• Use a working definition when it changes the argument.
• Make the thesis operational.
• Give paragraphs distinct roles.
• Use enough evidence, not all evidence.
• Let evaluation change judgement.
• Protect completion.

Last-minute Paper 1: what to stop doing

Stop memorising complete introductions, conclusions and fixed evidence paragraphs. Stop adding examples merely to feel safer. Stop practising only favourite topics. Stop treating every essay as an opportunity to display maximum knowledge.

Last-minute Paper 2: what to keep active

• Track who claims what.
• Preserve quantity, certainty and causality.
• Answer the command, not the broad topic.
• Define summary target before collecting points.
• Compare propositions rather than words.
• Anchor application to the passage.
• Use bounded effort on resistant items.
• Protect later-section time.

Last-minute Paper 2: what to stop doing

Stop mechanically swapping synonyms. Stop overannotating every passage line. Stop spending excessive time perfecting early answers. Stop changing answers during review without a concrete semantic or evidential reason.

Last-minute current affairs: use a small verified bank

The active bank should contain examples the learner can explain in under two minutes: factual anchor, mechanism, what it supports, and its limit. More examples can remain archived, but the final retrieval set should be deliberately small enough to access.

Last-minute vocabulary: precision, not ornament

Review functional language the learner already uses: degrees of certainty, causation, comparison, concession, evaluation and responsibility. Do not cram rare vocabulary with uncertain collocation. The wider eduKate ecosystem retains the specialist vocabulary owners; this final revision layer only protects functional use.

Last-minute model essays: deconstruct, do not absorb

If using a model, identify thesis and roles quickly, then close it. Do not immerse in someone else’s voice immediately before the exam. The learner’s own operating system now matters more than acquiring another script.

Last-minute mock exams: know when enough is enough

Use a full mock only if the information can still change useful action. Otherwise prefer shorter representative tasks. The Practice Papers and Mock Exams owner explains the measurement logic in depth.

The last-minute novelty gate

1. What active risk does this solve?
2. What evidence shows it is better?
3. How many repetitions can I give it before the exam?
4. What existing routine will it replace?
5. What happens if I simply keep the stable system?

The Last-Minute Laboratory: one hundred scenarios

Scenario 1 — Maren discovers a new notes pack ten days out. She samples it only for a documented gap; she does not migrate her system.

Scenario 2 — Iona wants to verify every statistic. She verifies volatile active examples and retires uncertain low-value numbers.

Scenario 3 — Leonie wants a full mock every day. She replaces reassurance volume with representative segments and repair.

Scenario 4 — Student forgets one example. Check whether the mechanism has another reliable case; do not reopen the whole topic.

Scenario 5 — Student forgets an entire issue map. Reconstruct, repair, retest next day; decide whether it belongs in active coverage.

Scenario 6 — Student learns a predicted topic. Use it for one practice question, then return to broad concept retrieval.

Scenario 7 — Student sees conflicting prediction lists. Treat both as non-authoritative practice ideas; do not change coverage.

Scenario 8 — Student finds a new essay template. Apply novelty gate; near exam it is usually too expensive unless current architecture is genuinely failing.

Scenario 9 — Student has an unresolved question-choice problem. Use several short unseen-set rankings rather than a full essay marathon.

Scenario 10 — Student has unresolved Paper 2 modality drift. Use proposition paraphrase and semantic audit, then one timed segment.

Scenario 11 — Student’s final mock is strong. Preserve routine; taper instead of chasing confirmation.

Scenario 12 — Student’s final mock is weak. Find one high-leverage cause; do not rebuild the year.

Scenario 13 — Student’s issue bank has fifty active examples. Prune by distinct function and retrieval quality.

Scenario 14 — Student’s issue bank has eight examples. Check concept-family coverage; add only critical missing functions.

Scenario 15 — Student studies one favourite topic repeatedly. Shift to mixed concept retrieval.

Scenario 16 — Student avoids a weak topic. Build minimum viable map if time allows; do not seek mastery.

Scenario 17 — Student stays up late to finish notes. Stop low-value formatting and protect cognitive readiness.

Scenario 18 — Student is too anxious to start. Use a five-minute retrieval opening and one defined task.

Scenario 19 — Student cannot stop revising. Use stopping conditions and next-action note.

Scenario 20 — Student wants new vocabulary list. Review functional existing vocabulary instead.

Scenario 21 — Student reads model essays all day. Limit exposure; end every model session with original output.

Scenario 22 — Student does no writing for a week. Add light representative Paper 1 output to preserve production fluency.

Scenario 23 — Student does no Paper 2 for a week. Add semantic and timing maintenance.

Scenario 24 — Student only does full essays. Add question-choice and planning repetitions.

Scenario 25 — Student only does Paper 2 drills. Add an integrated timed segment.

Scenario 26 — Student checks current affairs every hour. Use one scheduled freshness window.

Scenario 27 — Major news breaks days before exam. Understand the broad development if relevant; do not build an entire new issue system around it.

Scenario 28 — A core example changes materially. Update factual anchor and implication or retire it.

Scenario 29 — A core example remains stable. Stop rechecking it unnecessarily.

Scenario 30 — Student wants exact statistics for everything. Keep exact numbers only where understood and useful; accurate qualitative description is safer than fragile precision.

Scenario 31 — Student suddenly dislikes their thesis method. Test whether recent evidence actually shows a problem before changing.

Scenario 32 — Student’s planning time remains long. Use a ceiling and role sufficiency rule; do not eliminate planning entirely.

Scenario 33 — Student’s planning time is too short. Restore minimum architecture if drift persists.

Scenario 34 — Student’s Paper 1 conclusion is unstable. Practise conclusion-from-plan rather than repeated full essays.

Scenario 35 — Student’s evidence retrieval is slow. Retrieve by concept under a short timer.

Scenario 36 — Student’s evaluation is weak. Use one criterion drill on familiar content; avoid learning a giant new evaluation framework.

Scenario 37 — Student’s grammar errors are low-frequency. Add them to checking rather than broad grammar study.

Scenario 38 — Student’s grammar errors are frequent and structural. Repair the highest-cost pattern with sentence rewrites.

Scenario 39 — Student’s Paper 2 referents are weak. Use several slow referent traces, then one timed transfer.

Scenario 40 — Student’s summary target is weak. Practise target gates on short extracts.

Scenario 41 — Student’s summary expression is slow. Compress preselected points; then reintegrate.

Scenario 42 — Student’s application is weak. Use one source proposition across two contrasting contexts.

Scenario 43 — Student’s connections are vague. Practise one dimension at a time.

Scenario 44 — Student’s Paper 2 early answers consume time. Rehearse closure and later-section checkpoints.

Scenario 45 — Student never checks Paper 2. Protect a short personal-risk review reserve.

Scenario 46 — Student overchecks Paper 2. Use change-justification and stop rules.

Scenario 47 — Student panics when an example disappears. Use a sufficient-example rule and move.

Scenario 48 — Student panics when a passage is difficult. Map claim and movement; do not interpret unfamiliarity as inability.

Scenario 49 — Student wants another tutor consultation days before exam. Use it only for a specific unresolved bottleneck, not to import a new system.

Scenario 50 — Student receives peer advice contradicting tutor routine. Preserve evidence-supported routine unless new advice solves a documented problem.

Scenario 51 — Student compares revision hours with friends. Return to readiness evidence.

Scenario 52 — Student feels guilty resting. Use planned stopping conditions; cognitive readiness is part of preparation.

Scenario 53 — Student sleeps later because school is over. Move routine toward the examination schedule if practical.

Scenario 54 — Student wakes very early to cram. Prefer familiar light review over sacrificing rest for new content.

Scenario 55 — Student cannot remember every active issue. Prioritise concept-family coverage and transfer; no one needs encyclopedic recall.

Scenario 56 — Student can remember issues but not limitations. Retrieve one counterexample or condition beside each core claim.

Scenario 57 — Student can remember examples but not source quality. Keep provenance only for active high-value cases.

Scenario 58 — Student fears old examples. Keep them if mechanism remains relevant and facts stable.

Scenario 59 — Student overuses the newest examples. Select by explanatory power, not date alone.

Scenario 60 — Student reads predicted essay answers. Convert to question-family analysis rather than memorisation.

Scenario 61 — Student learns a new “perfect intro”. Discard unless it genuinely fits multiple changed prompts through function, not wording.

Scenario 62 — Student memorises quotations. Use only quotations already well understood; do not depend on them.

Scenario 63 — Student worries handwriting will fail. Include a brief realistic production block if this is a known issue, not hours of panic copying.

Scenario 64 — Student’s hand is fine. Do not invent a new physical training concern near the exam.

Scenario 65 — Student wants to simulate exact exam day repeatedly. One well-designed rehearsal may help; repetition has opportunity cost.

Scenario 66 — Student has no recovery cue. Practise a short procedural reset.

Scenario 67 — Student has too many recovery techniques. Keep the simplest one that works.

Scenario 68 — Student’s checking list has ten items. Reduce to highest-probability, highest-cost risks.

Scenario 69 — Student has no checking list. Build one from repeated historical errors.

Scenario 70 — Student’s final week feels “too easy”. Taper can feel less intense because the system is compressed; judge by readiness evidence.

Scenario 71 — Student increases workload because taper feels wrong. Preserve planned intensity unless performance evidence requires change.

Scenario 72 — Student’s active risk is unresolved three days out. Use a small direct repair and simple cue, not a wholesale system.

Scenario 73 — Student’s active risk keeps returning. Accept it may require a checking or containment strategy rather than complete elimination.

Scenario 74 — Student wants to “peak” by exhaustion. Peak performance requires usable cognition; exhaustive volume is not the objective.

Scenario 75 — Student has one day with poor concentration. Use lower-demand retrieval and rest; do not infer loss of all learning.

Scenario 76 — Student feels unusually strong. Preserve routine; do not add unnecessary tests.

Scenario 77 — Student reads official syllabus again and panics. Use it only to confirm requirements; do not reinterpret every objective as a new topic to master.

Scenario 78 — Student finds old uncorrected work. Review only if it maps to an active risk.

Scenario 79 — Student wants to redo every mistake. Retest representative high-leverage errors instead.

Scenario 80 — Student wants to review every model essay. Select a few for specific functions and stop.

Scenario 81 — Student feels weak on culture topics. Build minimum concept map—value, identity, market, public good, censorship—then one practice question.

Scenario 82 — Student feels weak on science topics. Build minimum map—evidence, uncertainty, risk, expertise, ethics—then one practice question.

Scenario 83 — Student feels weak on economics. Build minimum map—growth, distribution, incentives, security, market power—rather than a crash course in economics.

Scenario 84 — Student feels weak on government. Build minimum map—capacity, legitimacy, rights, accountability, trust.

Scenario 85 — Student feels weak on environment. Build minimum map—externality, mitigation, adaptation, distribution, intergenerational justice.

Scenario 86 — Student feels weak on media. Build minimum map—incentive, trust, verification, free expression, platform power.

Scenario 87 — Student feels weak on globalisation. Build minimum map—interdependence, resilience, trade, sovereignty, distribution.

Scenario 88 — Student has too many concept maps. Consolidate recurring concepts across domains.

Scenario 89 — Student wants exact exam question prediction. Replace with question-family and concept readiness.

Scenario 90 — Student worries Paper 1 will be all unfamiliar. Practise one mixed set and demonstrate concept translation.

Scenario 91 — Student worries Paper 2 passage will be impossible. Practise claim tracking on one dense unfamiliar passage.

Scenario 92 — Student thinks feeling anxious means being unprepared. Use procedures regardless of emotional certainty; judge readiness by evidence.

Scenario 93 — Student feels no anxiety and worries that means complacency. Review operating card and continue routine; emotion is not the measure.

Scenario 94 — Student loses confidence after one bad final drill. Compare with broader process trend before changing strategy.

Scenario 95 — Student gains confidence after one easy drill. Enjoy success, but preserve realistic representative work.

Scenario 96 — Student has no more major weaknesses to fix. Good. Maintain, taper and protect freshness.

Scenario 97 — Student still has several weaknesses. Choose the one with highest expected final-paper cost.

Scenario 98 — Final night contains unanswered questions. Accept residual uncertainty; the goal is not total closure.

Scenario 99 — Exam morning friend shares a new “must know” example. Do not allow it to displace the stable system.

Scenario 100 — Exam paper opens with surprise. The taper has done its job if surprise changes the content problem, not the learner’s operating process.

Fifty last-minute revision drills

Drill 1: Five-minute issue reconstruction.

Drill 2: Three mechanisms from one issue.

Drill 3: Three examples by concept.

Drill 4: One limitation per example.

Drill 5: One counter-position per issue.

Drill 6: Five unseen question rankings.

Drill 7: Three thesis calibrations.

Drill 8: One role-only plan.

Drill 9: One evidence substitution.

Drill 10: One conclusion from plan.

Drill 11: Compact passage map.

Drill 12: Three proposition paraphrases.

Drill 13: Modality audit.

Drill 14: Causality audit.

Drill 15: Inference gradient.

Drill 16: Summary target gate.

Drill 17: Summary clustering.

Drill 18: Cross-passage relationship label.

Drill 19: Context-mechanism application.

Drill 20: Bounded skip-return.

Drill 21: Ten-second reset.

Drill 22: Risk-based checking sequence.

Drill 23: Reconstruct three active risks.

Drill 24: Rewrite one risk as a cue.

Drill 25: Retire one old error.

Drill 26: Verify one volatile example.

Drill 27: Retire one redundant example.

Drill 28: Explain one example in thirty seconds.

Drill 29: Explain same example in two minutes.

Drill 30: State where example fails.

Drill 31: One unfamiliar-topic translation.

Drill 32: One abstract-term definition.

Drill 33: One comparison criterion.

Drill 34: One responsibility/capacity map.

Drill 35: One value-conflict hierarchy.

Drill 36: One timed Paper 1 half-segment.

Drill 37: One timed Paper 2 late segment.

Drill 38: One deliberate-disruption recovery.

Drill 39: One checking change-justification.

Drill 40: One stable process review.

Drill 41: Novelty-gate one new resource.

Drill 42: Reduce one note page by half.

Drill 43: Reduce one error list to three cues.

Drill 44: Reconstruct Paper 1 operating card.

Drill 45: Reconstruct Paper 2 operating card.

Drill 46: Reconstruct recovery card.

Drill 47: Reconstruct checking card.

Drill 48: Stop one low-value activity.

Drill 49: Schedule one real stopping time.

Drill 50: Explain the final plan without looking at it.

The last-minute audit: one hundred questions

• Is novelty becoming more expensive as the exam approaches?
• Is the issue bank shrinking?
• Does retrieval precede rereading?
• Are both papers maintained?
• Are only three risks active?
• Is recovery rehearsed?
• Is tapering intentional?
• Are core issues reconstructed without notes?
• Are redundant examples removed from active rotation?
• Are volatile examples verified?
• Is question-set ranking still practised?
• Is Paper 1 planning still active?
• Is Paper 2 semantic precision still active?
• Are predictions prevented from narrowing coverage?
• Is retrieval latency monitored?
• Are administrative details resolved?
• Does the final week use maintenance-first scheduling?
• Is full-mock frequency decreasing appropriately?
• Can the exam operating card be reconstructed?
• Is sleep consistency protected?
• Has the error log been compressed?
• Is confidence tied to performance evidence?
• Have major repairs mostly stopped by the final days?
• Are notes condensed?
• Are 48-hour tasks short and familiar?
• Is new resource acquisition stopped?
• Are new universal essay templates rejected?
• Are full mocks avoided when they cannot change action?
• Is peer-comparison volume ignored?
• Is the final 24-hour review light?
• Are logistics prepared?
• Is morning review familiar and short?
• Can Paper 1 wording be read before content recall?
• Can questions be shortlisted?
• Can finishability be judged?
• Can thesis be made operational?
• Can paragraph roles remain distinct?
• Can sufficient evidence be chosen?
• Can evaluation alter judgement?
• Can completion be protected?
• Are memorised introductions being avoided?
• Are memorised conclusions being avoided?
• Can Paper 2 source voice be tracked?
• Can modality be preserved?
• Can causality be preserved?
• Can summary target be identified?
• Can cross-passage relationships be named?
• Can application remain source-anchored?
• Can resistant items be bounded?
• Can late-section time be protected?
• Is mechanical synonym swapping avoided?
• Is overannotation avoided?
• Is overpolishing early answers avoided?
• Is answer changing justified?
• Is the active current-affairs bank small enough to retrieve?
• Can examples be explained with mechanism and limit?
• Is vocabulary functional?
• Are model essays used only for specific functions?
• Is the novelty gate used?
• Does each new item solve an active risk?
• Can it become reliable in time?
• What proven routine would it replace?
• Does the learner know when to stop?
• Does the learner know how to start a short session?
• Is the final plan sustainable?
• Are minimum viable concept maps available for weak domains?
• Can unfamiliarity be translated into known concepts?
• Can abstract questions be grounded?
• Can data-heavy questions be reasoned through without memorised scripts?
• Can culture questions be handled without panic?
• Can science questions be handled with uncertainty?
• Can government questions be handled with capacity and legitimacy?
• Can economics questions be handled with distribution and incentives?
• Can environment questions be handled with externalities and time horizons?
• Can media questions be handled with trust and incentives?
• Can globalisation questions be handled with resilience and sovereignty?
• Can one difficult drill be treated as a sample rather than catastrophe?
• Can one easy drill be treated as a sample rather than proof?
• Are final weaknesses ranked by expected exam cost?
• Are unresolved weaknesses contained with cues where necessary?
• Is exhaustion avoided as a performance strategy?
• Can low-concentration days use lower-demand tasks?
• Can high-confidence days avoid unnecessary testing?
• Are official requirements checked only through authoritative sources?
• Are old uncorrected scripts ignored unless relevant?
• Are historic errors prevented from crowding working memory?
• Can the learner accept residual uncertainty?
• Can the learner ignore last-minute peer panic?
• Can the learner ignore a new “must know” example?
• Can the learner expect a surprise question?
• Can the learner expect a difficult passage?
• Can the learner use procedures without emotional certainty?
• Can the learner distinguish anxiety from readiness evidence?
• Can the learner preserve both Paper 1 and Paper 2 routines?
• Can the learner use a small personal risk card?
• Can the learner stop expanding?
• Can the learner start the exam with a familiar operating system?
• Has final revision increased availability rather than merely activity?
• Has the revision system become smaller as the examination approaches?
• Would the learner still know what to do if the paper looks nothing like predictions?

Where to go next

Return to the JC2 General Paper hub. Use A-Level Exam Preparation if the runway still needs broader orchestration. Once revision is finished and the examination begins, move to the lane’s exam-day execution owner.