From 5 to 30 Units: How to Scale Your Rental Operation

Grow by operational capacity, not just unit count

Going from 5 to 30 units means handling more simultaneous work, not simply managing more apartments. Arrivals, cleaning and exceptions must keep moving when you cannot answer. Scaling a short term rental business starts with testing that capacity before accepting more inventory.

Unit count alone does not tell you when to hire or change tools. Look at how the work lands:

• Geography: travel between buildings takes time away from inspections and guest support.
• Turnover concentration: departures clustered together create a different workload from departures spread out.
• Building access: keys, reception desks and entry authorizations can hold up a release.
• Service promises: early arrivals leave less room for cleaning and checks.

Spot the four breaking points

Founder dependence means routine exceptions wait for your approval. Undocumented knowledge means only one person knows how to enter or inspect a unit. Reactive pricing means rates change under pressure without shared criteria. Scattered records mean reception and housekeeping act on different versions of the facts.

Tip: Test what your team can handle at the same time, not just how many units it manages.

Make the readiness decision

Check recent cases rather than relying on reassurance:

• Reception can complete an arrival using current information.
• Housekeeping can finish a departure turnover and show that the unit is ready.
• An accountable person can resolve or escalate an exception without searching your personal chat.

Can the team complete an arrival, a departure and an exception without waiting for the founder? If not, pause expansion and fix the specific dependency before adding units.

Remove the founder from repeat decisions

If every change needs approval in your personal chat, you have distributed tasks without handing over decisions. Your team needs to know what it can decide, what evidence it needs and when to escalate.

1. Identify recurring approvals

1. Review recent requests: late departures, booking changes, replacement items and maintenance visits.
2. Record who requested approval, what information was missing and why the request reached you.
3. Separate routine decisions from exceptions. A familiar request can still be exceptional if it affects another booking or exceeds the assigned authority.

2. Give each decision an owner and boundaries

1. Assign an accountable role and a backup. “Whoever sees the message” is not an owner.
2. Specify what that person must check before answering: availability, outstanding work and confirmed commitments.
3. Set your own authority limits and escalation conditions. Where spending is involved, identify who can approve it under your operating rules.
4. Name the escalation recipient when you are unavailable.

Delegating a decision does not mean granting unrestricted access to funds or guest information. Give each person only the access needed to carry out their responsibility.

Tip: Delegate a decision rule, not just permission to ask someone else.

Illustrative example: a late departure in unit 402

Unit 402 has a 10:30 checkout. The guest asks to leave later. Instead of forwarding the request to your personal chat, reception checks the cleaning plan and the promised arrival.

The agreed rule allows approval only if the revised departure will not disrupt cleaning, inspection or release. Reception checks that condition with the housekeeping coordinator. If it holds, reception confirms the option with the guest and records the approved departure time. If there is a genuine scheduling conflict, reception escalates to the designated decision owner. The team does not make a promise first and solve the conflict afterward.

3. Record the outcome and improve the rule

1. Save the request, checks, decision, accountable person and communicated commitment in the relevant operating record.
2. Review exceptions: was information, authority or capacity missing?
3. Revise the rule where needed. A one-off approval must not become permanent permission by accident.

Use a practical test: can the next shift understand and uphold the decision without calling you? If not, clarify the record or the authority boundary rather than taking every decision back.

Document the routines that prevent costly mistakes

Start with routines where a missed step blocks the next person: booking changes, arrival access, guest registration, departure cleaning, inspection and release, maintenance escalation, and shift handover. Prioritize routines that already cause rework or rely on someone remembering an unwritten detail.

You do not need a long manual. You need instructions another person can follow without calling you.

1. Separate the rule from the method

A policy sets the rule: do not confirm a unit is ready without inspection evidence. A procedure explains how to inspect it, record the result, and communicate its release. A checklist helps the person verify that nothing was missed. It does not replace the instructions.

2. Write one short procedure per routine

Identify the trigger, executor, ordered steps, completion evidence, and escalation route. Name the role responsible for keeping the document current, too.

Copy this template and complete it with your team:

