Hotel operations

Running a small hotel: the daily, weekly and monthly routine of a first season

Replace memory with a written routine for your first hotel season. This guide details the daily loop, weekly review and monthly decisions needed to stabilize operations and measure performance without prior history.

  • 11 min read
  • AI Otel Editorial

AI draft · awaiting editorial review

Contents

Key takeaways

  1. The first season has no history, so the routine replaces the benchmark: write down what you did each day and the pattern appears in weeks, not years.
  2. A daily loop that ends with the business day closed and a three-line handover note is worth more than any single report.
  3. Every weekly review should end with one decision and one owner, otherwise it is just reading.
  4. A service the team cannot deliver on a full house is a complaint scheduled in advance: staff it properly, narrow it, or stop it and say so.
  5. Measure five numbers on one page, defined the same way every week; a number nobody reads weekly is not a measurement.

Running a small hotel in its first season means replacing memory with a written routine: a daily loop from the arrival list to the business-day close, a weekly review of money, bookings, stock and reviews, and a monthly decision on what to keep and what to cut. The routine matters more than the tool.

The soft opening is behind you, the first guests have arrived, and the person who owns the hotel is also the person at the front desk at 23:40, with tomorrow's arrivals still unchecked. Nothing is going wrong yet. What is missing is an order to the day. After reading this you will have a daily loop you can write on one page, a weekly review that fits in an hour, and a month-three decision meeting that turns twelve weeks of notes into next season's plan.

What makes the first 90 days of a small hotel different?

In the first 90 days you have no history to compare against, so the routine itself is the only instrument you own. Everything you will later call a pattern starts as a note somebody wrote down.

There is no baseline. You cannot yet tell a good week from a lucky one, so record the inputs instead of judging them: rooms sold, the rate actually taken, complaints, staff hours. Judgement comes later, when the notes have a shape.

There are few hands. The same person covers reception, breakfast and the close, so the routine has to fit the people you have, not an organization chart you saw somewhere. If a step needs a person who does not exist, the step has to change, not the person.

The written order is also the handover. When the owner is ill or away for two days, the routine is what keeps the property running at the same standard. A routine that lives in one person's head stops the moment that person stops.

Some points of the day cannot move: the arrival peak, breakfast service, check-out, the identity notification at check-in, and the moment the business day is closed. Build the rest of the day around these fixed points rather than pretending they are flexible.

Decide in advance which decisions you will not make in month one. For example, do not cut a service after a single bad week. A bad Tuesday should not be allowed to rewrite the season.

One boundary on scope: this is the running order once guests are in the building. The pre-opening plan and the first-season rate are separate jobs, covered in a month-by-month pre-opening plan and in pricing a new hotel with no history.

What does the daily routine of a small hotel look like?

It is a fixed loop with two anchors: the morning, when you read yesterday and today, and the close, when the business day is finished and the handover is written. Everything between them is arrivals, rooms and charges.

The morning read

Before the first check-out, read four things: yesterday's rooms sold and the rate actually taken, today's arrivals and departures, in-house guests with an open bill, and anything the previous shift left unresolved. This takes ten minutes and it is the cheapest management tool you will ever own. If you want a fuller version of this page, see what a GM's morning page should contain.

Then set the housekeeping board. The board is the real plan of the day: which rooms are free, which are occupied, and which are out of order and cannot be sold. Room status codes differ between systems, so write your own short list once and keep it. An out-of-order room that nobody marked is a room you will sell twice.

Check-in is where the compliance steps happen. In Türkiye, every stay involves a payment, a fiscal document, a guest identity notification (KBS, the notification of guest identities) and personal data under the personal-data law (KVKK). Prepare the identity notification and the consent record inside the check-in flow, not reconstructed afterwards from memory. Reconstructing them later is slower and error-prone, and errors here are not customer-service problems.

Post charges to the guest's bill as they happen. A minibar or restaurant charge discovered at check-out is a dispute, not a record. The guest's memory of Tuesday evening and yours will differ, and the desk inherits the argument.

The close and the handover

Close the business day once, reconcile the day's takings against what the system says, and check tomorrow's arrivals against rooms that can actually be sold. This is the same job large hotels call the night audit, done at whatever hour a small property can staff it.

Then write the handover note. Three lines: what happened, what is unresolved, what the next person must do first.

ChecklistThe daily loop, in order

  • Read yesterday's rooms sold, rate taken and unresolved notes
  • Confirm today's arrivals, departures and in-house open bills
  • Set the housekeeping board, including out-of-order rooms
  • Check in with the identity notification and consent record completed in the flow
  • Post charges to the guest bill as they occur
  • Close the business day and reconcile the takings
  • Write the three-line handover note

Keep the loop identical on quiet days. The routine is practiced on the quiet days so that it survives the full ones.

What should the weekly review cover?

Four things, in this order: money, bookings, stock, reviews. Each item ends with one decision and one owner, and the whole review fits in an hour.

What you look atWhere it comes fromQuestion it answersDecision it can trigger
Cash in and outIncome and expense sheetAre we above or below break-even this week?Adjust next week's spending
Forward bookingsReservation listWhere are the empty nights?Release or push a channel
StockWeekly countWhat runs out before the next delivery?Reorder or change the breakfast list
Reviews and complaintsReview pages and complaint logIs the same cause repeating?Fix the process or the wording
Open guest bills and debtsThe systemWhat is unpaid and how old?Chase or write off

Money first: what came in, what went out, what is still owed. A simple sheet you can read in two minutes beats an accounting export you open once a month. For the sheet itself, see a monthly income and expense sheet a small hotel actually keeps.

Bookings second: what is on the books for the next four weeks, which channel produced it, and where the gaps sit. Look at pick-up (rooms already taken from a group block or an allotment), not only at the total. A block that has not moved in three weeks is a decision waiting to be made.

