Booking Pace Explorer
Compare how bookings are building for a date against how they built for comparable dates.
Inputs
What data is required?
- Reservations with the date they were made and the date they are for
- A comparable period to read pace against
Outputs
What does it calculate, display or help you decide?
- A pace curve for a rental date, read at a chosen number of days before pickup
- The same curve for comparable dates, so the shape can be compared rather than a single number
Build prompt
Not yet written. This module is proposed and not scheduled. The purpose, inputs, outputs and operating complication above describe what it would do; the build prompt, setup steps, dependencies and tests will be added if it is taken forward.
The part that catches people out
Booking pace. Pace is a shape over time, not a figure. Two dates can hold the same number of bookings today and be heading to very different places, because one is building steadily and the other took a single group booking early. Comparing pace means choosing a comparable date and a consistent read point, and saying which you chose.
Optional RME connection
To be defined. Any supported data connection would require approved interfaces and verified data rights.
Any connection to RateHighway services would require approved interfaces, authorisation, tenant isolation and verified data rights. Nothing about access or availability is approved.
Proposed, not scheduled
There is nothing to build from yet. Start with a module that has a written prompt, or read the playbook to decide whether this one is worth building at all.