How cricket clubs automate match-result and team-sheet posts
Updated
The short answer
A cricket club automates its match-result and team-sheet posts by reading fixtures, named teams and scorecards from play.cricket.com.au or PlayHQ, and having software turn each one into a branded card that posts on a schedule. With Morrie the team sheets post the night before once the XI is in, results post once a game is marked final, and the committee can stop or change any post before it goes.
Why clubs automate it
Most clubs post the same things every week: who's playing, where, and how it went. Done by hand, that means someone opening a design tool, retyping names and scores from the scorecard, adding sponsor logos and posting late on a Saturday night, for every grade.
The information already exists. Your competition publishes fixtures, team lists and scorecards on play.cricket.com.au (where PlayHQ competitions are published), so the work is copying it, not creating it. That copying is what automation takes away.
What gets posted, and when
Those times are Morrie's defaults, in your club's local time, and you can change each one.
- This weekend: the round's games, posted on Thursday evening before a round.
- Team sheets: on Friday evening, or as soon as the XI is named after that. A grade with no team sheet is skipped and an empty sheet never posts.
- Match day: on the morning of the game.
- Results: once the game is marked final on PlayHQ or play.cricket.com.au, never on a guess.
- Milestones such as fifties, five-fors and big partnerships, spotted from the scorecard the night it's entered.
Keeping the committee in control
Automatic doesn't have to mean unchecked. In Morrie a new club's first posts wait for someone to approve them, and after two weekends of approving everything unchanged, Morrie asks once whether to post them automatically from then on. It never switches that on by itself.
Anyone on the committee with the club's review link can see what's queued and stop a post before it goes. If a fixture or the XI changes after a post is queued, the post is drawn from the latest data at the moment it goes out, so a late withdrawal or a change of captain flows through. Once a card has posted, nothing changes it.
Where Morrie fits
Morrie reads your grades, fixtures, live scores and scorecards from play.cricket.com.au with nothing to connect, no login or key, and can use PlayHQ's own API as a backup. Cards come in your club's colours with your sponsors on them, and post to your Facebook Page and Instagram (Threads, LinkedIn and Google Business Profile too).
The cards product, including automatic posting, is the Starter ($399/season, or $69/month) plan. Every plan and price is on morrie.io/pricing.
How to set it up in Morrie
- Find your club by suburb or postcode in Get started. Morrie reads this season's grades, fixtures and a first squad from play.cricket.com.au.
- Check your club's name, logo and colours, and pick a card design from your own cards.
- Connect your Facebook Page and Instagram under Club → Club settings → Integrations. Until Meta approves Morrie, press Get early access there and we'll set you up by hand, usually within a day.
- Switch on Post our weekend for us. It turns on the four weekly posts: this weekend, team sheets, match day and results.
- Approve the first weekend's posts when the notification arrives, and share the review link with the committee.
Common questions
Do we need a PlayHQ key to automate results?
No. Morrie reads grades, fixtures, live scores and scorecards from play.cricket.com.au with no key. A PlayHQ key is an optional backup for results and ladders.
Can we post before Facebook and Instagram are connected?
Yes. Cards can be shared from your phone before Facebook is connected; connecting it lets them post on schedule.
What if the scorecard is wrong or late?
Results only post once the game is marked final. If a result changes before a card posts, the card is redrawn from the latest data when it goes out, and the weekend check flags any game whose result, scorecard or card hasn't come through.
