Self check-in vs front desk: how to choose

Choose an arrival process, not just a way to unlock a door

Choose a model you can support through to a completed arrival. Start with building restrictions, realistic staffing coverage and the full operating cost, including backup. Self check-in vs front desk is not a contest with a universal winner.

Whatever you choose, you own five outcomes:

1. Verify the arriving guest’s identity.
2. Complete the applicable guest registration. Check what applies to your operation with MinCIT and Migración Colombia.
3. Give the guest authorized access.
4. Explain what they need to know about the accommodation.
5. Confirm they are inside and settled.

Collecting information through a form does not, by itself, establish who has arrived.

Self check-in removes the in-person handover, not your responsibility for support. A staffed front desk provides on-site assistance within its assigned hours, which may not cover every arrival. A hybrid model combines remote tasks with in-person help. Building security has a separate role under the building’s arrangements; do not count it as reception coverage without an agreement.

Tip: Give each arrival an accountable owner, even when nobody from your team is on site.

For an illustrative booking in apartment 402, a sent code proves only that access information was sent. Keep the arrival open until you confirm the guest got inside and received the guidance they needed.

Compare all three models against the same criteria

Apply three filters before comparing preferences. Does the building allow the proposed access arrangement? Can you complete the applicable verification, rather than merely collect a form? Is support available, with an approved alternative if arrival stalls? An unanswered question means the option is not yet validated.

Use confirmed conditions to narrow your options

Do not score service preferences until you have settled the constraints. Use this matrix to retain arrangements you can actually operate.

Follow a short decision path

1. If your own team must attend, choose staffed or hybrid coverage for those arrivals. Required attendance does not automatically justify a permanent desk.
2. If physical assistance is occasional and foreseeable, consider a hybrid before staffing every arrival.
3. If you can complete and support the whole journey remotely, keep self check-in among your options.
4. Compare full costs only after establishing viability. Lower cost cannot override an access constraint.

Flexibility depends on the whole journey, not just the lock. Check whether connectivity, instructions and verification let guests finish it. Reception earns its place when on-site assistance resolves recurring obstacles. Remote arrival works when physical attendance is unnecessary and help is genuinely available. Neither option removes follow-up work, and a staffed desk does not automatically mean continuous service.

Tip: Choose from confirmed operating arrangements, not service labels. A model that depends on help nobody has agreed to provide is not yet a workable option.

Check building access rules and registration first

Before you offer self check-in, establish what the building permits and what remains your responsibility as the operator. Building entry approval is not the same as accommodation registration. Completing one does not establish that the other is complete.

1. Establish who approves entry

Ask building management for the current access procedure and keep a record of the arrangement. Confirm who approves arriving guests, how approval reaches the porter and how your team knows it has been received. Ask separately about visitors and changes to the arriving party.

Sending a guest list is not necessarily confirmation of entry permission. Identify the acknowledgement your team needs before telling a guest that access is arranged.

2. Set clear boundaries for the porter

Find out whether the porter only controls building entry or whether other tasks are covered by an explicit agreement. Do not assume they will check documents, hand over keys or troubleshoot your arrivals.

Ask whether in-person registration is required and who must handle it. If someone from your operation needs to attend, build that requirement into your arrival model. An advance form does not automatically replace that attendance or complete every applicable verification.

3. Check exceptions before promising flexibility

Confirm the process for out-of-hours arrivals, missing authorisations and an unavailable regular contact. Name an operational owner, a backup and the building contact authorised to resolve access questions. If management has not accepted a fallback, do not promise unattended entry under those conditions.

Tip: “The porter knows us” is not an access procedure. Keep current instructions and establish who has authority to resolve an exception.

4. Check registration requirements with official sources

Consult MinCIT about the Tarjeta de Registro de Alojamiento (TRA) requirements relevant to your property, including the current process, required information and registration method. Check with Migración Colombia whether SIRE reporting applies and confirm the current conditions, data requirements and deadlines for your situation. Do not treat these processes as interchangeable or assume your pre-arrival form completes them.

