IB Economics examiners can tell, usually within two sentences, whether a student is engaging with a real-world case or just citing its existence. The 2026 examiner instructions for Papers 1, 2, and HL Paper 3 make this distinction explicit: responses that name a real-world event to signal topical awareness are evaluated differently from responses that use that same event as evidence inside an analytical chain. That gap—between mentioning and arguing—is now a primary differentiator between mid-band and upper-band scores, and it applies across every command term on every paper.
The difference shows in specific writing moves, not topic choice. A response that writes “the ECB raised interest rates to reduce inflation” has cited an event. An engaged response moves differently: the European Central Bank (ECB) raised its deposit facility rate to 2.25%, effective June 17, 2026, a 25-basis-point increase. In an AD/AS framework, higher policy rates raise borrowing costs, reducing interest-sensitive components of aggregate demand—durable goods consumption and business investment—and thereby easing demand-pull inflationary pressure. The critical addition is the qualifier: monetary transmission operates with significant time lags, and rate rises address demand-driven inflation more effectively than cost-push drivers, so the impact on firms carrying variable-rate debt differs materially from the impact on cash-rich exporters benefiting from any resulting exchange-rate appreciation. That qualifier—the condition that modifies the clean-theory prediction—is the writing move the 2026 cycle rewards. What it requires, though, is a case with enough specificity to generate one in the first place.
Depth Over Breadth—What Makes a Case Analytically Productive Across Syllabus Areas
Students who prepare by collecting a wide range of loosely understood cases create the illusion of coverage without building the analytical fluency that timed examination conditions actually test. Under pressure, broad lists produce citation rather than argument: the student recalls that something happened, writes it down, and expects the examiner to infer the mechanism. The examiner won’t. What determines mark-band placement is what the student does with the event, not whether they can name it.
A case belongs in the deep bank only if it passes a quick pre-selection test. Does it have a traceable mechanism—a named channel that links the event to a predicted outcome? Does it carry a condition that modifies what standard theory predicts? Does it involve an identifiable stakeholder trade-off? If any answer is no at first encounter, the case belongs on a watch list, not in the deep bank. These three questions map directly onto what the 2026 examiner instructions require: linking theory to real-world issues and using examples to support analysis and evaluation, not merely to mention them.
What makes a case analytically productive shifts meaningfully across the four syllabus areas. In microeconomics, a price intervention case without a defensible elasticity reading is difficult to deploy evaluatively. In macroeconomics, a fiscal or monetary policy case collapses into assertion without the transmission mechanism and time-lag context. In international economics, the retaliatory or terms-of-trade dynamic following a trade policy is usually where the upper-band argument lives. In development economics, the evaluative layer is the gap between aggregate outcomes and household-level distributional effects. Applying these filters when vetting a candidate case is what keeps the bank from filling up with events that can only illustrate. But even a well-chosen case will forfeit marks if it’s deployed the same way in every paper.
Deploying the Same Example Differently Across Papers 1, 2, and 3
In Paper 1, a real-world example functions as argumentative evidence: specific enough to anchor a claim, integrated into the analytical chain, and qualified where its context modifies the theoretical prediction. The IB’s open-book exam pilot for Paper 1 makes the underlying demand concrete. Participating students could bring concise summaries of real-world examples into the room—but not definitions, full analyses, or diagrams—and performance still depended on real-time analytical deployment. Having the facts in front of them didn’t help students who couldn’t argue with those facts. Students who lead with their memorized case as the primary evidence regardless of paper type consistently forfeit marks their content knowledge should have secured because Paper 2 and HL Paper 3 make a fundamentally different demand on the same material.
In Paper 2, the stimulus is the primary evidence, not the memorized case. The reliable write sequence is: identify the relevant market, country, or variable exactly as the stimulus presents it; state the mechanism or diagram; cite a specific figure or trend from the extract and explain it through that mechanism; then introduce an outside example only if it does one of two jobs—explaining why the stimulus pattern could occur or strengthening the evaluation of a likely consequence. If you cannot point to a concrete stimulus figure you are explaining, you are about to example-drop. Return to the extract first.
For HL Paper 3, the quantitative data in the stimulus is itself the real-world evidence. The sequence runs: quote the relevant numbers; compute or compare what they imply; state what that means for the economic problem; then propose and evaluate a policy whose transmission mechanism targets what the numbers show. Across both papers, one explicit link sentence anchors the analysis: “This matters because [stimulus detail] implies [mechanism], so [claim or policy] is more or less likely to hold.” Without that explicit link, the analysis and the stimulus data exist in parallel—and examiners are practiced at noticing when students never quite connect them.
A Step-by-Step Protocol for Building Your Deep Example Bank
Four stages build the bank: Select, Record, Deploy, and Verify. Select a case only after confirming it crosses at least two syllabus areas and passes the pre-selection filters from the previous section. Record it using a five-field template—statistic or quantifiable outcome, policy context, exam-style deployment sentence, evaluation angle, and diagram link—a recording structure used in The Finance Chronicles’ IB Economics Real-World Examples Bank, which is built explicitly around deployability over coverage. The July 2026 U.S. Section 338 tariff action on Canada shows what a fully filled record looks like. Statistic: 50% additional duties on nearly $20 billion in imports, effective within 30 days. Policy context: a unilateral U.S. trade measure targeting Canadian goods in vehicles, alcohol, and dairy, framed as a response to alleged discriminatory treatment of U.S. exports. Exam-style sentence: “The U.S. imposed a 50% Section 338 tariff on nearly $20 billion of Canadian goods in July 2026, raising the domestic price of affected imports and reducing import volume via the price effect, as shown in a tariff welfare diagram.” Evaluation angles: retaliation risk, incidence elasticities determining how much of the tariff falls on domestic consumers versus Canadian exporters, and supplier-switching capacity within the 30-day implementation window. Diagram link: a standard tariff and welfare diagram, with terms-of-trade analysis available for the HL evaluation layer. Once recorded, drill the same case under rotating command terms—explain, evaluate, discuss—to build the cross-question flexibility real exam conditions require. Then test whether the case can qualify a theoretical prediction rather than merely illustrate one. The 90-second drill below is how that test runs in practice.
- Setup (30s): Write the case in one line plus one citable parameter—rate, percentage, dollar value, or date. If you cannot produce a number immediately, the record is not exam-ready.
- Chain (45s): Write a three-link chain—event → named mechanism (name the channel) → predicted outcome—and label the diagram or framework you would use.
- Engagement (15s): Add one qualifier that could weaken or modify the prediction—an elasticity condition, time lag, retaliation risk, or stakeholder constraint.
- Decision: If all three elements above are complete within 90 seconds, treat the case as exam-ready. If you stall at the event level, make two targeted fix attempts—add the missing element or rewrite the chain. If the case is still weak afterward, remove it from the bank and replace it.
That pass/fail outcome is what determines which cases survive the revision cycle—and building a bank where they consistently pass is exactly what the six-week plan below is designed to do.
A Six-Week Consolidation Plan
Weeks one and two: select eight to twelve cases across all four syllabus areas using the per-area filters—more cases at this stage defeat the purpose. Weeks three and four: record each using the five-field template and begin timed Paper 1 drills across rotating command terms. Weeks five and six: practice the same cases in Paper 2 stimulus-subordinated mode and, for HL students, Paper 3 data-as-evidence mode; replace any case that cannot adapt across question types. Eight to twelve is a deliberately tight ceiling—enough to cover the syllabus, but not so many that the depth discipline erodes into the same wide, thin coverage students started with.
Throughout, run a 15-minute weekly scan and capture at most two candidates, each with one concrete parameter and a one-line mechanism link; everything else is set aside. A candidate enters the deep bank only after passing the pre-selection filters from Section 2 with all five template fields fillable in one sitting. Monthly, remove any case that no longer generates a qualifier or repeatedly fails the 90-second drill. Keep the bank capped at eight to twelve—depth over breadth is the operating principle, not a one-time selection decision—with any addition requiring one deletion unless it clearly covers a syllabus area or mechanism you currently lack.
Turning Deep Examples into Exam Marks
Fluency with real-world examples isn’t measured by how many a student can name—it’s measured by how few they need and how hard each one works. A compact bank of eight to twelve deeply recorded cases, each able to generate a qualifying condition under timed conditions, is what converts analysis and evaluation marks from inconsistent to reliable. Start with one case: apply the per-area filter, fill all five template fields, and run the 90-second drill. If it passes, it’s not just an example you know—it’s an argument you can make.
