How to Write a Working Paper MUN: A Delegate's Guide

Do not index

You're probably in the exact moment when working papers start to feel more stressful than speeches. Committee has opened, blocs are forming, people are tossing around half-finished ideas, and someone just said, “Let's start a paper,” as if everyone is supposed to know what that means.

Many first-time delegates fall into one of two bad habits. They either treat the working paper like a mini essay, or they treat it like a rushed list of buzzwords. Neither works. A strong working paper is not a school assignment. It's not a speech on paper. It's a negotiation tool.

If you want to learn how to write a working paper MUN delegates will support, start with that idea. Your paper's job is to make other people say yes. Yes to your framing of the issue. Yes to your clauses. Yes to adding their country's name next to yours. The delegates who understand that early usually end up steering committee.

Understanding the Working Paper's Strategic Role

The moment a bloc says, "Let's get this on paper," the room changes. Ideas that sounded good in an unmoderated caucus suddenly have to survive scrutiny, amendments, and rival blocs trying to pull your supporters away. That is why a working paper matters. It is the first document that turns talk into bargaining power.

A working paper is a preliminary draft delegates use to collect, test, and refine proposals before they become a formal resolution. Conference guides describe it as a rough document meant for debate, amendment, and lobbying rather than a finished text, as outlined in this working paper format guide.

Good delegates treat the working paper as a political tool. It helps set the terms of debate, show potential allies what they are signing onto, and give undecided delegates something concrete to compare against competing ideas. A paper that is easy to read and easy to support usually gains sponsors faster than a paper with smarter ideas buried in messy drafting.

What the working paper is doing in committee

In committee, the working paper does more than record your bloc's ideas. It gives other delegates a fast way to answer three questions. What problem are you prioritizing? What action are you proposing? Is joining your paper politically safe for my country?

That last question gets ignored by first-timers. It should not. Delegates rarely support a paper because the writing sounds impressive. They support papers that are clear enough to defend in caucus, flexible enough to amend, and aligned enough with national policy that they can explain their support without getting trapped later.

I tell new delegates to judge every draft by one standard: does this document lower the effort required for someone to join us? If a potential sponsor needs a two-minute verbal explanation to understand clause one, the paper is still doing too little work for your bloc.

If you want a clearer sense of where this document sits in the process, this guide to working paper vs draft resolution in MUN breaks down the difference.

Why the structure looks familiar

Working papers usually follow a recognizable diplomatic structure because that structure helps a room full of delegates process proposals quickly. Chairs can review it faster. Other blocs can spot overlap faster. Potential sponsors can see where they agree, where they need edits, and whether your group understands how committee decisions are usually framed.

The standard layout is simple:

Header with the committee, topic, and sponsors or authors

Preambulatory clauses that frame the issue and establish shared context

Operative clauses that set out proposed action

Even at conferences with loose formatting rules, this structure gives you an advantage. It separates consensus-building language from actionable policy. It also makes mergers easier. When two blocs combine papers, they need to see which background points match and which operative ideas can be folded together without rewriting everything from scratch.

What each part should accomplish

The header looks administrative, but it carries political weight. Names on the page signal ownership, momentum, and seriousness. A paper with credible sponsors attracts attention faster than a document floating around without clear backing.

The preambulatory clauses create a foundation other delegates can accept before they commit to your solutions. Use common phrases such as Bearing in mind, Recalling, or Taking into account to establish context, prior action, and shared concerns. Done well, this section widens your coalition by giving skeptical delegates language they can agree to even if they still want to negotiate the operative section.

The operative clauses decide whether your paper has influence or not. They show what your bloc wants the committee to do, who is expected to act, and how ambitious your proposal really is. Weak operative clauses force you to sell the idea over and over in speeches. Clear ones let the document sell itself.

That is the strategic role of the working paper. It is the first proof that your bloc can turn preferences into policy and policy into support. Delegates who understand that early usually stop drafting for appearance and start drafting for votes.

Drafting Clauses with Purpose and Impact

You finally get your bloc around a laptop, everyone agrees on the problem, and then the draft stalls on lines like “promotes cooperation” and “improves access.” That is the moment many first-time delegates lose momentum. Other blocs can't tell what your paper would do, so they keep shopping for a clearer draft.

Strong clauses give people something they can support, amend, and defend in caucus. They turn a general political preference into a negotiable plan.

Build each clause around implementation

A clause earns support when another delegate can answer a few practical questions without guessing:

Who is expected to act?

What action are they taking?

When does it begin, or how is it phased?

How is it delivered, funded, or monitored?

Why is this approach likely to help?

