# Quenique

> A queueing and passenger management platform for pumpboat operations, bringing real-time tracking, analytics, and automation to a process that used to run on memory and paper.

- URL: https://renato-dulog.is-a.dev/works/quenique
- Author: Renato Dulog
- Category: web app
- Tech stack: Next JS, MongoDB, Tailwind CSS, Typescript, ShadCN, Socket IO, Framer Motion
- Source: https://github.com/renskiedulog/capstone
- Updated: 2026-06-07

**QueNique** is a queueing and passenger management platform built specifically for pumpboat operations. It centralizes real-time queue tracking, boat scheduling, analytics, and notifications into one system for both staff and passengers.

### What It Does

- Live dashboard for queue status and departures
- Role-based admin controls for staff
- Passenger-facing view for position in queue and departure times
- Reporting and analytics for historical operations and patterns

### Why It Exists

Pumpboat terminals often rely on:

- Word-of-mouth updates
- Manual, improvised lines
- Memory-based tracking of departures
- Little to no historical record when issues arise

QueNique replaces this with a structured, reliable system that staff can use daily and passengers can trust for clear information.

### How It Was Built

1. **Mapped the real workflow first**
1. **Designed for two audiences**
  - Staff: control, visibility, live states, schedules, and reports
  - Passengers: simple, clear status and timing
1. **Implemented real-time data flows**

### What Makes QueNique Unique

- **Workflow-first design**: Every screen maps to a real step in pumpboat queue operations, not a generic booking flow.
- **Actionable data**: Daily operations become graphs, statistics, and historical logs that reveal patterns and support better decisions.
- **Built for actual users**: Role-based access and focused interfaces give each user only what they need, no clutter.

### Key Takeaway

The core lesson from QueNique is that building effective software for real-world operations starts with deeply understanding the process, not the tech stack. Translating a messy, human workflow into a structured, dependable system was the real capstone challenge, and the main achievement of this project.