Creating A Simple App For Eisteddfod Schedules And Results

An eisteddfod can involve hundreds of performers, several venues, volunteer stewards, adjudicators, accompanists and families moving between sessions. A printed programme remains useful, yet it can become difficult to keep accurate when entries change, a session runs late or results are announced in a different order. A simple digital schedule and results app can give everyone a dependable source of current information.

For local Welsh cultural societies, the goal does not need to be a large, expensive technology project. A well-planned app can focus on the essentials: finding an item, checking where it will take place, seeing whether a session is on time, and viewing published results. The design should support the work of an organising committee rather than create another complicated system for volunteers to manage.

This approach is also valuable for Australian Welsh communities and cultural events. A society in Sydney, Melbourne or Brisbane may be coordinating performers across a wide area, while regional groups may need a system that works reliably on variable mobile coverage. Clear information, straightforward administration and respect for privacy will matter more than a long list of impressive features.

Define The App’s Essential Purpose

Begin by identifying the problems the app must solve during a real eisteddfod day. Parents may want to locate a child’s item quickly, a performer may need to confirm a room change, and a steward may need the latest running order. The organising team needs to update this information without relying on a developer or rebuilding the whole programme.

The first version should usually include a searchable event schedule, venue and room details, item numbers, age or section categories, start times, performer names where appropriate, and a results area. A simple status such as “scheduled”, “in progress”, “delayed” or “complete” can be more useful than a complex live-tracking system.

Results should be published according to the society’s policies. Some competitions may display names and marks publicly, while others may show only section winners or prize information. Before development begins, decide what information is suitable for public viewing, what should be restricted to administrators, and how long records should remain available.

A clear scope keeps costs under control. Features such as ticket sales, video streaming, messaging, adjudicator scoring and automatic notifications can be considered later. The core application should first make the event programme and competition outcomes easy to find.

Plan The Schedule Around How People Move

A useful schedule is organised around the way visitors experience the festival. People often search by performer, item number, section, venue or time rather than reading the programme from beginning to end. The app should support each of these routes with a clean search bar and simple filters.

Venue information needs careful attention. A large event may use a main hall, school rooms, a church, a community centre and rehearsal spaces. Each location should have a consistent name, an address, accessibility information and, where useful, a short note about parking or entry points. For Australian events, this may include venues in suburban Melbourne, community halls in regional New South Wales or Welsh society gatherings in inner-city Sydney.

Schedules should cope with changes without confusing users. If a choir session moves from Room Two to the main hall, the new detail should replace the old one wherever it appears. A visible “updated” time and a short change note can help people trust the information. Avoid leaving old details in downloadable documents, cached pages or separate screens.

Time zones also deserve attention when the app is used across Australia or when overseas Welsh participants are involved. An event in Perth is operating on a different local time from Melbourne, and daylight saving can affect people joining remotely from Wales. Display the venue’s local time clearly and avoid relying on unexplained abbreviations.

Choose A Practical Technical Setup

A responsive web app may be the best starting point for many committees. Visitors can open it through a QR code printed in the programme, a link on the society’s website or a message shared through social media. They do not need to download anything from an app store, which reduces barriers for occasional visitors and older users.

A progressive web app can provide some app-like benefits, including a home-screen shortcut and limited offline access, while remaining relatively simple to maintain. This is useful when a venue has patchy reception or when many people connect to the same local network. Critical schedule data should be cached so that the programme remains available if the signal drops.

The administration area should be separate from the public display. Approved committee members can sign in to import entries, edit sessions, publish announcements and release results. Access levels are helpful: a schedule editor may not need permission to delete a whole event, while a results officer may need to update marks but not alter performer registration data.

A spreadsheet import can make the system realistic for volunteers. If the event already uses a spreadsheet containing item numbers, names, sections, times and rooms, the app should accept a well-defined template. Data validation should identify missing rooms, duplicate item numbers and invalid times before anything becomes public.

Design For Volunteers And Busy Families

The interface should be readable at a glance, especially for someone standing in a crowded foyer with one hand occupied by a programme or instrument case. Large buttons, strong contrast, plain language and uncluttered screens are more valuable than decorative animation. Users should reach a performer’s session or a results page in a few taps.

The home screen might offer four prominent choices: Today’s Schedule, Search Events, Results and Venue Information. A “What’s On Now” view can display current and upcoming sessions, with the room name and any delay notice. Families attending several sections can save selected items or create a personal view without making their details public.

Accessibility should be part of the initial design. Use text that can be enlarged, provide meaningful labels for screen readers and do not communicate important changes through colour alone. Results and schedule data should remain usable on smaller phones. If Welsh and English are both supported, language switching should be obvious and consistent throughout the app.

Australian users may be checking the schedule during an arvo break, travelling from a nearby suburb or sharing a phone between family members. A fast-loading page matters more than a large image banner. The app should work on common mobile browsers and modest devices, including those used by volunteers who are not carrying the latest smartphone.

Protect Personal Information And Results

Children’s names, age groups, photographs and performance details require particular care. Collect only the information needed to operate the event, and establish a clear policy for displaying names in the public schedule. In some cases, an item number and section may be sufficient until results are officially released.

The application should use secure connections, strong administrator passwords and separate accounts rather than one shared login. Keep an audit trail showing who changed a schedule entry or published a result. This helps resolve mistakes quickly and provides accountability when several volunteers are working across the festival.

Australian privacy obligations should be considered alongside the society’s own safeguarding policies. If registration or contact information is stored, explain why it is collected, where it is held and who can access it. The committee should also consider whether an external hosting provider stores data overseas and whether its terms suit the organisation’s responsibilities.

Results need a controlled publishing process. A results officer can enter marks privately, review spelling and placings, and then select “publish” when the adjudication is complete. A correction should be labelled clearly rather than silently changing a published result, particularly if certificates or announcements have already been made.

Test, Launch And Improve The Service

Testing should happen with realistic event data rather than a few sample entries. Load a full day of sessions, multiple rooms, shared performers and several result categories. Ask volunteers to find a particular item, update a delay, publish a winner and correct a misspelled name without technical assistance.

Run a live trial before the main festival. A small Welsh singing workshop, folk dancing gathering or local competition can reveal practical issues such as poor Wi-Fi near the stage, confusing venue labels or an administration screen that is too slow under pressure. In Queensland, an outdoor event may also need a plan for sudden weather changes and venue relocation.

Prepare a fallback process. Keep a printable schedule, a downloadable PDF or a spreadsheet that can be accessed by authorised staff if the app is unavailable. Display a short link and QR code at entrances, information desks and major rooms, but make sure people can still obtain help without a smartphone.

After the event, review search terms, update frequency, support requests and common errors. The committee can then improve the following year’s workflow rather than adding features at random. Feedback from performers, parents, stewards and adjudicators will show whether the app genuinely reduced confusion.

A successful first version may eventually connect with online entries, email notices, digital programmes or a membership database. Those links should be added carefully, with clear ownership and testing. The strength of the service will come from reliable information and an easy experience, not from technical complexity.

A simple schedule and results app can help a local eisteddfod feel more welcoming, organised and accessible. Start by mapping the event’s real information flow, choose technology that volunteers can manage, and set firm rules for privacy and publishing. Cymdeithas Eisteddfodau Cymru can support committees by sharing practical guidance, encouraging tested approaches and helping local organisers preserve the human, community-focused character of the tradition.

Begin with one event, one clear data template and the smallest useful set of features. Gather feedback from the people who run and attend the festival, refine the service, and build from evidence. With careful planning, digital tools can strengthen Welsh cultural activity in Australia and beyond while keeping the eisteddfod experience personal, lively and connected.