Home · Solutions · Operations & production · Club competitions: from entries to results
Solution · Operations & productionThe shooter enters by himself, the start list builds itself, and the referee referees instead of counting
Club competitions: from entries to results
A robot collects entries from a form, watches the start fees, builds start lists by relay and event, and turns the scores entered by referees into a bulletin with the classification, ready to publish the same evening. Refereeing, protests and the entire shooting side of the match stay with people.
Executive summary
A club match today is organised by a mailbox and a spreadsheet: entries by email, fees fished out of the statement, a start list in three versions, and after the match an evening of retyping score cards and assembling the bulletin.
The robot takes entries from a form, watches the fees, builds start lists by relay and event, publishes them in advance and sends every shooter his start time.
Scores entered by referees in a simple view turn into a classification and a bulletin from a template; shooters get the results the same evening, and the club gets a match archive without a binder.
an entry form and match register in SharePoint; fees from the statement export; referees entering scores in Power Apps; the bulletin and classification from a template
Business problem
Most of the work around a match happens off the range
A club match looks simple until you organise one. Entries arrive by email, by text and in passing between sessions, so the start list grows in a spreadsheet with as many versions as editors. Start fees land in the account under references that need interpreting, or in a cash box on match day, and the treasurer reconciles one with the other long after it is all over.
On match day, paper takes charge: relay lists printed in the morning can be stale before the first shot, because somebody dropped out, somebody joined, somebody needs to shoot early because of a work shift. Referees keep score cards by hand, which is fine, but then somebody has to retype those cards into a spreadsheet, compute the classification and not slip up on shoot-offs and event weightings.
In the evening the organiser, usually the same person as always, assembles the bulletin: tables, categories, corrections after a call from a shooter who counted differently. Publishing at 11:40 pm is not an anecdote, it is a ritual. And in the morning somebody still asks when the results will be out, because he missed the email.
The club does not need a league system costing thousands; it needs the part that is neither refereeing nor shooting taken off its hands: entries, fees, lists, counting and publication. All of that is secretarial work, and the secretary can be a robot.
How it works today
Below is what the work looks like before anything is automated.
- PersonEntries by email, by text and verbally between sessions
- Risk of errorA start list in a spreadsheet with as many versions as editors
- Risk of errorStart fees reconciled with the statement and the cash box long after the match
- WaitingMorning relay lists stale before the first shot
- Risk of errorReferees’ score cards retyped into a spreadsheet in the evening
- WaitingThe bulletin published near midnight, the questions arriving anyway at dawn
Why the current process costs more than it appears
The bill that never shows up in a budget.
- How many hours does one match cost beyond the range day itself: entries, lists, fees, results?
- How many corrections does the start list absorb between publication and the first shot?
- How long after the match do shooters wait for the results bulletin?
- How many start fees from the last match were reconciled with the list only after the fact?
Cost of inaction
The model assumes 10 matches a year of about 40 shooters and 12 hours of organisational work per edition, counting entries, fees, lists and results. The person who publishes bulletins before midnight knows your own numbers best.
The estimate omits the hardest cost to count: the burnout of the one volunteer all editions hang on. Clubs lose such people not to membership fees but to spreadsheets.
A model organisation with realistic proportions – the numbers exist so you can run the same maths on your own data; they are not a client result.
A shooting club: 10 matches a year, about 40 shooters across several events, entries by email, fees by transfer and cash, results in a spreadsheet, Microsoft 365.
Until now: a start list in a spreadsheet, three versions before match day, the bulletin published late in the evening by the vice-president.
Two weeks before the match the robot opens entries: a form with event choice and relay preference. Every entry gets a confirmation and an individual transfer reference.
Three days out, the robot closes the list, builds relays by event and preference, publishes the start list and sends everyone his start time. A last-minute change is one edit in the register, not a new spreadsheet.
On match day the referees enter scores in a simple phone or tablet view, event by event. Paper score cards remain as the source document, but nobody retypes them at night.
At 6:20 pm the robot assembles the bulletin from the template: classifications, categories, shoot-offs marked by the referee. Shooters get a link, the club gets an archive. A model scenario, not a record of a specific match.
Proposed solution
Entries come through a form: the shooter picks events and a preferred relay, and the robot confirms, watches the entry limit, keeps a waiting list and recognises the start fee by an individual transfer reference from the statement export; a cash payment on match day is ticked off with one tap. The start list builds itself by the rules you set: events, relays, breaks for referees, and is published in advance, with every correction being a register edit visible everywhere at once.
On match day the referees get a simple view for entering scores, event by event, shooter by shooter. Paper score cards can remain as the source document; the difference is that nobody retypes them afterwards. The robot computes the classification by the weightings and rules of your regulations, and everything that needs judgement, including shoot-offs and protests, it flags and leaves to the chief referee.
Once the chief referee approves, the robot assembles the bulletin from your template: full classifications, categories, acknowledgements, sends it to the shooters and files it in the club archive. The organiser’s evening ends with the match, not five hours later. The regulations, event weightings and sporting decisions remain entirely with the club and its referees.
UiPath Orchestrator: the entry queue, publication deadlines, retries and an audit trail of every list edit; UiPath Integration Service connectors to SharePoint, Teams and Outlook 365; Power Apps as the referee’s score-entry view
An entry form with limits and a waiting list, start-fee recognition, automatic start lists by your rules, classification computing, a template bulletin and a match archive
The club’s bank statement via CSV/MT940 export; the bulletin template in Word; optionally a club screen showing the start list and live results from the same register
How the automated process works
- AutomationA form entry confirmed, with limits and a waiting list
- AutomationThe start fee recognised by reference; cash ticked off with one tap
- SystemThe start list built by your rules and sent out with start times
- PersonReferees enter scores in a simple view; the cards remain as the source
- PersonShoot-offs and protests are decided by the chief referee; the robot only flags them
- AutomationThe bulletin with the classification assembles from the template the same evening
Human-in-the-loop model
Automation handles
- Entries, limits, the waiting list and start-fee recognition
- Start lists by the club’s rules, corrections and start-time dispatch
- Classification computing, the template bulletin and the match archive
People decide
- Refereeing, score cards and every sporting decision on match day
- Shoot-offs, protests and the chief referee’s approval of the results
- The match regulations, event weightings and categories: set by the club
Before and after
Systems and integrations
The stack is short on purpose: one engine, one execution layer, one place where a person decides.
Inputs
- the entry form with events and relay preference
- the club’s bank statement as a CSV/MT940 export
- scores entered by referees in the Power Apps view
- the chief referee’s approval of the classification
Automation layer
- UiPath Orchestrator
- UiPath Robots
- UiPath Integration Service
- UiPath Action Center
Target systems
- start lists and start times to the shooters
- a template bulletin with the classification
- a match archive in SharePoint
Human touchpoints: relay-building rules before the season; referees entering scores; the chief referee approving the bulletin
Technologies used
the entry queue, publication deadlines, a trail of every list edit
Ascore entry on a phone or tablet, event by event
Athe register, the match channel, dispatches to shooters
Aclassifications and categories assembled automatically after approval
Afees from the export; on-site display of lists and results as you wish
BHow we deliver this
From this description to a running process
We deliver this solution through our process automation service: first we measure the process on company data, then we build, test and maintain the robots.
Industry
Case studies
Delivered client work is described under Case studies.
Illustrative economic model
Numbers you can check against your own data.
The model assumes 10 matches a year of 40 shooters; the harder value to count is the volunteer who does not burn out on spreadsheets. Put your own figures into the calculator beside.
Run the numbers on your data
An illustrative estimate based on your inputs. It models freed capacity, not promised savings.
Business benefits
- Entries and fees tie themselves together before anyone opens a spreadsheet
- The start list has one version, and every correction is visible everywhere at once
- Referees enter scores once; nobody retypes cards at night
- The bulletin with the classification goes out the same evening, with an archive for years
- The organiser goes home with the shooters, not after midnight
The management view
- The club can run more matches with the same people, because an edition stops costing evenings
- Results published promptly raise the match’s standing with shooters and sponsors
- An archive of classifications and turnout gives the board hard data for season planning
Board-level KPIs
organisation hours per match · time from the last shot to the bulletin · start-list corrections after publication · fees reconciled before match day · entry turnout year over year
Security and governance
The automation has exactly the permissions it needs. Not one more.
- Shooter data processed solely for entries, fees and classification, in line with GDPR
- Scores are entered solely by referees, and the classification is approved by the chief referee; the robot computes, it does not adjudicate
- Every start-list and score correction is logged: who, when, what changed
- The robot has no access to the club account; it reads only the treasurer’s statement export
- Data stays in your Microsoft 365 tenant; the robots run in the EU region of UiPath Automation Cloud
Why now
The match season is planned in advance; a system started now serves every edition this year.
Shooters compare clubs by organisation too: clean lists and fast results are the cheapest promotion a match can get.
The club’s busiest volunteer does not need a raise, he needs the spreadsheets taken off him.
Relevant executive roles
More matches without more evenings; the archive and reconciliations ready for the annual meeting
Scores entered once, the classification computed by the regulations, sporting decisions untouched
An entry in two minutes, the start time on his phone, results the same evening
Common questions and objections
No. The robot computes by the weightings and rules of your regulations, and everything needing judgement it flags and leaves to the chief referee. The bulletin assembles only after his approval.
We write the classification rules down from your regulations at the start, and those rules drive the computing. A regulations change is a rules change in one place, not a spreadsheet rebuild.
Staff tick the payment off with one tap at check-in and the shooter’s status changes immediately. The cash box stops being a separate bookkeeping system.
When this is not the right solution
- Matches of a rank requiring a homologated results system: then we integrate with it, we do not replace it
- A ten-person match twice a year: a spreadsheet genuinely suffices
- Expecting electronic targets and live scoring hardware: that is separate equipment on a different price shelf
A question for the next management meeting
At what hour after our last match did the organiser send the bulletin, and who thanked him for that evening?
Implementation approach
Scope without ambiguity, before anything is signed.
We deliver
- An entry form with limits, a waiting list and confirmations
- Start-fee recognition from the statement export and one-tap cash ticking
- Start lists by your rules with start-time dispatch
- A referee score-entry view and a template bulletin after approval
- A match archive and two weeks of assistance after the first edition
We need from you
- The match regulations with event weightings and classification rules
- Access to Microsoft 365 and the club account’s statement export
- An hour with the organiser and chief referee to walk the last edition
Stages
Discovery
How the last match ran from announcement to bulletin; an hour’s conversation
Rules
Events, weightings, relays, limits, the bulletin template
Build
Entries, fees, lists, the referee view, the bulletin generator
Parallel run
One match run in parallel: the spreadsheet beside the system
Go-live
The next match fully in the new mode; a review after the bulletin
A quick win. Most of the work is a one-off write-up of the classification rules from your regulations; after that each edition is a form, referees’ entries and one button.
Sunday, 6:20 pm: the last shot fell at 5:40, and the bulletin with the full classification is already up. The vice-president eats dinner at home, for the first time in years.
Send us the regulations of your last match and the hour the bulletin went out. We will send back a draft of the entry and results flow and the arithmetic of the hours a season can give back to the club.
Count your last matchThe neighbouring process usually has the same problem
The course starts on Saturday. The sign-ups sit in emails, the payments in the bank statement, the certificates in a word processor.
See the solution Management & planningUtilisation of lanes, rooms and studios, weeklyEvenings burst at the seams, mornings stand empty, and the price list has been one for years.
See the solution HR & peopleInstructor payouts without the spreadsheetThree rates, four contracts, hours from memory. Payday ends in a discussion every month.
See the solution