Guide
Run an office or team lunch pool with order windows and monthly billing
How teams publish menus, collect lunch orders, and bill members without a spreadsheet fight at payday. About 9 minutes to read.
By ManagerBhai Editorial TeamPublished Updated
Who this fits
Small offices, startup pods, and study groups often run a shared lunch fund. One person orders from a kitchen or restaurant; others pay later. Without structure, the organizer absorbs risk and reminders.
Publish the menu, then open the window
Create meal days with a short menu and a clear cut-off. Members place orders before the window closes. That replaces chaotic replies in chat and gives the organizer a single list to send to the kitchen.
Example week: Saturday–Thursday office days, menu posted by 9:00, order cut-off at 10:30, delivery by 13:00. Stick to the same cut-off every day so nobody claims they “didn’t see the message.”
- Name dishes clearly (and note vegetarian options).
- Close orders early enough for delivery or cooks.
- Record guests separately so visitors do not invisibly raise the rate.
What not to do in WhatsApp
Do not take final orders only as emoji reactions. Do not edit yesterday’s list after food is ordered. Do not hold cash “for next week” without a wallet entry. Chat is fine for reminders; the ledger should be the source of truth for money.
Map the invoice to the week
When the caterer sends a weekly bill, log it as one or more expenses with dates that match the meal days. If Monday was 18 meals and Tuesday was 14, keep those counts so monthly averages stay honest even when attendance dips.
Bill from actual orders, not memory
At week or month end, use meal and expense reports to see quantities and costs. Charge the shared wallet or create settlement amounts based on who ordered. When the caterer invoice arrives, log it as an expense tied to those meal days.
Keep organizers happy
Rotate admin duty if ordering is a load. Keep approval rights with people who handle money. Transparent numbers reduce the feeling that “someone is profiting from lunch.” A monthly 10-minute review in the team standup is enough to catch missing deposits early.
Frequently asked questions
- How should we handle guests who join lunch once?
- Log them as guest counts on the meal day and bill the hosting member or create a one-off expense assigned to that person. Do not silently fold guests into everyone’s monthly rate—visibility prevents the “why is lunch more expensive?” debate.
- What is a practical order cut-off?
- Post the menu early and close orders with enough time for the kitchen or delivery partner—many offices use a 10:30 cut-off for a 13:00 lunch. Consistency matters more than the exact minute.
- Who should hold approval rights for the lunch wallet?
- Keep approvals with people who handle money or ordering that week. Rotate the organizer load if needed, but do not let every chat message rewrite the ledger after food is already ordered.
Use this workflow in ManagerBhai
Create a group, invite members, and keep deposits, expenses, and meals in one shared ledger. Stay on the free plan with ads, or upgrade with bKash when you need more groups and history.