How to Read a Background Guide
Background guides are your roadmap to committee. Learn how to extract maximum value, spot what's missing, and turn the guide into an actionable research plan.
Anatomy of a Background Guide
A background guide (BG) is the document your committee's dais writes to frame the topics you'll debate. Most guides follow a predictable structure: a letter from the chair, a committee overview, and then one or two topic sections, each with historical context, current situation, key issues, questions to consider, and a bibliography.
Here's the critical insight most delegates miss: the background guide is not neutral. It's written by your chairs, who are college students with their own perspectives, biases, and research limitations. The BG tells you what the dais thinks is important — but it doesn't tell you everything, and it doesn't tell you what your specific country thinks.
The best delegates use the BG as a starting point, not an endpoint. They read it once quickly to get the lay of the land, then read it again slowly with a pen, marking three things: facts to verify, gaps to fill, and clues about what the chairs care about.
Facts to verify: Background guides sometimes contain errors — misattributed quotes, outdated statistics, or oversimplified histories. When HMUN 2024's DISEC guide stated that the Arms Trade Treaty had 113 states parties, the actual number was 112. Small? Yes. But a delegate who caught this and cited the correct figure signaled to the dais that they'd gone beyond the guide.
Gaps to fill: What's conspicuously absent? If a guide on climate change doesn't mention loss and damage financing, that's a gap you can fill with your own research — and potentially build your entire resolution around.