That checklist matters because a working paper is a negotiation tool, not a wish list. If your wording leaves all the hard choices unstated, your bloc has to explain the same idea in every speech and every unmoderated caucus. Clear drafting saves political energy.

Compare these two versions.

Weak clause

Improve access to education in underserved areas.

Stronger clause

Requests that the relevant UN body coordinate with member states to expand school access in underserved areas through teacher training, local infrastructure support, and periodic reporting, with implementation adapted to national capacity.

The second version is stronger because it gives other delegates several entry points. A finance-focused delegation can ask about cost. A sovereignty-focused delegation can focus on national adaptation. A delegate who likes the idea but wants oversight can propose tighter reporting language. That is useful friction. It helps you build a coalition around real text instead of around vague intentions.

Keep the main action clear, then use subclauses to manage detail

Many first drafts fail in one of two ways. The paper says almost nothing, so nobody sees a reason to sign on. Or it tries to settle every detail at once, which makes the text hard to read and even harder to merge with another bloc's paper.

The better approach is simple. Write a main operative clause that states the policy action in one clean sentence. Then use subclauses for administration, funding, eligibility, review, and timelines.

That structure helps in negotiations because delegates rarely object to every part of a proposal. They object to one cost line, one reporting burden, one timeline, or one actor. If those pieces sit in subclauses, you can trade them without giving up the whole clause.

If your paper proposes a training initiative, other delegates will ask who runs it, who pays for it, who qualifies, and how results are assessed. If your draft cannot answer those questions, it is still at the idea stage.

A related drafting skill is setting up context cleanly before the committee reaches the action. This guide to writing effective preambulatory clauses is useful if your background language keeps spilling into your operative section.

Here's a quick walkthrough that shows the drafting mindset in action:

What strong drafters do differently

Strong drafters choose a lane.

They do not try to solve the entire agenda in one paper. They pick a manageable intervention, develop it far enough that other delegates can picture implementation, and leave enough flexibility for amendments. That balance is where influence sits. If your draft is too thin, it gets ignored. If it is too rigid, it gets isolated.

Use this test before you circulate a clause:

Name the actor. Someone must be responsible for carrying it out.

Name the action. “Support” or “address” is rarely specific enough.

Name the mechanism. State whether this happens through a program, partnership, reporting system, fund, or review process.

Check committee authority. The idea has to fit the mandate of the body you are simulating.

Leave negotiating room. Allies need places to contribute language without rewriting the clause from scratch.

That is how clauses start pulling votes instead of just filling space. A good working paper gives delegates language they can adopt, defend, and improve together.

Mastering Diplomatic Language and Formatting

A working paper often wins or loses support before anyone challenges the policy. A delegate skims the page during an unmoderated caucus, sees blunt wording, inconsistent structure, or a wall of text, and decides your bloc will be hard to work with. That reaction matters. In committee, style signals whether you understand process and whether your paper is safe to sponsor.

Diplomatic writing is a negotiation tool. Good phrasing keeps doors open, protects coalition space, and makes it easier for hesitant delegates to say yes without looking like they abandoned their policy line.

Match the language to the job of the clause

Preambulatory and operative clauses serve different strategic purposes. Preambulatory language frames the issue in terms other delegates can accept. Operative language proposes action in terms they can defend.

Here is the practical distinction:

Preambulatory Phrases (Context and Framing)	Operative Phrases (Action and Direction)
Recalling	Requests
Recognizing	Encourages
Deeply concerned by	Recommends
Noting with concern	Urges
Acknowledging	Decides
Affirming	Calls upon

Choose the opener based on political effect, not habit. “Recalling” ties your idea to prior agreement. “Acknowledging” gives room to recognize different national situations. “Encourages” is easier to sell than “demands” when state cooperation is voluntary. “Requests” works well when you are tasking a UN body rather than trying to order member states around.

That choice can decide whether a clause gets amended, merged, or ignored.

Formatting affects how easily people can negotiate your paper

Delegates need to reference your text quickly. Chairs need to read it without cleaning up your structure. Sponsors need to point to specific language and suggest changes under time pressure. Clean formatting helps all three.

Working papers usually follow the same basic logic as draft resolutions: clear clause separation, standard diplomatic phrasing, and an obvious distinction between background framing and proposed action. That convention exists for a reason. It makes debate faster and amendments easier.

Use formatting that helps people work with your paper:

Number operative clauses so delegates can cite them in caucus and during amendments.

Break clauses clearly instead of hiding multiple ideas in one paragraph.

Use consistent capitalization for clause starters, institutions, and formal program names.

Keep each clause focused on one decision before adding subclauses.

Use subclauses only when they add implementation detail, not when they pile on extra ideas.

