Hotel operator contract: review before the season

A hotel operator contract must do more than record a general intention before the season begins. It should state who may use the hotel, which services are owed, who makes day-to-day decisions and how costs, investments and liability risks are allocated. Unclear points become particularly difficult once the first guests have already booked.

In Austria, the label hotel operator contract can describe a lease, a business lease, a management agreement or a mixed arrangement. The heading is not decisive. The actual transfer of use, the economic responsibility and the duties assumed by the operator matter. This article focuses on the review immediately before the season and complements the overview of accommodation and guest admission.

Section 1090 ABGB defines a lease as an agreement under which one party receives the use of a non-consumable thing for a certain period and at a certain price. Section 1091 ABGB distinguishes a lease for use from a business lease according to whether only use or also the taking of fruits and income is transferred. A hotel can make this distinction difficult. If the operator receives rooms, inventory and the running business at its own risk, the arrangement may have the character of a business lease. If the operator runs the business for the owner in return for a management fee, the allocation of risk is different.

Before the season, do not review only the title of the document. Important points include the operator status, instructions, revenue and cost risk, responsibility for staff, booking and pricing decisions and access to operating accounts. A combination of rent, extensive owner instructions and no real decision-making power can later create disputes about responsibility and accounting.

The Austrian Tenancy Act must not be assumed to apply or not apply in a blanket way. Section 1(2)(1) MRG lists premises rented in the course of operating an accommodation business as an exception from the relevant main parts of the Act. Whether this exception applies depends on the actual use and contractual model. The general article on the hotel operator contract in Austria addresses the broader structure. This article focuses on seasonal implementation.

An operator can only provide the services for which the necessary assets are actually available. The contract or a binding schedule should therefore identify the building and rooms, reception, kitchen, storage, wellness and outdoor areas, parking, technical equipment, keys, software, brand materials and movable inventory. For each important asset, it should be clear whether it remains owned by the owner, is brought in by the operator or may be replaced jointly.

A handover record with photographs, meter readings, a defect list and a functional check is useful before the season. In a hotel, heating, hot water, ventilation, lifts, kitchen equipment, fire protection and security systems, as well as digital booking systems, are not minor details. The contract should also state who may commission urgent repairs and whether the operator may act immediately in an emergency.

Uncertainty often concerns ancillary areas and mixed use. A staff room, storage area, breakfast room or parking space may be essential to the hotel without being expressly mentioned in the main text. A room and inventory schedule prevents the parties from attaching different factual premises to the same contract.

The financial model must be understandable from the contract documents before the season starts. In addition to a fixed rent or management fee, the parties may agree revenue shares, minimum payments, operating costs, marketing contributions or variable remuneration. Each component needs a clear calculation basis, accounting period, due date and rule for corrections or chargebacks.

Running costs and investments must be kept separate. Consumption, cleaning, laundry, maintenance and minor repairs are ongoing expenses. A new heating system, kitchen renewal or adaptation to an official requirement may be an investment. The contract should address not only payment, but also the decision, commissioning, ownership of the replacement and its treatment when the contract ends.

Revenue-based models require verifiable information for the owner. The contract should define turnover and address cancellations, vouchers, platform fees, discounts, direct bookings and related services. A reasonable audit and information right should protect confidentiality without making the accounting dependent on one party’s unverified statement.

Section 111(1) GewO 1994 identifies accommodation of guests as an activity that generally requires a trade licence for the hospitality trade. The provision also contains rules on serving food and beverages. Section 111(2) provides exemptions from the certificate of competence under certain conditions, including certain simply equipped businesses and accommodation with no more than ten guest beds. An exemption from the certificate of competence does not automatically remove every regulatory review of the business.

Before the season, owner and operator should therefore establish who holds the trade licence, which services are actually offered and whether the premises and operating facility match them. Official requirements, operating hours, fire safety, food hygiene, building changes and regional rules may also matter. The contract should assign responsibility for maintaining and producing the necessary documents to a specific party.

A clause requiring the operator to obtain all permits at its own cost can be problematic if the owner controls the structural or property-related prerequisites. The review should distinguish a personal trade licence, an approval relating to the property and an ongoing official requirement. Only then can the parties identify who must act and who bears the cost if a requirement is delayed.

The contract should not leave day-to-day operations at a general level such as “proper hotel operation”. It should address opening hours, quality standards, reception, cleaning, maintenance, safety checks, complaints and reporting to the owner or operator. It is also important to state whether subcontractors may be engaged and who is responsible for their conduct.

Sections 970 to 970c ABGB contain special rules for innkeepers concerning property brought in by guests. The liability of the innkeeper, the treatment of valuables and prompt notice of damage cannot simply be replaced by a general notice. The internal operator contract should therefore allocate the organisation of safes, custody, damage records, insurance claims and communication with the guest. This allocation does not automatically change statutory liability to the guest, but it avoids gaps between owner and operator.

Insurance should be reviewed by risk rather than by product name alone. Public liability, building insurance, business interruption, cyber risks and damage to property of others may have different scopes. The contract should connect the insured party, minimum cover, excess, proof of insurance, premium payment and prompt notification of a loss.

Owners often want to protect standards for branding, equipment, prices or distribution. Operators also need enough freedom to manage the daily business. The contract should state which instructions are binding, how much notice is required for changes and when consent is needed. Urgent safety measures should not depend on a complicated approval process.

Digital systems must be included as well. Booking platforms, guest data, cash register systems, review accounts, domains, social media profiles and newsletters should not be left in an unclear position when an operator changes. Before the season, the parties should identify who processes data, who controls access, which reports are owed and how access and data are returned or deleted at the end.

A reasonable control right usually includes access to relevant accounts, operating records and maintenance documents. It should be combined with notice, confidentiality and protection of business secrets. A control right without defined records, or an instruction right without limits, rarely creates reliable management in practice.

A seasonal business needs a clear start and end date. The contract should also address renewal, preparation, the post-season period, accounting and access to the premises. If renewal is automatic, the notice period, form and receipt of a declaration must be clear. Phrases such as “in good time before the season” do not create reliable planning.

Early termination should distinguish ordinary notice, good cause, cure periods, non-payment, official prohibition and permanent impossibility. The consequences of the end should be described as well: return of premises and inventory, existing bookings, vouchers, deposits, guest data, suppliers, staff, keys, brand materials and ongoing proceedings.

The treatment of investments should be settled before the season. Is an installed item taken over, removed or compensated? Who bears the cost of an upgrade requested by the other party? The more precisely these points are answered at the start, the less the final accounting depends on later valuations.

A reliable review needs more than the contract and its signature page. Owner and operator should collect the current agreement and amendments, schedules, handover records, inventory list, permits, official requirements, insurance certificates, pricing and booking terms and the latest accounts. A change of operator also requires bookings, outstanding vouchers, deposits, supplier agreements and service contracts.

Check every document against the actual business. Do the number of rooms, ancillary areas, opening hours, services and responsibilities match? Are there promises in emails that are not reflected in the contract? Do investment duties fit the budget and official requirements? The business documents checklist supports this preparation.

For a first classification, use the accommodation check. The term accommodation contract describes the relationship between business and guest and must be distinguished from the operator contract between owner and operator. Keeping these relationships separate prevents guest obligations and operating obligations from being confused.