Late checkout decline
Send this as soon as they ask, once you know the listed checkout time has to stand.
{Guest name}, checkout at {Property name} stays at {Checkout time}. I cannot move it.
{Reason line}
Please plan to be out by {Checkout time}, with the checkout tasks on the listing done. If a train or flight makes that hard, reply with the constraint and I will tell you whether any earlier option exists. I do not have a later one.
When to send
Send the no as soon as the answer is no. {checkout_time} is the reservation’s time, repeated twice on purpose so a skim still catches it. {reason_line} is one sentence a guest can picture: “The next guests arrive this afternoon and the cleaner needs the morning” or “The building’s quiet hours and the cleaner’s only slot both start at 11.” Skip a reason that blames them for asking. People ask. The no is about the clock.
{guest_name} may be asking for an hour, not a half day. If you can do the hour, use the yes template instead of stretching this one. This template is for when {checkout_time} is firm. Do not write “I cannot do 2pm but maybe 12” inside it. That is a yes to 12, and it should be the other message with a real time.
If they have not asked and you are only reminding them, use the checkout reminder. A decline of a request they did not make sounds hostile.
Timing tip
Speed matters more than tone. A no sent the night before lets them move a car or a train. A no sent at {checkout_time} is just an eviction from the kitchen. If you need ten minutes to check with a cleaner, say you are checking and name when you will answer. Then send this.
If the ask arrives after they have already missed {checkout_time}, the message changes: they are late now, the next arrival is the fact, and {reason_line} should say who is waiting. Do not open with a policy paragraph. Open with the time they should have been gone and the time you need the door.
Automating a no is a bad fit. Late checkout asks are individual. A saved reply you edit is the right use of this template.
Common mistakes
A lecture is the first one. They do not need the history of your turnovers. {reason_line} is one sentence. The rest of the message is the time and the offer to hear a constraint, which is not an offer of a later leave. Keep that last distinction. “Tell me your constraint” lets you suggest leaving bags in a place you approve, or an earlier checkout, if those exist. It is not a crack in the no.
The second is a fee that was not listed. “It will be $50 if you stay” added the morning of checkout is a new charge. If a listed late fee exists, you can name it only because it is already in the price terms. If it does not exist, do not create it here. The consequence of staying is the next guest and the cleaner, which {reason_line} can say.
The third is leaving them without a time. Some hosts write “sorry, that will not work” and never restate {checkout_time}. The guest then uses the time they wished for. The template repeats the real time. Do not delete the repetition when you edit.
Bags and lobbies
If the building allows bags in a lobby after {checkout_time}, you can add that as a fact you know, not as a guess. If you do not know, do not send them to a front desk that will refuse them. The template does not mention a lobby. Add a sentence only after you have asked the building, and only if this guest’s stay is in that building.
Then stop writing. A second message that rephrases the no feels like pressure. One clear answer is the favor.