Routine: [name]
Version and date: [version, date]
Document owner: [role]
Trigger: [event that starts the task]
Executor and backup: [roles]
1. [initial action]
2. [required check]
3. [completion record and notification]
Completion evidence: [record or supporting material]
Exception: [when to stop and whom to contact]

3. Make completion verifiable

Here is an illustrative internal unit-release note:

Unit: 402
Event: [departure identifier]
Cleaning: completed by [responsible person]
Inspection: performed by [responsible person]
Result: release pending, one key still needs checking
Escalation: [responsible person and notification time]
Final release: [responsible person, date and time, evidence]

Cleaning finished does not mean ready for arrival. Reception needs a confirmed status, not a conversation to interpret.

Tip: Test the procedure with someone who did not write it. If they need a spoken explanation to finish, add that explanation to the document.

4. Test, then revise

1. Watch someone follow the procedure without supplying missing steps from memory.
2. Mark unclear instructions, missing evidence, and exceptions with no escalation recipient.
3. Revise the document, identify the current version, and remove outdated copies.
4. After a failure, fix the step that allowed it and test again.

Common mistakes include writing “check everything,” closing tasks without evidence, and leaving documents without an owner. Keep internal operational notes separate from guest messages. Never copy access credentials, staff comments, or internal escalation details into an external reply. The guest needs confirmed information and the next step, not your operational conversation.

Separate responsibilities before adding job titles

Separate responsibilities when tasks compete for the same attention, not when you reach a particular unit count. Guest messages can interrupt inspections. Maintenance follow-up can disappear during arrivals. Financial checks can keep slipping because the person responsible is always covering reception. These are coverage problems, not necessarily reasons to create four new positions.

One person can hold several roles. Each outcome still needs one clearly accountable owner.

1. Plan coverage around overlapping work

1. Map the busy periods. Identify when messages, departures, inspections and maintenance requests overlap. Include travel between properties, access delays and the work itself. A person travelling to another building is not available at reception.
2. Assign an owner and backup. Cover breaks, days off and absences. Check that the backup is actually available, can find current records and has the authority needed for the role.
3. Test simultaneous demands. In an illustrative example, the housekeeping coordinator is inspecting unit 402 when reception needs another unit checked. Name who handles that second inspection. Do not allocate the same person to both locations.
4. Make the handoff explicit. Record the open issue, current commitment, next step and receiving person. Ask the receiver to confirm understanding rather than assuming that a sent message completes the transfer.
5. Decide what needs separating. Redistribute duties, extend coverage or establish a dedicated role when interruptions repeatedly leave work unfinished, travel creates response gaps or financial review becomes rushed and unreliable.

Tip: A backup who cannot access the current record or make authorized decisions is only a name on a roster.

Before changing contracts, working hours, rest arrangements or outsourced services in Colombia, check current rules with the Ministerio del Trabajo and qualified local advisers. Do not assume that outsourcing a task automatically settles your obligations.

Plan cleaning and releases around actual workload

Your capacity is not the number of people available. It is the work you can finish, inspect and release before each confirmed arrival. A cleaned apartment that still needs inspection is not ready for a guest.

1. Build the plan from observed timings

1. Match departures to confirmed arrivals. Identify which units need a turnover and the arrival commitment for each one. Keep requests for early arrival separate from promises you have already made.
2. Allow for the whole job. Use observed durations from comparable units. Include supplies, building access, travel, cleaning, inspection and corrections. Cleaning time alone does not tell you whether the schedule works.
3. Assign cleaning and inspection. Name the person doing each job and confirm an available backup. Check that assignments do not overlap with other work or the travel needed between properties.
4. Check the resources. Confirm keys, entry authorization, linen, products and equipment before accepting the schedule. An available cleaner without access or supplies is not usable capacity.
5. Update readiness with evidence. Reception needs the outstanding work, its owner and a confirmed release time. Mark a unit ready only after its inspection is complete.

Worked example: several departures on the same day

Every time below is an illustrative planning assumption, not a service standard. Work windows cover preparation and cleaning; travel must be checked separately.

Ana's assignments work only if travel from 402 to 308 fits between those windows. Check the inspector's travel too. Empty space in a schedule is not automatically available working time.

