Write hospitality SOPs your team will actually follow

Define one task and one result, not a manual

A usable procedure tells you what to do and how to know you have finished. A policy manual sets general rules. When you run an aparthotel or short-term rentals in Colombia, keep that distinction clear: standard operating procedures in hospitality turn repeatable work into executable steps, rather than reading material detached from the job.

Separate these four tools:

• Policy: sets the rule, such as not releasing an apartment before inspection.
• Procedure: explains who inspects, what they check and how they communicate the result.
• Checklist: prompts the specific checks during that inspection.
• Completion evidence: records the outcome, who checked and any unresolved issue.

“Leave the apartment ready” is not a finish standard. In an illustrative example, releasing unit 402 could require checked cleaning, the agreed supplies in place and no unresolved issue that prevents guest use. Reception needs an explicit release confirmation. The housekeeping team leaving the apartment does not establish availability.

Give each procedure six boundaries: one task, its trigger, the role doing it, ordered steps, a completion standard and a route for stopping and escalating exceptions. As the owner or manager, you also need to identify who receives that escalation.

Tip: If your team cannot tell when the job is finished, your completion standard is not clear enough.

Use this decision question to set the scope: can the same person follow this sequence through to a verifiable result? If responsibility changes, specify the handoff or split the procedure. Do not leave reception and housekeeping to guess who owns the next step.

Start with the mistakes you most need to prevent

Prioritize standard operating procedures using failures you can point to: a reception log entry, a task sent back or an incomplete shift handover. Do not start with the easiest process to write. Start with the mistake you most need to prevent.

1. Sort the failures before drafting

1. Look for observed recurrence. Review issues with reception and housekeeping. Separate repeated failures from isolated incidents, but do not dismiss a single incident with serious consequences. If records are missing, collect observations before calling something frequent.
2. Describe the consequence. For arrival access, a guest may be unable to enter. For departure cleaning, an apartment may be released without inspection. For checkout, an unconfirmed departure can prevent housekeeping from starting.
3. Find the handoff. Identify who sends the information, who receives it and what confirmation is missing. “Reception sent a message” is not enough if housekeeping cannot tell which apartment is available.
4. Assess recovery difficulty. Ask what correcting the failure requires: finding a responsible person, obtaining authorization or repeating an inspection. Give it priority when recovery depends on someone unavailable during that shift.

Use this worksheet to compare cases. These are illustrative examples, not findings about your property.

Include emergency escalation in this review. Document contacts, backups and where to find the property’s applicable emergency plan. Do not improvise technical rescue or intervention instructions. Check relevant guidance with the alcaldía or local emergency authority in Colombia.

Tip: Prioritize knowledge held by just one person, too. When that person is absent, the safeguard disappears.

2. Choose your initial set

Which failure keeps recurring? Which consequence is hardest to contain? Where does the handoff break down? Which procedure would let staff act without relying on the manager’s memory? Choose a small set with available owners. Keep the other cases on record rather than trying to document everything at once.

Write with the person doing the work, then test it

A procedure written at a desk often leaves out what staff handle from memory: where a tool lives, who approves an exception or what happens when permission is missing. Observe before you draft. You are not testing the worker's ability. You are checking whether someone else can complete the task using the instructions and resources provided.

1. Observe, draft and test under controlled conditions

1. Watch the actual task. Follow the person doing it and note the sequence, questions and obstacles. Record what happens rather than replacing it with your preferred version.
2. Ask about exceptions. What is often missing? When should they stop? Who can help when they cannot continue? Capture required tools and permissions as well as actions.
3. Draft with that person. Turn their decisions into concrete instructions. If they say “reception knows that,” ask exactly what reception needs to know and where to find it.
4. Give the draft to another suitably trained colleague. Use a simulation if testing could disrupt guests, expose credentials or put staff at risk. Never remove safeguards to make the test feel realistic.
5. Observe without prompting. Record hesitation, backtracking, questions and repeated work. Stop the test if a risk appears. Withholding hints does not mean allowing harm.
6. Correct and retest. Address missing access, equipment or authorization before treating the problem as a lapse in attention.

Worked example: an access fallback only the manager knows

In this illustrative example, the night receptionist tests the procedure for an access failure. The instruction says “use the approved fallback,” but the receptionist cannot find it. The manager knows it by heart.

The receptionist's question is not the failure. The draft relies on invisible knowledge. Specify where to find the authorized fallback, which permission is needed and who receives the escalation if it cannot be used. Then repeat the test without exposing real credentials.

Tip: If you need to explain a step aloud during the test, record that explanation as a required correction to the procedure.

Accept the procedure when another suitably trained person completes the task independently, recognizes when to stop and escalates correctly. A signature confirms reading. It does not demonstrate successful execution.

Use one page with steps, photos and a finish standard

