Demand snapshots

Demand snapshots records when an observation was made, which stay date it covers and the unit type involved. Available and booked unit counts sit beside the competitor rate. Revenue Manager can compare observations over time without treating a competitor quote as an automatic price instruction. Each observation links to a reservation, giving the team an operational case to inspect when reviewing the rate context.

• Observation. Demand by Stay Date keeps the snapshot date distinct from the stay date.
• Inventory. Available and booked counts describe the same unit type at that observation.
• Rate context. The competitor amount is one input to a reasoned recommendation.

Take a Saturday stay date and record an observation on the preceding Tuesday. The team should be able to explain both dates. Check that counts are nonnegative, the competitor amount is positive and the linked reservation is the intended case. A corrected observation should be recorded as a separate evidence point rather than silently replacing the earlier one. This protects the reasoning behind a later rate review.

Decide who supplies the competitor rate and how Revenue Manager identifies the observation date and intended stay date. Keep the unit type spelling aligned with units and rate plans. Require a linked reservation, nonnegative counts and a positive competitor rate before keeping an observation. Agree how to record a correction as a new observation so the earlier evidence remains available for the rate discussion.

Record a Tuesday observation for a Saturday stay, linking it to the intended reservation. Include available and booked units for the stated unit type and a positive competitor rate. Revenue Manager compares it with the existing rate plan before writing a recommendation. Now try a negative booked count and then omit the linked reservation. Each invalid submission should return its precise reason and leave the earlier observation intact. Keep both dates visible when discussing a later rate change with Property Manager.

• Demand by Stay Date — Shows recorded observations by stay date and unit type.
• Recommendations Awaiting Review — Shows rate decisions informed by an observation.
• Unit Occupancy — Shows the stay intervals behind the operating context.

Walk the linked records in the demand to rate process. Use implementation to agree the first operating cycle and the data model to check the imported references.