In a small accommodation facility, many things run on autopilot. The owner knows who is arriving today. The reception remembers which guest requested a late check-in. The cleaning staff know which room needs to be prepared first. Someone has in mind that one booking still awaits payment, and another requires an invoice.
Until then.
The problem starts when more bookings come in, there are several people on the team, seasonal traffic, changes to dates, late arrivals, and queries from guests on different channels.
Then "everyone more or less knows what to do" stops being enough.
However, this does not mean that a small venue needs a large book of procedures, hotel bureaucracy, and documents that no one reads. Sometimes it is enough Mini-SOP, i.e. a simple set of rules: what to check, who is responsible for what, and where to find up-to-date information.
A mini-SOP in an accommodation facility is a simple procedure that describes the most important steps in daily work: during reservations, before the guest's arrival, during check-in, at departure, cleaning, and payments.
It's not about creating complicated instructions. It's about ensuring the team doesn't have to guess every time what to do, where to check data, and who should respond.
What exactly is an SOP?
SOP stands for Standard Operating Procedure, which is the standard operating procedure.
In large hotels, such procedures can span tens of pages and cover every detail of the work of reception, housekeeping, the restaurant, or the technical department.
There is no need to create such extensive documents for a small accommodation facility.
A practical version is enough:
- short,
- Understood,
- ready to use
- suited to real work
- available to those who actually need it.
This mini-SOP isn't meant to make work harder. It's meant to simplify it.
Why do small objects need procedures too?
Small business owners often think:
"Everyone here knows what to do."
And that's often true. But only when everything goes according to plan.
Procedures only become important when a deviation occurs.
- The guest is arriving early.
- The room is not ready yet,
- the payment has not been credited
- Someone is changing the booking date.
- The seasonal worker doesn't know where to check for information.
- The guest is asking for an invoice.
- Cleaning was not informed of the late check-out.
- the owner is away from the premises, and a quick decision needs to be made.
It's in moments like these that the lack of a simple process causes chaos.
Not because the team doesn't get it. But because there isn't one clear way of operating.
A Mini-SOP doesn't have to be a 30-page document.
The biggest mistake is thinking that a procedure has to be long.
In practice, a mini-SOP can be a table, a checklist, or a short instruction.
Example:
| Situation | What should I check? | Who is responsible? | Where to save the information? |
|---|---|---|---|
| New booking | date, room, number of people, payment | reception / owner | PMS system |
| The day before arrival | Arrival time, payment, guest details | reception | booking + message |
| Room after departure | cleaning status, faults, items left behind | Housekeeping | Note / Status |
| Late check-in | Instructions for entry, code, emergency contact | Owner / Reception | Message for the guest |
| Non-payment | Booking status, payment deadline, reminder | reception | booking + message |
This is already the procedure.
It doesn't have to be more complicated to work.
Where to start creating a mini-SOP?
It's best not to start by writing a document.
It's better to start with a question:
At what moments does chaos most often appear?
In most facilities, these will be similar situations:
- New booking
- payment or deposit
- Pre-arrival message,
- room preparation,
- Check-in,
- Guest departure,
- cleaning
- fault,
- rescheduling
- The transmission of information between people.
There's no need to describe everything at once. Just choose 3–5 situations that most often cause problems.
Mini-SOP 1: new reservation
A new booking shouldn't just mean putting a date in the calendar.
It's worth checking straight away:
- From which channel did the reservation come?
- which room or apartment this refers to,
- Is the guest's data complete?
- Is payment or a deposit required?
- Does the booking require an additional message?
- Were there any special notes?
This means the booking has a clear status from the outset.
Without a procedure, it's easy to get into a situation where a booking is made, but no one knows if the guest has paid, received a confirmation, or if anything else needs to be done.
Mini-SOP 2: The day before arrival
The day before arrival, it is worth checking a few things:
- Is the booking confirmed?
- Has the payment or deposit been settled?
- Is the arrival time known?
- Is the room assigned,
- Has the guest received instructions?
- Do the staff know about the extra requests?
This is a good time to send a message before the stay: with information about arrival, check-in, payment, parking or house rules.
This procedure limits the number of questions on the day of arrival.
Mini-SOP 3: Room Preparation
Preparing a room is not just cleaning.
This also ensures that the right person knows:
- which room needs to be prepared
- What time?
- For how many people
- Are there any special requests?
- Has the previous guest checked out?
- Is there a fault?
- Can the room be marked as ready.
If this information is only in conversations or messages, it is easy to lose something.
Therefore, the mini-SOP should clearly state where the team checks current information on arrivals, departures, and room statuses.
Mini-SOP 4: Late Arrival
A guest's late arrival is one of those situations that's worth having an explanation for in advance.
The procedure may include:
- When to send the entry instructions
- What must be in the message,
- Who is responsible for emergency contact,
- is payment settled,
- Does the guest have all the information?
- What to do if the guest does not reply.
This means late check-ins don't require improvisation every time.
Mini-SOP 5: Guest Departure
The guest's departure also triggers several tasks.
It needs to be checked:
- is the payment closed,
- Does the guest need an invoice?
- Is the room free?
- Do we need to inform housekeeping?
- Have any damages or defects occurred?
- Should I send a thank-you message or a request for feedback.
If we don't sort this out, departure day can be just as chaotic as arrival day.
What does a simple mini-SOP look like in practice?
A simple scheme can be adopted for each procedure:
| Procedural element | Follow-up question |
|---|---|
| Cell | Why are we doing this procedure? |
| Moment | Kiedy procedura się uruchamia? |
| Responsibility | Who is doing the task? |
| Dane | What information is needed? |
| Recording location | Where do we save the status or note? |
| Next step | What must happen next? |
Example for a guest's arrival:
| Element | Example |
|---|---|
| Cell | The guest is to arrive without any further questions or ambiguities. |
| Moment | The day before arrival |
| Responsibility | Reception or owner |
| Dane | Arrival time, payment, room, entry instructions |
| Recording location | booking in the system |
| Next step | Sending a message before arrival |
This is enough for the team to have a common point of reference.
How does mobile-calendar help keep procedures simple?
The mini-SOP only works when the team has access to current information. The procedure on paper itself is not enough if bookings, messages, payments, and notes are scattered across several places.
In the mobile calendar, the system is the basis PMS, in which reservations, availability, prices, and communication with guests can be managed. The system describes its application for various types of accommodation, from hotels to apartments, guesthouses, and holiday homes.
With the mini-SOP, the most important thing is that the booking calendar can become the starting point for daily work. Instead of checking notes, messages, and spreadsheets separately, the team can base procedures on up-to-date data in one place: who is arriving, who is leaving, which slot is occupied, and which booking requires attention.
Another important element is Employee accounts and permissions. Mobile-calendar describes the ability to create individual employee accounts, tailored to tasks and roles within the facility, as well as managing staff access – from managers to cleaning staff. This fits well with mini-SOPs, as a procedure should state not only "what to do", but also "who should do it".
The third element is Guest communication.
Mobile-calendar enables the use of dynamic templates for messages, emails, SMS messages, and trigger-based automation. The system also allows for managing guest communication in one place and provides access to contact history. In practice, this means that procedures such as "pre-arrival message," "payment reminder," or "post-stay thank you" do not have to be created manually each time.
The fourth element is notifications.
Mobile-calendar informs about bookings, payments, upcoming stays, changes, and cancellations. This helps keep procedures moving as the team doesn't need to remember everything themselves.
The fifth element is mobile application.
Mobile-calendar allows you to manage bookings, control availability, check statistics, use notifications, and manage cleaning from your phone. This is important for smaller establishments, as the owner, reception, or staff are not always at a computer.
In practice, mobile-calendar does not create procedures from objects. However, it helps to maintain them in daily work: data is in one system, roles can be assigned to specific people, messages can be prepared in advance, and notifications help not to miss important moments.
Mini-SOP for immediate implementation
To begin with, there is no need to create procedures for the entire object.
You just need to start with one list:
Daily operating checklist
Morning
- check today's arrivals,
- Check today's departures,
- check pending reservations for payment,
- pass on cleaning information
- Check messages from guests.
Before arrival:
- ensure the room is prepared,
- check payment status
- Send directions
- record special guest requests,
- Ensure the team sees up-to-date information.
After departure:
- to mark a room for cleaning
- Check payment or invoice
- record any comments,
- send a message after the stay,
- prepare the room for the next booking
It's a simple procedure, but it already Organises the workday.
When does the mini-SOP take effect?
The mini-SOP works when it meets three conditions:
- It's short
If a procedure has several pages, nobody will go back to it during the season. - It is related to daily work
It doesn't describe theory, only specific situations: arrival, departure, cleaning, payment, message. - One reference place
The team needs to know where to check the latest data. Otherwise, the procedure will become another note alongside other notes.
Summary
Mini-SOP is not bureaucracy.
This is a simple way to make fewer things depend on the owner's memory, casual messages, and verbal agreements.
In a small accommodation facility, there's no need to create extensive procedures. It's enough to describe the most important moments of the day: a new booking, arrival, room preparation, payment, departure, and passing on information to the team.
This way, everyone knows what to check, where to save the information and what the next step is.
Because a well-organised facility isn't one where everything is documented in a thick binder.
It's one where the most important things don't get lost when things start moving.
