Bookings Tape Chart

Problem

• Streamline charged per property and didn't fit internal workflows.
• Teams needed fast answers on availability, pricing, reservations, and conflicts.
• Booking state spread across systems made cross-team coordination hard.

Solution

• One property-by-date view of pricing, availability, reservations, owner stays, blocks, and conflicts.
• Rows are homes, columns are dates, cells show nightly state with multi-day spans.
• One shared operational surface for managing booking state across the portfolio.

System Design

The tape chart sat on top of a property-date state engine that merged raw pricing, availability, reservation, and block data into one canonical state model consumed by the UI.

What I Owned

• Led the engineering pod across PMs, developers, revenue stakeholders, operations, and guest-experience teams.
• Scoped the system, broke it into engineering milestones, coordinated implementation, made architecture decisions, reviewed work, and translated complex operational requirements into a usable internal tool.

Challenges

• Seasonal pricing: tiered seasonal pricing windows per market sat on top of the base algorithm. A home's nightly rate depended on market, date range, season tier, demand, and availability — resolved into one property-date state for accurate nightly pricing alongside reservations, owner stays, and blocks.
• Dense, responsive UI: the tape chart had to make many homes, dates, reservation spans, blocks, owner stays, pricing cells, and conflict states readable at a glance — balancing density and clarity while keeping the calendar responsive.