2. Replan when the day changes

In this example, checkout from 402 runs late and Luis does not arrive for his shift. Do not leave the schedule unchanged.

1. Confirm the revised departure and contact the backup.
2. Reprioritize by arrival commitments and remaining work, not by who asks most insistently.
3. Assign the backup only after confirming travel, access and supplies. Recheck inspection capacity as well.
4. Tell reception which releases remain achievable and which are at risk. If a commitment cannot be met, escalate the conflict and offer guests only confirmed alternatives.

Tip: Stop promising early arrivals when capacity has not been validated. A possibility is not a confirmation.

If the plan works only by skipping inspections, assuming unconfirmed help or ignoring travel, stop adding bookable inventory until you close that capacity gap.

Choose where each record lives and who maintains it

One authoritative location per record type does not mean one application for everything. Reservations can live in one tool and tasks in another. Your team must know which record governs, who updates it and where to resolve a discrepancy.

Choose around the work, not a unit-count threshold. A maintained spreadsheet beats a platform nobody keeps current.

1. Give every record a home and an owner

1. Inventory your records: reservations, physical units, tasks, incidents and supporting files. Name the authoritative location, maintainer and backup for each type.
2. Clean duplicates. Resolve conflicting details before moving them, while preserving the history you need.
3. Map stable identifiers. In an illustrative example, BLDG-A-402 identifies a physical apartment. Its listings on different channels have separate identifiers linked to that apartment. Do not count each listing as another unit.
4. Test a sample: a changed reservation, a cancellation and a task with an attachment. Check dates, unit, status and ownership against the source.
5. Validate role-based access. Reception and maintenance do not automatically need the same guest information. Check attachment permissions too. For personal-data handling in Colombia, consult guidance from the Superintendencia de Industria y Comercio.
6. Set the cutover point and stop duplicate editing. Keep the old record read-only, with restricted access where appropriate.

Check that the record stays current

A reservation change belongs in its authoritative record and must reach affected tasks. Each task needs an owner, status and completion evidence. A chat message can notify the team; it should not become a competing record.

For integrations, check last successful sync, direction of exchange and unresolved errors. Do not assume every field updates immediately. Assign someone to reconcile differences against the agreed source, especially after a failed sync or manual correction.

Tip: Before relying on a tool, test an export. Check that you can retain identifiers, useful history and links to supporting files, not just a list of current reservations.

Avoid three common mistakes: migrating duplicates untouched, leaving two editable versions in circulation and treating a photo buried in chat as evidence the next shift can reliably find. Your record is only useful if the next person can trust it.

Control pricing and contribution by unit

A booking does not prove that a rate works. You need visible assumptions and a named reviewer. More revenue does not automatically mean more money left over.

1. Set authority for rate changes

1. Name a pricing reviewer and a backup. Define which units and stay dates they cover.
2. Record the assumptions: stay length, turnover costs, channel charges, discounts and included services.
3. Set your own rate-floor rules and approval conditions. Do not copy another property's floor without checking its costs.
4. Assign an approver for exceptions. If that person is unavailable, follow the current rule rather than assuming permission.
5. Log the previous rate, new rate, affected dates, reason, reviewer and approval. Check what was actually published afterward.

Tip: Compare the expected revenue from the whole stay with its costs. A nightly rate can look adequate until you include the work between guests.

Keep sales, revenue and cash separate

Gross booking value is the recorded booking total before deductions; identify its components. Earned accommodation revenue relates to accommodation already provided, not every future booking. A channel payout reflects what the channel settles after its adjustments. Cash received is money that actually arrived, potentially for a different period.

Do not substitute one figure for another. For tax treatment, invoicing and accounting questions in Colombia, check current guidance with DIAN and your accountant.

2. Define the period and calculation base

1. Cost per completed turnover: cleaning, laundry, supplies and inspection costs attributable to turnovers completed in the period, divided by those completed turnovers. Exclude unfinished work from both sides.
2. Operational cost per booking: operating costs attributable to bookings departing in the period, divided by those completed bookings. Count each booking's turnover once and state which shared costs you allocate.
3. Unit contribution: accommodation revenue earned during the period minus the corresponding direct costs and allocated shared operating costs. This is an amount, not net profit. State which expenses remain outside it.

