Hotel Management System

A 3-star hotel was operating using a fragmented mix of manual processes and disconnected third-party platforms (MMT, OYO, Hosteller portals, internal registers, spreadsheets).

The result: Operational friction. Departmental misalignment. Data inconsistencies. Delays in guest servicing.

I was brought in to design a centralized, role-based web application to unify hotel operations across Admin, Reception, Housekeeping, Kitchen, and End Users.

This was not a UI project. It was a workflow system redesign.

The hotel relied on manual booking tracking, third-party platform updates, paper-based housekeeping logs, and verbal coordination between departments.

There was no single source of truth. Reception didn’t always know room readiness. Housekeeping didn’t get real-time updates. Kitchen order coordination was inconsistent. Admin had limited operational visibility.

• Create a centralized system that reduces dependency on manual tracking
• Improve inter-department coordination

This was not a linear app. It was a multi-role, interdependent operational ecosystem.

The biggest complexity challenge: Maintaining structured relationships between departments.

• Housekeeping ↔ Reception
• Reception ↔ Admin
• Kitchen ↔ Reception
• Reception ↔ Customer

I defined clear role-based access control, department-specific dashboards, controlled data visibility, and hierarchical permissions.

Each role had custom navigation, task-based interface, and contextual action triggers.

Example: Reception updates check-in → Housekeeping auto-receives cleaning status → Admin dashboard reflects occupancy in real-time. This reduced communication dependency on manual follow-ups.

Each flow required clear state transitions, status indicators, and escalation logic.

I created structured user flows before UI design. System clarity came first. Screens came later.

• Booking flow (direct + third-party)
• Room allocation logic
• Cleaning status tracking
• Food order flow (room service)
• Administrative reporting

Dashboards were not cosmetic. They were operational control centers. Each dashboard focused on real-time status, pending tasks, alerts, and critical updates.

Design followed workflow priority, not visual aesthetics.

This system aimed to replace paper logs, WhatsApp coordination, third-party dashboard switching, and manual reconciliation.

Instead of jumping between apps, staff interact with one structured system.

Accessibility was not decorative. This was critical because operational staff use the system for extended hours. Fatigue reduction matters in workflow tools.

• Color contrast compliance
• Clear typography hierarchy
• Keyboard navigation
• Status-based visual indicators

Kiosk experience was identified as an expansion opportunity. I intentionally parked it to prevent scope creep and ensure stable core system logic first.

That’s product discipline.