1. Revenue Management System
  2. Process
  3. Demand to rate proposal
Process · Demand to rate proposal

Demand to rate proposal

Demand to rate proposal starts with a dated observation and ends with a proposal for a particular stay date. Revenue Manager checks the unit type and linked reservation before comparing the competitor amount with the standing rate plan. A snapshot is evidence of what was observed, so a correction becomes another observation rather than an edit to the earlier one.

Step by step

  1. Record demand Revenue Manager

    Revenue Manager records the observation date, stay date, unit type, unit counts, competitor rate and linked reservation.

    • Retains the observed demand context.
    • Updates Demand snapshots, Reservations
  2. Prepare seasonal rate Revenue Manager

    Revenue Manager checks the effective nightly plan and minimum nights for the unit type.

    • Shows the standing price and stay rule.
    • Updates Rate plans, Units
  3. Propose rate Revenue Manager

    Revenue Manager records current and proposed amounts and explains why the stay date needs a change.

    • Creates a Proposed recommendation linked to a stay.
    • Updates Rate recommendations, Reservations

Where it usually breaks

And how to keep it from happening.

  • Mismatched dates. A Tuesday snapshot for a Saturday stay should identify both dates; a proposal for Sunday needs its own context.
  • Invalid observation. A negative unit count, nonpositive competitor amount or absent linked reservation rejects the entire submission with a reason.
  • Unclear price basis. If two rate plan periods cover the same date, Revenue Manager resolves the intended standing rate before comparing a proposed change.

Set up Revenue Management System your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started