How to Write a Model United Nations Background Guide for Committee Chairs

A delegate opens a pack and finds a twelve-page study guide that reads like a Wikipedia summary. Every person in the room has read the same document. Their opening speeches repeat the same three facts. The committee never reaches a differentiated debate because no one has been given a reason to hold a distinct position. That is the cost of a weak background guide. A guide that works gives participants enough policy detail to write distinct position papers, but not so much that it homogenises the committee into a single informed consensus. The distinction between a topic summary and a substantive research brief is the first thing to grasp. It determines whether participants arrive with competing positions or a shared script.

A topic summary tells the reader what the issue is. A substantive research brief tells the reader what has been done about it, who has taken which side, and what the unresolved policy questions are. A shallow guide covers the history of the issue, lists a few UN resolutions, and ends with a paragraph of guiding questions. A deep guide provides a policy landscape: past UN action with resolution numbers and voting records, bloc positions with named countries, and a citation standard that lets every claim be traced back to primary UN documentation. Writing a deep guide does half the research for the participants. That is the trade-off. A deep guide reduces the research burden and ensures a baseline of factual accuracy across the room. It also narrows the range of positions anyone can credibly take. A shallow guide forces participants to find their own sources. That produces more varied positions but also more factual errors and weaker policy arguments. Decide which outcome serves the committee's purpose.

Start With The Committee Mandate

Begin with the committee mandate. Every UN body has a jurisdiction defined by its founding resolution or charter document. A General Assembly committee cannot authorise peacekeeping troop deployments; the Security Council has that power. A WHO committee cannot set trade policy; that belongs to the WTO. State the committee's mandate in the first section of the guide. Participants who do not know what their body can and cannot do will write resolutions that must be ruled out of order. The mandate also determines which bloc positions are relevant. An ECOSOC committee debating development financing will hear from the G77, the OECD bloc, and the BRICS grouping. A Security Council committee debating the same topic will hear from the P5 and the elected members, and the veto power changes everything about how blocs form. State the mandate, cite the governing document, and move on.

Write A Policy Narrative, Not A Summary

The topic history section must cover the origin of the issue, the major turning points, and the current state of play. Do not write a Wikipedia summary. Write a narrative that explains why the issue is on the UN agenda now and what previous attempts at resolution have failed or succeeded. Include specific UN resolution numbers, the vote tallies, and which countries were the main sponsors. This is where the citation standard begins to matter. Every claim about past UN action must be traceable to a UN document reference. A participant who wants to argue that a resolution was weakly enforced should be able to find the exact text and check the enforcement language. Omitting the reference forces a hunt for it, which wastes time and produces lower-quality work.

A guide that works has six mandatory sections. Each serves a specific function in the preparation cycle.

• Committee Mandate: The governing document that defines the body's jurisdiction, membership, and powers. Cite the relevant UN Charter articles or founding resolution. This section tells participants what their committee can and cannot do, which prevents resolutions that violate the committee's authority.
• Topic History: The origin, evolution, and current state of the issue. Include specific dates, key events, and the actors involved. Keep this section focused on the policy problem, not on general background.
• Past UN Action: Every relevant UN resolution, treaty, or programme of action, with full document references and vote records. This is the section that distinguishes a substantive research brief from a topic summary. Anyone who reads this section should know what has already been tried and why it did or did not work.
• Bloc Positions: The stated positions of major country groupings, regional blocs, and individual key states. Name the countries that lead each bloc and the policy rationale behind their stance. This section gives participants the raw material for coalition-building before they arrive.
• Guiding Questions: Three to five questions that force policy choices. Not "What should be done about X?" but "Should funding be directed to prevention or enforcement?" A good guiding question has no obvious right answer and splits the room.
• Citation Standard: The required format for citing sources in position papers and during debate. Specify whether the conference uses Chicago, APA, or a custom format. Require that every factual claim in a position paper be supported by a UN document reference. This standard is not optional; it is what lets claims be traced back to primary sources.

Use The UN Digital Library

Go straight to the primary UN documentation system. The UN Digital Library is the single source for General Assembly, Security Council, and ECOSOC resolutions. The UN Treaty Collection holds international agreements. The UN Statistics Division provides data for economic and social topics. Relying on news articles or secondary academic sources produces a topic summary, not a substantive research brief. Pulling resolution texts, vote records, and Secretary-General reports produces a guide that participants can build on.

Align With The Conference Rules

Consult the conference's own rules of procedure document to ensure the guide is consistent with the procedural framework. Writing for a THIMUN conference means structuring the guide around the lobbying and merger process, because participants need to know which blocs will be negotiating over a single resolution. Writing for a Harvard-style conference means structuring the guide around caucus topics and competing resolutions, because participants need to know which sub-issues will be debated in separate moderated caucuses. The rules of procedure summary in the pack should align with the guide's structure. Participants must see how the research connects to the procedural tools they will use.

Structure The Document

The standard length is 8 to 15 pages of substantive content, not including the rules summary and position paper prompt. Open with the committee mandate and topic summary. Follow with the topic history and past UN action, then bloc positions and guiding questions. Put the citation standard at the end, after the guiding questions, so that participants read it immediately before they start writing. Keep the position paper prompt as a separate document or a clearly marked appendix. Anyone who has to dig through fifteen pages to find the submission deadline and format requirements will miss both.

State The Preparation Expectation

