Managing competitor scores and results with spreadsheets

A well-designed spreadsheet can turn a busy eisteddfod results desk into a calm, reliable operation. It gives organisers one place to record competitor details, enter marks, apply the rules, check totals and prepare results for announcements. For volunteer committees, this reduces repeated calculations and makes it easier to find an entry when a judge or parent needs clarification.

The best workbook is simple enough for a new volunteer to use during a full programme, yet structured enough to handle solo items, duets, choirs, folk dancing, folk singing and cerdd dant. Whether an event is held in a community hall in Brisbane, a school auditorium in Melbourne or a Welsh society venue in Sydney, consistent data entry matters as much as the formulas.

Spreadsheet approach Best suited to Main benefit Main risk
Basic score sheet Small events with few classes Fast to build and understand More manual checking
Class-by-class workbook Medium eisteddfodau with several judges Keeps each competition easy to follow Requires careful sheet naming
Central results database Large programmes and multiple venues Strong search, filtering and reporting Needs more setup and training
Shared online workbook Committees working from different locations Live access and automatic saving Internet or permission problems
Offline master workbook Event-day scoring with uncertain connectivity Reliable without a network Results must be backed up manually

Plan the workbook around the event

Begin by listing the information the committee actually needs. A competitor register might include an entry number, class number, competitor name, age group, school or organisation, item title, contact details and payment status. A scoring sheet needs some of the same fields, but its priority is the judge’s marks, penalties, rank and status.

Use separate worksheets for different jobs rather than placing every detail in one crowded grid. A practical structure could include:

Give every competitor and class a unique identifier. Names can be entered in different ways, especially when a child’s name, school and parent contact are recorded by different volunteers. An entry number such as F203 or D118 is more dependable than searching by name alone. The class code should also remain stable if the programme is rearranged.

Set the date format to the Australian convention, DD/MM/YYYY, and record event times with the correct local time zone when files are shared across states. A committee coordinating between Perth and Sydney should be aware of Australian Western Standard Time and Australian Eastern Standard Time, including daylight saving changes. Clear labels prevent an online meeting or results export from being misunderstood.

Build a consistent scoring sheet

Create one row for each competitor and one column for each scoring component. For a singing class, the columns might cover vocal quality, diction, musicality, interpretation and presentation. A folk dance class could use timing, technique, teamwork, costume and cultural expression. The scoring categories should come from the published rules, so the spreadsheet reflects the judging system rather than inventing a new one.

If a class has three judges, keep each judge’s marks in separate columns. For example, Judge 1 might occupy columns F to J, Judge 2 K to O and Judge 3 P to T. A total column can then add all permitted marks. If the judges use different maximum scores, record the maximum beside each category and calculate a percentage rather than comparing raw totals.

A formula such as =SUM(F2:T2) is suitable only when every mark in that range should be included. A safer design adds defined components individually, for example =SUM(F2:J2)+SUM(K2:O2)+SUM(P2:T2). This avoids accidentally including a note, penalty or hidden helper column. If penalties are recorded separately, use a clear formula such as =RawTotal2-Penalty2.

Protect formula cells so volunteers cannot overwrite them while entering scores. Apply data validation to mark columns, limiting values to the permitted range, such as 0 to 10 or 0 to 25. Validation can also prevent a user from entering text in a numerical field. Use conditional formatting to highlight blank marks, scores above the maximum and duplicated entry numbers.

For sensitive information, keep contact details and children’s personal data in a restricted workbook or protected sheet. The public results file should generally contain only the information needed for announcements and publication. A separate version can include full administrative details for authorised committee members.

Automate totals, rankings and ties

Once marks are entered, automation should handle repetitive work while leaving the rules visible. Use formulas to calculate raw totals, average marks, percentages and adjusted scores. If the event requires a dropped score, make the method explicit. For three judges, a formula might remove the lowest mark, but that approach should be used only when the eisteddfod rules approve it.

Ranking formulas vary by spreadsheet application and workbook design. In Excel or Google Sheets, a rank function can order totals from highest to lowest, while COUNTIF or COUNTIFS can help identify duplicates. A simple rank formula might be =RANK.EQ(U2,$U$2:$U$20,0), where column U contains the final score. If ties are allowed, the same rank may appear more than once. If ties must be resolved, add a published tie-break rule, such as the higher interpretation mark or the chairperson’s decision.

