4 months · in production / active

Gym operations across 5+ branches

One platform for the daily work of a regional gym chain: attendance, schedules, payroll adjustments, customer visits, and stock. I built and deployed it end to end in four months, for use across 5+ branches.

  • 5+ branches
  • Four-month delivery
  • Built end to end
My role
Full-stack development & deployment
Selected stack
Django · Next.js · PostgreSQL

Inside the system

Different jobs. One shared record.

  • AttendanceOn-site check-in and check-out
  • PeopleShifts, schedules, and leave
  • AdjustmentsPayments, reimbursements, bonuses
  • CustomersVisit tracking across branches
  • StockInventory and branch management
One operations platformNext.js interface · Django application · PostgreSQL data
Delivered system scope · Five areas of daily work across 5+ branches. Client interfaces and data remain private.
01 / Context

One business, several moving parts

Staff attendance, shift changes, leave requests, payroll adjustments, visits, and stock all affect the same daily operation. Each branch needed to record its work while managers needed a shared view across the business.

The brief was to bring those processes into one usable system. The client interface and operational data are private; the map above shows the delivered scope.

02 / Decisions

Build around the daily workflow

I handled scoping, the data model, backend, frontend, and deployment. Django and PostgreSQL support the application, with a Next.js interface for staff and managers.

Attendance uses a branch geofence to check the reported location at clock-in and clock-out. Schedules and leave sit alongside payments, reimbursements, and bonuses, so related work can be managed in the same platform.

  • Geofenced employee check-in and check-out
  • Shifts, schedules, and leave management
  • Payroll adjustments, reimbursements, and bonuses
  • Customer visits, branch records, and stock management
03 / Delivery

Delivered across 5+ branches

The platform is in production across the branch network. Staff and managers use one system for the operational processes that were in scope, from attendance through stock.

The important design work was connecting those records while keeping each daily task straightforward. That is the approach I bring to other business systems: understand the work, define the shared model, then build the interfaces people need.

Your project

Need something
like this?

Tell me what your team needs to do and what is getting in the way.

Talk about your project