One page does not mean tiny print. It means you can find what to do, when to stop and how to finish without searching through a manual. On a phone, use short blocks in a vertical sequence. Put lengthy specifications and manufacturer instructions in a separate reference, clearly identified in the procedure.

1. Turn instructions into actions

Start each step with a verb: check, place, compare, record. Give each step one action. “Check the room” leaves the worker guessing. “Compare the bed setup with the reference photo” gives them something specific to do.

Put decisions where they arise: “If you find stained linen, set it aside and request a replacement before continuing.” Do not bury exceptions at the end of a long document. Distinguish a correction the worker can make from a condition that requires them to stop.

2. Copy this structure and fill in the fields

Use this template to write instructions, not to collect paragraphs. If one step needs several screens of explanation, move supporting detail into a reference without removing the essential directions.

PROCEDURE: [title] | ID: [identifier]
Applies to: [task and location]
Does not cover: [exclusions]
Starts when: [observable trigger]
Performed by: [role]
Procedure owner: [name or role]
Backup: [name or role]
Before starting: [supplies, tools and permissions]

1. [Verb + one action]
2. [Verb + one action]
   If [condition], [action or escalation route].
3. [Verb + one action]
Reference photo: [identifier and what to compare]

Finish standard: [observable result to check]
Completion record: [where to record result and open issues]
Stop if: [condition preventing further work]
Notify: [authorized contact and channel]
If unavailable: [backup and approved route]
Supporting reference: [location of detailed instructions]

Version: [identifier]
Approved by: [owner and date]
Review date: [date]

3. Make photos explain the standard

For example, an illustrative bed setup photo could say: “Compare the pillow orientation and the position of the bed cover.” Show the detail that matters. A wide room photo with no clear focus makes the worker guess what to inspect. A bed setup photo does not prove hygiene.

Keep guest documents, access codes and personal data out of these images. Define who can view them, where they are stored and when they are deleted. For photo access, retention and personal-data handling in your Colombian operation, check guidance from the Superintendencia de Industria y Comercio (SIC) and your applicable privacy policies and arrangements.

Before publishing:

• Every step names a clear action.
• Each photo has a purpose and a specific caption.
• Completion requires checking an observable result.
• Stop conditions and the route for getting help are easy to find.

Compare paper, spreadsheets and software

Choose the format around how your team finds instructions and records work, not how modern it looks. If someone has to search a chat history or ask the manager for access, the format is getting in the way.

Choose through a point-of-work test

1. For a small property, start by testing a controlled paper copy or a shared index. Ask a housekeeper to find the instruction and record the result where the work actually happens.
2. For several properties, check that staff can retrieve the right property's instructions rather than a similar document for another location. Consider software if coordinating assignments, attachments and updates across separate files is becoming difficult.
3. Test access without a connection and with an ordinary staff account. If either fails, establish a usable fallback before relying on the format.

A QR code is an entrance, not permission. It can lead to the current procedure, but the destination still needs access controls. Put a clear fallback beside the code, such as a controlled paper copy or directions to the backup available on that shift. Do not let the link expose guest information or restricted operational details.

Tip: Test with the team's actual phones and permissions. Working on your laptop is not the same as working during cleaning or at the front desk.

Keep the decision practical: use the simplest format that lets staff retrieve the current instruction and leave a usable completion record. Software is an option, not a prerequisite.

Assign ownership and put procedures into daily work

Every procedure needs an owner who keeps it current, not just someone who performs the task. Separate four responsibilities:

• Procedure owner: answers questions, proposes changes and schedules the next review.
• Person doing the task: follows the steps and records the result or blockage.
• Reviewer: checks the result against the completion standard.
• Backup: takes over when the primary person is unavailable.

In a small team, one person may fill several roles. Write down who holds each responsibility and who covers absences. If someone checks their own work, make that clear. Do not describe it as an independent check.

1. Attach the procedure to the task

Each recurring task should reference the current approved version, identify its assignee and state the completion check. Record the outcome and any blockage, including who owns the next action. Opening a document does not show that the work was completed correctly.

This illustrative schedule uses operational triggers, not regulatory deadlines.

Keep the next owner visible when work is blocked. A shift change does not make an unresolved task disappear.

2. Demonstrate, then ask for a teach-back

1. Demonstrate the task with the procedure open at the point of work.
2. Ask the employee to perform it and explain what they check before marking it complete.
3. Confirm they know when to stop and how to reach the backup.
4. Resolve uncertainties before assigning independent work.

Tip: During handover, confirm who accepts each open item. A shared list is not a substitute for accepted responsibility.

3. Review and replace outdated copies

Set a specific review date and name the person conducting it. Also review after an incident or a change to equipment, access or working methods. The designated approver must authorize a revision before it becomes the working version.

Use this update checklist:

