Role-specific surfaces
Administrators and members receive different capabilities without duplicating the underlying business logic.
03 / Operational platform
Mess Management
A role-aware operations system for attendance, meal planning, billing, reporting, and member management.
This project replaces fragmented cafeteria administration with one system designed around the daily decisions of members and operators.
The challenge
Attendance, menus, payments, and billing affect one another but are often tracked separately. The core challenge was preserving reliable records while giving administrators useful control and members a simple experience.
The approach
I modeled the product around meal-level events and role-specific workflows. Administrative controls, member actions, reporting, and billing use the same underlying operational record.
02 / System story
One connected product flow.
01Authenticate
02Select role
03Record activity
04Calculate billing
05Export reports
Core stack
ASP.NET Core 8C#Entity FrameworkJWTSQL
03 / Key decisions
Designed around the hard parts.
The most important work is often deciding what the system should make obvious, durable, or intentionally limited.
Meal-wise records
Attendance is captured at the level where billing and operational decisions actually happen.
Reports as a core workflow
Export and reporting are treated as daily operational tools, not as a final dashboard add-on.
04 / Current outcome
The system combines secure authentication, role-based access, attendance, payments, menus, suggestions, exports, and automated billing in one ASP.NET Core application.
This case study reports only publicly supportable outcomes. No usage or business metrics have been invented.