5. Decide how guest information will be handled

Review guidance from the Superintendencia de Industria y Comercio on purpose, access, retention and secure handling of personal data. Choose an appropriate collection channel and specify who can view the information. Do not retain document copies by default. Establish why they are needed and the applicable basis for processing before requesting them.

Before selecting your model, check:

• Building management has confirmed the entry procedure.
• Porter duties and any in-person registration are clear.
• Visitors and out-of-hours arrivals have an agreed process.
• An owner, backup and escalation contact are identified.
• TRA, SIRE and data handling have been checked with the relevant official sources.

Match arrival patterns to the help guests actually need

Review how guests arrive, not just their scheduled arrival times. A late arrival can work without a staffed desk when access is approved and backup is available. An arrival during reception hours can still stall if several guests need help at once.

1. Review the arrival records you already have

Compare expected and actual arrival times. Look for overlapping arrivals, requested languages, connectivity problems and reasons guests asked for help. Mark missing information as unknown: no record does not mean no problem.

Separate assistance needs from service preferences. A guest who needs instructions in another language may not need an in-person welcome. Someone who prefers a personal handover may still be comfortable using a lock. Ask what support would help rather than making assumptions based on age or nationality.

2. Check whether support matches those arrivals

For each arrival, confirm:

• The guest can retrieve the instructions on arrival, including without mobile data.
• The language and format of the instructions work for them.
• A named person is available to handle difficulties during their expected arrival.
• Simultaneous arrivals do not depend on one person already occupied elsewhere.

Tip: Sending instructions is not proof that self check-in will work. Check whether guests can use them at the point where access begins.

Worked example: apartment 402 at 22:30

In this illustrative scenario, the guest arrives without mobile data. The building porter is still waiting for entry authorization.

1. Identify the barriers: the porter contacts the arrival lead through the agreed channel. The lead separates the connectivity problem from the missing authorization.
2. Assign ownership: the arrival lead checks the booking and arranges authorization through the building’s accepted process. They do not ask the porter to skip controls.
3. Use the approved alternative: if the guest cannot retrieve the instructions, the lead arranges an in-person handover with the designated backup.
4. Confirm entry: the lead checks that the guest entered apartment 402, not merely that they passed the building entrance.

Connectivity, authorization and backup availability should have been checked before promising an independent arrival. If these situations recur and require someone on site, choose hybrid or staffed coverage for those arrivals. If remote support can resolve them with workable backup, you do not need to staff every arrival.

Count the full cost, including backup coverage

Compare the same arrival volume and service scope: coverage hours, assistance offered and backup when access fails. A desk staffed for a limited window is not equivalent to self check-in with round-the-clock support.

Complete a common worksheet

Copy this header and fill it in before calculating. Use the same period, currency and arrival volume for every proposal.

Reporting period: [period]
Currency: [currency]
Comparable arrival volume (L): [number]
Coverage hours: [days and hours]
Service scope: [included tasks and backup arrangements]

Enter costs attributable to that period in the table. The source column identifies the inputs and where to find them. Do not assume an expense disappears when you switch models.

Complete this companion note for each proposal. Retained shared costs describe resources you still use, not savings.

Proposed model: [model]
Current cash spending for the period (D): [amount]
Avoidable spending that disappears (E): [amount and items]
Retained shared costs: [amount and allocation basis]
Additional spending required (A): [amount and items]
Owner-time valuation: [hours and valuation basis]
Separate initial cash outlay: [amount]

Worked comparison using variables

For a proposed switch to self check-in, calculate D − E + A = proposed cash spending. Use the same calculation for reception or hybrid coverage. Unless an expense actually disappears, do not classify it as avoidable.

For an illustrative example, a receptionist handles arrivals and coordinates housekeeping. Allocating part of that shift to check-in measures resource use, but creates no cash saving if you must retain the shift. Do not charge the full shift to both activities or add tasks already included in coverage costs.

