Back to Work

Case study

Staff Attendance & Review System

An internal staff operations platform for attendance, reporting, audit history, and employee review workflows.

This project demonstrates the kind of operational tooling I like building most: high-frequency, manager-facing software where clarity, speed, and traceability all have to coexist.

At a glance

  • Manager-facing operations platform joining attendance entry, reporting, audit history, and employee review in one system.
  • Dense daily workflow optimized for speed without losing traceability or role-aware control.
  • Longer-horizon staff development kept in the same operating context instead of split into disconnected tools.

What I was solving

Attendance, staff records, reporting, and review often end up spread across separate tools or documents. I wanted one internal platform where managers could operate quickly and still keep context intact over time.

What made it hard

Manager workflows are dense, high-frequency, and easy to slow down with too much chrome. At the same time, permissions, live data, and audit requirements make the underlying system too important to simplify carelessly.

What I chose

I treated auditability and role-aware access as part of the primary UX, not backend extras. Real-time sync, logs, and review history all reinforce trust in a system that affects everyday management decisions.

How it feels to use

The UI is intentionally dense but organized around the manager hot path: fast attendance entry, clear reporting transitions, and review workflows that feel connected to daily operations rather than buried in an admin back office.

What it shows

  • React frontend built for dense manager-facing workflows
  • Firebase-backed live sync and role-aware data access
  • Audit logs and reporting layers tied to day-to-day operations
  • CSV export and review workflows inside the same operating surface

What I learned

  • Operational density is not a flaw if the hierarchy supports fast scanning and confident input.
  • Audit history becomes a UX feature when people rely on a system for accountability.
  • Connecting daily workflows to longer-term review creates a more useful internal platform than splitting them apart.