Penalty Clause in Hotel RFPs (Plain English Definition + Examples)
Definition
A penalty clause in a hotel contract is a contractual amount the breaching party must pay the non-breaching party for a defined failure — late deposit, no-show, exceeded attrition — separate from actual damages and usually pre-negotiated as a fixed sum or formula.
In European MICE sourcing, penalty clause sits inside a broader workflow that includes the brief, the longlist, the shortlist, the contract negotiation, and the post-event reconciliation. Understanding it in isolation is not enough — what matters is how it interacts with the other levers a planner can pull. The definition above is the textbook version; the sections below explain how it actually behaves in real RFPs.
Why Penalty Clause matters
Penalty clauses look painful but often save money: they convert messy litigation into a known number. In most European jurisdictions (especially France, Germany, Italy) penalty clauses are enforceable if the amount is proportionate to the breach; in common-law jurisdictions (UK, Ireland) excessive penalty clauses can be voided as 'penalties' rather than 'liquidated damages'. Knowing the local rule changes how you negotiate the cap.
Example
Hotel contract includes a penalty clause: 'If client cancels within 30-15 days of arrival, client pays 75% of contracted room revenue.' Group of 200 rooms × 2 nights × €189 ARR = €75,600 × 75% = €56,700 penalty. Compared to leaving the hotel to sue for actual damages (potentially €100k+ in lost F&B), the planner accepts the clause as bounded risk.
Where Penalty Clause appears in contracts
Penalty clauses sit inside the cancellation, attrition, or default sections of the hotel contract. EU contract law treats them differently from liquidated damages — pay attention to whether the contract is governed by Civil Code (DE/FR/IT/ES) or Common Law (UK/IE).
Related terms
Deeper reading
Related guides on the blog
Put this into practice
Easy RFP builds penalty clause thinking into every hotel RFP — so you negotiate from data, not from memory.
Review your contract risk →