Calculate C / L to compare attributable resources. Keep that measure separate from the change in cash spending. Do not include both the full purchase price and its amortized share in the same period total.

Tip: Count the owner's time even when no immediate payment is involved. Show its valuation separately from cash spending so unpaid work does not look like a saving.

Self check-in can shift costs into support and callouts. Hybrid coverage requires coordination. Reception still needs backup outside staffed hours. Distinguish active work from paid availability.

For working hours, pay premiums and employment conditions in Colombia, check current information from the Ministerio del Trabajo and seek a professional budget review. Incomplete employment costs are not a sound basis for projected savings.

Design hybrid coverage with clear handoffs

Hybrid coverage needs one clear owner for each arrival, even when several people contribute. Define who acts, what they can decide and who takes over unfinished work. Guests should not have to coordinate your team.

Choose between two workable arrangements

Advance details followed by a short in-person handover. Collect information before arrival and review outstanding items. At reception, complete the applicable checks, confirm the unit is released and hand over access. Preparation does not replace unfinished verification.

Self-service access with remote support and agreed on-site backup. Name someone to handle difficulties during the stated coverage window. Arrange who can attend when physical help is needed. Confirm their availability and authorized building access before promising that backup.

Set ownership and coverage boundaries

1. Name the lead and backup. Assign both for each arrival window, including who takes over when the lead is busy.
2. State coverage hours. Separate desk hours, remote support and on-site backup availability. Define the alternative for arrivals outside those windows.
3. Set escalation triggers. Missing authorization or a problem requiring physical attendance needs a named recipient with clear decision limits.
4. Require acceptance. Pass on the status, outstanding task, agreed update time and any event requiring an earlier update. The current owner keeps responsibility until the recipient accepts.

Tip: A handoff ends when someone accepts the task, not when you send it.

Worked example: three arrivals, two support channels

In this illustrative example, guests for units 401, 402 and 403 arrive together. The housekeeping lead has not yet released 402. A remote question also comes in from a later arrival, identified as P04.

The receptionist stays with the guests on site; the backup takes P04 and confirms ownership. The remote query no longer interrupts every face-to-face handover.

The receptionist completes the authorized arrivals for 401 and 403 and agrees on an available waiting arrangement with the guest for 402. Access is not issued early. The receptionist agrees on a time to update that guest, even if housekeeping has not confirmed release by then. If the unit becomes ready earlier, the guest hears immediately.

The housekeeping lead confirms release when ready. The receptionist retains the 402 case until the handover is complete or another person accepts it. The backup resolves P04 or escalates it within the agreed decision limits.

Copyable handoff sheet

Use a shared sheet restricted to the people who need it. These rows reflect the example after arrivals 401 and 403 are complete. Leave out identity documents and access credentials. Replace each bracketed field with an agreed time. An event can bring the update forward, not postpone it.

Before each arrival period, review assignments, coverage windows and open tasks. If the agreed time arrives without a resolution, explain the status and agree on the next update. No progress is still a reason to communicate.

Build an arrival runbook the whole team can follow

Your runbook should show what is missing, who owns it and what allows the next step. Keep it in a shared sheet or your existing operating tool. Assign an owner to each arrival. Sending instructions does not complete the job.

1. Review the booking and prepare the guest

Check the assigned unit, expected arrival and contact channel. Record outstanding information and verification checks, with an owner. A completed form does not mean verification is complete.

You can send the location, intended entrance and help contact before the unit is released. Make clear that this is preparation information, not permission to enter. Explain that you will confirm when access is ready.

2. Check the conditions for enabling entry

Wait for explicit unit release from the person responsible. Also confirm applicable verification, building authorization and current instructions. “Cleaning finished” does not mean “ready for arrival” if an inspection remains outstanding.

3. Deliver access with clear limits

