The Mess Manager Guide: Run a Mess Without Arguments

Every successful mess has one thing in common: someone takes responsibility for the system. In most messes that person is the mess manager — sometimes elected, sometimes the flat's owner, sometimes just the organized one who got stuck with the khata. Good mess management is not about being strict; it is about being transparent, consistent and slightly boring. This guide is the complete playbook.

What a mess manager actually owns

• The meal count — making sure every meal is marked daily (or that everyone marks their own), and that the count stays visible to all members.
• The bazaar and bills — receipts collected, totals recorded, and the shared costs (rice, gas cylinder, wifi, electricity) paid on time so services do not get cut mid-month.
• The money — collecting contributions, tracking who paid what, and never letting the mess run out of cooking cash in week three.
• The month-end — running the closing calculation, presenting it, and getting the settlement executed in the first days of the new month.
• The peace — writing the rules down once so the same argument is never argued twice.

The weekly rhythm

1. Daily (2 minutes): meals marked after dinner, tomorrow's bazaar list checked against the kitchen.
2. Weekly (30 minutes): verify the meal sheet against memory and the cook's count; pay bills due; announce each member's running balance so nobody is surprised at month-end.
3. Month-end (1 evening): close the khata, present the totals, agree the settlement, collect signatures, and set next month's plan.

The weekly balance announcement is the single highest-value habit on this list. A member who hears "you are ৳2,000 short" in week two adjusts quietly; a member who discovers it on closing day argues loudly.

Rules that kill disputes before they start

• Rule 1 — Everyone sees the same numbers. A noticeboard khata, a shared sheet, or an app every member can open. Private notebooks create suspicion even when they are correct.
• Rule 2 — Decide the half-meal rule on day one. What counts as half, who can claim it, and whether guests pay cash or go on the khata as extras. Written, not remembered.
• Rule 3 — Receipts or it did not happen. Bazaar entries without a receipt still get recorded, but the habit of keeping receipts keeps the totals honest.
• Rule 4 — Today and yesterday are editable; older days are final. A short correction window prevents both typos and history-rewriting.
• Rule 5 — The manager does not get a discount. The manager's meals and bills go through the exact same math as everyone else's. Nothing protects trust more cheaply.

The month-end meeting agenda

Run the closing as a ten-minute standing meeting with a fixed agenda, not an open-ended trial:

1. Present the month's numbers: total meals, meal bazaar, meal rate, fixed bills, each member's total and balance. (One page or one screen.)
2. Invite checks — members verify their own meal counts against their memory for a minute. Corrections only for real errors, before signatures.
3. Announce the settlement plan: who pays whom, minimum transactions.
4. Collect dues or schedule transfers within 3 days.
5. Plan next month: roster changes, expected bills, any rule adjustments, and the bazaar advance each member should keep.

A realistic month in numbers

Five members, 440 meal units, a rate of exactly ৳40, fixed bills of ৳1,000 per head — and a settlement that clears every balance in four payments. A well-managed month is exactly this unremarkable.

Tools: from notebook to app

Start where you are: a paper khata with three sections beats no khata, and a spreadsheet beats a paper khata. But if you are reading this on a phone, consider what a purpose-built tool removes from your week: MessMeal gives every member their own meal-tap screen, locks past days for you, tracks bazaar and bills with the right split automatically, and produces the closing table and settlement plan on demand — the entire manager workload reduced to about two minutes a day. The first month is free, which is roughly the cost of your last argument.