Don't post that review yet: why the refund should land before the rating goes up

Freeze the moment. It's 11pm in a hotel lobby; the room smells of damp, the front desk has shrugged twice, and your thumb is hovering over a 2-out-of-10 and a paragraph that names names. Every word of it is true. Posting it feels like the one move you have left — the button that finally makes them take you seriously.

This guide is about that exact second, and the one belief driving it: that the angry review is your best weapon, best fired at once. Fired early, it mostly does the opposite of what you want — it hardens the property against you at the moment you need its cooperation, and it spends your strongest card for nothing in return. The review matters, and you should write it. The question is only when. What follows is general information rather than legal advice; the call, at every step, stays yours.

Two drafts of the same review

Picture the two versions of what you're about to write.

The midnight draft is loud and half-blind. You don't yet know whether the property will move you, fix the boiler, or refund half the booking without a fight — so the draft can only describe the failure, never the ending. It's also written at the exact moment the property still has something to protect. Before your score lands, a complaint sitting in the message thread is a private problem with a cheap exit: fix it or refund fairly, and the story closes quietly. The manager reading your message knows that.

Post the draft, and that exit disappears. The rating is public, the score has taken the hit, and nothing done for you now will change what the next guest reads. The person deciding your refund is no longer weighing "settle quietly or risk the write-up" — they're reading a public account of their own failure, written at your angriest, and deciding whether to reward it. Some still pay what's owed. Many go quiet, argue every point, or route you to "the team" — not because your case got weaker, but because their reason to be generous is gone.

The after-the-ending draft is a different object. It knows how the story went. It can say "they brought a fan the same night and refunded a third" — or "they stopped replying and the refund took the platform's involvement". A property that failed and made it right honestly deserves a different score from one that failed and stonewalled, and only the second draft can tell them apart.

None of this is cynical — it's how the marketplace is built. A property's score is its shop window: a few tenths of a point decide how high it sits in search results and how many travellers click past it, so managers watch the number the way shopkeepers watch the till. An experience the property can still keep off its public record is an experience it has a business reason to fix. You're not inventing pressure by waiting; you're keeping the pressure the marketplace already created.

The clock is slower than your anger

The panic behind the instant review is usually about the moment — the feeling that if you don't post now, the anger will go unrecorded and the property will get away with it. The platform's own rules remove the hurry.

• The window is about three months. Booking accepts reviews submitted within three months of checkout. Waiting a week or three for the refund conversation to play out costs you nothing; the option stays open the whole time, and what you eventually write will be better for the distance.
• Reviews come from real bookings. Only guests who booked — and stayed, or at least arrived — can leave one (§1F). Your right to rate the stay isn't something the property can take away by settling with you, and it isn't something you forfeit by accepting a refund. The money and the rating are separate by design.
• Posted means posted. Changing what you've already submitted isn't a self-service edit — it goes through Customer Service. Treat what you publish as close to final, which is one more reason to publish the finished story rather than the first draft of it.
• Old ratings fade anyway. Reviews can be taken off display once they're about 36 months old, and recent ones weigh more in the score. The system is built around fresh, considered accounts — not around who typed fastest on the night.

So the honest position is unhurried: the account is yours to give, the window is long, and nothing about waiting weakens it. What waiting does is keep the property's best reason to settle alive while the money is still on the table.

Two lanes that never touch

This part carries the whole guide, so it's worth being precise. There is a world of difference between sequencing your review and selling it.

Sequencing is what this guide describes: you're going to review honestly either way, good ending or bad — you're only not rushing to publish before the property has had a fair chance to put things right. You never mention the review in your refund request at all. The unposted review does its work silently, the way an unspent card does: the property knows reviews exist, knows yours is coming, and behaves accordingly. You never have to say a word about it — and you shouldn't.

Selling it is the ugly cousin: "refund me or I post", "pay and I'll say something nice", "delete my charge and I'll delete my rating". Don't go anywhere near this, in either direction. A review traded for money stops being honest, and both sides' rulebooks treat the trade as a serious offence. Booking's guidelines require reviews to be genuine and unbiased and bar properties from offering incentives for them — and in the contract every property signs with the platform, manipulating guest reviews is listed as grounds for ending the whole relationship (4.2.3). A host who proposes the trade is risking their listing to fake the score other travellers rely on; a guest who proposes it turns a fair refund case into something that reads as a threat.