Check what your system supports: limited validity, deactivation or manual handover. Do not promise controls you do not have. If a key must be collected or a credential disabled manually, assign that task. Keep credentials off open worksheets and remove old access details from reused messages.

Use this template only once all entry conditions are satisfied:

Subject: Ready for your arrival at [property]
Hello [name],
Your expected arrival is [date and time].
Your apartment is ready. You can now enter using the instructions below.
Address and entrance: [location and directions].
Apartment: [unit].
Arrival instructions: [current entry steps].
Access handover: [authorized channel or collection point].
Access conditions and validity: [verified conditions].
For help: [contact channel and coverage hours].
If you cannot reach that contact: [approved alternative].
Once inside the apartment, please reply here to confirm.

4. Confirm entry and close the task

A read receipt does not prove that the guest got inside. For example, record “guest confirmed entry to unit 402,” rather than just “instructions sent.” Confirm that the guest also received essential guidance on using the unit and getting help.

If the guest does not respond, record “entry unconfirmed.” Assign a follow-up owner and record the next contact action through the agreed channel. Silence proves neither successful entry nor a lockout. Keep the task open until the situation is clear. If coverage changes, require the next owner to accept the handover.

Tip: Close the arrival on a confirmed outcome, not a sent message.

• Verification, authorization and unit release are confirmed.
• Access is delivered and credential control tasks are assigned.
• Entry and orientation are confirmed, or follow-up is assigned.
• Outstanding items are resolved or accepted by the next owner.

Resolve failed arrivals without bypassing verification

An access failure needs a decision, not an improvised exception. Keep verification in place and change the support route. A booking does not justify handing over any available key.

1. Confirm location and booking

Confirm the building, entrance and booking through the authorized channel. Do not request identity documents in an open group chat. If the guest’s phone is dead, use the agreed in-person contact point. Building security can help only within its authorized role. Another message to the same phone is not a fallback.

2. Identify the barrier and choose a response

Use this table as an operational reference. Replace role labels with your team’s assigned contacts. No fallback permits bypassing checks, sharing master codes or forcing doors.

Do not treat a screenshot alone as sufficient proof. Check applicable registration requirements with MinCIT and Migración Colombia. Do not promise a handover time nobody has confirmed.

3. Assign ownership and check the outcome

Put one person in charge, with a backup if they cannot respond. Tell the guest who is helping and what happens next. Confirm entry into the assigned unit and record the barrier, intervention and closure without recording credentials.

Tip: Close the incident when you confirm the solution worked, not when you send it.

Worked example: a credential fails at night

In this illustrative example, the night receptionist confirms that the guest is outside unit 402. The credential still fails after its validity is checked. The receptionist requests the authorized backup for that unit, rather than sharing a master code or opening another apartment as a shortcut.

Smoke, threats or physical danger require an emergency response, not just access support. Check your emergency plan and response routes with the alcaldía (local mayor’s office) and the relevant cuerpo de bomberos (fire service). Do not improvise unsafe entrances or exits.

Avoid mistakes that push the work onto guests

Asking guests to resend information or work through conflicting directions makes them carry your unfinished work. Fix the source instead of adding another message to their arrival.

Three mistakes you can remove

Requesting information you already hold. Guests repeat themselves while your team creates competing versions. Your registration owner should check the existing record before asking for anything else. Request only what is missing and track its status rather than making another copy. If staff cannot see information already submitted, investigate that internal access problem before contacting the guest again.

Leaving old instructions in circulation. Editing the original does not update saved replies or printed copies. Your instructions owner should identify the current version and remove superseded copies wherever staff send directions. In an illustrative example, changing the pedestrian entrance for apartment 402 also means checking reception's saved reply. Saving the correction is not the end of the job.

Keeping permissions out of habit. A change in duties can leave someone with access they no longer need. Your system administrator should remove obsolete permissions and check that remaining access matches each person's responsibilities.

Copyable instructions and access control checklist

Paper requires replacing physical copies. A shared spreadsheet makes updates easier, but you still need to check permissions and history. With software, verify those controls before relying on them. No format makes decisions for you or guarantees compliance.

