A school fair is prepared with people who don't all know each other, don't use the same tools and don't have ten minutes to spend on a chat thread. A list shared by link puts everyone on the same level of information.
Create the party list
The message thread goes in every direction, nobody scrolls back through eighty messages to check what is missing, and the families who aren't in the group don't take part at all. The result: twelve quiches, no dessert, and two volunteers making up for the rest.
The list opens with no account, no phone number and no app. Every family sees what is needed, what is already taken and what is still missing — the same state everyone else sees.
Savoury, sweet, drinks, supplies: one line per need with the quantity expected. Ordering the categories keeps the list readable for parents in a hurry.
One message to the class mailing list is enough. Families click, sign up for an item and have nothing to install.
Every "I'll bring it" moves the list forward for everyone. You only chase people for what genuinely remains.
A shared buffet is ideal on paper: every family brings a little something, it costs the school nothing and everyone takes part. In practice, coordinating it through messages quickly becomes a headache.
The thread scrolls by, and it becomes impossible to tell at a glance what is already covered. A parent joining late won't scroll back to check whether anyone thought about drinks. Things get duplicated, you end up with ten savoury dishes and no dessert, and the same people always make up the difference.
There are also the families who aren't in the chat group, or who would rather not give their number to the whole class. What you need is a single list, shared through one link, showing what is asked for, what is already taken and what is still missing.
You add what you need — savoury dishes, desserts, drinks, supplies — with a quantity on each line: three quiches, six bottles of water. You share the link, and each family checks off what they are taking care of.
Every line shows the quantity requested, the number of people already signed up and the progress. A counter at the top tells you where you stand overall. When a parent signs up, the item is marked covered for everyone straight away: no more duplicates, no more gaps.
You build the list to start with, and you can let guests suggest their own items if you enable that option. It is up to you to strike the balance: enough entries to have a bit of everything, without so many that the list puts people off.
The fair takes place on a Saturday in late June and you are coordinating the buffet. You create a "School fair buffet" list with a short note: everyone brings a dish or a hand, sign up for what you are taking so we have a bit of everything. Then you fill it in:
The buffet is only part of the organising. The same event often involves supplies bought together to be paid back, sometimes a preparation date to settle, and at the end of the year a collective gift for the teaching team.
Those three topics live under the same project link, with no account for participants and no commission on the amounts. You only switch on the tools you actually use, and the party stays told in one place.
Every tool works on its own or attached to the same shared link. You only turn on what you really need.
The item list with quantities, free-form categories and live tracking of what is already taken care of.
Explore KontribTo settle the date of a planning meeting or a set-up session the day before, with no account for participants.
Explore KalFor supplies bought together: the amounts people fronted are split and settled.
Explore KountFor the end-of-year gift to the teaching team, with a pool the contributors can follow.
Explore KdoCreate the item list, share it with the families and keep supplies, dates and the gift in the same place.
Create the party list