Operational context
Attendance decisions and staff reviews lived in separate tools, which created duplicate work and accountability gaps.
Back to Work
Earlier operations proof
Staff Attendance & Review System
Internal operations system for attendance, reporting, audits, and employee reviews.
Built for manager speed, permission clarity, and traceable decisions.
Product pressure
The same system had to support fast daily inputs, role boundaries, and reliable history for later review.
What I built
A connected manager system that treats auditability, reporting, and review context as product requirements from day one.
Why it matters
It reduces operational friction while improving traceability and handoff quality between day-to-day management and formal reviews.
Technical notes
- React UI built for dense manager-facing workflows and fast scanning
- Firebase-backed sync with role-aware access rules
- Audit logs and reporting connected directly to attendance events
- CSV export and review workflow support in the same interface
What I learned
- Dense internal tools can still feel usable when hierarchy and defaults are deliberate.
- Audit history becomes a trust feature when teams rely on it for accountability.
- Internal systems are strong portfolio evidence when they solve real operational friction.