The Block Makan: Running a Void Deck Potluck That Comes Back
A void deck potluck, known across Singapore as a block makan, block party or community lunch, is a shared meal held on the open ground floor of a public housing block, at which residents of that block cook at home and bring the food down to a common table rather than buying or catering it. Nobody is a guest and nobody is a host. The food is the contribution and the contribution is the point. It is one of the cheapest neighbourhood activities in existence, it needs no skill, no equipment and no fitness, and it is almost always run in the one way that guarantees it will not build anything.
That last sentence is the reason this article is long. A block makan is not a weak activity. It is an activity with a dial on it, and the dial is set wrong in the overwhelming majority of cases, by people who did everything else right. Get the dial correct and a potluck is one of the strongest things a block can do. Leave it where it usually sits and you will have spent a Saturday producing photographs.
This is written for you as a resident who wants to start one, or as a committee member who has run the same festival lunch for six years and has begun to suspect it is not doing what the annual report says it does.
What a block makan actually is, once the nostalgia is stripped out
Underneath the kampung language there is a simple machine with four moving parts, and it helps to see them separately, because three of them are easy and one of them decides everything.
There is a space, which is the void deck, and which you do not own and generally have to ask for. There is food, which arrives in pots from between fifteen and sixty kitchens, at ambient temperature, in a tropical climate, on a schedule nobody controls. There is a table layout, which quietly decides who eats what and therefore who stands next to whom. And there is an interval, which is the gap between this makan and the next one.
The space is an administrative problem with a known answer. The food is a logistics and safety problem with a known answer. The table layout is a design problem that most organisers never realise is a problem at all. The interval is the thing that decides whether any of the rest of it matters, and it is the only one of the four that is genuinely a choice.
Notice what a potluck is not. It is not a meal provided to residents. The moment the committee orders catering and residents turn up to eat, the activity has changed species: it becomes an event with an audience, and an audience is not a group. The contributed pot is not a charming detail of the format. It is the format. Everything durable that a block makan produces comes from the fact that a specific household cooked a specific thing and carried it downstairs.
The cadence question, and exactly where the line sits
Here is the claim this page exists to make, and it is the most useful thing in it.
A void deck potluck held once a year is a resetting activity. A void deck potluck held once a month is a compounding activity. These are not two intensities of the same thing. They are different activities that happen to look identical on the day, and the difference is not warmth, attendance, budget, food quality or how good everyone says it was. It is the interval and nothing else.
Almost every other neighbourhood activity has its cadence imposed from outside. A garden is watered daily because plants transpire, and no committee can vote that down. Breaking fast during Ramadan happens on twenty-nine consecutive evenings because the lunar calendar says so. A morning exercise group meets daily because a habit needs to be daily to stay a habit. A monthly ration round is monthly because that is how often a household needs rice. The potluck is unusual, and possibly unique in the heartland, in that its interval is set by whoever is organising it, freely, with no external constraint at all.
And because it is free, it gets attached to the nearest available occasion. Which is a festival. Which makes it annual. The single most common way a block makan is destroyed is not poor turnout or bad weather. It is being scheduled as part of something else.
Where the line falls
Monthly compounds. Thirty days is inside the window in which you still hold a face, a name, a flat number and a dish together as one object. When you meet someone at the next one, you are not being reintroduced; you are continuing. Monthly also means that the sentence "see you next month" is a real statement about a real date rather than a pleasantry, and a role can hang off it.
Six-weekly is the outer edge, and survives only with a written roster. At six weeks the face holds and the name has usually gone. It still works, but only if there is a list somewhere with people's names beside jobs, because the list is now doing the remembering that the interval no longer does. Without the list, six-weekly decays into quarterly by accident, because one postponement costs you three months.
Quarterly resets, while pretending not to. Ninety days is past the point where an ordinary acquaintance survives without reinforcement. You will recognise faces at a quarterly makan and you will not reliably produce names, and you will certainly not remember what anyone brought. What you get is a pleasant, well-attended series of separate occasions with overlapping guest lists. That is a perfectly nice thing. It is not accumulation, and calling it accumulation is how a block spends four years getting nowhere.
Annual is a photograph. Twelve months is longer than the memory for a stranger's name by an enormous margin. Every annual edition starts at zero and reaches roughly the same point by the time it ends, which is why year six feels exactly like year two.
So the line sits between monthly and quarterly, and if you want it in one sentence: the interval has to be short enough that the next one is a plan rather than an intention. Six weeks is the furthest you can stretch it and still be building. Beyond that you are running a series of events.
The uncomfortable consequence
Here is what follows, and it is the part committees resist.
If you want a monthly makan, you must make it much smaller. These two variables are locked together and almost nobody treats them as locked. A gathering of a hundred and fifty residents needs tentage, a public address system, a permit conversation, sponsorship, a working group, and a month of preparation. You cannot do that twelve times a year. Nobody can. So the scale forces the interval out to annual, and the annual interval guarantees the reset.
Turn it round. A gathering of thirty residents from one block needs eight tables, some chairs, a few bins, thirty pots of food and one person who booked the space. That is small enough to do every month for years, because no single edition costs anyone more than an afternoon.
The move from resetting to compounding is therefore a move downward in size, not upward in effort. If your block makan currently draws two hundred people once a year and you want it to start building something, the correct change is not a bigger one. It is a smaller one, twelve times, on the same Sunday of every month, for one block rather than the precinct. You will be asked why attendance dropped. The answer is that attendance was never the output.
What changes at each interval, specifically
It is worth walking down the scale, because different things break at each step.
Annual. The work is organisational, the cost is real, and the food is mostly catered or bought because a committee cannot ask residents to cook a year out. The named roles are committee roles, held by people who already know each other. For a resident who attends, there is no role at all, just a plate. Cross-block contact happens and evaporates. The honest description is an occasion.
Twice a year. Nothing changes structurally. Two annual events.
Quarterly. Something real starts to appear: a core of twenty or so people recognise each other and a few take on a job. But the gap does the damage. Each edition needs to be re-announced from scratch, re-staffed from scratch, and re-explained to newcomers, which means the organiser's workload per edition never falls. That is the tell for a resetting activity: the effort per cycle does not decline.
Monthly. The workload per edition drops sharply after the third one, because the same people bring the same dishes to the same layout and nobody needs to be told. Dishes become expectations. Absence becomes visible. New residents can be absorbed one or two at a time rather than in a crowd. Announcement stops being a campaign and becomes a reminder. This is the interval at which the activity starts to run itself, and that shift, more than any warm feeling, is what compounding actually means in practice.
Fortnightly and weekly. Possible, and a handful of blocks manage it, usually because one household drives it. Weekly cooking is a real burden, so the format almost always mutates: it becomes one cook providing a pot and neighbours bringing drinks and sitting down, which is a different and also excellent activity, but it is no longer a potluck, and its weakness is that it now depends on one person's stamina. A documented 2026 example in Tampines is exactly this: a resident who cooked two large soups himself, capped attendance at fifty, and said plainly that he did it because most people do not know their neighbours well. He intended to repeat it monthly. That is the correct instinct, and monthly is the correct number.
The dish you always bring
Of every named role in neighbourhood life, this is the lightest and probably the most durable, and it deserves to be argued for properly rather than mentioned in passing.
Start with what a role has to do. A role is not a title. A role is a slot that a specific person occupies such that their absence is noticed by a specific other person within one cycle. That is the whole test. Most community activities cannot hand out roles at all, because there is nothing to occupy; you can attend, and attendance is not a slot.
A potluck hands out a slot to every single household that brings food, automatically, with no committee decision, no appointment and no ceremony. And the slot has an unusual property: it is identified by an object rather than by a person. After three or four rounds, you are not the resident from the eleventh floor whose name somebody half remembers. You are the one who brings the curry puffs. That is a working social handle. It survives the name being forgotten, it can be used by a stranger without embarrassment, it gives people a safe opening line, and it converts to your actual name within a few months because somebody eventually asks.
Now look at what this role costs. One cooking session a month, of something you already know how to make. No committee seat, no fixed hour, no physical capability, no English, no daytime availability, no equipment, no money beyond ingredients. You can hold it at thirty and at eighty. You can hold it while pregnant, while working shifts, while caring for a parent. There is almost nothing else in the heartland that hands a resident a genuine, noticed, repeating role at that price.
And the absence mechanism is unusually gentle, which is why it works. When you skip a month, what registers first is not your absence but a gap on the table. Somebody says the curry puffs are not here. That is a much lower-stakes form of being missed than a roll call, and low stakes is what makes it survive: nobody feels policed, and yet the noticing happens.
Four practical rules make the dish behave like a role instead of a coincidence.
Ask people to bring the same thing. This sounds like it would be boring and it is the opposite. Variety is what an event wants; repetition is what a relationship wants. Tell people outright at the second makan: bring what you brought last time, we liked it. Most will be delighted, because being known for a specific thing is quietly flattering and requires no further effort from them.
Write the dishes down next to the names. Not to police anybody, but because the list is how a new organiser inherits the block's map, and because it lets you notice a household that has quietly dropped out.
Do not let the committee buy food. The instant there is catering, the dish stops being a contribution and becomes a choice between your own cooking and something free and easier. Contributed food and provided food cannot occupy the same table without the provided food winning. If money is available, spend it on drinks, ice, bins, tables and the booking, never on the main dishes.
Let someone hold the role without cooking. Some households will not cook and should not be pushed. The equivalent slots are real: the person who brings the ice, the one who brings cut fruit, the one who brings the drinks, the one who owns the bins. Name them the same way. The ice is as recognisable a contribution as the rendang.
Feeding a mixed block, and why the tables decide it
This is the section that makes or breaks an actual event, and it is where good intentions do the most damage, because organisers tend to treat dietary practice as sensitivity rather than as layout. It is layout. Handled as logistics, it disappears as an issue and everybody eats. Handled as an apology, it becomes the thing everyone is quietly managing all afternoon.
Begin from a clear-eyed position: a Singapore block contains households that eat no pork, households that eat no beef, households that eat no meat at all, households that eat no meat and also no onion or garlic, households avoiding shellfish or nuts for medical reasons, and households with no restrictions who simply want to know what is in the pot before they feed it to a toddler. All of these are ordinary and all of them are satisfiable at the same table if you build the table correctly.
Islands, not a buffet line
The default layout is one long line of dishes with a queue running down it. It is the worst possible arrangement for a mixed block, for three separate reasons.
A single line forces one order of travel, which means every dish is a decision made in public with people waiting behind you. A neighbour who does not eat pork must either inspect and skip repeatedly in front of a queue, or take the safe option of eating almost nothing and saying the food was lovely. A line also puts serving spoons within splashing distance of each other, which is the actual mechanism of concern rather than proximity in the abstract. And a line produces a single flow of people who all take the same path, talk to nobody, and sit with whoever they arrived with.
Use islands instead. Four separate tables with space between them, each self-contained, each with its own plates and its own serving utensils.
The no-meat island, placed in the centre. This is the table everyone in the block can eat from without asking a single question, which makes it the only place where genuine mixing is structurally guaranteed. Put it in the middle, give it the most space, and ask for more of it than you think you need, because dishes without meat are eaten by everybody and always run out first. Ask two or three households to double their quantity.
The halal island. Food with no pork and no alcohol, no lard, and no ingredients derived from either, kept physically separate with its own serving utensils and its own stack of plates.
The non-halal island, placed downstream and apart. Everything containing pork, lard, non-halal meat or cooking alcohol goes here, on its own table, set at a distance rather than at the far end of the same surface, and positioned so that people do not pass it before reaching the other islands. Its serving utensils never leave it and its plates are stacked at that table only.
Drinks and dessert, set apart from all of it. This island does more social work than any of the others, because it is the one people return to repeatedly and stand around, and standing around is where conversation happens. Put it away from the food so that a queue does not form through it.
Two habits protect the separation once it exists, and both need to be said out loud at the start rather than assumed. Nobody ever serves themselves with the cutlery from their own plate. And nobody carries a serving spoon from one island to another, even to be helpful, even for a second.
A note on what certification does and does not mean here, because people get tangled in it. Halal certification is a thing that applies to businesses and their premises and processes. A neighbour's home kitchen is not certified and will never be certified, and nobody expects it to be. What matters at a void deck table is far simpler and entirely within your control: what went into the dish, and what the dish and its spoon have touched since. Some neighbours will happily eat home-cooked food prepared by a Muslim household; some will eat only food without meat from any kitchen; some will prefer commercially packaged items with a certification mark; some will eat anything on the halal table without further thought. All of those positions exist within the same block and sometimes within the same family. Your job is not to know where any individual draws the line, and certainly not to ask them to explain it. Your job is to label clearly, separate physically, and let each person make their own decision in two seconds without having to say anything to anybody.
Vegetarian is not one thing
Writing the word vegetarian on a card conveys almost no information, and organisers who think they have solved the problem by providing one meat-free dish usually have not.
The distinctions that matter in a Singapore block are practical, not theological. Some people avoid meat but eat eggs and dairy. Some avoid eggs as well. Some avoid all animal products including fish sauce, belacan, oyster sauce, dried shrimp, anchovy stock, gelatine and lard, all of which hide inside dishes that look entirely plant based. Many Hindu households avoid beef absolutely while eating other meats. A portion of vegetarian practice, associated with Jain observance and with some Hindu and Buddhist practice, also excludes onion, garlic, shallot, leek and chives, which rules out a great deal of otherwise suitable cooking.
The practical consequence is a labelling rule rather than a research project: never label a category, label the contents. A card reading "no meat" tells your neighbour nothing about the fish sauce in it. A card reading "vegetables, tofu, soy sauce, no garlic" tells them everything and takes ten extra seconds to write.
And one quantity rule. Meat-free dishes are chosen by people with no restrictions at all, because they are lighter and because they are there, so demand always exceeds the count of vegetarian households by a wide margin. Plan for the whole block, not for the six flats you had in mind.
What "please label your dish" has to actually mean
Every potluck notice contains this line and almost every potluck ignores it, because the instruction is too vague to follow. Here is how to make it work, and it takes about five dollars of card.
Print the cards yourself and have them waiting on the tables, blank. Do not ask people to prepare labels at home; they will forget, and a label written at the table by the person who cooked the food is more accurate anyway.
Each card carries five things. What it is, in whatever name the cook uses. Who cooked it, by name and floor, which is not administrative detail but the entire social mechanism, because that is how a dish becomes attached to a person. What is in it, written as a short ingredient list rather than a category, with the things people actually need to know named explicitly: pork, beef, chicken, fish, shellfish, egg, dairy, nuts, peanuts, cooking wine or any alcohol, and the presence of fish sauce, belacan or shrimp paste. Whether it is spicy, because that is the question most often asked and it saves a hundred small conversations. And when it was cooked, which is a food safety field and is dealt with below.
Two design decisions make the cards usable by everyone in the block rather than by the fluent readers only.
Colour before text. Use a consistent colour of card for each island, the same colour every single month, so that residents learn the code once and then never read at all. Consistency month to month is what does the work here; a new scheme each time is worse than none.
Symbols beside words. A drawn chilli, a crossed-out chilli, a simple mark for no meat. Hand drawn is fine. This is not about presentation, it is about a card that a neighbour who does not read your language can still use, and about a card a child can use.
Then appoint somebody to own the cards, which is a genuine role and one of the easiest to fill. That person meets each pot as it arrives, hands over a card, and does not let a dish onto a table without one. Doing it at the point of arrival is the only version that works, because an hour later the cook has gone to sit down and nobody can tell you what is in the pot.
Serving utensils and the rest of the small hardware
The equipment that decides whether a makan works is unglamorous and cheap, and running out of it midway is the most common practical failure.
One dedicated serving utensil per dish, supplied by you rather than by the cook. If you rely on cooks to bring their own, roughly a third will not, and the result is people using their own spoons in the shared pots, which undoes every separation you built. Buy a box of long-handled spoons and tongs once and keep them in a crate. Long handles matter, because a short spoon ends up submerged and then handled by the next person.
Tongs for dry, ladles for wet, and a rest for every one of them. A serving spoon put down on the table travels; a spoon left in the dish or on a saucer beside it stays where it belongs.
Far more plates than headcount. People take a second plate rather than reuse one, especially at the point where they cross between islands, and that is behaviour you want to encourage rather than ration.
A hand hygiene point, set up before the food arrives. You do not have a sink at a void deck you would want to use for this. A pump bottle of sanitiser at the head of each island, plus a bucket of soapy water and a roll of paper towel on a side table, covers it.
Covers for everything. Void decks are open, breezy and have insects, birds and dust. Mesh food covers cost very little and are the difference between food you can serve at hour two and food you cannot.
Bins with liners, placed before anybody asks. Put them away from the food but in obvious sightlines, and put a second one near the drinks, which generates the most rubbish.
Ice, and twice as much as you estimate. In this climate ice is the single most consumed item and the one most frequently underestimated.
Booking the void deck: who applies, what it costs, how far ahead
This is administrative and completely learnable, and the rules differ between town councils, so the mechanism matters more than any particular figure.
The void deck of a public housing block is common property managed by the town council for that constituency, and permission comes from the town council rather than from HDB. Applications are typically restricted to residents of flats within that constituency, usually with a minimum age of twenty-one, with proof of address. Bookings generally open somewhere between three and six months before the event date and run first come, first served, so the constraint on a monthly series is not availability so much as remembering to apply.
Charges vary by town council and are modest for a void deck. Published rates for a social function at a void deck sit in the low tens of dollars per day, with some councils in the region of twenty dollars and others around fifty. Electricity and water are charged separately and per point per day, typically around ten to fifteen dollars each. Deposits for a void deck are often nil, though open spaces, turf and hard courts attract deposits that run into four figures, which is one good reason to stay under the block rather than move onto the field.
For a sense of the real all-in number: the resident who ran the Tampines free soup session in 2026 reported the whole venue cost at $89.38, comprising a $50 venue charge plus electrical and water charges. Plan for under a hundred dollars for the space, and treat any figure you read anywhere, including this one, as something to confirm with your own town council.
Free use exists, and getting it is the highest-leverage administrative move available to you. Several town councils waive rental for activities jointly organised by grassroots organisations, and at least one publishes free rental and utilities for a block party with resident participation on production of a letter from the constituency office. Many councils in any case require endorsement from the constituency office or the adviser for social events at common property. The practical reading of all this is simple: if you approach as a lone resident you will pay a modest fee, and if you approach with your Residents' Committee, Residents' Network or Neighbourhood Committee as joint organiser you will frequently pay nothing and get help with tables as well. For a monthly series, that difference compounds into real money and, more importantly, into an institutional relationship that survives you.
Cooking on site is usually not allowed, and this catches people out. The standard condition in general event permissions is that common property may not be used for the sole purpose of cooking or preparing food, with cooking permitted only as a declared part of an approved event, and details of any caterer and gas supplier required. Read this as: cook at home, carry it down, and do not turn up with portable gas burners unless you have specifically asked and been told yes. It also shapes your menu, because it means nothing can be finished on site.
End times are real. Permits commonly require all activity to cease by 10.30pm, and permit windows are often written as specific hours. A makan that begins at 5pm and is cleared by 8.30pm sits comfortably inside every version of this and avoids the whole category of problem.
Power, water, tables, bins and the things that fail on the day
A void deck looks like it has everything and mostly has less than you assume. Go and stand there a week before with a checklist.
The power point. Find it, and check the socket type physically rather than assuming. A documented and entirely typical failure at a recent void deck session was arriving with the wrong plug. Common property points are not always ordinary domestic sockets, they are frequently locked, and access may need to be arranged with the town council when you book. Assume your electricity needs to be declared and paid for per point per day. Also note the load limit: general event conditions can specify a maximum of around fifteen amperes for lighting, with anything heavier requiring approval for a generator. In practice that means a few slow cookers or urns, not fifteen of them. Bring extension leads with residual current protection, tape the leads to the floor, and never run a lead across a walkway.
The water point. Also frequently locked, and sometimes simply dead. The same 2026 session found a non-functional water point on the day. Test it in advance, and bring water regardless, because you will want it for cleaning even if you do not need it for cooking.
Tables and chairs. The town council or your Residents' Committee can often lend them, and that is worth asking about in the same conversation as the booking. Work out the transport before the day; eight tables and forty chairs is more trips than one person with a trolley can manage in an hour. If tables are borrowed, someone specific owns returning them, and that job is the one most often left undone at 9pm.
Bins and where the rubbish actually goes. Find out in advance where your bags go at the end. It is not the litter bin by the lift, and leaving eight bags beside it is exactly how a block loses permission. Ask the town council when you book which bin centre to use.
Shade, wind and rain. A void deck is covered, which handles most of it, but wind blows rain sideways into the open edges and will reach the tables nearest the perimeter. Set up towards the sheltered core, and decide in advance which side you retreat to, rather than moving thirty pots of food in a hurry.
A wet weather rule, decided before you need it. The great advantage of this format over almost every other outdoor neighbourhood activity is that a void deck is already covered, so your rule can simply be that it happens anyway. Say so in the notice. Never make a monthly series conditional on weather, because a cancellation costs you two months.
The residents living directly above you
Four to six households, on the second to fifth floors, above and around the pillar you are using, will determine whether your series continues. They get the noise, the chairs scraping, the cooking smells, the crowd at the lift lobby, and the stairwell full of people. They are also, and this matters, the easiest attendees you will ever recruit, because they are thirty seconds from the table.
So go and see them, in person, before the first one. Not a notice in the lift. A knock, an introduction, the date, the hours, and a phone number that is actually answered. Say the end time and then honour it exactly, because the single most reliable way to lose the goodwill of the flat above is to run an hour past what you told them.
Then be specific about the things that actually travel upward. Chairs dragged across a void deck floor are a loud, sharp, repeated noise, and putting the chairs down rather than dragging them removes most of the complaints a makan generates. Amplified sound is rarely necessary at a thirty-person meal and is the other main source; if you use any, keep it low and switch it off half an hour before the end. Watch the lift lobby, because a crowd standing between the lifts and the letterboxes makes residents who are not at your event feel they have to push past their own neighbours to get home.
And give the households above a role rather than an apology. The family on the third floor who lends the extension lead, or brings the ice down, or lets you use their tap, is no longer a potential complainant. They are a participant, and the conversion costs you one conversation.
The four-hour clock, and cooking for a crowd in this heat
This is the part where a block makan can actually harm somebody, and it is governed by a number worth memorising.
National guidance for catered food at functions is that no food should be kept at room temperature for more than four hours from the time it was cooked to the time it is eaten, and that anything left after that window is discarded rather than kept. That four hours is not four hours on the table. It includes cooking, cooling, packing, carrying, the lift, the setting up, and the whole time the pot sits out before people start eating. By the time a dish cooked at noon reaches a table at four, most of the budget is already spent.
The supporting numbers are simple. The temperature danger zone, where bacteria multiply fastest, runs from 5C to 60C. Hot food that is being held hot must stay above 60C. Cold food must stay below 5C. Cooking above 75C kills the ordinary bacterial hazards, and soups, curries and stews should be brought to a proper boil. Nothing at a void deck stays above 60C on its own, so in practice every pot on your table is inside the danger zone from the moment it is put down, and the clock is running.
Translate that into rules you can actually enforce.
Publish a cooking window, not just an arrival time. Ask people to cook that afternoon and to write the cooking time on the card. The card field exists for this.
Open the table at a fixed minute and eat early. A makan where food sits out from 4pm and people drift in at 6.30pm is a genuinely poor idea. Announce a serving time, serve then, and let the socialising happen after the food rather than around it.
Set a hard close on the food, at two hours after the table opens. That leaves margin for the cooking and transport you cannot see. After that, food goes away and the drinks and dessert island carries the rest of the evening, which it does perfectly well.
Do not let food go home. This is the rule most likely to be argued with, and it matters, because taking a container upstairs at 8pm and eating it at 10pm pushes the food far past any safe window and does it out of your sight. If someone wants to send a plate to a housebound neighbour, it goes up in the first hour, in a clean covered container, straight upstairs.
Use insulated carriers rather than reheating. You very likely cannot cook on site. That makes insulation the whole game: a hot pot inside a thick towel inside a box holds temperature far longer than an uncovered pot, and slow cookers or urns on a single power point will hold a couple of dishes hot but not thirty.
Have a sick rule, stated in the notice. Anyone who has had vomiting or diarrhoea in the preceding forty eight hours, or has it in their household, brings drinks rather than food. Writing it into the standing notice makes it a rule about the event rather than a judgement about a person.
Separate the jobs. Whoever handles rubbish, chairs or money does not then serve food without washing properly first.
What travels badly and should stay home
Some dishes are structurally unsuited to sitting at ambient temperature for hours, however well made.
Anything containing raw or lightly cooked egg: homemade mayonnaise, dressed salads bound with it, mousses, tiramisu, raw egg desserts. Cut fruit, especially melon, which is one of the most reliable sources of trouble at buffets anywhere. Cooked rice held warm, which is a specific and well known hazard because the spores involved survive cooking and multiply while the rice sits at a comfortable temperature, and it is exactly what a large tray of fried rice does over three hours. Cream-filled pastries and anything custard based. Seafood, especially shellfish and anything lightly cooked. Cold noodle dishes with sauces already mixed in. Anything that has already travelled a long way in a warm car boot.
What travels well: dry curries and rendang, braises with high salt or sugar content, roasted and baked items, breads and buns, kueh that is designed to be eaten at ambient temperature, biscuits and cakes without cream, whole uncut fruit, and sealed commercial drinks. Fried food is excellent in the first hour and unpleasant afterwards, so put it at the front of the serving time rather than banning it.
What to refuse, and how to refuse it
You need a rule before you need it, and you need it to belong to a named person, so that refusing is a policy rather than an insult.
Refuse anything that arrives with no label and no cook available to describe it. Refuse anything that has clearly been in transit a long time and arrives lukewarm. Refuse leftovers brought across from some other event. Refuse anything sitting over a tealight warmer that is obviously not holding heat, since a warmer that keeps food at forty degrees is worse than no warmer at all. Refuse raw or lightly cooked egg and raw seafood. Refuse home-fermented or home-bottled items you cannot ask questions about.
Say it kindly and structurally: put the rule in the standing notice every month, in the same words, so that by the third makan it is simply how things are done here. And when you do refuse something, take the cook's side out loud. Thank them, put their dish aside, and ask them to bring the same thing next month cooked later in the day. You are protecting a series that needs them in it.
Clearing up, which decides whether there is a next one
A monthly makan lives or dies on the state of the void deck at nine o'clock, and this is the most underrated part of the entire operation.
The formal lever is the deposit and the permit, and permits can be terminated for breach without notice. The informal lever matters more: the cleaner who works that block, the residents above, and the town council officer who will be asked whether these people are any trouble. A void deck returned spotless twelve times is an argument that needs no words. One left greasy is remembered for years.
Grease is the real enemy, not litter. Oil that reaches a void deck floor does not sweep up, it spreads, it becomes a slip hazard, and it stains. Put cardboard or a cheap plastic sheet under every table carrying oily food, and under the whole serving area if you can. Bring a degreasing detergent, not just water.
Plan cleanup as a shift with named people, not as a general appeal. Three people, agreed beforehand, staying to the end, is worth thirty people who say they will help. Announce who they are at the start.
Start clearing before the end. Pots and tables from the edges come down while people are still talking at the drinks island. This shortens the tail enormously and stops the last twenty minutes from falling on two exhausted people.
Bag, tie, and carry to the right place. Not the litter bin by the lift lobby. The bin centre or the point the town council specified.
Wipe and sweep, then photograph. Take a picture of the cleared void deck each time. It costs nothing, it settles any later question about the state you left it in, and it is the single most useful thing to show a town council officer when you ask for the next twelve dates.
Return everything the same night. Borrowed tables and chairs left out overnight are how a block loses lending privileges.
Named jobs beyond the dish
A makan can hand out more roles than almost any other neighbourhood format, because the work is genuinely divisible into small pieces. The rule for all of them is the same: a job with a name attached and a next month attached is a role, and a job done by whoever is free is not.
The dish itself, for every contributing household.
The island owner. One person owns each table: sets it up, keeps its utensils on it, keeps it tidy, closes it at the food deadline. Four islands, four owners, and the halal island owner in particular has a job that genuinely matters.
The card writer, meeting each pot as it arrives.
The ice and drinks run.
The chairs out, and the chairs back. Two separate roles, because the second is harder and nobody ever volunteers for it in advance.
The floor caller. The person who knocks on the doors of the lowest four floors the day before. This is the highest-value job in the list and looks like the smallest.
The greeter. Somebody standing at the lift lobby for the first thirty minutes whose whole job is to catch people arriving alone, take them to the food, and hand them to a conversation. Without this role, every newcomer eats with whoever they came with and leaves knowing nobody. With it, the makan becomes an entry point for every other activity in the block.
The bin owner.
The photographer, who is also the person who takes the after picture.
The cleanup shift, three named people.
The booker, who applies for the space and who should train a second person to do it within six months, because a series that only one person can book has exactly one point of failure.
And one job that should be given a name of its own: the person who announces the next date before anyone leaves. Do this while everybody is still there with a plate in their hand. A date announced on the day is remembered; a date circulated later is read by a fraction of the people. This single habit is the difference between a monthly series and a series of intentions.
The tier this sits in, and a reply to the garden's claim
Within this hub's split between compounding, recruiting and resetting, the void deck potluck is the only activity whose tier is not a property of the activity at all. It is a setting.
Monthly, single block, contributed food, named dishes: compounding. Same faces, roles that are noticed when vacant, an interval inside the memory window, and a workload that falls with repetition.
Festival-attached, annual, precinct-wide, catered: resetting. A good day. Attendance and photographs. Year six equals year two.
Quarterly: resetting wearing the clothes of a compounding activity, which is the most expensive of the three, because it costs organiser effort at a compounding rate and produces resetting results.
There is also a real recruiting function, and it is worth taking seriously, because it may be the potluck's strongest suit. A makan is the lowest-threshold activity in the entire neighbourhood. It asks nothing, it needs no fitness or commitment or skill, it is legible to everyone without explanation, and it draws people who would never join anything. That makes it an unmatched catchment. An hour at a table is where the garden finds its next three gardeners, where the patrol roster finds a volunteer, and where somebody first hears that there is a group exercising at seven in the morning. Put the standing activities of the block on one small board next to the drinks island and have a person, not a poster, beside it. A potluck that both compounds and recruits is doing two jobs, and very few activities can do either.
Now the argument. The community garden article in this hub makes a strong claim: that a plant beats a potluck for contact across communities, because a plant belongs to no culture while a dish declares a heritage and lets a table sort itself. That claim is correct on its own terms and this is the honest response from the other side.
Concede the mechanism. Food does sort. A table left to itself will produce clusters of people eating what they recognise, standing with people they already know, which is exactly the thing designed contact events fail at. Concede too that a garden's task is parallel and largely wordless, so two people with no shared fluency can cooperate all morning, while a meal demands conversation immediately, and demanding conversation immediately is a barrier that falls hardest on exactly the people you most want to reach.
Then take the two points where the potluck is the stronger instrument.
First, sorting at a table is visible and therefore designable, which is more than can be said for most activities. Nobody can see self-sorting happening across a neighbourhood's activity calendar, so nobody fixes it. At a makan you can see it from where you are standing, and you can change it with furniture: a meat-free island in the centre that everyone can eat from, a drinks island placed away from the food so people stand and mix instead of queueing, a greeter whose job is to break up arrival groups, fewer seats than the number of people so that nobody settles into a fixed table for two hours. A garden is unsorted because it is neutral. A table can be unsorted on purpose. Those are different achievements and the second one is repeatable by anyone who can move a table.
Second, and more fundamentally: neutrality has a cost. A plant tells you nothing about your neighbour. A dish carries actual information, and it is information about the part of a person's life that is hardest to get at any other way. Eating the food someone's grandmother taught them to make, in a building you both live in, and asking what is in it, is a specific and unusually rich kind of contact. The garden produces contact that is easy but thin. The potluck produces contact that is harder to arrange and substantially thicker when it happens.
And there is a matter of reach. A garden gives ten to forty residents an exceptional experience. A block makan gives sixty households a mediocre one and three of them an exceptional one. Both numbers are real. A block with the energy for only one activity should probably choose the garden, and the honest reason is the cadence: the garden's interval is enforced by biology while the potluck's has to be enforced by a person, and things enforced by people slip. A block with the energy for two should run the makan as well and treat it as the mouth of the funnel, because the garden cannot recruit a household that will never touch soil, and the table can.
Where a block makan actually breaks
Five failures, in the order you will meet them.
The third one. The first runs on novelty and the second on goodwill, and the third is the real number. It will be smaller and that is not a signal to stop, it is the baseline appearing. Decide now that you will hold the third one at full effort regardless of what the second one looked like, because a series that survives its third edition usually survives its second year.
The same eight households. By month four you have a core, and a core that is not deliberately widened becomes a clique with a table. The counter is mechanical rather than attitudinal: one floor per month gets knocked on personally, in rotation, and you keep a list of which floors you have done. Twelve months of that reaches a whole block.
The slide into catering. Somebody will propose, reasonably and helpfully, that the committee provides the main food to save residents trouble. Accepting is the end of the activity as a tie-building machine, because the contributed dish is the only thing handing out roles. Spend the money on tables, ice, drinks, bins and the booking instead, and say why.
The slide into scale. The second most dangerous proposal is to make it bigger, or to open it to the neighbouring blocks, or to add a stage. Each of these makes the next edition harder, and hard editions cannot be monthly, and non-monthly editions do not compound. Growth in this format means more households from the same block, not more blocks.
The single point of failure. One person books the space, holds the crate of serving spoons, writes the notice and knows the town council officer. When that person moves, changes job or gets tired, the series stops inside two months. The fix is dull and must be done early: a second booker trained by month six, the crate kept somewhere two people can reach, the notice as a document anyone can edit, and the standing rules written down once rather than held in a founder's head.
Your first three makans, in order
Before the first one. Walk the void deck and pick the exact spot, away from the lift lobby, away from the bin chute, under the most sheltered part. Find the power point and look at the socket. Find the water point and turn it on. Ring the town council and ask four questions: what the void deck costs for a residents' gathering, whether joint organisation with the grassroots organisation makes it free of charge, how far ahead you can book, and where the rubbish goes. Then ask your Residents' Committee, Residents' Network or Neighbourhood Committee to co-organise, because that one conversation is likely to remove the fee and produce tables. Pick a Sunday. Fix a serving time at 5pm and an end at 8.30pm. Knock on the lowest four floors yourself.
The first makan. Keep it to one block and expect thirty people. Four islands, the meat-free one in the centre. Blank cards on the tables and one person writing them. Your own crate of serving utensils. A greeter at the lift lobby for the first half hour. Ice, bins, covers, cardboard under the oily tables. Serve at 5pm exactly. Close the food at 7pm. Announce the next date before anyone leaves, out loud, with everyone holding a plate. Clear, wipe, photograph the empty floor, return everything the same night.
The second. Same Sunday of the month, same spot, same layout, nothing new. Tell people to bring what they brought last time. Write the dishes against the names. Knock on floors five to eight this time. Recruit your second booker now rather than later. Resist every offer to expand.
The third. Hold it at full effort whatever the headcount. Add exactly one thing: a small board next to the drinks island listing the standing activities in the block, with a person standing beside it who can talk about them. That is the month the makan stops being an event and starts being infrastructure.
And the rule that outranks all the others in this article: the date of the next one is announced while the current one is still happening. Everything else here is detail. That is the mechanism.
Questions residents ask about running a block makan
Do I need to book the void deck for a potluck?
Usually yes. The void deck is common property managed by your town council, and a gathering with tables, food and exclusive use of an area normally needs a permit. Call your town council early, because conditions and charges differ between councils.
How much does a void deck booking cost?
Rates vary by town council, typically in the low tens of dollars a day for a social function, plus separate charges of roughly ten to fifteen dollars per power or water point. One documented 2026 resident session came to $89.38 in total including utilities.
Can we get the void deck free of charge?
Often, yes. Several town councils waive rental for activities jointly organised with grassroots organisations, and some publish free rental and utilities for resident block parties on production of a constituency office letter. Approaching with your Residents' Committee is the effective route.
Who is allowed to apply for the booking?
Generally a resident of a flat within that constituency, usually aged at least twenty one, with proof of address. Grassroots organisations apply through their own channel with an adviser's endorsement. Bookings typically open three to six months ahead, first come first served.
Can we cook at the void deck itself?
Normally no. Permission conditions commonly prohibit using common property for the purpose of cooking or preparing food, allowing it only as a declared part of an approved event. Cook at home, carry the food down, and ask before bringing any gas equipment.
How often should we hold it?
Monthly. Thirty days is short enough that people, names and dishes carry over from one to the next, which is what builds anything. Six weeks is the absolute limit, and quarterly or annual events restart socially from zero every time.
Why does a monthly potluck need to be smaller?
Because scale and frequency trade against each other. A hundred and fifty person event needs tentage, sponsorship and a working group, which nobody can repeat twelve times a year. Thirty people from one block is repeatable indefinitely, and repetition is the active ingredient.
How long can home-cooked food sit out?
Four hours maximum from cooking to eating, according to national guidance for catered functions, and that window includes transport and setting up. Close your food table two hours after serving starts, and discard rather than keep whatever is left.
How do we handle halal and non-halal food properly?
Use separate tables rather than two ends of one table, each with its own serving utensils and plates, and place the non-halal table apart and not on the route to the others. Label ingredients clearly, and never move a serving spoon between tables.
What should the labels actually say?
Ingredients, not categories. Name pork, beef, chicken, fish, shellfish, egg, dairy, nuts, alcohol and fish sauce or shrimp paste explicitly, add the cook's name and floor, whether it is spicy, and the time it was cooked. Use pre-printed blank cards.
How much vegetarian food should we ask for?
Considerably more than the number of vegetarian households suggests. Meat-free dishes are taken by everybody and always run out first. Ask two or three cooks to double their quantity, and label contents carefully, since some households also avoid eggs, fish sauce, onion or garlic.
Which dishes should people not bring?
Anything with raw egg, cut melon and cut fruit, cream and custard fillings, seafood, and large trays of rice held warm, which is a well known hazard. Dry curries, braises, baked items, ambient kueh and whole fruit all travel well.
What do we do about the residents living above us?
Visit them in person before the first one, give the date, the hours and a phone number, then finish exactly when you said. Lift chairs instead of dragging them, keep amplified sound minimal or absent, and invite those households in by giving them a job.
What most often kills a monthly makan?
Four things: the committee starting to provide the food, which removes everyone's role; growing the event, which makes it unrepeatable; skipping a month, which usually costs two; and one person being the only one who can book the space.