I tell first-time delegates to treat formatting as coalition maintenance. If another sponsor can say, “We support clause 3 but want to revise subclause a,” your paper is doing its job.

Strong diplomatic phrasing sounds cooperative and controlled

Weak phrasing usually fails in familiar ways. It overstates, stays vague, or tries to sound important by using more words than the idea can carry.

Weak

Demands that all countries immediately fix the issue.

Supports better cooperation on the matter.

Tries to improve awareness and strengthen systems worldwide.

Stronger

Encourages member states to expand information-sharing through existing regional mechanisms.

Requests the relevant body to develop guidance in consultation with member states.

Recommends targeted support for states facing implementation barriers.

Notice what changed. The stronger version names a realistic actor, uses language other delegates can defend, and leaves room for negotiation. That is how you write a clause people can sponsor without taking unnecessary political risk.

One more habit helps. Read every operative clause aloud and ask, “Would my assigned country realistically sign onto this wording?” If the answer is no, revise the tone before someone else forces the revision for you.

If your writing still feels stiff, study short-form policy writing outside committee as well. This article on how to write a policy brief sharpens the same skill: saying enough to persuade without saying so much that the reader loses the thread. For research habits that support cleaner legal and institutional phrasing, see TheLawGPT's guide to legal research.

Building Credibility with Research and Evidence

You feel the pressure in unmoderated caucus when a delegate scans your clause, looks up, and asks, “What body would do this?” or “Has the UN tried anything like it before?” If you cannot answer in one sentence, your paper loses ground fast.

Research matters because it gives your proposal political cover. Delegates do not support text only because it sounds smart. They support text they can defend to their bloc, their sponsors, and the dais.

The strongest working papers usually rest on three kinds of support: an institution with a real mandate, a precedent that shows the committee is not inventing authority from scratch, and facts that explain why the problem deserves action now. That mix makes your draft easier to negotiate because other delegates can see the logic behind it.

What to research before you draft

Start with the mechanism, not the wording. Before drafting any clause, confirm who could carry it out and under what authority. A paper becomes much more persuasive when each idea already has a home inside the UN system or another recognized framework.

Focus your prep on a short list:

Relevant UN bodies, agencies, or offices that could realistically implement the proposal

Past resolutions, treaties, or agreed language that show precedent or accepted framing

Your country's position and likely allies' positions so you do not draft yourself into isolation

A few solid facts or examples that establish urgency, scale, or feasibility

This is the trade-off new delegates often miss. More research is not always better. Useful research helps you defend a clause in debate and negotiation. Decorative research just fills notes you will never use.

How much evidence belongs in the paper

Keep the paper readable. Put most of the detail in your speaking notes.

A working paper is a negotiation document, so the text itself should stay clean. One well-chosen reference to an existing framework can reassure cautious delegates. One factual premise can justify why a clause belongs on the agenda. Ten facts packed into one paragraph usually slow readers down and weaken your pitch.

Use attachments, charts, or visuals only if your conference allows them and only if they make a complicated point easier to grasp. If they create more explanation work, skip them.

If you need a better method for tracing treaties, legal texts, and prior authority, TheLawGPT's guide to legal research is useful for building the habit of citing specific sources instead of making broad claims from memory.

How to use evidence without slowing the draft down

The best delegates separate drafting from proof. The clause stays short. The backup sits in a notebook, a Google Doc, or a marked-up background guide.

That gives you room to lobby well. If someone questions your proposal, you can point to a past resolution, a relevant office, or a country statement without stuffing all of that into the paper itself. That is how research becomes influence. It helps other delegates trust that joining your text will not embarrass them later.

Be careful with precision. If you cannot support a detailed claim, do not force one into the draft. Broad but accurate language is usually safer than a specific claim that another delegate can knock down in thirty seconds.

For a clean model on source placement and attribution, see this guide on how to cite sources in a policy brief.

One practical note. If you are gathering background quickly, Model Diplomat can help generate sourced answers to political and diplomatic questions for student prep. That can save time when you are trying to identify the right institution, prior action, or policy framing before caucus starts.

The Art of Collaboration and Sponsorship

You finish a draft during unmoderated caucus, feel good about the wording, then look up and realize nobody else is attached to it. At that point, the paper is not a bloc document. It is still your notes.

A working paper matters because it gives other delegates something they can join, revise, defend, and trade around. The delegates who shape committee are rarely the ones with the prettiest draft. They are the ones who turn a draft into a coalition. That usually means keeping the paper focused enough that another delegate can read it quickly and decide, "Yes, my bloc can live with this."

