Volunteer Slots

Slots first, then the people who fill them

Volunteer Slots is built the way a rota is actually planned: the shifts exist before the volunteers do. A slot carries what the job is, a date, a start and an end time, a place, and the number of people it wants. Everything else is derived from that number. A slot shows how many of its places are taken, a row of pips shows it at a glance, and a banner across the top adds up every unfilled place, so the organiser has one figure to watch instead of a list to scan.

The kind of day this is built for

School fairs, a charity stall, a village hall clean up, a shelter's weekend cover. The common shape is a fixed day broken into hours, a job that needs a specific headcount at a specific time, and people who will help if asked clearly. The failure it prevents is three volunteers turning up for the busy hour and nobody being there at four.

Laying the day out without typing thirty rows

Building the grid is the dull part, so hand it over. Describe the hours, the jobs and how many people each one needs, and your AI writes every slot in one go. What you get back is a page you correct rather than a form you fill in, which is a much shorter piece of work and far less likely to end with a two hour hole nobody spotted.

After that the sheet is a web address you send round. Everyone helping needs an invitation, which is an email address and a sign-in link, after which the page opens on their phone with no app store in the way.

Taking a slot, and giving one back

Taking a slot is one button, and it writes a row that belongs to you. Giving it back is the same button again. Nobody else can hand back your place: changing or removing a sign-up is restricted to whoever made it, plus the organiser.

A sign-up is also pinned to the slot it was made for. It cannot be quietly moved to a different shift later, which keeps the record of who agreed to what honest. Sign-ups appear as they happen, so two people looking at the last place on the cake stall do not both take it.

What the organiser can ask for

The question an organiser has all week is which slots are still short and by how much. Ask, and your AI reads the shifts against the sign-ups and answers in the order the day happens. Told somebody has dropped out of Saturday morning, it removes their place and says what that leaves uncovered.

It can reshape the day too. Splitting a three hour shift into two, or widening the headcount on the busy hour, is a sentence rather than a rebuild, and adding to an app never disturbs the sign-ups already in it.

The limits worth knowing before you send it round

This is a sheet for a known group, not a public sign-up link. Everyone who takes a slot has to be someone you invited, which is exactly what makes the names on it trustworthy and exactly what makes it the wrong tool for collecting help from a hundred strangers.

There is no waiting list: a full slot is simply full, and somebody has to give a place back before another person can take it. Slots do not repeat, so a weekly rota means writing the weeks out, which is a good job for your AI and a tedious one by hand. And nobody is reminded of anything. No message goes out the night before, so the sheet tells you where you stand and does not nudge.

The part that makes any of this work is that each person arrives as themselves rather than as an anonymous visitor, which is also the thing a published page with a shared data store cannot offer. how a published page stores what people type into it covers what that shared pool can and cannot hold.