MUN Head Delegate Guide: Leading a School Delegation

Head delegate is the only senior role in school Model UN with no handbook. Chairs get training, faculty advisors get a job description, and the head delegate gets a title and a group chat of twenty people who need answers. The job is a real one: you decide who goes, who gets which country, what preparation looks like, and whether the delegation behaves like a team or like twenty individuals in the same blazers.

What the role actually is#

Strip away the variations and the head delegate does four things: selects and assigns, runs preparation, holds the team together at the conference, and hands the whole system to a successor. Everything else is negotiable with your faculty advisor, and it should be negotiated explicitly rather than discovered in week six.

Agree that table in your first meeting of the year and write it down. The two rows that matter most are the last two: anything involving money, safeguarding or a student's wellbeing goes to the adult, immediately, every time, without you trying to solve it first. Our faculty advisor guide is worth reading even though it is not written for you, because it tells you what your advisor is carrying.

Selecting the delegation#

Selection is where head delegates lose friends, and almost always because the criteria arrived after the decision. Publish them first.

Three rules make the process defensible. Assess more than one thing: a delegation built only on speaking confidence is a delegation of people who cannot draft. Use two assessors, because one person's impression of a nervous first-timer is noise. And assess in a committee rather than an interview, since the job is to perform in a committee.

Then decide in advance how you are balancing two things that genuinely conflict: sending the strongest possible team, and developing people who will be the strongest team next year. Most delegations solve this by reserving a fixed number of places for delegates below a certain year group or with fewer than a set number of conferences, and saying so upfront. That converts an argument about fairness into a published rule.

Telling people no

Do it individually, in person, before the list is published, and with one specific thing to work on. Never by seeing their name missing from a group message. Say what the gap was, say what would close it, and name the next opportunity to try. A delegate told "your research was the strongest in the room but you did not speak in the second session, so work on getting on the speakers list early" usually comes back. A delegate told nothing usually leaves the club.

Distributing countries and committees#

You will receive an allocation from the conference: a country or a set of countries, and a number of seats in named committees. Distributing them inside the team is your highest-leverage decision of the year.

• Put experience where the room is hardest. Security Council, crisis and specialised agencies punish inexperience. General Assembly committees with large rooms are the right place for a first conference.
• Match interest where you can. A delegate who wanted the health committee prepares more.
• Pair deliberately. In double delegations, pair an experienced delegate with a newer one rather than two of either.
• Spread the delegation across committees unless the conference requires otherwise, so the team has eyes everywhere and nobody sits in a room alone all weekend by accident.
• Watch the hard countries. A delegate given a country with an unpopular position needs more support, not less, and should know that going in.

Publish assignments with a one-line reason each. It takes twenty minutes and removes the entire "why did they get UNSC" conversation.

Running preparation#

Preparation fails in the same way every year: everybody intends to start six weeks out and actually starts four days out. The fix is deadlines with a person attached, not a schedule on a wall.

The mock committee is the part most delegations skip and the part that changes results most. Run it with real procedure, a real speakers list and real timers, chair it strictly, and stop it twice to explain what just happened. Delegates do not learn procedure from a document; they learn it by losing a vote to a motion they did not understand. You can run one from a laptop with a free practice session, with the speakers list, motions and timers live on every phone in the room, which takes the administration out of it and lets you concentrate on chairing.

Do not personally review twenty position papers. Pair delegates to review each other against a checklist, then read the ones flagged as weak. Our position paper guide works well as that checklist, and it keeps the standard consistent when three different people are marking.

The head delegate at the conference#

You have two jobs at once: your own committee and everybody else's. Accept upfront that the second one costs you something in the first, and decide in advance how much.

• Be the first point of contact for problems that are not welfare or money. A lost badge, a confusing rule, a delegate who cannot find their room.
• Know where everyone is. A single sheet: name, committee, room number, country, phone number.
• Be visible between sessions. Most of the value you add is in three-minute conversations in corridors.
• Do not walk into other committees to check on people. It undermines them with their chair and their room.
• Never negotiate with a chair on a delegate's behalf. If something is genuinely wrong, it goes to the faculty advisor, who goes to the secretariat.

The daily rhythm

Three fixed points, short, every day, is more effective than one long meeting.

• Morning brief, ten minutes. What today looks like, what each person is trying to achieve today, one reminder. Not a speech.
• Lunch check-in, informal. Sit with different people each day. Ask what is stuck rather than how it is going.
• Evening debrief, twenty minutes. Each delegate says one thing that worked, one thing that did not, and what they will do tomorrow. You say almost nothing.

