MUN Closing Ceremony: How to Run Awards Without a Controversy

Almost every complaint a secretariat receives about awards arrives in the last ninety minutes of the conference, and almost none of them are really about the last ninety minutes. They are about a policy that was never written down, a quota a chair invented on the morning of the final session, or a delegation tally nobody could explain. The ceremony is where the decisions become visible. The work that makes it uncontroversial happens weeks earlier.

Decide the award policy before you need it#

Write the policy when you write the rules of procedure, not on the last morning. A usable policy fits on one page and answers six questions.

• Which categories exist, and are they the same in every committee?
• How many of each are given per committee, and is that a maximum or a fixed number?
• Does a position paper award exist, who judges it, and against what? A judging rubric helps here.
• Are there delegation awards, and exactly how are they calculated?
• Who ratifies a committee slate, and what can they change?
• What happens when two chairs on one dais disagree?

Publish it to chairs when you appoint them and to faculty advisors when registration opens. An advisor who knows in advance that your conference gives no Honourable Mentions in crisis committees will not send you an email about it on Sunday afternoon.

Categories and quotas per committee#

The conventional ladder is Best Delegate, Outstanding Delegate, Honourable Mention and Verbal Commendation, usually with Best Position Paper alongside. Our guide to MUN award categories explains each one. What varies, and what you must fix, is how many of each a committee of a given size may give.

These are the bands most school and university conferences settle on. Pick one row per committee size and put it in the policy: the point is that every chair reads the same number.

Two decisions matter more than the exact figures. First, whether a quota is a ceiling or a requirement. A ceiling lets a chair give fewer awards in a committee that genuinely had fewer strong delegates, which is honest but produces awkward comparisons between rooms. A requirement produces consistency and occasionally an award nobody earned. Most conferences use a ceiling for Verbal Commendation and a requirement for the top three. Second, whether double delegations count as one recipient. Decide it once. A double delegation that wins Best Delegate and receives one certificate between two students is a memorable way to spoil an afternoon.

Collecting slates from chairs#

Set the deadline before the ceremony, not at it. A slate that arrives while the hall is filling cannot be checked, and an unchecked slate is how the same school ends up with Best Delegate in six committees.

Ask for exactly four fields per recipient and nothing else: the award, the delegation, the delegate name as they want it read aloud, and one line of evidence. The evidence line is the part that does the work. It gives you something to say when a faculty advisor asks why, it forces a chair to think past their favourite speaker, and it takes fifteen seconds to write.

Good evidence lines are specific: "wrote and defended operative clauses 4 to 7 of the passed resolution, and brokered the merger of the two working papers on day two". Bad ones are adjectives: "excellent throughout". Tell chairs that in the briefing and show them one of each.

Ask the dais to bring the record with them, not their memory. A committee that ran on paper has a speakers list and a sheet of notes. A committee that ran on software has the speaking log already. Our own guide to how Best Delegate is chosen covers the delegate side of the same question, and it is worth sending to chairs too: they judge better when they know what delegates have been told.

Ratification: what the secretariat actually checks#

Ratification is not a second judging round. You were not in the room. You are checking four things, and you should be able to do all four for a committee in about two minutes.

• Quota compliance. The slate matches the policy for that committee size.
• Conflicts of interest. No chair has awarded their own school, their own club, or a delegate they coached. Ask chairs to declare conflicts when they are appointed, and keep the list.
• Concentration across the conference. Not fairness within a committee, which is the chair's call, but a pattern across all of them.
• Names and spellings. Against the registration list, not against the chair's handwriting.

There are only two good reasons to send a slate back. The first is a policy breach: too many awards, a missing category, an undeclared conflict. The second is an evidence line that does not support the award it is attached to, which in practice means a chair who has awarded on impression alone and will usually correct it themselves once asked. Send it back with the specific problem named and a deadline in minutes. Never send a slate back because you would have chosen differently.

Delegation awards, and publishing the formula first#

Delegation awards cause more disputes than individual ones because the arithmetic is invisible. Fix that by publishing the formula in the same document as the policy, before anyone competes for it.

Then state the two rules that decide what the table actually rewards. Rule one: is the total raw, or divided by the number of delegates the school sent? Raw totals reward large delegations, which is defensible if you say so. An average rewards small ones and produces a winner with three students and two awards. Many conferences split the difference with a minimum delegation size to be eligible for the top delegation award, and a separate award for small delegations. Rule two: ties. Decide the tiebreak in advance, usually the greater number of Best Delegate awards, then Outstanding, then a shared award.

