These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Revenue Management System
- Features
- Rate recommendations
Rate recommendations
Put a reason and a person behind each rate change.
OverviewRecommendations Awaiting Review×
Revenue Management System · Rate recommendations
New
Recommendations Awaiting Review
Approval waits for the revenue manager
| Id | Unit type | Stay date | Current rate | Proposed rate | Reason | |
|---|---|---|---|---|---|---|
| IDD-613 | UT-309 | 03 Oct | 670 | 830 | Proposed rr-412 | |
| IDD-118 | UT-756 | 13 Oct | 490 | 300 | Proposed rr-184 | |
| IDD-424 | UT-922 | 09 Oct | 520 | 170 | Proposed rr-332 | |
| IDD-614 | UT-156 | 22 Oct | 740 | 580 | Proposed rr-305 | |
| IDD-818 | UT-363 | 06 Oct | 560 | 820 | Proposed rr-667 |
6 of 6 records
IDD-613Rate recommendations · RR-43190
ProposedUnit typeUT-309
Stay date03 Oct
Current rate670
Proposed rate830
ReasonProposed rr-412
What you can do
Keep the proposal tied to a stay
Rate recommendations records a unit type, stay date, current rate, proposed rate and reason. Its linked reservation gives Revenue Manager a concrete case to examine. Proposed is the review state; Approved records the approval decision, and Published records the released recommendation. An invalid submission returns a reason for correction. The review should check the linked reservation and ensure the proposed amount is positive before deciding.
How the work is organized
- Queue. Recommendations Awaiting Review holds proposed changes with their reason and linked stay.
- Decision. Revenue Manager compares current and proposed amounts for the specified stay date.
- Release. Published Rates shows the decisions made available to the operating team.
Suppose booked units rise for a holiday Saturday while a competitor observation also changes. Revenue Manager can cite those facts in the reason and propose a new nightly amount for that Saturday. Approval records the decision on that recommendation. Publication follows approval; it does not rewrite an existing reservation’s recorded nightly rate. An invalid submission remains unchanged so the owner can correct it and try again.
What to agree during setup
Agree who may enter a proposal, who decides approval and who publishes the approved result. Keep the proposal linked to the intended reservation and check that its unit type and stay date describe the same case. Require a positive proposed amount and a reason that a reviewer can inspect. Decide how Revenue Manager handles a rejected recommendation while retaining the earlier decision record. Publication should follow approval without rewriting the nightly rate already recorded on the stay.
Check the handoff on an actual case
Start with a Saturday reservation and a demand observation for that stay date. Revenue Manager records the current and proposed amounts with a reason, then approves the valid proposal. Publish that approved recommendation and compare its status with the reservation rate, which remains the booked amount. Try another proposal with a nonpositive proposed amount. Show the reasoned rejection and unchanged proposal, then correct it as a separate review step. Ask Property Manager to inspect the same linked stay.
What your team sees
- Recommendations Awaiting Review — Shows proposed rate changes with reason and linked stay.
- Published Rates — Shows approved changes released for the stay date.
- Demand by Stay Date — Shows the observation that informs the review.
Follow the work through
Walk the linked records in the rate review process. Use implementation to agree the first operating cycle and the data model to check the imported references.
What it keeps track of
Data model- Rate recommendations
- Proposed nightly rate changes for a stay date, with reason and review status.
- Reservations
- Guest stays with arrival, departure, rate and lifecycle status.
- Demand snapshots
- Daily demand and competitor rate observations for a stay date and unit type.
- Rate plans
- Seasonal nightly rate plans by unit type with minimum stay rules.
Who uses it
Permissions- Revenue Manager
- Approves or rejects the rate proposal and releases an approved decision.
- Property Manager
- Reviews the operating impact.
Set up Revenue Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.