Airbnb Rate Change Log

The host problem

You lowered price on three nights last month. You don’t remember exactly when, exactly why, or what the lead time was at the time. Those nights filled. But you can’t tell if the fill was because of the cut or in spite of it. Without a log, pricing history becomes legend — a story you tell yourself without evidence.

What the rate change log helps you decide

A rate change log creates a decision trail. It tells you, six months from now: what you changed, when you changed it, why, and what happened afterward. That record is the foundation for testing hypotheses about your pricing rather than repeating adjustments that felt right at the time.

Inputs required

Each rate change entry should record: the date the change was made, the night or nights affected, the previous rate, the new rate, the reason for the change, the lead time at the moment of the change, and the outcome — whether the night filled, at what BLT, and at what final ANR.

If you use smart pricing tools, note when a tool made an automatic adjustment and what triggered it. That data belongs in the log just as much as manual changes.

Outputs produced

A completed log for two to three months produces: a frequency pattern (how often you change price and on which day types), a lead-time pattern (when you tend to intervene), a reason distribution (cuts for softness, raises for demand, reshapes for shape), and an outcome record (which changes produced the result you expected and which did not).

That output lets you see whether your instincts are consistent with results — or whether you’re making changes that don’t affect outcomes.

Example

A host logs six changes in a single month. Three were weekday cuts made at BLT 12–18. All three filled within a week. Two were Saturday raises made at BLT 40. Both Saturdays filled within four days at the higher rate. One was a minimum-stay reduction on a Wednesday orphan at BLT 9. It did not fill.

The log shows: weekday cuts at BLT 12–18 are productive, Saturday raises at BLT 40 are productive, and minimum-stay reductions on isolated weekday orphans are not. That three-finding summary is more useful than a feeling that pricing is going well.

What most hosts get wrong

Hosts change price frequently but track outcomes only loosely. They know last month was “good” or “slow” but cannot explain what drove the difference. The log closes that gap without requiring complex analytics — just a disciplined record.

How to use it this week

Create a simple six-column record — date, nights affected, old rate, new rate, reason, lead time. Add a seventh column for outcome, which you fill in after the night passes. Start logging every change you make from today forward. Review the log at your monthly KPI review.

Connected articles

This tool connects to The Simple Airbnb Pricing Review Checklist, Airbnb Price Testing for One Listing, and How to Track Airbnb KPIs Once Per Month.

Educational note

This page is educational. It is not tax, legal, investment, or guaranteed-income advice.