Front Desk & Housekeeping for Nigerian Guesthouses: Running a 10–30 Room Property Properly

The short answer: a 10 to 30 room Nigerian guesthouse loses money in three specific places — rooms sitting dirty because reception does not know they are clean, bar and restaurant charges that never reach the guest bill, and the shift handover where everything one receptionist knew fails to reach the next. Fix those three and you have fixed most of the gap between what your property earns and what it should.

This is about operations rather than purchasing. If you are still choosing a system, our buyer's guide to hotel management software in Nigeria covers that decision, and Nookpal for hotels and guesthouses covers what we built.

The room status lifecycle

Every room in your property is in exactly one of a small number of states at any moment. Most small Nigerian guesthouses do not name these states, which is precisely why reception and housekeeping disagree about them.

Status	Means	Who changes it
Vacant clean	Ready to sell right now	Housekeeping, after inspection
Occupied	Guest in residence	Front desk, at check-in
Vacant dirty	Guest departed, not yet cleaned	Front desk, at check-out
Out of order	Cannot be sold — leak, AC failure, no water	Maintenance or supervisor

The money is in the transition from vacant dirty to vacant clean. A guest checks out at 11am. The room is cleaned by 12:30pm. A walk-in arrives at 1pm. If reception does not know that room is ready, you either turn away a paying guest or sell a room that has not been touched — and in a 20-room property, one avoidable empty night a week is fifty-two nights a year.

Which is why housekeeping status has to be updated by the person doing the cleaning, on the device they actually carry, at the moment they finish. Not on a clipboard collected at 4pm. Not by a supervisor phoning reception. If updating status requires walking to a shared desktop at reception, it will happen in batches, and batched status is stale status.

Out of order is not the same as dirty

Small properties routinely conflate these, and it costs them twice. A room with a broken AC that is marked dirty gets cleaned and sold, and the guest complains. A room marked out of order with no reason and no expected return date silently disappears from your inventory for weeks. Record the reason and the expected fix date, and review the list weekly — out-of-order rooms are lost revenue that nobody is watching.

The guest bill is where small hotels leak

For most Nigerian guesthouses, food and beverage is a meaningful share of revenue and the single largest source of leakage. The classic flow is: barman writes a chit, waiter carries it to reception, reception types it into the guest's bill, guest disputes it at checkout, manager waives it to keep the peace.

Every step in that chain is a place a charge disappears. Some of it is genuine error. Some of it is not — a manual chit system with no attribution is an invitation, and staff know it.

What good looks like:

• The charge is posted where it happens, at the bar or restaurant, at the time it happens.
• It carries the room number and the staff member who posted it. Attribution changes behaviour more than any policy does.
• It appears on the guest's folio immediately, so the guest can query it that evening rather than argue at 7am checkout with a taxi waiting.
• Checkout is one settlement of an accumulated bill, not a reconstruction.

If you change one thing this quarter, change this. It usually pays for the system on its own.

Shift handover: the invisible failure

Ask any guesthouse manager where problems come from and they will describe something that happened on a shift they were not on. The night receptionist promised a late checkout. A guest complained about the generator and was offered a discount. Room 12's shower was reported broken. None of it was written down, so the morning shift knows nothing.

A handover needs four things recorded against the property, not in someone's memory:

1. Arrivals expected on the next shift, including late arrivals and anyone who called ahead.
2. Departures and any agreed late checkouts, with who agreed them.
3. Open issues — maintenance reported, complaints made, promises given to guests.
4. Money — what was collected, in what form, and what is outstanding.

Point three is the one that decides your reviews. A guest who reports a problem and sees nothing happen for two shifts writes a very different review from one whose problem was visibly picked up by the next person on duty.

What Nigerian conditions actually change

Generic hospitality advice assumes reliable power, reliable connectivity and card payment. None of those hold, and the operational design has to account for it.

• Check-in must survive an outage. If the front desk cannot check a guest in when power or the line drops, staff fall back to paper — and once a shift has run on paper, your system's data is unreliable until someone reconciles it, which nobody does. Test this before you commit to any system.
• Power is a guest-experience feature, not a background cost. Rooms without reliable supply generate complaints regardless of how well they are cleaned, and generator noise at night shows up in reviews. Track fuel against the property so you know what the reliability is costing you.
• Payment is mostly transfer, not card. Reception needs to confirm a transfer has genuinely landed before releasing a guest at checkout — the same fake-alert discipline that applies to taking direct payments applies at a hotel front desk, and it is worse here because the guest is leaving.
• Corporate accounts bill monthly. A contractor staying three weeks does not settle at checkout; their company pays on invoice. Your front desk process has to allow a guest to leave with a balance that is not a debt problem.
• Staff share devices. Design for one shared reception terminal and cheap phones for housekeeping, not a device per person.

Access: who should see what

Small properties tend to run on one shared login, which means every receptionist can see revenue, edit rates and delete bookings. That is a control problem and an accountability problem at once — when something is wrong, nobody can be asked about it, because it could have been anyone.

A workable minimum for a small guesthouse:

• Reception — arrivals, departures, room status, posting charges, taking payment. Not rate changes, not revenue reports.
• Housekeeping — their assigned rooms and status updates. Nothing else.
• Bar and restaurant — post charges to an occupied room. Cannot see the folio total or the guest's details.
• Manager or owner — everything, including who did what.

Individual logins matter more than the exact permission split. The point is that actions have names attached.

All of this assumes each person can see their own work and not everyone else's. In Nookpal reception, housekeeping and bar staff each get their own login scoped to their role — housekeeping updates room status from a phone, the bar posts a charge to a room without seeing the folio total, and only the owner sees revenue. Individual logins are also what turn "someone voided that charge" into a name and a timestamp.

The three reports worth reading weekly

Small properties either produce no reports or produce twenty nobody opens. Three are enough to run a guesthouse:

1. Occupancy and average rate by week. Together these give you RevPAR, which is the only figure that tells you whether a rate change worked. A discount that fills rooms but lowers RevPAR made you poorer.
2. Revenue by department. Rooms versus food and beverage versus other. If F&B is flat while occupancy rises, charges are leaking.
3. Out-of-order rooms and open maintenance. Directly measurable lost revenue, and the report nobody runs.

Two of the three are reports Nookpal produces from what reception and housekeeping are already entering — occupancy and average rate by week, and revenue split between rooms and food and beverage — so reading them weekly is a habit rather than a spreadsheet exercise.

A week to fix the basics

• Monday: name your room statuses and brief both reception and housekeeping on who changes what, and when.
• Tuesday: get housekeeping updating status from a phone at the moment they finish a room.
• Wednesday: put bar and restaurant charges onto the room bill at the point of sale, with the staff member recorded.
• Thursday: introduce a written shift handover covering arrivals, departures, open issues and money.
• Friday: give every staff member their own login, scoped to their role.
• Weekend: run the three reports and see what they tell you about the week you just had.

None of that requires new software to begin — a disciplined paper handover beats an undisciplined system. But each of those five habits gets substantially easier when the front desk, housekeeping and the bar are looking at the same live picture, which is what a property management system is actually for.