\n| Polish<\/td>\n | Maximise marks under exam conditions<\/td>\n | Quick reference sheets and checklists<\/td>\n | Timed past-paper runs and full-mark reviews<\/td>\n | Timed papers, markscheme comparison, examiner language drills<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\nHow to design notes that actually serve practice<\/h3>\nNotes should not be a passive archive. Design them so they directly aid questionbank practice and exam output.<\/p>\n \n- Make them answer-focused:<\/strong> For each major topic keep a 1\u2013page problem-to-answer map: common question stems, key points to include, command terms, and one strong model sentence for the introduction\/conclusion.<\/li>\n
- Embed mark-scheme language:<\/strong> Use the terms examiners use. If the markscheme rewards \u201canalysis\u201d or \u201cevaluation,\u201d write a 2-line prompt in your notes about what constitutes analysis in that topic.<\/li>\n
- Create micro-model answers:<\/strong> For typical 6\u20138 mark questions, write one compact model answer (80\u2013150 words) in your notes. When practising, compare your answer against your model.<\/li>\n
- Use layered condensation:<\/strong> Keep three layers: full notes (for deep study), condensed notes (one A4 page per topic), and quick swipe cards for last-minute checks. Each layer serves a distinct purpose when you move between Build and Polish.<\/li>\n
- Tag by syllabus objective:<\/strong> Mark which IB assessment criteria each note targets (knowledge, application, evaluation, experimentation). This helps choose questionbank sets that test the right skills.<\/li>\n<\/ul>\n
How to use questionbanks strategically (not randomly)<\/h3>\nRandomly doing questions is one of the most common wastes of time. Use a deliberate loop: pick \u2192 attempt \u2192 mark \u2192 reflect \u2192 update notes \u2192 retest.<\/p>\n \n- Pick with intention:<\/strong> Choose questions that map to the exact learning objective you want to check. Use your notes\u2019 tags to select targeted practice.<\/li>\n
- Attempt first, then refer:<\/strong> Attempt a question without looking at notes if it\u2019s an application test. Only refer to notes if you\u2019re completely stuck; the goal is retrieval and application.<\/li>\n
- Use the markscheme as a coach:<\/strong> Mark your answer against the official criteria. Translate marks into concrete actions\u2014if you lose marks on reasoning, add a prompt to your notes that scaffolds argument steps.<\/li>\n
- Keep an error log:<\/strong> Record the exact reason for lost marks and a short plan to fix it. Over time, trends will appear and tell you where to focus revision.<\/li>\n
- Retest smartly:<\/strong> After updating notes, retake similar questions. Spaced repetition applies to mistakes as much as facts.<\/li>\n<\/ul>\n
Sample weekly rhythm: balancing both without burnout<\/h3>\nHere\u2019s a compact weekly pattern that balances note upkeep and focused question practice. Use it, adapt it, and calibrate the intensity depending on where you are in the revision timeline.<\/p>\n \n\n\n| Day<\/th>\n | Main Focus<\/th>\n | Notes<\/th>\n | Questionbank<\/th>\n | Time<\/th>\n<\/tr>\n<\/thead>\n | \n\n| Monday<\/td>\n | Concept deep-dive<\/td>\n | Rework one topic sheet<\/td>\n | 1\u20132 short concept questions<\/td>\n | 60\u201390 min<\/td>\n<\/tr>\n | \n| Wednesday<\/td>\n | Application practice<\/td>\n | Annotate notes with model answers<\/td>\n | 3\u20134 untimed questions; reflection<\/td>\n | 90\u2013120 min<\/td>\n<\/tr>\n | \n| Friday<\/td>\n | Timed conditioning<\/td>\n | Create a one-page checklist<\/td>\n | Timed section practice<\/td>\n | 60\u201390 min<\/td>\n<\/tr>\n | \n| Weekend<\/td>\n | Review and retention<\/td>\n | Flashcard session, spaced recall<\/td>\n | Retest past mistakes<\/td>\n | Variable<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\nSubject-specific tweaks (because IB subjects are different beasts)<\/h3>\nEvery subject asks different things. The combination of notes and questionbanks must be tailored.<\/p>\n \n- Maths & Further Maths:<\/strong> Notes should be procedural cheat-sheets\u2014key formulas, common substitutions, and worked exemplars. Use questionbanks to practice technique until it\u2019s automatic; time your solutions and log typical time per question.<\/li>\n
- Sciences (Physics, Chemistry, Biology):<\/strong> Keep diagrams, units, and experimental setups front and center. Use questionbanks to connect theory to data interpretation and experiment-based questions. Write short \u2018if-then\u2019 prompts in your notes: if this data pattern appears, what does it imply?<\/li>\n
- Humanities (History, Geography, Economics):<\/strong> Build scrap-books of evidence\u2014dates, quotes, case studies\u2014tagged to topics. Practice writing structured paragraphs to command terms (compare, assess, evaluate) and use questionbanks to time essay planning and execution.<\/li>\n
- Languages & Literature:<\/strong> Notes should include character maps, thematic threads, and short textual analyses. Use questionbanks to practise unseen analysis and oral prompts; apply note-tagged model phrases for commentary.<\/li>\n
- TOK & EE:<\/strong> Notes are your argument skeletons and theory maps. Use questionbanks or past prompts to practise building tight, source-aware argument chains; have one page of critique moves ready in your notes.<\/li>\n<\/ul>\n
Tracking progress: the metrics that actually tell you something<\/h3>\nGood tracking lets you move from vague \u201cI studied a lot\u201d to concrete \u201cI improved my evaluation clarity by X.\u201d Focus on a few meaningful metrics.<\/p>\n \n- Accuracy by question type:<\/strong> Percentage correct on definitions, data-response, longer essays, or problem-solving questions.<\/li>\n
- Time per mark:<\/strong> Measuring time spent per mark earned helps you spot slow areas.<\/li>\n
- Repeat-failure rate:<\/strong> How often does an error reappear after correction?<\/li>\n
- Model-alignment score:<\/strong> Subjectively rate how closely your answers match model answers on content and structure (0\u20135).<\/li>\n<\/ul>\n
\n\n\n| Metric<\/th>\n | How to track<\/th>\n | What to change if low<\/th>\n<\/tr>\n<\/thead>\n | \n\n| Accuracy by type<\/td>\n | Spreadsheet by question category<\/td>\n | Targeted practice; update notes with missing links<\/td>\n<\/tr>\n | \n| Time per mark<\/td>\n | Stopwatch + mark tallies<\/td>\n | Practice speed drills; simplify steps<\/td>\n<\/tr>\n | \n| Repeat-failure rate<\/td>\n | Error log with retest dates<\/td>\n | Rethink underlying misconception; seek feedback<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n | | |
<\/p>\n
<\/p>\n