Keep the tally on one sheet as the slates are ratified, not at the end. Fourteen slates entered as they arrive takes no extra time. Fourteen slates entered at once, while the hall waits, is where the arithmetic error happens.

Certificates without a crisis#

Four hundred certificates is a printing problem, not a design problem. Solve it in this order.

1. Print participation certificates in advance, unnamed or mail-merged from the registration list, and distribute them through faculty advisors during the last session. They do not belong on stage.
2. Print award certificates blank, with the category preprinted if your design allows it, and fill names by hand on good paper with a real pen. Handwriting a name looks deliberate. A misspelled laser print looks careless.
3. Hold back ten blanks per category. You will need them.
4. Check spellings against registration, never against the slate form, and never against what a chair heard someone called all weekend.

If you are mail-merging, merge from the same registration export you used for badges, so a name is wrong in both places or right in both places. Two different spellings of one delegate's name across a badge and a certificate is the version of this mistake people photograph.

A run of show that takes 45 minutes#

Ceremonies run long for three reasons: speeches that were not timed, an announcement order nobody rehearsed, and photographs taken one recipient at a time. All three are fixable. The ceremony is one part of conference day operations, and it runs on the same discipline.

Twenty-six minutes for fourteen committees is under two minutes each, which is enough for four to six names if, and only if, the chair reads and does not speak. Give every dais the same script and mean it.

No preamble about how hard this committee was to judge. No thanking the delegates from the stage. If a dais wants to say something to their room, they say it in the room, at the end of the last session, where it means more anyway.

Announcement order, and the small things that make it an occasion#

Announce upward within a committee, from Verbal Commendation to Best Delegate. Announce committees in a fixed order that you publish on the screen, so a delegation knows roughly when to pay attention and nobody spends forty minutes at maximum alertness.

Read the delegation before the name: "the delegate of Brazil, Amara Okoye". In committee they were a country, and that is the thing they will remember being. Have recipients come forward as a group per committee rather than one at a time, receive the certificate, then stand together for one photograph. A photographer taking fourteen group shots finishes in the run time. A photographer taking a hundred and twenty individual shots does not.

Pronounce the names. Ask chairs to write a phonetic spelling on the slate form for any name they are unsure of, and have whoever reads it practise before the doors open. It takes five minutes and it is the difference between recognition and embarrassment.

When an award is disputed#

It will happen at least once, usually from a faculty advisor, usually within ten minutes of the ceremony ending, and usually in the corridor. Decide the handling in advance so whoever is standing there does not improvise.

• Never relitigate on the spot, and never in public. Take the name, the committee and the complaint.
• One named person handles all of them. Usually the academics lead, not the SG, who is still on stage duty.
• Say what the process was, not what the judgement was. "The dais submitted a slate with written evidence, the secretariat checked it against the published policy and for conflicts of interest, and the dais decision stands."
• Offer feedback instead of review. Most advisors are asking for feedback for their delegate and phrasing it as a dispute. Offer a written note from the dais within a week and the temperature drops immediately.
• Reverse only for a factual error. A miscounted quota, a wrong name, an undeclared conflict. Never because the complaint was loud.

The one thing that ends a dispute faster than anything else is evidence you can quote back. That is the real reason to insist on evidence lines: not bureaucracy, but the ability to say what a delegate actually did.

After the ceremony#

Publish the full results within twenty-four hours, on the conference page, with committee, category and delegation. Advisors need it for their school newsletters, delegates need it for their applications, and a result that exists only in a photograph of a certificate stops existing the moment the certificate is lost.

Send each delegate their own record: which committee, which country, which award if any, and the dais feedback if you promised it. A delegate can cite a published result years later when they are writing a personal statement, or listing MUN on their CV. A paper certificate in a box under a bed cannot be cited by anybody, which is why the conferences that publish properly get mentioned by name in applications and the ones that do not, do not. Our director's guide covers the rest of the post-conference wrap-up, and the conference planning guide places the award policy in the wider timeline.

Finally, debrief the chairs while it is fresh. Ask two questions: did the quota fit your committee, and was the slate form quick to fill in? Both answers change next year's policy, and both are forgotten within a fortnight.

If you want somewhere to practise the record-keeping side of this before your own conference, you can open a free practice session and run a mock committee with the speaking log and chair notes turned on, then try writing a slate from it. Most chairs find the evidence lines much easier to write the second time.