(Taming the Recurring Booking Loop)
Transform a rigid, repetitive recurring booking system into a flexible, billing integrated revenue engine.
I rearchitected a brittle, “all or nothing” repetitive booking system into a live, flexible, conflict aware booking workflow . By introducing an inline exception engine and a direct invoicing pipeline, I cut the time required for complex enterprise scheduling and billing from days to hours.
A highly complex area of the software. Enterprise clients were struggling with a fragmented booking system that couldn’t handle the complexity of their operations.
- Recurring booking failures: A single conflict in a six month series could force operators to delete and recreate months of bookings just to make one change.
- Fragmented scheduling: Two separate tools were needed to manage bulk bookings and individual date exceptions, with neither reliably identifying conflicts.
- Disconnected billing: Products couldn’t be added directly to existing bookings, requiring separate transactions and invoices.
The result was a brittle, inefficient workflow where small changes could trigger hours of rework.
I designed the underlying booking logic to move away from an all or nothing model towards flexible, more exception based handling.
A real time conflict engine identifies scheduling issues before save, allowing users to resolve individual date conflicts without disrupting an entire series.
I also connected booking and billing logic, automating block booking invoices and supporting product additions without separate billing workflows.
I worked with operators and internal teams to understand where the existing booking workflow broke down, uncover the rules governing complex scheduling and billing, and establish how the system could become more flexible without compromising data integrity.
Through 20+ user interviews, I explored how operators managed recurring bookings, individual date changes and exceptions across diverse operational needs. This helped surface the critical distinction between changing a single booking and updating an entire series and the risks of getting that distinction wrong.
I combined user research with technical discovery to translate these findings into a system level strategy:
-
User interviews to understand real world booking behaviours, pain points and the consequences of failed changes.
-
Workflow mapping to expose fragmented processes across recurring bookings, date exceptions and invoicing.
-
Exception and edge case analysis to define how the system should handle conflicts, partial changes and series level updates.
-
Engineering collaboration to understand data relationships, technical constraints and the implications of changing existing bookings.
-
Dependency mapping to trace how booking changes affected availability, products and invoices.
-
System rules and implementation strategy to establish a consistent approach to exceptions, conflict resolution and billing, prioritising data integrity alongside operational flexibility.
The central design challenge was balancing user control with system integrity. Giving operators the flexibility to make individual changes without creating conflicting bookings, breaking recurring schedules or disconnecting financial records.
The bottom drawer challenged familiar full page workflows, raising internal concerns about usability. I advocated for the design because it let users check availability and resolve conflicts without losing context.
Once tested, user feedback was overwhelmingly positive, validating the decision to challenge convention.
I can create a booking, check availability and resolve conflicts without ever losing my place or having to start over. It makes the whole process so much easier.
Booking & Billing Velocity: 3-7 Days saved (depending on business size)
System Integrity: Zero double bookings or recursive overlaps.
Operational Leakage: Eliminated the gap between booking and invoicing, slashing delayed payments.
Before
After
Interested in working together?