The evening debrief is the highest-value twenty minutes of the weekend. It surfaces the delegate who has not spoken all day, it spreads tactics between committees, and it turns twenty separate conferences into one delegation.

Supporting a delegate who is struggling#

There is always one, usually by the second session, and the temptation is to do it for them. Do not write their clauses, do not brief their bloc, and do not tell them what to say.

Instead, diagnose. Struggling almost always means one of four things, and the response is different for each.

• They cannot get on the speakers list. Mechanical, and the easiest to fix. Tell them to put their placard up the moment the list opens, and to send the dais a note rather than waiting to be noticed.
• They are speaking but nobody is listening. Usually no specific proposal. Give them one sentence to end every speech with: "my delegation proposes X, and we are drafting it now, come and find us".
• They are not in a bloc. The hardest to fix from outside. Tell them to find the person writing the most and offer to write a section, which is how blocs actually form.
• They are overwhelmed. Not a tactics problem. Shrink the goal to one thing for the next session and tell them the rest of the weekend is off the table.

The delegation's reputation#

Chairs talk to each other, and secretariats remember schools. A delegation is remembered for two things: whether it is easy to deal with, and whether its delegates are decent to the smaller delegations in the room.

Set three standards and enforce them yourself. Arrive on time to every session, including the one after lunch. Be courteous to chairs even when a ruling goes against you, and take disagreements to the advisor rather than the dais. And treat first-time delegates from other schools as people to bring into your bloc rather than as an obstacle, which is both decent and, since chairs are watching, effective.

Delegation awards, which are won by consistency#

Most conferences tally delegation awards from individual honours, so the arithmetic rewards spread rather than peaks. One Best Delegate and eleven delegates with nothing loses to zero Best Delegates and six Honourable Mentions at almost every conference that publishes a formula.

What follows from that is unglamorous and true: the way to win a delegation award is to raise the bottom of your team, not the top. Your weakest four delegates are worth more of your preparation time than your strongest two, who will be fine. Check the conference's published formula, and if it divides by delegation size, send a smaller and better-prepared team.

Conflict inside the team#

This is the part that ends friendships, and it is nearly always one of three situations.

• Two delegates in one committee competing rather than cooperating. Usually a double delegation or two seats in the same room. Assign roles explicitly before the conference: one leads on drafting, one leads on the floor, and they share credit.
• A delegate who thinks they should have had a better assignment. Answer once, with the published reason, and then do not reopen it.
• Someone not doing the preparation everyone else did. The only one with a real deadline: address it privately at the four-week mark, and if nothing changes, tell your advisor before travel is booked rather than after.

What makes all three worse is handling them in the group chat. Have the conversation in person, alone, and confirm what you agreed in a message afterwards so there is a record.

Handover, and the document that makes it survivable#

Most school delegations rebuild themselves from nothing every year because everything lived in one person's head. Spend one afternoon in your final term writing it down.

• The conference list: which ones you attend, when applications open, what they cost, who to email
• Selection criteria and the trial format, with the scoring grid
• The preparation timeline, as a calendar with deadlines
• Templates: position paper, country profile, opening speech, mock committee plan
• The last three years of assignments and results, so patterns are visible
• What went wrong, honestly, and what you would do differently
• Logins, shared drives and the group chat, transferred properly

Then name your successor early and give them real work before they take over: let them run one preparation session, one selection trial and one conference brief while you are still there to catch the mistakes. Deciding the succession in the last week produces a head delegate who learns everything you learned, in the same order, at the same cost.

Your own performance, honestly#

It will suffer, and you should decide by how much before the conference rather than resenting it afterwards. Two approaches work. Either accept a quieter conference, take a general assembly committee rather than a crisis seat, and treat the delegation as your event. Or protect your own committee, delegate the daily rhythm to a deputy, and be explicit with the team that the deputy is the first point of contact.

What does not work is pretending you can do both at full intensity. That is the head delegate who misses their own committee's drafting window at eleven on Saturday morning because somebody could not find the lunch hall, and who is then irritable with a team that has no idea why. Pick one, say which, and let people plan around it. If you are still choosing which conferences your delegation should aim at this year, the conference directory is a reasonable place to start comparing dates, sizes and fees before you take a shortlist to your advisor.