Do not hide tie-breaking logic inside a complicated formula that only one person understands. Add columns for the primary total, tie-break score and final placing. This makes the decision auditable. A status field can distinguish Winner, Runner-up, Highly commended, Equal first, Withdrawn and Disqualified. Text labels are easier for announcers to interpret than unexplained numbers.

Create a dashboard for the results desk, showing class code, class title, competitor, final score, placing and award. Filters allow a volunteer to display one class at a time. A pivot table can summarise entries by age group, school, suburb or cultural category, which may help with participation reporting after the event. Save a locked master copy before results are edited for publication.

Check the data before announcing results

Human checking remains essential. Before a class is called, compare the number of competitors listed in the programme with the number of score rows. Confirm that every judge’s mark is present, every competitor has the correct class and no withdrawn entry has been included in the ranking. A short verification checklist can prevent an embarrassing announcement caused by one blank cell.

Use a separate audit column to record who entered or checked a score and when. In a shared Google Sheet, version history can show changes, but a manual check column is still useful when several volunteers work during a noisy event. In Excel, save dated copies such as Eisteddfod_Results_Master_2025-08-16.xlsx rather than repeatedly replacing the same file.

Export a PDF of each completed class after the chairperson or authorised official approves it. A PDF preserves the appearance of the result and is less likely to change when opened on another computer. Keep the editable spreadsheet as the official working record, and use a PDF or carefully formatted CSV for the announcer, website administrator or printer.

For an Australian event, test the file on the equipment that will be used on the day. A workbook built on a committee member’s modern laptop may behave differently on an older venue computer. Check printer settings, page breaks, projector readability and whether Excel or Google Sheets is available. If the venue’s internet service is unreliable, download an offline copy and store backups on an encrypted USB drive held by an authorised organiser.

Results should be released consistently and respectfully. Children’s full names, schools and contact information should not be placed in a public file unless the committee has a sound reason and appropriate permission. A public report can show competitor name, class, placing and award while keeping registration details private.

Use results to strengthen the community

A spreadsheet is more than a mark calculator. Over several years, carefully managed records can show which classes attract entries, which age groups need encouragement and whether workshops lead to new participation. A committee might discover strong interest in folk singing but fewer entries in cerdd dant, then plan a development session with an experienced tutor.

Keep historical workbooks in a consistent format so annual comparisons remain meaningful. Record the event year, venue, class rules and judging scale. If a class changes from a 100-point system to a 50-point system, note the change rather than comparing percentages without context. A small data dictionary explaining each column will help future volunteers understand old files.

Cultural events benefit from the same care for continuity seen in traditional craft methods, where knowledge is carried forward while techniques adapt to new circumstances. A spreadsheet cannot preserve a tradition by itself, yet it can document participation, support fair administration and give organisers evidence when applying for council grants, community funding or local sponsorship.

Use summaries carefully when speaking to funders or partners. A report might show the number of competitors, volunteer hours, workshops delivered and schools or community groups involved. Australian committees can present these figures to local councils, Welsh societies and arts supporters, using Australian dollars for budgets and clearly separating entry income, sponsorship, venue costs and prize expenses. Accurate results data strengthens the wider case for sustaining local eisteddfodau.

The workbook should serve people rather than dictate the event. Judges need an uncluttered scoring interface, announcers need clear placings, volunteers need straightforward instructions and competitors need confidence that marks have been recorded fairly. Ask two or three volunteers to test the system with sample entries before opening registration. Include unusual cases such as a late withdrawal, equal scores, a missing judge’s mark and a competitor entered in the wrong age group.

Keep a one-page operating guide beside the event computer. It should explain where to enter marks, how to correct an error, who can approve changes, how to save a backup and how to export results. This small document is valuable when the usual spreadsheet expert is absent or when a last-minute volunteer joins the results desk.

Start with one well-structured workbook for the next eisteddfod, test it with sample scores and have an authorised committee member verify the formulas. Once the process works, reuse the template for future classes and events, updating the rules without losing the clear audit trail. Reliable score management gives judges and volunteers more time to focus on the performances, the people and the living Welsh culture at the heart of the festival.