Approvals and payments by code
Join requests are accepted first. Only then do payment details appear, with a personal code that matches the transfer even when a parent pays. Only “approved” is saved.
For MUN organizing teams
One place for the team that runs a Model United Nations conference.
Who is accepted and has paid, who does which task, which position papers are reviewed, and what each committee needs on conference day.
Clickable demo with sample data. No account needed.
The problem
Organizing work is spread across WhatsApp, Drive and hallways
Existing tools focus on the committee session or on finding conferences. None of them manages how the organizing team works together.
- Payment details travel by message, so a fake “our IBAN changed” message can’t be checked against anything.
- Parents send the bank transfer, so the name on it doesn’t match the delegate and matching is done by hand.
- Team tasks are given verbally and get lost.
- Position papers live in Drive and email; nobody knows who submitted, and feedback stays verbal.
- On conference day, committee needs are shouted down the hall, and nobody knows who took the request.
- No one records who entered the building, so in an emergency there is no answer to “who is inside?”
How MUNCore helps
Every request, task and approval has an owner
MUNCore does only the organizing side. The committee session itself stays in the tools your club already uses.
Team tasks
Only the team head assigns tasks. Each member sees exactly what is theirs and marks it submitted.
Position paper reviews
Chairs send feedback the delegate will see, and keep a private note for the chairs that never reaches the delegate’s screen.
Conference-day requests
A committee asks for water in room 3; the team sees it within seconds, assigns it and marks it done. Unclear requests wait in an open pool until a team head claims them.
Door check-in
Security records each entry by the same personal code. Only the organization heads see who is in the building.
Roles
Each person sees what their role needs
Everyone joins the same event with one invite link. The organizers decide who does what.
- Organizer
- SG, DSG, DG and DDG set up the event, accept people, match payments and see who is in the building.
- Team head
- Assigns tasks inside the team, handles incoming requests and claims requests from the open pool.
- Team member
- Sees their own tasks and sends requests to the open pool.
- Chair
- Runs committee preparation: study guide, position paper reviews and committee tasks.
- Delegate
- Sees everything assigned to them on one screen, with the chair’s feedback.
- Committee admin
- An Admin team member placed in a committee; opens that committee’s requests.
- Security
- Records entries at the door by code, without seeing the list.
Demo videos
Watch MUNCore at work
Four short screen recordings on a phone, about a minute each, with sample data.
Collect almost nothing
Most users are under 18, so MUNCore stores only an email, a display name and, for delegates, the country they represent. No phone, address, birthday, photo, school name or financial data, and no analytics or tracking. In this demo the rules are enforced on screen only; hiding something on screen is not security. In the full version, the database enforces who sees what.
About
Why I built MUNCore
I’m a high school student and a Model United Nations organizer in my school’s MUN club. When we organize a conference, the work is scattered across WhatsApp groups, Drive folders and conversations in the hallway, and things get lost between them.
I designed MUNCore to bring that work into one place. I decided what it must do, who sees what and what it leaves out. I built it with AI-assisted development using Anthropic’s Claude, and I tested it myself.
Right now you can try MUNCore as a clickable demo with sample data, and accounts for real conferences are on the way.
Zeynep
Contact
Questions, feedback, or want to use MUNCore for your conference?
Write to hello@mymuncore.com