Who Owns the Christmas Fair Spreadsheet? A Survival Guide for Festive Chaos

It starts with the best of intentions. One volunteer opens a spreadsheet, names it something sensible like Christmas Fair 2026, and shares the link in the group chat. By the middle of November there are six versions, three names on the stall booking list, a raffle prize tab called misc final FINAL, and a polite but slightly panicked message asking whether the church hall has actually been booked.

The Christmas fair is supposed to be a bit of festive chaos. The spreadsheet is not. When a small group cannot agree where the stall bookings live, it is not just an admin hiccup. It is a community tech problem in miniature: shared information without a shared home, permissions without purpose, and a file that depends entirely on the person who made it remembering everything.

The mystery tab is a symptom, not the disease

Most groups do not set out to create a maze. They create one because everyone is trying to be helpful. One person keeps the stallholder contacts in their inbox. Another tracks payments in a notebook. A third has the 'real' version on a laptop at home, which is fine until that laptop goes on holiday.

This is not really a spreadsheet problem. It is an ownership problem. A file can only be a single source of truth if people know it is the source, trust it is current, and can get to it without asking a human password reset question at 10pm.

So before you shop around for another platform, do the unglamorous thing: choose one home for the fair. It can be Google Sheets, Microsoft 365, a Nextcloud instance, or whatever your group already pays for and half understands. The tool matters less than the agreement around it.

Pick one home and say so out loud

Name the file clearly. Something like Christmas Fair 2026 — Master is less exciting than Festive Funz, but it does the job. Put the link in one pinned message, in the group chat, and in the email that goes to stallholders. Then say the sentence that saves hours: 'This is the only version we are using. If you have an older one, please archive it.'

That last part is important. Old files do not disappear just because a new one exists. Rename them with ARCHIVED — do not edit and move them to a folder. If you are feeling kind, add a note at the top of the old file pointing to the new one. It is not glamorous community tech, but it is the sort of small act of care that keeps volunteers sane.

Give people jobs, not keys

A shared edit link is not a permission strategy. It is a hope. In a village hall committee, a PTA, or a community trust, not everyone needs the same level of access. The fair organiser needs to edit the stall list. A stallholder needs to check their booking and maybe update their contact details. A general volunteer needs to see the rota. The person who runs the raffle probably needs their own tab and a quiet word about not renaming everything.

Use view-only links where you can. Use a simple booking form for stallholders so their details land in one place rather than in twelve separate messages. Keep personal information in a separate tab that is not shared more widely than necessary. If you are collecting contact details, allergy information, or accessibility needs, think about who really needs to see them. UK GDPR does not have to be scary, but it does reward a bit of common sense: collect less, share less, delete when it is no longer needed.

The aim is not to build a fortress. It is to make the file useful without making it fragile.

Make the handover note part of the file

The handover note is the bit everyone promises to write and nobody does. Do not leave it as a separate document that will be lost in a downloads folder. Put a Read me tab at the front of the spreadsheet. Keep it short and human.

List who owns the file and who is the deputy. Explain what each tab is for. Note where stall bookings come from, who updates the payments column, and which deadlines actually matter. Add the date of the last update. If there are passwords or accounts involved, do not put them in the spreadsheet; use a password manager and note who has access. A handover note should survive the volunteer who created it, not depend on them being available in December 2027.

This is where community tech becomes community practice. The spreadsheet is not just a grid of cells. It is a small piece of shared memory. Write it down as if the next person is tired, busy, and doing this on a Tuesday night after work. They probably will be.

A five-minute rescue plan for this week

If your fair is already mid-chaos, do not start a grand digital transformation. Do a rescue.

1. Freeze the current mess. Pick the file that looks most complete and stop editing the others.
2. Merge the missing bits into it: stall bookings, payments, raffle prizes, volunteer rota.
3. Rename it clearly and put a Read me tab at the front.
4. Change the sharing settings so the group chat gets a view-only link and only the core organisers can edit.
5. Archive the duplicates with a note pointing to the master file.
6. At the next meeting, spend five minutes showing everyone where it lives.

That is it. No new app, no training course, no committee paper. Just a single place for the truth and a small agreement to keep it there.

The fair is a rehearsal for the rest of the year

If your group can do this for the Christmas fair, you can do it for the room booking calendar, the volunteer rota, the newsletter list, and the summer fete. The point is not to become spreadsheet enthusiasts. The point is to build small habits that make it easier for people to join in, help out, and hand over without drama.

Good community tech is often less about the platform and more about the promise: this is where the information lives, this is who looks after it, and this is how you find your way in. The Christmas fair spreadsheet is a tiny test of that promise. Pass it, and the mince pies taste better.