Allocate shared costs using a documented basis, such as recorded working hours or occupied nights, appropriate to the cost. Keep the basis consistent between periods and explain changes. Match costs to the activity they support, rather than simply using payment dates.

Illustrative example: equal occupancy, different workload

Over six nights, unit 402 completes three two-night stays. Unit 705 completes one six-night stay. Each earns accommodation revenue R and has comparable other costs O. Each departure requires one completed turnover costing C.

Contribution is R − O − 3C for unit 402 and R − O − C for unit 705. The difference is 2C, without assuming any market rate.

Before adding units, decide whether you can absorb the extra turnovers without weakening contribution. Revenue can rise while travel, replacement cover and shared costs grow faster. If contribution deteriorates, review pricing and capacity before making more inventory available.

Approve each unit before making it bookable

Available inventory is not ready inventory. Before opening bookings, collect evidence that you can deliver what the listing promises. Do not copy another property's permissions, instructions or assumptions, even when both units share a building.

1. Complete the operational readiness gate

Copy this checklist for each unit. Give every outstanding item an owner and evidence of completion.

• Physical inventory: check equipment, furniture, linen and condition against the proposed offer.
• Owner agreement: document responsibilities, authorisations and responsibility for handling damage.
• Building access: confirm guest and staff entry arrangements with building management.
• Maintenance: identify defects, assign responsibility and verify conditions for use.
• Cleaning capacity: include cleaning, inspection, supplies and backup coverage in the team's actual workload.
• Listing accuracy: check photographs, location, amenities and restrictions against the property.
• Pricing review: have the designated reviewer record approval, conditions and exceptions.
• Guest instructions: check arrival and usage instructions; exclude internal notes and unrelated access credentials.
• Accountable sign-off: identify the approver and store supporting evidence before enabling bookings.

2. Verify what applies to this property

This checklist does not establish legal compliance. Check current conditions and resolve applicability with qualified local advice:

• RNT: verify applicability and property coverage with MinCIT and Confecámaras.
• Guest reporting: consult Migración Colombia and MinCIT.
• Invoicing: check the relevant treatment with DIAN.
• Local use and safety conditions: confirm with the alcaldía, the local municipal authority.
• Personal data: check handling requirements with the Superintendencia de Industria y Comercio.

Use this internal record for each verification. Keep it separate from guest-facing instructions.

Unit: [identifier]
Topic checked: [topic]
Official source consulted: [authority and document or enquiry]
Verification date: [date]
Responsible person: [name and role]
Evidence stored at: [location]
Unresolved issue: [issue or none]
Decision and approval: [status, approver and date]

3. Release or hold

Open bookings when evidence supports the offer and applicable checks are resolved. Keep the unit blocked when access, safety, delivery capacity or operating conditions remain uncertain. If an amenity is unavailable, correct the offer first and check it again.

Tip: Sales pressure is not approval. Record who can remove the block and what evidence they need.

When something fails, contain it and close the loop

Give every incident one owner and one agreed set of commitments. Several people offering different solutions can turn an access failure into a coordination failure.

1. Protect people and establish the facts

1. Stop use of an area or equipment when there are signs of danger. Follow your emergency escalation process where appropriate. Do not improvise repairs or unsafe access workarounds.
2. Confirm the unit, booking, guest’s location and reported problem. Separate verified facts from assumptions.
3. Assign an owner and backup. If the founder is unavailable, escalate to the role authorised for that shift. Do not leave the incident waiting in the founder’s personal chat.

2. Confirm options and record commitments

1. Check which remedies the owner can authorise. If none resolves the situation, escalate before promising anything.
2. Put one person in charge of guest communication. Offer confirmed options only. Record what the guest accepted and when you will provide the next update.
3. Keep facts, decisions, ownership and outstanding work in the incident record. Keep credentials and internal notes out of guest-facing messages.

Tip: Commit to an update you can deliver, not a resolution time you cannot yet confirm.

Worked example: evening access failure in unit 705