• The task references the approved version.
• Obsolete copies have been removed from points of use.
• The backup can find and access the procedure.
• Affected staff acknowledge material changes and explain what changes in their work.
• Earlier completion records retain the version used at the time.

Worked example: from checkout to a ready apartment

Illustrative scenario: unit 402, checkout at 10:30

A 10:30 checkout is the scheduled departure time, not evidence that the apartment is empty. In this example, reception confirms departure through the property's agreed channel and records that turnover can begin. Until then, do not mark the apartment available or assume staff are authorized to enter.

1. Confirm departure and assign the task

1. Reception records confirmed departure and creates the turnover task for unit 402.
2. Assign a housekeeping team member to carry out the work and the housekeeping lead to inspect it. If your team combines roles, still identify who verifies the result.
3. Reference the current procedure and check prerequisites: authorized access, supplies, the protective equipment specified for the work, and serviceable equipment.
4. If something is missing, record the blockage and notify the lead before starting the affected step.

2. Follow the sequence and stop for the leak

These are abbreviated example steps, not a complete cleaning protocol:

1. Check the apartment's initial condition and report damage or found belongings under the property's procedure.
2. Remove waste and used linen using the property's defined separation arrangements.
3. Clean the bathroom, kitchen and other surfaces in the approved sequence, following the relevant product instructions.
4. Make the bed, replenish the specified items and compare the setup with the reference photos.
5. Check your work before requesting inspection.

Give photos practical captions: “Bed: pillows and linen arranged as shown” or “Kitchen: listed items in their designated positions.” A photo shows the setup standard; it does not prove hygiene.

During cleaning, the team member discovers a leaking fixture. They record its location and what they observe, without attempting a repair they are not authorized to perform. They stop the affected work and request that release be blocked. The housekeeping lead retains ownership of the turnover task and coordinates with maintenance. Sending a message does not transfer responsibility by itself.

Tip: A clean apartment is not ready if an unresolved issue prevents its release.

3. Inspect and explicitly release

After maintenance intervenes, the lead checks the reported correction and reinspects the affected areas. If cleaning must be repeated, the turnover task stays open.

• Departure confirmed and turnover work recorded.
• Cleaning and setup checked against the current standard.
• Leak addressed and the result checked.
• Inspection recorded and release authorized by the designated role.
• Reception informed before availability changes.

If the shift changes before resolution, reception receives the blocked status, outstanding work, next responsible person and next update point. The lead continues tracking the task until another person explicitly accepts the handoff.

Worked example: access fails on the night shift

Illustrative scenario: the guest at unit 305 cannot get in

A guest calls the night receptionist because the entrance will not open. The receptionist finds the booking, but the procedure only says “contact the manager.” It does not explain what to do if the manager is unavailable. That missing branch leaves the guest waiting and the receptionist guessing.

1. Verify before attempting a fix

1. Check the correct booking in the authorized record: property, unit and arrival status. Do not assume the guest is at the right building.
2. Confirm that the person is authorized to enter, using the property’s approved verification method. Urgency is not a reason to skip this check or request identity documents through an improvised channel.
3. Confirm which entrance the guest is using and what happens when they try it. Ask for a description of the fault, not passwords or photographs revealing credentials.
4. Follow the approved fallback for that property. In this example, an authorized on-duty colleague provides in-person assistance after guest verification. Do not share a master code or suggest forcing a door.
5. If the fallback is unavailable, escalate to Laura, the duty manager, then Andrés, the operations backup, following this example’s internal route. Your actual procedure needs current names, authorized contact channels and a clear condition for moving to the backup. “Call someone” is not an instruction.
6. Record who owns the case, which fallback was authorized and the outcome. Close it only after confirming that the authorized guest has entered and that any remaining fault has an owner.

Tip: When the approved fallback fails, escalate. Pressure to solve the problem does not authorize an improvised entry method.

Separate guest updates from restricted notes

Tell the guest: “I’m coordinating authorized assistance for your entry. I’ll update you through this channel once it is confirmed.” Do not promise an arrival time that nobody has confirmed.

Keep verification results, the reported fault, contact attempts, decisions and entry confirmation in the restricted operational record. Do not copy credentials into it. Do not send internal notes, staff personal details or security arrangements to the guest.

Add the missing decision branch

Common mistakes include skipping verification, repeating attempts without a stopping rule and leaving the case unowned at shift change. If Laura did not answer and the procedure had no backup, add the escalation condition, alternate contact and interim case owner. Have the revision approved and tested before replacing the current copy.

If a safety concern arises, follow the property-specific safety arrangements. Check their alignment with guidance from the alcaldía or relevant local emergency authority in Colombia rather than inventing technical response instructions.

Fix the process when something goes wrong

Recover the operation before assigning blame. A failed task does not, on its own, show that someone ignored the procedure.

1. Contain the problem and assign recovery

