Append a real-world example to the end of a finished paragraph and it does no evaluative work — the argument is already closed, and evidence that arrives after the conclusion can’t test anything. This is the problem behind the mark plateaus that catch many IB Economics students: the theory is clear, the diagrams are correct, and then a vague case appears at the close of the response like a box that needed ticking.
Formulations like ‘a developing country’ or ‘a government might subsidize X’ give examiners nothing concrete to compare against. They’re too generic to count as real application. In practice, precise, named, verifiable cases push answers into the higher bands — because the examiner can see you testing a model against an actual outcome rather than restating it. Knowing that precision matters is one thing. Building it into a paragraph while the analysis is still in motion is where most scripts fall short.
Evidence as Analytical Instrument, Not Decoration
Two paragraph patterns show up in exam scripts, and the difference in marks between them is larger than it should be. In the bolt-on pattern, the model is fully developed, a conclusion is reached, and only then does a loose example follow: ‘in a country, the government might impose a tax.’ The evidence can’t influence the reasoning because the reasoning is already finished. In the analytical-input pattern, you name a place, time frame, policy or event, and an outcome while you’re still developing the argument, then ask whether that outcome fits the model’s prediction and why. A practitioner guide to the IB Economics Internal Assessment captures the same distinction: high-scoring work applies theory explicitly to real-world material, using correct terminology to build analysis and evaluation rather than narrating what happened.
- Model claim: state the model’s prediction clearly in one sentence — direction and channel — such as ‘contractionary monetary policy should reduce inflation by lowering aggregate demand.’
- Case payload: in one sentence, name the place, time frame, specific instrument or event, and one outcome metric you will use as your test.
- Mechanism link: in one sentence, explain which part of the model the case is operating through — for example, interest rates affecting investment, or an indirect tax shifting supply.
- Gap or fit explanation: in one sentence, say why the observed outcome matches or diverges from the prediction, using a single tight reason such as time lags, a supply shock, low elasticity, expectations, or a policy constraint.
- Evaluation hinge: close the sequence with a sentence stating the condition under which the model would be more or less accurate, or the trade-off the case reveals.
Three decision rules keep this from expanding into a mini-article:
- If you can’t name the place and time frame and recall at least one concrete outcome metric, don’t use that case.
- Use one main metric; add a second only when the question explicitly asks you to weigh trade-offs.
- Get the case payload into the paragraph before the evaluative hinge; evidence that appears only at the end will read as bolt-on.
That five-step structure takes roughly the same time whether you’re reaching for a case you built last week or improvising one mid-exam — which is exactly why the bank you build during the course is worth more than it looks.
Building Your Evidence Bank
A usable evidence bank is built from notes small enough to recall and deploy in about 30 seconds. Each note should fit into five short lines: the country or region; the month or quarter and year; the economic mechanism in syllabus terms, such as cost-push inflation or a negative production externality; the named policy instrument or event located in time; and one clear outcome metric you can cite, optionally tagged with one or two topic labels. The discipline is the five-line cap: you’re building deployable inputs, not mini-essays. If it takes longer than one sentence to use, it won’t survive the exam. The IB Economics HL Revision real-world example bank takes the same position — concise, named, mechanism-focused notes, not ‘in many countries’ summaries.
Consider what this looks like with a recent macro case. A note on U.S. inflation in April–May 2026 would record the country (United States), the time frame (April–May 2026), the mechanism (inflationary pressure with a strong energy component — qualifying any simple aggregate-demand-only explanation), the named policy instrument (the Federal Reserve holding the federal funds target range at 3.5–3.75 percent as of late April 2026), and one concrete metric as the test (CPI up 0.5 percent month on month in May, 4.2 percent year on year, with the energy index up 3.9 percent on the month and 23.5 percent over the year). Turned into an analytical-input sentence, that becomes: ‘In the U.S. in April–May 2026, despite the Fed holding the policy rate at 3.5–3.75 percent, CPI inflation rose to 4.2 percent year on year and energy prices surged — showing how cost-push shocks and time lags can keep inflation elevated even after demand-side policy has tightened.’ One note. One sentence. One evaluative move.
When you read economics news, scan for this pattern — mechanism, named instrument or event, concrete outcome metric — then decide whether the case earns a five-line note under the relevant topic tags. Two or three cases per major topic cluster, understood in depth, will almost always outperform a longer list you can barely reconstruct under pressure. When you have several options, run a quick filter: keep only cases where you can state place, time frame, instrument or event, and one metric without hand-waving; prefer cases that create a real test against the model rather than simply confirming its prediction; and make sure the mechanism links clearly to the syllabus point being examined, not just to something that was interesting in the news. If two cases still survive, pick the one you can compress into a single analytical-input sentence — because that’s what actually survives timed writing.
Deploying Evidence Under Exam Conditions
In Paper 2, the extracts hand you real-world material. The examiner wants you to identify the mechanisms in that data, apply theory, and then qualify or judge the model against what actually happened — not paraphrase the passage. Adding one well-chosen case of your own can sharpen evaluation, but keep it tightly linked and within the response limits. In Paper 1 and Paper 3, where there are no extracts to lean on, two or three well-analyzed cases almost always outperform a scattered list. Confirm all four precision criteria are met from memory. Then run the five-step sequence so the case payload arrives before — and drives — your evaluative hinge.
Anxiety about whether your examples are ‘good enough’ is usually misplaced. Examiners aren’t awarding marks for how famous the case is; they’re rewarding the precision and relevance of the link between the case and the model. A small, well-understood policy change you can describe specifically is far safer than a headline-grabbing event you can only gesture at. In the exam, if a case can’t pass the precision criteria from memory, switch to another note. The gap that actually costs marks isn’t knowing which case to reach for — it’s being unable to compress it into one tight analytical sentence when the clock is running.
Weekly Preparation for Evidence-Bank Building
Building a strong evidence bank doesn’t have to compete with topic study. Schedule one or two short reading sessions a week — half an hour is enough — skimming accessible economics sources for cases that match whatever unit you’re currently covering. For at least one item per session, spend five to ten minutes converting it into a five-line note under the relevant topic tags. Timing matters more than volume: capturing a case while the underlying theory is still fresh tends to lock the mechanism in. Then, about once a month, run a quick health check on a sample of notes to confirm they’re still short, precise, and deployable in a single sentence; the lightweight framework below keeps the collection exam-usable rather than letting it quietly accumulate into something too long to use.
- Once a month, pick 6 notes at random from your bank — roughly 2 micro, 2 macro, and 2 international or development.
- Length test: if a note runs over five lines, trim it to only what you can deploy in one tight sentence under exam pressure.
- Action rule: immediately refresh or repair 2 of the sampled notes, and retire any note you can’t make deployable within about 2 minutes.
- Long-run aim: track the growth of your ‘solid’ set — notes that pass both recall and precision tests — not your total note count.
Turning Your Evidence Bank into Exam Performance
Once this workflow is in place, you stop hoping that a few half-remembered stories will surface under pressure and instead walk into the exam with a small, indexed set of analytical instruments for every major topic. Each note is a precision instrument, not a memory aid — and the moment it enters an exam response, the examiner has to engage with your argument rather than step around it.
