Face-scan verification
A stronger identity check around sensitive employee check-in actions.
Workforce SaaS case study
A secure check-in system built for pharmacy operations.
A production-style workforce platform that brings staff check-ins, employee records, payroll review, location management, and sensitive administrative work into one focused system.
01 / 05
Employee management
Project overview
One operational view for staff activity.
The system pairs a straightforward check-in experience with a protected administration area for the records and decisions behind it. Private names and account details are blurred in the public gallery.
Employee, location, check-in, payroll, and settings administration
Face verification around sensitive attendance actions
Filters, manual punch controls, record locking, and exports
Private operational data separated from the public experience
Operational challenge
Attendance is simple until the exceptions arrive.
A useful check-in system has to do more than record a timestamp. A pharmacy operation also needs confidence in who completed the action, a clear location and timezone context, a way to correct legitimate mistakes, and records that can support payroll review.
The administrative side therefore carries most of the complexity: employee accounts, roles, rates, locations, record status, manual punches, exports, and private information all need to remain understandable without making the employee-facing flow harder to use.
This public case study describes the delivered product surfaces and technical shape. It does not invent time-savings, financial returns, or adoption figures that were not formally measured.
System capabilities
Designed around the real administrative work.
Protected access
Authenticated, role-aware administration for private workforce information.
Employee operations
Searchable records, account controls, rates, roles, and employee status management.
Check-in records
Punch history, date filters, manual corrections, locked records, and operational review.
Multi-location setup
Location details, timezones, assignments, and controls for more than one operating site.
Payroll reporting
Hours, rates, totals, summaries, and CSV exports for downstream review.
Architecture decisions
Structure the product around trust and review.
The system design separates quick daily actions from sensitive operational controls while preserving the context administrators need to review exceptions.
Separate user surfaces
Keep the focused employee check-in flow distinct from the denser administration experience used to review and manage records.
Role-aware boundaries
Protect employee, payroll, location, and settings work behind authenticated administrative access instead of exposing one shared interface.
Identity verification step
Use browser-based face tooling around attendance actions where stronger confidence is more useful than a simple unchecked button press.
Reviewable record states
Support filters, manual corrections, locking, and exports so operational exceptions can be reviewed rather than silently overwritten.
Technical shape
A web stack selected for secure, usable operations.
Node.js and Express API
Supabase data services
Secure authentication and role-aware access
ONNX Runtime Web and MediaPipe face tooling
Responsive administration interfaces
Vercel deployment workflow
Verification
Check the workflows that carry operational risk.
Employee check-in and administrative flows remain usable at narrow mobile widths.
Private administration routes require authenticated access and appropriate roles.
Location and timezone context remains attached to attendance records and review flows.
Manual record changes, locking, filtering, and exports have visible states and feedback.
Public portfolio screenshots obscure employee names and other private account details.
Related capability
Planning a dashboard, portal, or internal system?
See how custom software projects are scoped around users, roles, data, review states, and the smallest useful release.
Contact
Have an operational system in mind?
Share the workflow, users, private data considerations, and the work the system needs to make easier.