A shared laundry-room booking app for a small building — no landlord software
6 flats, one machine, slots per day. How to describe a booking grid your neighbours will actually use, how to get them onto it, and the three rules that stop the arguments.
Leanfinit · 6 min read
One washing machine, six flats, and a group chat with four hundred messages about who is next. The “property management” apps are built for landlords with fifty buildings — logins, tenant records, maintenance tickets. What six neighbours need is a grid: days across, time slots down, tap to claim. This guide walks through describing it, the rules that matter more than the design, and the part nobody writes about: getting six people to use the same thing.
Step 1 — Agree the rules before the app exists
An app cannot settle a rule the building has not agreed. Spend ten minutes on paper (or in the chat, one last time) on three questions. The answers go straight into the description.
- 1How long is a slot?Two hours fits a wash and a dry for most machines. Shorter slots create more bookings and more friction; longer slots waste the machine.
- 2How many slots can one flat hold at once?Two upcoming slots per flat is the usual fair limit. Without a limit, one household books the whole weekend on Monday morning.
- 3When does a slot expire?If nobody has started within 20 minutes, the slot is free again. This single rule removes most of the arguments.
Step 2 — Describe the grid
“A laundry booking grid for our building. Seven days across, two-hour slots down from 07:00 to 23:00. Each slot shows “free” or the flat that booked it. Tap a free slot to claim it with my flat (I pick my flat once, from Flat 1–6). Tap my own slot to release it. Rules: each flat can hold at most 2 upcoming slots; a slot is released automatically if not marked “started” within 20 minutes of its start time. Show “today” first, and a small list of my upcoming slots. Works offline for viewing; no accounts.”
Keep the flat picker to a single tap the first time the app opens. Do not ask for names, emails or phone numbers — the flat number is identity enough in a building of six, and it is the reason nobody has to “sign up”.
Step 3 — Get six people onto it
This is where most shared tools die, so do it deliberately. Post one message in the group: the link, the three rules, and a start date three days away. Pre-book the first week for anyone who replies with their usual time so the grid is not empty on day one. An empty grid looks like an abandoned project; a half-full grid looks like the new normal.
What about other shared things?
| Shared thing | Slot length | Extra rule worth adding |
|---|---|---|
| Guest parking spot | 1 day | Max 3 days in a row per flat |
| Courtyard / barbecue | Half day | Weekend slots rotate between flats |
| Shared guest room | 1 night | Book at most 30 days ahead |
| Cleaning rota | 1 week | Auto-assign the next flat; tick when done |
The grid is the same; only the slot length and one rule change. Describe each as its own small app rather than one “building app” with tabs — simpler apps get used, combined ones get argued about.
Where the bookings live
For six flats, a shared list of bookings is the one thing that has to be visible to everyone, so this is a case where you decide knowingly how to share: a shared text summary pinned in the chat, or a small shared sheet the app reads. Keep everything else — your own flat, your upcoming slots — on your phone. Nobody needs a tenant account, and no landlord ever enters the picture.
- Agree 3 rules
- Describe the grid
- Pre-fill week 1
- Tape it to the machine
Describe your own app →
Takes a few sentences. Private, yours.