Project 02 / 3
Club check-in
Workflow and validation-rule design
The challenge
A campus-club concept needed a simple attendance workflow. The central issue was data quality: duplicate submissions, spelling variations, and a registration that might not match an event.
My contribution
Workflow and validation-rule design
The decisions
I used a stable member ID instead of a name as the unique identity. An attendance record is unique on event ID plus member ID. A second submission returns the existing record rather than creating another row.
The evidence
The proposed data model separates members, events, and attendance. The test plan includes a repeated scan, an unknown member, a closed event, and two simultaneous submissions. Personal contact information is outside the check-in screen.
The outcome
The design produces a data model, duplicate-handling rule, and validation checklist. It is not represented as a deployed system or a security audit. A working build would need access controls and retention rules.
Limits and next steps
Use constraints to protect the data instead of relying on the interface to prevent every mistake.
The next conversation
Let’s make something useful.
Your approved contact links go here. This fictional candidate cannot be contacted.