State the pre-conference preparation expectation explicitly. If participants should read two UN resolutions, a Secretary-General report, and three academic articles before arriving, say so in the guide. If they should arrive with a draft position paper ready for peer review, say that too. The research burden is a function of the guide's depth. A deep guide with full citations and bloc analysis reduces the burden to verification and synthesis. A shallow guide forces everyone to find everything from scratch. Be honest about which approach the guide takes. People who underestimate the research burden arrive underprepared and the committee suffers.

Guiding questions are the most underused section in most background guides. Vague questions produce vague position papers. A question like "What should the international community do about climate change?" produces a paragraph of generalities. A question like "Should the Green Climate Fund be restructured to require co-financing from recipient states, and what is the position of your assigned country on this condition?" forces research into a specific policy mechanism and a stance on it. Mirror the structure of the position paper prompt in the guiding questions. If the position paper requires sections on Topic Background, Past International Action, Country Policy, and Proposed Solutions, then the guiding questions should map to those sections. A question about country policy should ask the participant to reconcile their assigned country's stated position with the bloc positions described in the guide. That is where differentiated positions emerge.

The position paper prompt must include the submission deadline, the required length, the required sections, and the citation standard. State whether the position paper is required for award eligibility. Many conferences disqualify people who miss the deadline. Read every position paper submitted. At large conferences, the practical reality is that papers get skimmed the night before or during the first session. To take position papers seriously, build time into the pre-conference schedule to read them, or reduce the committee size so that reading every paper is feasible. If you cannot read the papers, do not weight them heavily in awards. A gap between stated criteria and actual practice damages the credibility of the awards process.

The citation standard is not a bureaucratic formality. It is the mechanism that prevents unsupported factual claims during debate. Someone who states that "the Security Council has repeatedly failed to act on this issue" must be able to cite the specific resolutions that were vetoed and the vote tallies. Without that requirement, the statement is rhetoric, not evidence. Enforcing the citation standard in position papers and during formal debate raises the quality of every argument in the room.

The standard should require that every factual claim in a position paper be supported by a UN document reference. Secondary sources such as news articles and academic journals are acceptable for context and analysis, but the primary claim must trace back to a UN resolution, treaty, Secretary-General report, or official statement. Provide a sample citation in the guide, formatted according to the conference's required style. Anyone who cannot find a UN document to support a claim should not make the claim.

The bloc positions section is where the background guide becomes a strategic tool. People who read this section before the conference arrive knowing which countries will be their natural allies and which will be their opponents. Describe the major blocs relevant to the topic, the countries that lead each bloc, and the policy rationale behind their stance. For a topic on disarmament, the blocs might include the Nuclear Non-Proliferation Treaty states, the non-signatory states, the NATO bloc, and the Non-Aligned Movement. For a topic on development financing, the blocs might include the G77, the OECD donors, the BRICS grouping, and the Small Island Developing States.

Do not list every country in each bloc. Name the leading countries, the policy rationale, and the key points of disagreement between blocs. Someone representing a small country within a bloc should be able to infer their stance from the bloc's stated position and their country's known foreign policy priorities. Someone representing a country that sits between blocs, such as India in climate negotiations, needs to know which bloc they are likely to join and what policy trade-offs that choice involves. The bloc positions section should make these strategic decisions visible before the first unmoderated caucus begins.

The past UN action section is the most research-intensive part of the guide. Identify every relevant UN resolution, treaty, programme of action, and Secretary-General report. List them with full document references. Explain what each one achieved or failed to achieve. This section is what distinguishes a substantive research brief from a topic summary. Anyone who reads this section should know that the issue has been debated before, that resolutions have been passed, and that implementation has been weak for specific reasons. Knowing those reasons means writing a position paper that addresses the implementation gap rather than proposing a solution that has already been tried and failed.

Include the vote tallies for each resolution. A resolution that passed unanimously is different from one that passed with fifty abstentions and ten votes against. The vote tallies tell the reader which countries opposed the resolution and why. That information is the raw material for bloc analysis and coalition-building. Omitting the vote tallies hides the political landscape. The committee will spend the first session rediscovering what the guide could have provided.

The most common failure is writing a document that is too long and too general. Chairs who are experts on the topic want to include everything they know. The result is a forty-page guide that nobody can finish reading before the conference. The guide should be long enough to cover the six required sections but short enough to read in two hours. Cut every sentence that does not serve the ability to write a position paper or negotiate a resolution. If you cannot edit your own writing, ask a colleague to review the guide and cut anything that is not essential.

The second most common failure is writing a guide that presents the chair's own policy preferences as neutral fact. A background guide is not a policy paper. It should present the range of positions on the issue, including positions the chair disagrees with, and let the participants make their own arguments. A guide that clearly favours one policy outcome will pressure people to adopt that stance, which undermines the simulation. The chair's job is to provide the research base, not to steer the committee toward a preferred result.

Writing a background guide suits the chair who wants to control the quality of debate in their committee and who is willing to invest the research time to produce a substantive research brief rather than a topic summary. It suits the conference organiser who wants a consistent standard of preparation across all committees and who is willing to enforce a citation standard and a guide length limit. It does not suit the chair who expects participants to do all the research themselves and who wants to write a short guide that covers only the basics. A shallow guide in a competitive circuit produces people who rely on Wikipedia and who repeat the same three facts in every speech. That committee will not produce differentiated debate. The chair will spend the weekend refereeing procedural disputes instead of managing substantive discussion.