The hours a syndicate organiser never gets back
Nobody sets out to take on a second job. They agree to “look after the ticket”, and a year later they are the person who chases six people for four dollars each, every week, forever.
The reason it creeps up is that no single task is big enough to complain about. It is two minutes here and five minutes there. So it is worth actually adding it up.
Where the time goes
Take a middling syndicate: twelve members, playing both Wednesday and Saturday. That is 104 draws a year.
Before each draw — check who is still in, work out the split of the ticket cost, reduce twelve balances, and let people know they are in it. Even done briskly, that is five minutes. Over 104 draws: about nine hours.
After each draw — check the result, and when there is a win, divide it across the members who were actually on that draw, credit each one, and tell everybody. Small wins are more common than people remember, and they are the fiddly ones. Call it four minutes a draw: about seven hours.
Payments — contributions arrive by transfer, in cash, in advance, in arrears. Reconciling a bank statement against a member list once a fortnight, at fifteen minutes a session: about six and a half hours.
Questions — “Am I still in?”, “How much do I owe?”, “Did we win anything last week?”, “What happened to my twenty dollars?”. Two or three a week, two minutes each: about four hours.
The annual reckoning — someone leaves and wants their balance out. Someone joins mid-run. Somebody’s total does not reconcile and you spend an evening with two spreadsheet versions open trying to find where it diverged. Conservatively: three hours.
That is around thirty hours a year — the better part of four working days — spent on arithmetic and messaging, for no pay, on behalf of people who are mostly unaware it is happening.
And the count above assumes it all goes right.
The part that isn’t the time
The hours are the visible cost. The invisible one is that every one of those jobs is a chance to make a mistake that you will personally have to explain.
Charge eleven members for a draw twelve were in, and someone is quietly a dollar short for the rest of the year. Divide a $140 win by the current member list rather than the list from that Saturday, and someone who left in July has been paid and someone who joined in August has not. Miss a payment on the statement and a member is told they owe money they already handed over — which is the single fastest way to make an ordinary favour feel like an accusation.
These are not exotic failures. They are the normal failure modes of doing careful work quickly, in a spreadsheet, on a Sunday night.
What automation actually removes
The useful question is not “can software do this faster”, but “which of these jobs can stop being a job at all”.
Draw creation and cost splitting. If the same numbers play every draw — a standing Lotto subscription, or a line you buy by hand each week — upload that ticket once and every draw is generated from it. You are not re-entering the same numbers weekly. It snapshots the members who are active at that moment, splits the ticket cost evenly between them, and takes it off their balances. Nine hours, gone — not sped up, removed.
Play a different ticket for a draw and you add that one yourself, which is a few seconds rather than nothing. The splitting, the charging and the emails still happen on their own, so most of that nine hours still goes.
Telling people they are in. Each member is emailed automatically when the draw is created, with the ticket photo and their share of the cost. Nobody has to be told; they are told.
Dividing a win. You enter what the ticket won. The division across the members on that draw, the crediting, and the emails all follow from that one entry. Seven hours becomes a few minutes a month.
Payments. Batch entry: one screen with repeating lines, so a session of statement reconciliation is one form and one save rather than twenty separate edits. Realistically this halves the time rather than eliminating it — someone still has to read the bank statement.
Questions. Most questions are asked because nobody knows. When every member receives the entry email — with their own balances in it — and the results email after each draw, the questions largely stop being asked, because they have already been answered.
The annual reckoning. An append-only ledger means the history is always there: every movement, with a reason and the name of whoever recorded it. Reconciling is reading, not archaeology.
Add it up and the recurring work drops to entering results and recording payments — something like two to three hours a year, down from thirty.
The honest caveats
Software does not buy the ticket. Somebody still has to play it, and somebody still has to hold and distribute the actual money — Lotto Syndicate Manager records the transactions, it does not process them.
Setup is not zero either: naming the syndicate, setting the draw days and ticket cost, and entering members with their opening balances takes an evening if you are carrying history across from a spreadsheet.
But that is an evening once, against four days a year forever. And the thing you get back is not really the time. It is not being the single point of failure for twelve people’s money.
Want the arithmetic to stop being your problem? Start a syndicate free for three months and see what a draw day looks like when it looks after itself.