Bobby Fitz

← All projects

Project case study

ShiftFlow

Employee scheduling and workforce operations

Workforce operations system that replaces an Access-based process and supports rotation schedules, overtime, PTO, vacancies, swaps, and payroll-related workflows.

  • Workforce operations
  • Scheduling
  • Legacy replacement

Principles demonstrated

  • Build systems, not fixes
  • Technology should reduce cognitive load
  • Leadership is measured through execution

Executive summary

ShiftFlow is an employee scheduling and workforce operations product designed to replace a fragile Access-based process.

It covers rotation schedules, overtime, PTO, vacancies, swaps, and payroll-related workflows that real operators use.

Trigger

The Access-based scheduling process became increasingly difficult to maintain as workforce rules and exception handling grew more complex.

Problem

Legacy Access tools and manual coordination create schedule risk, knowledge dependency on a few people, and error-prone payroll handoffs.

Who was affected

  • Schedulers and supervisors
  • Employees participating in rotations, PTO, and swaps
  • Payroll and operations stakeholders

Why the previous process failed

Access systems and informal scheduling coordination do not handle evolving rules, multi-person ownership, or auditability well. Exceptions become tribal knowledge.

My role

Led product thinking and solution design to replace the legacy process with a purpose-built workforce operations system.

Product decisions

  • Model rotation, overtime, vacancies, and swaps as first-class workflows
  • Design for operators, not generic calendar aesthetics alone
  • Include payroll-related handoffs inside the product boundary

Build-order rationale

Establish a trustworthy schedule core before advanced automation. Exception workflows only help after the base rotation model is reliable.

Architecture

Core capabilities

  • Rotation schedule management
  • Overtime handling
  • PTO workflows
  • Vacancy management
  • Shift swaps
  • Payroll-related workflows
  • Reporting

Technical stack

Constraints and tradeoffs

  • Must replace an existing Access-based process
  • Must support operational scheduling realities beyond simple shift assignment

Challenges

Business impact

Concrete project facts

Lessons learned

Workforce products succeed when they encode real exception handling. A clean calendar UI is not enough if rotation rules live outside the system.

Current status

Future roadmap

Screenshots and artifacts

Named media slots are ready for production assets. Placeholder frames stay intentional until real screenshots are supplied.

Hero view

Screenshot slot

Scheduling dashboard

Scheduling dashboard (screenshot pending)

Gallery

Screenshot slot

21-day schedule

21-day schedule (screenshot pending)

Screenshot slot

Vacancy management

Vacancy management (screenshot pending)

Screenshot slot

Employee portal

Employee portal (screenshot pending)

Screenshot slot

Payroll workflow

Payroll workflow (screenshot pending)

Screenshot slot

Reporting

Reporting (screenshot pending)

Screenshot slot

Fullscreen schedule view

Fullscreen schedule view (screenshot pending)

Screenshot slot

Mobile schedule view

Mobile schedule view (screenshot pending)

Architecture diagram

Screenshot slot

Architecture diagram

Architecture diagram (screenshot pending)

Before and after

Screenshot slot

Access-based process before

Access-based process before (screenshot pending)

Screenshot slot

ShiftFlow after

ShiftFlow after (screenshot pending)

Continue

Interested in similar operational systems work, or ready to discuss a role or engagement?