Stock third: breakfast, minibar, cleaning supplies and the small items that quietly run out on a full weekend. Count the same list every week; a changing list produces numbers that cannot be compared.

Reviews last: read the new ones aloud, assign one person to reply, and note the cause rather than the tone. The rule that keeps the meeting short is simple: nothing leaves the table without an owner and a date.

Keep the same hour every week. A review that moves gets skipped, and a skipped review is how a small problem becomes a seasonal one.

How do you handle the first complaints and reviews?

Fast, in writing, and without promising anything the person at the desk cannot authorize. The first complaints are the only free information you will get about what to fix.

Separate the two things. A complaint is a guest standing in front of you; a review is a public record read by future guests. They need different handling, but they usually have the same cause, and the cause is the part worth logging.

Fix the room first, then decide what the guest is owed. Whoever is on the desk must know the limit of what they can offer without calling the owner.

Watch outAuthority at the desk

Do not promise a refund, an upgrade or a free night unless that person has the authority and the amount is written down. An unauthorized promise becomes a discount you never priced, and the next shift inherits it.

Log every complaint in one place: date, room, cause, what was done, who did it. The same cause three times is a process problem, not a guest problem.

Reply to reviews within the week, in the language the guest wrote, naming the specific thing and the change made. Never argue about the facts in public. And do not answer a review in the hour you read it: read it, write the reply, send it the next morning. A calmer reply is a better one, and nothing on a review page is so urgent that it cannot wait a night. For the full routine, see a weekly reputation routine for a small team.

Ask one question at check-out: what would have made the stay better. The answer is worth more than a form nobody returns.

What should you measure when you have no history?

Five numbers on one page, read at the same time every week. They are not targets yet; they are the baseline you will compare next season against.

First, rooms sold and rooms available. The second is not the same as rooms in the building: out-of-order rooms and refurbishment reduce what you can actually sell. Second, the rate you actually sold at, not the rate published on the website. The gap between the two is the first thing to explain to yourself. Third, occupancy rate, computed the same way every week, so that the comparison is honest even when the definition is imperfect. Fourth, revenue per guest night: total revenue divided by the number of guest nights in the week. Fifth, complaints and reviews, counted rather than remembered.

Write the definition of each number next to it. A number whose definition changes is not a measurement, it is an opinion with a decimal point.

Do not import a target from another hotel. The only honest first-season target is your own break-even, and that comes from your costs, not from the market.

TipOne page per week

Put the date at the top, the five numbers in a row, and one line of comment in plain words. At the end of the season you have a stack of pages, and that stack is the history you did not have in week one.

When should you stop offering a service, and what goes on next year's list?

Cut a service when it fails on a full house, not on a quiet one, and when fixing it costs more than it earns in goodwill. The month-three review is where that decision is made once, in writing.

The test is occupancy pressure. A breakfast that works at half capacity and collapses on a full weekend is a promise you cannot keep, whatever the reviews said in week two. Count the hidden cost too: staff hours, the manager's attention pulled off the desk, and the complaints the service itself generates.

There are three options, in order: staff it properly, narrow it (fewer hours, a shorter list, on request only), or stop it and say so clearly on the website and at check-in. Removing something is a communication job. Tell the guests who already booked it, and update the channel content the same day, not at the end of the month.

Keep one running page all season: every time something annoys you twice, it goes on the page. The month-three review is a reading of that page, not a memory exercise in October. It answers four questions in writing: what we keep, what we cut, what we add only if we can staff it, and the three fixes for next season.

Key pointThe cut test

If the team cannot deliver it on your fullest night, it is not a service, it is a future complaint.

What to do next

Write the daily checklist on one page today and run it unchanged for seven days. Then add the weekly review and the five numbers. The three loops fit together in one direction: the daily loop produces the records, the weekly review turns them into one decision, and the month-three review turns twelve weeks of decisions into next season's plan.

If you later move the routine into software, move the routine, not just the records. AI Otel's PMS assistant is built: it answers questions about a hotel's own property in plain language, carries out routine actions, and a person confirms anything sensitive. It is ahead of launch and not in hotels' hands yet. If you want to see where this is heading, request a briefing.

Frequently asked questions

How many staff does a small hotel need in its first season?

There is no universal number, and any ratio quoted from another property will mislead. Derive it from the daily loop: list every step that cannot be skipped, name who owns it, and ask what happens when that person is off. The count of steps that have no second owner is the real staffing gap.

What should I do if I am overbooked in my first season?

Treat it as hotel practice, not law: find the alternative room before the guest arrives, tell the guest as early as you know, write down what you offered and who approved it, and fix the cause, which is usually the same inventory being sold in two places. Türkiye-specific rules on relocating a guest and on compensation could not be verified for this article, so confirm your own case with a legal adviser.

Do I have to run a night audit?

Night audit is common hotel practice rather than a legal term, and small hotels often close the day in the morning instead. What matters is that the business day is closed once, the takings are reconciled against the system, and the next day's arrivals are checked against rooms that can actually be sold. One cut-off, done the same way every day, is the point.

When does a notebook stop being enough for a small hotel?

Not at a particular size, but at a particular symptom: the same room gets sold twice, the day's charges have to be reconstructed from memory, or the identity notifications and the invoices live in different places. Until one of those happens, a notebook and a weekly sheet are a legitimate system. After it happens, the routine is what you move into software, not the other way round.

AI Otel EditorialEditorial team

Drafted with AI assistance from AI Otel’s published fact base. Not yet reviewed by an editor.

For hotels: OtelCiro.

OtelCiro, AI Otel’s hotel growth and consultancy arm, is operating today.

Talk to OtelCiroRequest a briefing