BafsWorkout

Context

A large on-site fitness assessment moves participants through several stations while multiple staff members record results at the same time. The software has to support the physical event, not merely store a finished score afterward.

Problem

Paper forms and disconnected files make it easy for a measurement to lose its participant, station, or sequence. Staff also need to know who is waiting, which tests are complete, and where an incomplete record should go next without slowing the assessment floor.

My role

I worked from the assessment requirements through product design, bilingual interface decisions, workflow modelling, and full-stack implementation. The system was shaped around how the testing event actually operates on site.

What was built

• Participant registration, barcode identification, and one continuous assessment record.
• A defined sequence for each physical-fitness testing station.
• Visible progress and completion status.
• Station-specific result entry designed for rapid use.
• Thai and English interfaces for staff and participants.

Design story

Let the event set the structure

The public introduction now follows a testing round from setup to participant selection, station entry, and results. A numbered station example makes incomplete work visible before someone enters the application. Its numbers explain the flow; they are not a live assessment.

Give each person a relevant view

The round administrator, station team, and participant work with the same testing round but need different actions. The design explains those responsibilities separately. Participant results and exercise guidance complete the journey after measurements have been recorded.

Key workflow

1. Register or locate the participant.
2. Confirm the next required station.
3. Record the station result against the same participant record.
4. Move the participant forward while keeping incomplete steps visible.
5. Review the completed assessment and prepare the result for the programme team.

Constraints

The interface must work on a busy assessment floor, where staff cannot stop to interpret subtle controls. Actions need generous targets, status must remain obvious, and the system must tolerate participants moving at different speeds.

Verified operational footprint

The snapshot verified on 29 August 2026 records 418 tested participant records, 1,229 fitness examination records, and 1,204 completed basic examinations. These are system usage counts, not evidence of improved health outcomes or efficiency.

Implementation recorded in the original case study

Front end: Blazor WebAssembly, Microsoft Fluent UI, Syncfusion and ECharts. Back end: ASP.NET Core (.NET 8), PostgreSQL and Entity Framework Core. Authentication: Suttisak.Blazor.Identity and Passkey.

These implementation details are retained from the original case study; this content refresh does not establish the application's current package versions.

Image and source notes

Public introduction, October 2026. The station-progress panel is an explanatory example, not a participant record.

Content refreshed on 7 November 2026 from the published Quack & Honk BafsWorkout page.