This is an illustrative scenario. A guest reports being unable to enter. Reception verifies identity through the approved procedure and checks the problem without asking the guest to post access codes in a shared chat. The incident owner contacts authorised support and validates an alternative before offering it.

Tell the guest the current status and next update. Keep verification details and internal coordination in the restricted record. Do not duplicate credentials there if they belong in an authorised credential store.

3. Verify recovery and address the cause

1. Confirm with the guest that access works. A completed task does not prove service has been restored.
2. During a system outage, use a restricted fallback record containing the incident identifier, owner, commitments and outstanding work. Afterwards, reconcile changes into the main record and retire the temporary copy under your retention policy.
3. Review the cause and assign a correction whose completion you can verify.

Avoid three common mistakes: closing on a supplier’s assurance, making parallel promises and leaving lessons in chat. Counter them with guest confirmation, one spokesperson and a specific procedure update.

Measure whether the operation works without you

Record outcomes, not just checked boxes. You need to know whether a unit was ready as promised, who removed the obstacle and whether someone had to find you before making a decision. A closed task does not prove an on-time release.

Copyable operating record

This template contains illustrative sample rows. Times are example planning assumptions, not service standards. Replace bracketed fields and keep supporting evidence in an access-controlled record.

Calculate on consistent terms

Use the same period and scope for each numerator and denominator:

• On-time releases: verified releases completed by the commitment ÷ releases scheduled for the period. Count overdue, unfinished releases as missed; exclude cancellations made before the commitment and record why.
• Founder dependence: decisions requiring founder intervention ÷ logged decisions. Receiving an information-only copy does not count as intervention.
• Reopened tasks: tasks closed during the period that subsequently reopened ÷ tasks closed during that period. Use a consistent observation window and label provisional results.
• Cost per completed turnover: costs attributable to completed turnovers ÷ completed turnovers.
• Operational cost per booking: operating costs attributable to bookings departing in the period ÷ those completed bookings.

Keep the shared-cost allocation rules established earlier. Do not mix bookings created with completed stays or change the inclusion basis between reviews. Missing costs mean a provisional calculation, not zero cost. Missing completion evidence cannot support an on-time result. With a zero denominator, report “not applicable.”

Tip: Review every decision that needed you: was authority, information or coverage missing? Fix the cause, not just the incident.

Compare equivalent periods and separate newly added units from established units. Show the underlying counts and missing records alongside each metric. Small samples and a larger portfolio do not prove improvement. Set your own review thresholds based on observed capacity and service commitments. Assign an owner to investigate recurring deviations rather than treating the dashboard as a score to defend.

Prepare the next expansion before accepting it

Accept more units when you can show how you will service them, not when you hope the team will work it out. Treat this sequence as readiness gates, not a universal timetable.

1. Test capacity before committing it

1. Map decisions and workload. Identify recurring approvals and overlapping departures, cleaning, inspections and arrivals. Include travel between properties and unresolved exceptions.
2. Assign owners and backups. Every outcome needs an accountable person and a replacement who understands their decision limits.
3. Test core routines. Ask someone other than the author to handle a unit release and a booking change using the available instructions. Fix gaps before adding work.
4. Consolidate records. Confirm that backups can find current bookings, tasks and instructions without searching your personal messages.
5. Check financial visibility. Verify that you can review pricing, exceptions, costs and contribution by unit without mistaking revenue for profitability.
6. Rehearse your absence. Simulate a concentrated turnover day or a period when you are unavailable. Record where work stops, correct the cause and repeat the test.

Decide: proceed, pause or narrow the scope

• Can reception confirm a unit is ready using completion evidence?
• Can backups find current records?
• Does every pricing exception have an owner?
• Will contribution remain visible as units are added?

Proceed when the test demonstrates capacity. Pause when unresolved risks remain. Narrow the scope when you can support only part of the proposed expansion without weakening service.

Tip: More staff or software will not repair unclear accountability.

If you evaluate multi-property operational tools, test those same cases before choosing. Look for fewer broken handoffs and reliable access to records, not simply more features. Your next expansion should run on demonstrated capability, not your constant availability.