Your spreadsheet works.
Until it doesn’t.
For a syndicate of four with one aeroplane, a shared spreadsheet and a WhatsApp group genuinely do the job most of the time. Whoever wants it says so in the chat, somebody keeps a tab of the hours, and it mostly balances. We are not going to pretend that is broken.
What we would like to show you is the handful of Sundays a year when it is not enough, because those are the ones that cost a friendship as much as they cost money.
What the spreadsheet and the chat cannot do
A spreadsheet holds numbers and a group chat holds messages. Neither of them knows anything about the aeroplane, which is where the gaps are.
- Two people book the same Saturday. One message scrolls past unread and both owners drive to the airfield. The chat did not stop it because the chat cannot see the diary.
- Nobody checked the aeroplane was fit to book. The check was due, or the ARC lapsed, or there was an open snag from last week nobody logged. The spreadsheet will let you write a name in a box next to an aeroplane that should not fly.
- The reserve fund drifts. Somebody was supposed to top it up per hour. In practice it was last updated in March, and the first anyone thinks hard about the engine fund is the quote for the overhaul.
- The month-end split gets disputed. The hours were copied across from a scrap of paper, one flight got missed, and now two owners are politely disagreeing about forty quid.
- Nobody can answer a question about last year. How many hours did it fly? What did the last annual cost? Who flew it most? The tab that would tell you was overwritten months ago.
The one thing a spreadsheet structurally cannot do
Book the aeroplane in FlyerOS and it checks whether it can actually fly then, before it lets you. If the aeroplane will be out of check on the day, or it is grounded on a snag, or a document has lapsed, it refuses and says why, so the problem surfaces on the sofa on Sunday, not at the airfield.
That is not a spreadsheet with better formatting. It is the thing a spreadsheet cannot be, because a spreadsheet does not know the aeroplane exists.
Keep the group chat. Move the bit that goes wrong.
A syndicate is a configuration of FlyerOS, priced per aircraft with no minimum, from £25 per aircraft a month with members unlimited, so a one-aircraft group splits one small bill between the owners. You keep the chat for chat, and the diary, the tech log and the money move somewhere that can actually check them. See the exact numbers.
Tell us your aeroplane and how the four of you run it, and we will set it up the way your group works and show you the Sunday, not a demonstration.
“We’re five blokes with one aeroplane. Isn’t this overkill?”
It would be if you got the whole thing. You do not. A syndicate sees a calendar, a tech log, a due list and shared documents, and nothing about students, instructors, courses or compliance, because those are switched off for a group like yours. The shortness of the menu is the answer to the question.
“We manage fine on a spreadsheet.”
You do, and we would rather concede that than argue it. So here are the three things the spreadsheet cannot do: tell you the aeroplane is out of check before you book it, stop two owners taking the same slot, and produce a statement nobody disputes. If none of those has ever bitten you, keep the spreadsheet.
“What if the organiser gets bored?”
The strongest reason to move and the one nobody says out loud: the admin stops depending on one person’s goodwill. When it lives on FlyerOS instead of in the organiser’s head and their spreadsheet, the group keeps running whether or not they stay interested.