1. Contain the immediate impact. For example, if housekeeping finds a leak in unit 402, stop its release and notify reception. Do not improvise repairs beyond your training.
2. Name the next owner. Record who coordinates the fix, what they need to resolve and who covers their absence. “Maintenance notified” does not establish ownership.
3. Preserve the facts. Note what happened, when, which step applied and which version was available. Separate observations from assumptions and avoid unnecessary personal data.
4. Set the next update. Specify who will update reception and when they will report again, even if the task remains blocked. Give the guest only the information needed to manage their stay.
5. Restore and verify. Check the result before closing the task or releasing the apartment. Record who checked it and what they found.
6. Review the cause. Work with the person who performed the task, using the record and the instructions they actually had available.

2. Fix the cause, not just the document

For a knowledge gap, demonstrate the step and ask the person to repeat it independently. Missing supplies, permissions or capacity to handle simultaneous tasks need operational fixes. More training will not supply those resources.

For contradictory versions, withdraw obsolete copies and publish the current one. For inaccessible files, correct permissions and provide a usable fallback. For excessive detail, separate instructions from reference material. For unrealistic steps, redesign the task around available resources.

A ticked box without verification needs an observable completion standard. Knowledge held only by the manager needs shared, tested instructions. If a clear, feasible step was genuinely skipped, discuss what happened without automatically treating it as misconduct. Check Ministerio del Trabajo guidance and applicable policies before drawing employment-policy conclusions in Colombia.

Tip: An edited file is not a completed correction. Have another person test the revised step without coaching.

Copyable note: from incident to procedure change

Observed facts: [what happened and when]
Affected step and version: [reference]
Temporary control: [measure pending correction]
Correction owner: [name]
Proposed change: [adjustment]
Approval: [name and date]
Retest result: [outcome and outstanding issue]

Measure execution, rework and current versions

Opening an SOP does not prove it was followed. Measure task results, inspection findings and closure records instead. Use a consistent reporting period and keep the underlying records so you can check each calculation.

Define what counts in each measure

• First-inspection pass rate: inspected tasks meeting every completion criterion at the first check, divided by all tasks with a recorded first inspection, multiplied by 100. Exclude uninspected tasks and subsequent checks. Report the total number of completed tasks separately from the inspected sample.
• Rework rate: completed tasks that needed correction because they failed their completion criteria, divided by completed tasks with recorded follow-up, multiplied by 100. Count each task once. Exclude cancellations and new requests that change the scope. Show tasks without follow-up separately.
• Current SOP coverage: active SOPs with a named owner and an up-to-date review, divided by all active SOPs, multiplied by 100. Treat a review as current when it is recorded, its next review date has not passed and no incident-related change remains unassessed. Exclude drafts and withdrawn documents. A missing owner or review date stays in the denominator as an outstanding item.

Copy a tracking sheet

The rows below are illustrative examples, not actual results. Replace them and add rows for your tasks. Closure evidence should let someone verify the outcome, rather than merely confirm that a box was ticked.

If you measure turnaround time, define the start, finish and blocked time. For example, start at confirmed departure and finish at recorded release. Log when each blockage begins and ends. Distinguish total elapsed time from time excluding blockages; they answer different questions.

Tip: Always show the numerator and denominator beside the percentage. A result without its sample size can hide more than it reveals.

Missing information means unknown, not success or confirmed failure. With small samples, examine individual cases before claiming a trend. Compare equivalent tasks using the same criteria and comparable conditions. Do not combine departure cleaning and access checks into one performance figure. Use the records to identify which step needs fixing, not to impose a universal target.

Launch your first procedure and check it works

1. Put one task into use before expanding

1. Choose an observed failure, not an entire department. An illustrative starting point is an apartment marked available before its inspection was confirmed.
2. Name the procedure owner and backup. Draft the instructions with the person who performs the task.
3. Ask another suitable team member to test the draft without coaching, under conditions that do not put guests at risk. If they need help, revise and test again.
4. Publish the approved version where the work happens. Remove obsolete copies and connect the current procedure to its task, using paper, a spreadsheet or a task tool.
5. Review completion evidence and blockages with the person who did the work. Improve before expanding to more tasks or properties.

2. Run a readiness check

Copy these questions into your launch checklist:

• Can you find the procedure at the point of work?
• Can you perform the task without coaching?
• Can you recognize when to stop?
• Can you contact the responsible person and their backup?
• Can you demonstrate that the completion standard was met?
• Can you identify the current version?

If any answer is no, fix that gap before extending use.

Tip: Scale what people can execute, not what you have finished writing.

3. Keep one core and controlled local details

Maintain a shared core procedure with clearly identified property references for entrances, equipment and contacts. Give those references owners and versions. Avoid creating a separate, uncontrolled copy of the whole procedure for every building.

Your next action: choose one actual failure and assign drafting and testing as a task, with a named owner and a record of the test result.