A shorter paper usually gets support faster for a simple reason. Delegates need to understand what they are backing before they put their country name near it. If your text tries to solve every problem on the agenda at once, you force potential sponsors to accept weak clauses just to keep the good ones. A paper built around a few clear policy moves gives people room to negotiate without losing the plot.

Support is earned in conversation

Good drafting helps. Clear lobbying gets signatures.

You need a pitch that another delegate can repeat to their bloc in under thirty seconds. It should cover three things. What problem the paper is solving, why the mechanism is politically realistic, and which countries gain something by joining it. If you cannot explain those points cleanly, your support will stay shallow and disappear the moment someone asks a hard question.

The same basic logic shows up outside committee rooms. In partnership work, people back proposals that show fit, clarity, and a practical ask. That is why this guide for creators on finding sponsorships makes a useful comparison. Support follows proposals that make the value obvious.

If you want a sharper sense of how these conversations play out in caucus, read this breakdown of what lobbying in MUN looks like.

Sponsors, signatories, and who is actually with you

Treat sponsors and signatories differently. A sponsor is helping carry the paper. A signatory may only want the topic discussed. First-time delegates often count both groups together and assume they have a stable bloc. Then the room shifts, amendments start flying, and half that support turns out to be soft.

Ask directly what kind of support a delegate is offering. Do they want to help write? Will they speak for the paper in formal debate? Or do they just want to keep the option open? Those are different political commitments, and your strategy should change with each one.

A few habits make a real difference in caucus:

Lead with your strongest operative idea first.

Ask for one concrete edit instead of a vague reaction.

Trade wording where you can, but protect the mechanism that makes the clause work.

Keep notes on who proposed each change and who objected.

Confirm support again after major edits.

That last point matters more than new delegates expect. A delegate who backed version one may not back version three.

How to collaborate without giving your paper away

Collaboration is not the same as accepting every suggestion. A paper gets stronger when other delegates can see their fingerprints on it, but it gets weaker when you accept changes that pull it in three directions at once.

The standard I use is simple. If an edit broadens support without damaging the policy logic, take it. If it only adds names while making the clause harder to defend, reject it politely. You are not collecting signatures for decoration. You are building a text your bloc can still explain under pressure.

Many first-time delegates frequently lose control. They concede the clause that gave the paper identity because they want one more sponsor. Then they are left with a document everyone helped write and nobody wants to defend.

Mergers are political decisions, not drafting exercises

Merging papers is normal. In many committees, it is the only way a serious text survives. The question is not whether to merge. The question is whether the merged paper still makes strategic sense.

Before you agree, test the other bloc on three points:

Are you defining the problem the same way?

Do the main clauses work together as one policy line?

Will your current supporters still defend the merged version in speech?

If the answer is yes, merge and do it quickly. If the answer is no, keep negotiating or walk away. A bloated compromise can collect names and still fail on the floor because nobody can explain what it is trying to do.

The strongest delegates understand this trade-off early. They do not treat sponsorship as a popularity contest. They use the working paper to gather aligned countries around a plan they can pass.

Final Polish A Pre-Submission Checklist

By the time your paper is almost ready, most errors are no longer about ideas. They're about preventable sloppiness. A mistyped clause starter, a funding mechanism nobody explained, an institutional role assigned to the wrong body, a paragraph so dense nobody wants to read it.

This final review should be fast but ruthless. Read your paper like a skeptical delegate from another bloc.

The checklist that catches most problems

Use this before you hand anything to the dais or circulate it for names:

Formatting correct? Check header details, clause numbering, spacing, and any conference-specific rules.

Grammar and spelling clean? Errors make serious ideas look unserious.

Clause clarity tested? Every clause should survive the question, “What does this require?”

Institutional fit checked? Make sure the body named in the clause could plausibly do the action proposed.

Delegation stance aligned? Your paper should still sound like your assigned country, not your personal opinion.

Coalition-ready language used? Remove phrasing that sounds needlessly absolute, moralizing, or politically careless.

Two final tests worth doing aloud

First, read each operative clause out loud. If you run out of breath or lose the sentence halfway through, the clause is too bulky.

Second, ask a blocmate to summarize your paper after one read. If they can't explain your main proposal clearly, the issue is usually structure, not intelligence.

That's the standard to aim for. A good working paper gives your committee something to organize around. It reflects your research, your diplomacy, and your judgment about what other delegates will support. If you learn to treat it as a strategic tool rather than a formatting task, you'll write better papers and build stronger blocs.

And that's the heart of how to write a working paper MUN chairs respect and delegates rally behind.

If you want help turning research into usable MUN writing, Model Diplomat is built for exactly that kind of prep. Students can use it to get sourced answers on political topics, sharpen country-position research, and draft more credible papers, memos, and resolutions before committee starts.