How to read an ESS SL Paper 2 extended-response mark scheme without copying its phrasing
IB ESS SL Paper 2 Section B essay architecture: 4 answer frames, a word-budget by band, and the stakeholder versus actor line that decides a 5 from a 7.
IB Environmental Systems and Societies at Standard Level is often sold as the Diploma Programme subject where thoughtful writing can rescue weaker data work. The opposite is closer to the truth on Paper 2. Section B extended-response questions are marked against a level descriptors grid, and that grid is unforgiving about structure. Most candidates lose marks not because their content is wrong, but because their essay architecture does not let the examiner find the descriptors on the page. This article is a senior-tutor walk-through of how to build an ESS SL Paper 2 Section B answer that survives a tired examiner at 4:30 pm on a marking day. The goal is to give IB candidates preparing for ESS a working architecture they can apply to almost any Section B prompt, plus a word-budget by band and a checklist of the descriptive drift that quietly caps a response at band 3.
How Paper 2 Section B is actually marked in IB ESS
Before a single essay framework is sketched, the marking logic of IB ESS SL Paper 2 Section B deserves a slow read. Extended-response questions carry the highest mark weight on the paper, and the mark scheme is structured around level descriptors rather than tick points. An examiner reads your response once for the descriptor that best matches the totality of your answer, then assigns a band. The bands run from 1 to 4 within the question's available mark range, and the top band demands an answer that is relevant, focused, well structured, and supported by specific evidence drawn from the case material, the syllabus, or a candidate's own background reading.
Three marking realities tend to surprise candidates. First, content accuracy is necessary but not sufficient; the rubric allocates marks for the quality of reasoning, the use of appropriate terminology, and the structure of the response, not just for correct facts. Second, generic statements about sustainability, ecosystems, or pollution almost never move a response up a band. Markers are trained to spot and discount language that could be lifted into any question. Third, partial understanding presented in a structured way usually outscores complete understanding presented in a tangle. For most candidates reading this, the biggest single gain available in Section B is not a new piece of knowledge but a cleaner architecture.
The implication is practical. A good ESS SL Section B answer is built in two passes. The first pass is design: a skeleton of claims, each tied to evidence, arranged in a sequence the marker can scan. The second pass is writing: filling the skeleton with terminology-precise prose, no waffle, and explicit signposting of where the answer is moving. Candidates who skip the design pass and write linearly tend to run out of time before they reach the most rewarding band descriptor, which is the one that rewards synthesis across concepts.
The four essay architectures that hold up under marking pressure
Across several years of marking and teaching ESS SL, four Section B essay architectures have proved durable. They are not the only shapes that work, but each one resolves a common architectural problem.
1. The claim-evidence-evaluator pattern
This is the safest default. The response makes a series of explicit claims in topic sentences, each followed by a paragraph of evidence drawn from the case study, the syllabus, or wider reading, and closes with a paragraph that explicitly evaluates the strength of the claim. It is a strong fit for questions that ask candidates to discuss the extent to which a strategy is effective, or whether a particular environmental approach is sustainable. The architecture forces the candidate to commit to a position early, and the evaluation paragraph is the natural place to deploy the level-4 descriptors that reward reflection.
2. The stakeholder matrix essay
Some Section B questions are fundamentally about the social side of an environmental issue. For those, a stakeholder matrix built into the essay works better than a single argumentative spine. The candidate identifies three to four stakeholders, names their interest in the issue, sketches their power relative to the issue, and assesses the legitimacy of their claim. This architecture fits questions about resource management conflicts, urban air quality, fisheries policy, or protected-area disputes. The trap to avoid is treating the stakeholder essay as a list of paragraphs. A matrix only scores a top band if the candidate compares stakeholders explicitly and reaches a synthesised conclusion about how the issue should be managed.
3. The systems-loop essay
ESS is taught as a systems subject, and the rubric explicitly rewards systems thinking. A systems-loop architecture draws a feedback loop in words: identify the inputs, the flows, the stores, and the outputs of the system in question, then describe the feedback mechanisms that govern its behaviour. It is the right architecture for questions on nutrient cycling, climate systems, population dynamics, or energy flow through a community. The candidate should commit to a labelled loop early in the response, then refer back to specific nodes of the loop when making evaluative points. The architectural risk is that the loop becomes a decorative diagram, so the candidate must integrate the loop into the prose rather than parking it in a corner.
4. The values-framework essay
A small number of Section B prompts ask candidates to weigh environmental, social, and economic values explicitly. For those, a values-framework essay is the strongest fit. The candidate names a value or a set of values at stake, defines the value in operational terms, then applies it to the case at hand, and closes with a justified judgement about how the values should be traded off. The architecture is the same shape as a TOK essay, and IB candidates often under-use it. It scores well on Section B because the rubric's top band descriptors reward sustained ethical and values-based reasoning combined with subject-specific content. Candidates who reach for it without specific environmental content will plateau at band 3, so the architecture must be filled with the relevant case data.
Word-budget by band: how long a 7 actually is
Candidates tend to overestimate how long a band-4 ESS SL Section B response needs to be. The mark scheme is designed to reward concision, not volume. A typical 10-mark extended-response question can reach the top band inside 350 to 500 words, assuming the architecture above is in use. The level descriptors do not contain a word count; they contain a quality threshold, and a tightly argued 380-word response will outscore a padded 750-word response every time the descriptor is applied.
The word-budget heuristic that holds up well in marking rooms is this. For a 10-mark Section B extended-response question, plan on roughly 60 to 80 words of claim and signposting, three body paragraphs of 80 to 110 words each, and a closing evaluative paragraph of 60 to 90 words. The total sits inside 400 to 500 words. Going past 550 words is a strong signal that the response has lost architecture. Going under 300 words is a strong signal that the candidate has not earned the higher band because the rubric needs at least three pieces of evidence and a synthesis to credit the top two descriptors.
For a 15-mark Section B question, scale the same architecture upward. Plan on four to five body paragraphs of 80 to 110 words each, plus a slightly longer closing evaluative paragraph. Most strong 15-mark responses land in the 550 to 700-word range. For a 20-mark Section B, plan on five to six body paragraphs plus a synthesis and a closing evaluation, and expect to write 700 to 900 words. In every case, the marker is not counting words; they are reading for the descriptors. The word-budget exists so the candidate's architecture fits the available mark range and so time can be budgeted across the paper.
Common pitfalls and how to avoid them
ESS SL Section B pitfalls cluster into a small number of architectural failure modes. Recognising them in advance is the difference between a 5 and a 7.
- Drift into description. The candidate narrates the case study or the syllabus topic instead of answering the question. The marker discounts descriptive accuracy that does not advance a claim. Counter-move: write a topic sentence in the form of a claim, not a statement of fact.
- Stakeholder blur. A stakeholder essay is written as four independent paragraphs about four different groups. The marker cannot see how the candidate is comparing them. Counter-move: build an explicit comparison sentence at the end of each stakeholder paragraph, then summarise the comparison in the closing synthesis.
- Generic sustainability language. Phrases such as 'we need to protect the environment for future generations' do not move the descriptor. Counter-move: replace each generic sentence with a specific operational claim tied to the case study or to a measurable sustainability principle from the syllabus.
- Systems diagram as decoration. A feedback loop is drawn and then never referenced in the prose. Counter-move: write the response so that each body paragraph refers to a labelled node in the loop by name.
- Values essay without content. A values-framework response is written at a TOK-essay altitude with no environmental content. Counter-move: name the value, then apply it to a specific decision, policy, or trade-off drawn from the case material.
- Forgetting the command term. Discuss, evaluate, to what extent, and examine are not interchangeable. Counter-move: in the planning stage, restate the command term in the candidate's own words and check that the architecture answers that restatement.
- Last-paragraph surprise. The candidate introduces a new claim in the closing paragraph. Markers treat this as a sign that the response was not planned. Counter-move: state the closing-paragraph claim at the end of the introduction so the marker knows where the response is heading.
The stakeholder versus actor line that quietly decides a band
In ESS, the words stakeholder and actor are used close together, but they are not the same. A stakeholder is anyone with a stake in the outcome of an environmental decision: a community, a species, a sector of the economy, a future generation, an ecosystem service. An actor is a stakeholder with the capacity to act on the system: a national government, a multinational company, a local NGO, an international body. The distinction is not decorative. Markers read for it. A response that treats all stakeholders as actors will over-attribute agency to passive groups and under-attribute it to the bodies that actually shape the system. The result is a stakeholder analysis that sounds inclusive but fails to explain how the system moves.
The architectural fix is to build two short lists during planning. The first list names the stakeholders relevant to the question. The second list names the actors, and for each actor notes their power, their legitimacy, and their urgency with respect to the issue. The essay then compares actors against stakeholders to make a single precise claim about who is shaping the system and who is being shaped by it. In my experience this usually separates a band 4 from a band 6 in a single paragraph. The marker recognises the conceptual move and credits it under the descriptors for analysis.
How to plan Section B inside the exam room
The planning pass is where most candidates under-invest. A Section B plan should take no more than 6 to 8 minutes for a 10-mark question, and no more than 10 minutes for a 20-mark question. The plan needs only three things: a one-sentence claim, a list of three to five pieces of evidence, and a closing evaluative sentence. Everything else is architecture chosen to fit the claim. ESS candidates who plan only the claim, or only the evidence, usually have to rewrite the response mid-flow and lose coherence markers as a result.
A simple four-line planning template works well. Line 1 states the claim as a thesis sentence. Line 2 names the architecture chosen from the four above. Line 3 lists the evidence, tagged to the source (case, syllabus, wider reading). Line 4 writes the closing evaluative sentence. Once those four lines are on the page, writing is a mechanical task of filling the architecture with content. Candidates who skip the template and try to plan in their head tend to run out of time at the closing evaluative paragraph, which is the single most under-written paragraph in the average ESS SL Paper 2 response.
Comparing the four architectures at a glance
The table below summarises when each architecture is the right choice, and the kind of command term it tends to answer. Use it as a triage tool in the first minute of reading a Section B prompt.
| Architecture | Best fit for command terms | Best fit for question type | Common failure mode |
|---|---|---|---|
| Claim-evidence-evaluator | Discuss, evaluate, examine | Strategy effectiveness, sustainability of an approach | Claims are too general, evidence is descriptive |
| Stakeholder matrix | Discuss, to what extent | Resource conflict, policy dispute, management strategy | Four unconnected stakeholder paragraphs |
| Systems loop | Explain, discuss | Cycling, energy flow, climate, population dynamics | Loop drawn once and never referenced |
| Values framework | Examine, evaluate, discuss | Trade-offs between environment, society, economy | TOK-style altitude with no ESS content |
Why an ESS SL Paper 2 revision plan should be built on architectures, not topics
The final piece of the architecture argument concerns revision, not exam technique. Most IB candidates preparing for ESS SL revise by topic list. They work through ecosystems, then pollution, then resources, then conservation, and so on. This builds content knowledge but does not build the architectural reflexes that Section B is actually scored on. A stronger revision plan is built on the four architectures above. The candidate picks a recent paper, identifies which architecture each Section B question is testing, and practises the architecture against content they already know. Over a 12-week revision window, this produces a student who can pick up any Section B prompt and reach for a working architecture inside the first 90 seconds of reading time.
The plan that holds up best in practice is a 12-week cycle with three architectures per four-week block. Each block starts with a worked example of the architecture from a real mark scheme, then a timed practice against an unseen Section B question, then a personal critique in which the candidate marks their own response against the level descriptors. The candidate repeats this for all four architectures. The result by week 12 is a portfolio of four reusable essay templates, each with the evidence slots pre-filled, and a personal error pattern that the candidate can hand to a tutor. IB Courses' ESS SL Paper 2 preparation programme builds this portfolio with each student, then drills it against the mark scheme until the architecture is automatic.
None of this replaces content knowledge. The architecture is the vessel; the case study, the syllabus content, and the wider reading are the cargo. But in a marking room, the vessel is what the examiner can see. A response that arrives in a clean architecture with specific content outscores a response that arrives as a well-stocked bag of facts and no spine. For most candidates preparing for IB ESS SL, the difference between a band 4 and a band 6 is not what they know, it is how they have arranged it on the page.
Conclusion and next steps
IB ESS SL Paper 2 Section B is a writing paper disguised as a science paper. The mark scheme rewards architectural discipline, terminological precision, and the use of specific evidence over volume. Candidates preparing for ESS should pick one of the four essay architectures above, practise it on a real Section B prompt under timed conditions, and mark their own response against the level descriptors until the architecture becomes reflex. The next step for any candidate serious about a band 6 or a 7 is to build a portfolio of worked Section B responses, one per architecture, and to mark each against the published level descriptors.