A club statistician, a sixty-tab spreadsheet and a hundred years of history. What it actually takes to get decades of cricket stats into one reconciled record, and what changes once it is there.
Most of the clubs we sit down with have a version of the same spreadsheet. One person built it, usually years ago, and has been quietly keeping it alive ever since. At one of the older clubs in Western Australia, that spreadsheet runs to more than sixty tabs and covers over a hundred years of cricket.
The club's statistician had done exactly what you would hope someone would do with a century of results: kept it. Season by season, tab by tab, every batting card and bowling figure typed in by hand, going back further than anyone at the club can remember first-hand. It is an enormous piece of work, and it is also a single point of failure.
Ask most clubs where their pre-2010 stats live and you tend to get a shrug, a filing cabinet, or the name of someone who left the committee years ago. The spreadsheet at this club was the opposite of that: complete, current and cared for. The problem was never the data. It was that all of it depended on one person continuing to update it by hand, forever.
We walked the committee and a few volunteers through what happens when that spreadsheet goes into BetterCricket. Not a demo on a blank system, their own hundred years, imported and reconciled against the club's live PlayHQ data, on screen in minutes. Every season, every player, every honour board entry.
The reaction in the room was not really about the software. It was relief. The statistician had spent years quietly worried about what happens to all of that history once he is no longer the one keeping it. That is a succession problem, not a stats problem, and it is the one a spreadsheet can never solve on its own.
The import is the effort. Once a club's history is in, it stays in. New games sync automatically after every match, so the job that used to repeat every week becomes something nobody has to think about again. A season's worth of scores does not wait for a volunteer to find a Thursday evening free.
The stats were the headline of that conversation because they were the most obvious hundred-year problem in the room, but they were not the only thing on the table. The same evening covered team selection and availability, vote counts for club awards, the club's social media and match-day posts, general admin, event management and bulk emails. Once a club's data is in one place, most of the jobs a committee does by hand turn out to run off the same information.
You do not need to tidy it up before you talk to us. Bring whatever you have, however many tabs it runs to, and however far back it goes. A little bit of work at the start is what secures a club's history for good, instead of leaving it one resignation away from starting again.
Why your club's history keeps getting lost · 5 reasons your cricket club is losing its stats history · What to look for in a historical stats import · Pricing · Start your free trial
BetterCricket imports a club's full history, however many decades and however many spreadsheet tabs it runs to, then keeps it current automatically after every match. Search for your club at betterat.cricket/trial to get started. Learn more
Usually nothing good. Most clubs run their history through one person's spreadsheet, and when that person leaves the committee, the updates stop and the record freezes wherever it was left. BetterCricket imports the spreadsheet once, syncs live match data automatically after that, and the record no longer depends on any one volunteer.
Yes. Clubs bring in whatever they have, however it is organised, and BetterCricket reconciles it against the club's synced PlayHQ or Play-Cricket data into one career history per player. The historical import is included in the subscription, not charged as a separate fee.
No. BetterCricket sits on top of however the club already scores and registers. Nothing about match day changes. It reads the data already being generated and reconciles it with whatever historical records the club hands over.
The import itself typically runs in minutes once the data is handed over. Most of the time in the process is a club gathering what it has, whatever shape that is in, before the sync runs.