So keep two separate lanes. In one, a refund request that stands on its own facts — the listing, the photos, the dates. In the other, an honest review, written when the story ends, whatever the ending was. The lanes never touch, and you never threaten. The request lane, as it happens, is the one we can help with: 2refund turns your answers into a clear request that's yours to send.

When waiting is the wrong call

Sequencing is a tactic for ordinary refund disputes — a spoiled room, a broken promise, money owed and slow to move. It has limits, and it's worth knowing them as well as the tactic itself, because holding back the wrong warning isn't patience; it's leaving the next traveller to walk into what you walked into. Some situations shouldn't wait for any settlement:

• Safety and scams. A property that felt unsafe, a listing that looks fraudulent, a "pay outside the platform" trick — warn other travellers promptly and report it to the platform. Protecting the next guest outranks your refund timeline, every time.
• A host pressuring you about the rating itself. Messages leaning on you to promise a good score, or to delete a bad one, are worth reporting rather than negotiating. The whole system stays useful only while it can't be leaned on.
• No money at stake. If you've decided not to pursue a refund at all, there's nothing to sequence — write it up whenever it's fresh and fair.
• The window is closing. As above: the three-month limit doesn't pause for a slow dispute. Past a certain point, waiting stops being patience and starts costing you the review itself.

My dispute is still dragging and the review window is closing — do I post or keep waiting?

Post. The review window doesn't pause for a dispute, and losing your chance to warn other travellers helps nobody. Write a calm, factual review of what happened — including that the refund is still unresolved — and keep the refund case moving through the platform separately. The two can run side by side; you only sequence them while you have the choice.

The host offered a refund if I promise a good review — can I take it?

Take the refund conversation, decline the promise. Booking bars properties from offering incentives in exchange for reviews — for a property, manipulating reviews is serious enough to end its whole contract with the platform. Settle the money on its own merits, then write whatever honest review the stay deserves. A refund that's owed doesn't need your rating as payment.

Writing the ending, not the outburst

When the time comes, the settled-case review is a better piece of writing than the lobby draft could ever have been — calmer, fairer, and more useful to the person actually reading it. Remember who that reader is: not the manager who wronged you, but a stranger with two tabs open, trying to work out whether this place can be trusted with their one week off. Write for them.

• Tell the whole arc. What was promised, what you found, what you asked for, what they did. "The air conditioning was dead in August; the property brought a fan the same night and refunded a third of the stay" tells the next guest more than a row of angry adjectives.
• Let the scores carry the nuance. Booking's subscores — cleanliness, staff, comfort, value — let you mark the failure where it happened and credit the response where it's due (§1F).
• Stay factual, skip the revenge. A write-up that reads as score-settling is the kind that gets challenged and taken down; one that reads as information stands. You want yours to stand.
• A good resolution deserves saying so. A property that failed and fixed it fairly has earned that sentence — and properties that see fair complaints end in fair reviews keep settling fair complaints. That's the quiet system your timing protects.
• Your account becomes someone else's evidence. A pattern of guests describing the same dead boiler or the same fictional sea view is what turns the next person's complaint from bad luck into a documented habit. The considered version you post is worth more to them than the furious one ever would have been.

The same discipline that holds the review back — everything in writing, on the day, with photos and a named amount — is what wins the refund itself; the small habits that quietly decide a refund are a guide of their own.

If I accept the refund, can I still write a negative review?

Yes. A refund settles the money, not the truth about the stay. Reviewing honestly afterwards — the problem, and how it was handled — is fair to the property and useful to the next guest. Many settled cases end in a mixed review: a real failure, dealt with properly. That's not ingratitude; it's exactly the information other travellers want.

Can I tone my review down later if they finally pay?

Not easily — changing a submitted review means contacting Booking's Customer Service rather than tapping an edit button, so treat what you post as close to final. That's the strongest practical reason to wait: a review written after the story has ended describes the whole story, and never needs the correction you can't conveniently make.

Which brings us back to the lobby, 11pm, thumb over the button. Put the phone down — not to spare the hotel, but to keep your strongest card unspent. Send the calm written request tonight instead, let the property choose its ending, and then write the review that tells all of it. You give up nothing by waiting. Most of the time you end up with both: the refund, and the rating that's actually worth reading.

The cases in this article are illustrative composites, not real client records. We build them from the patterns we see again and again across the disputes we help with, because we can’t share real customers’ booking details. The stories are invented; the way they play out is true to our experience.

This article is general information, not legal advice. We’re a self-help tool, not a law firm. Rules, fees and deadlines change and vary by country, so always check the policy attached to your own booking and your local consumer protections.