• Current instructions have a named owner.
• Superseded copies and saved replies have been removed.
• Authorized viewers and editors have been reviewed.
• Change history has been checked; where unavailable, someone owns a manual change record.
• Obsolete access has been removed and the removal checked.

Tip: Before resending a request or directions, check what the guest has already received and which version is current.

Use a simple log to see whether your model works

Log every arrival using the same definitions, including arrivals without problems. Recording only failures gives you no reliable basis for comparing self check-in, a staffed desk and hybrid coverage. Use an operational reference, not guest names, identity documents or access credentials.

A log you can copy

These rows are fictional examples, not measured results. “Actual arrival” means the guest reached the agreed access point. “Access confirmed” means you established that they entered their unit, not simply that they read your instructions.

Example A takes 12 elapsed minutes but requires 5 minutes of active work. Waiting time is not working time. Example C has no usable arrival-to-access duration yet. Do not turn that missing value into zero.

Four measures worth tracking

1. Arrival-to-access time: confirmed access time minus actual arrival time. Use your operational log and entry confirmation as sources. If you calculate an average, include only complete cases and report how many remain unresolved.
2. Share requiring unplanned help: arrivals needing unplanned help ÷ arrivals with a completed intervention classification × 100. Use the intervention field. A scheduled in-person handover is service, not a failure.
3. Active support minutes per arrival: total active support minutes ÷ arrivals with complete support records. Count everyone's work, including your own. Enter zero only when you know no intervention occurred.
4. Attributable cost per arrival: total cost attributable to the model ÷ arrivals handled during the same period. Use your operating-cost calculation and arrival log. Do not count shared working hours twice.

Tip: Compare like with like: arrival hours, assistance needs and coverage scope. A late arrival with unresolved support needs is not equivalent to a scheduled front-desk handover.

At each review, check:

• Open cases remain visible and have an owner.
• Planned assistance is separate from access failures.
• Missing values have not become zeros.
• Findings lead to changes in coverage, instructions or handoffs, rather than automatic blame for staff.

Compare periods with similar guest needs and arrival patterns. You do not need a universal target. You need to understand where guests wait and how much work each model actually creates.

Choose, test and set clear reasons to change course

Choose the model you can support throughout an arrival, including when something fails. Copy this checklist and tick only what you have confirmed:

• Building rules allow the proposed access process, and building staff understand their role.
• You can complete applicable verification and registration. Resolve outstanding questions with MinCIT or Migración Colombia, as appropriate.
• You know the assistance needs of the arrivals included.
• A lead, backup and coverage hours are confirmed.
• Your full cost includes backup support.
• The unit will be released before you authorize entry.
• You have tested an approved alternative if access fails.
• Someone owns incident logging and the review of results.

1. Run a bounded trial

1. Select arrivals that fit your building rules and available coverage. Exclude cases with unresolved verification questions.
2. Confirm who makes decisions, who responds and who accepts the handover. Tell guests how to request help.
3. Have a responsible person review each arrival: confirmed entry, assistance needed and unresolved issues.
4. Pause the trial if verification cannot be completed, authorization is missing, the unit is not ready or agreed backup becomes unavailable. Resolve the case before expanding the trial.

Tip: Set your stop conditions before you start. Self check-in should not rely on someone improvising a rescue.

2. Record the decision and review point

Use this short note without guest details or access credentials:

Chosen model: [model]
Arrivals included: [scope]
Restrictions: [conditions]
Coverage and backup: [roles and hours]
Tested alternative: [procedure and result]
Evidence still needed: [item and owner]
Stop conditions: [conditions]
Review date: [date you choose]
Decision owner: [role]

Move from self check-in to a hybrid when arrivals need predictable in-person help. Strengthen reception when simultaneous arrivals or assistance needs exceed available coverage. Keep the model only when your records show you can support it, not because you have already paid for it.