Declare the capacity behind the percentage
Occupancy alone does not explain a week with rooms closed to sale. State which room-night denominator you use. Physical capacity and capacity actually offered may differ. Naming both views separately helps colleagues compare like with like. This is not an industry benchmark or pricing method: it is a fictional seven-day example with explicit assumptions. It contains no real customer results or private commercial data. The unit is a room-night, not a reservation or a person.
Separate source information from our calculation
Oracle’s public documentation illustrates different inventory treatment for room statuses. Airbnb’s preparation-time article provides another calendar-blocking example. Both were read on 8 October 2026; the Airbnb article dates from 2025 and is not presented as new news. They do not establish identical status names or reports across all software. Our table is an editorial example. Confirm the meaning and date scope of “closed to sale” in your own reporting rather than assuming another vendor’s label behaves identically.
Calculate two capacities
Assume 12 rooms for seven nights: 12 × 7 = 84 physical room-nights. Two rooms closed for three nights each remove 2 × 3 = 6 room-nights. Assuming every other room is offered, sellable capacity is 84 − 6 = 78. There is one closure period and no private coefficient or commercial ratio. Write down the dates and your definition of available inventory first. Daytime preparation does not automatically mean an unsellable night; identify exactly which nights the calculation excludes.
Same sales, different denominators
Assume 60 sold room-nights. Physical occupancy is 60 ÷ 84 = 71.43%; occupancy against sellable capacity is 60 ÷ 78 = 76.92%. Sales have not changed. The higher second percentage does not prove better selling: its denominator is smaller. Use these as clearly defined internal views, without automatically equating the adjusted view to an external industry benchmark. Show sold nights and capacity beside percentages when comparing weeks so a denominator change does not become an unsupported success story.
A capacity ceiling is not actual lost revenue
At a fictional flat rate of TRY 3,000 per sold night, revenue is 60 × 3,000 = TRY 180,000. Six closed nights multiplied by that rate give TRY 18,000, a gross capacity ceiling under this assumption, not established lost revenue. With no additional demand, extra revenue is zero; two additional nights would yield TRY 6,000 and six would yield TRY 18,000. These invented scenarios are before costs, not profit or guaranteed outcomes. Demand must not be inferred from capacity alone.
Count each room-night once
A room closed for both preparation and maintenance on the same night may represent one unavailable room-night, not two. Deduplicate by room and night. A training table can use invented room labels; it need not expose actual reservations or describe a product’s internal data model. The difference between physical and sellable capacity should equal unique closed room-nights. If it does not, revisit the scope of the table before interpreting the figures or presenting them as reliable management evidence.
Link decisions to readiness and demand
Do not reopen an unready room because the potential gross amount looks attractive. Operational readiness checks govern that decision; this calculation does not replace safety procedures. Review closed nights, sold nights and the capacity definition together, then discuss supported demand and hypothetical sales separately. A planned reopening is not realised revenue growth. Measure the next week using the same definitions. A small explicit table helps distinguish capacity, demand and revenue and identify what evidence each decision still requires.