Duties & Responsibilities of a General Manager - Resort (Single or Multi Unit)

By Nigel Thomas | Hospitality Operations & F&B Consultant

Ask ten hoteliers what a Resort General Manager actually does, and you will get ten different answers. Some will describe a glorified front desk supervisor. Others will describe a financial controller with a name badge. The truth sits somewhere in between, and it changes shape depending on property size, ownership structure, and whether you are managing a single asset or several units under one banner.

This article breaks down the real responsibilities of a Resort GM - not the responsibilities listed in a job description template, but the ones that actually determine whether a property thrives or quietly bleeds money and reputation. It is written from the ground level, based on what actually works in independent and boutique resort settings, including remote and hill-station properties where the usual corporate playbook does not apply.

1. The Modern Resort GM: Single-Unit vs Multi-Unit

Before getting into the duties themselves, it helps to separate two very different versions of this role.

The Single-Unit GM

At a single property - say, an 18-cottage boutique resort on a 2.5-acre hillside plot - the GM is the operation. There is no regional office two floors up to escalate a problem to. Decisions on staffing, vendor contracts, guest complaints, pricing, and even minor capital expenditure often land directly on the GM's desk. The advantage is speed: a single-unit GM who knows the property well can fix a problem in hours that would take a corporate chain weeks of approvals to resolve. The disadvantage is exposure - there is no backup system if the GM gets it wrong, and no shared resource pool to lean on during a crisis.

The Multi-Unit GM (or Operations Head)

When a GM oversees two, three, or more properties, the job shifts from hands-on execution to systems design and oversight. The multi-unit GM cannot be physically present at every property every day, so the entire job becomes about building reliable systems, training competent on-ground teams, and creating reporting structures that surface problems before they become guest-facing disasters. Multi-unit GMs spend less time solving today's problem and more time preventing tomorrow's - through standardized SOPs, shared vendor agreements, and performance dashboards that work across locations with different terrain, staffing pools, and guest profiles.

Both versions of the role share the same five core pillars. What changes is scale, delegation, and the tools used to maintain control without being physically present everywhere at once.

2. End-to-End Operations Ownership

The single biggest difference between an average GM and an excellent one is whether they treat the resort as a collection of departments or as one system.

In too many properties, front-of-house, back-of-house, food & beverage, housekeeping, and guest experience operate as separate silos. The front desk doesn't know what the kitchen is running low on. Housekeeping doesn't know a VIP guest is checking in two hours early. F&B doesn't coordinate with the activities desk on a group booking's dinner timing. Each department might individually be "doing fine," and yet the guest still experiences friction, because nobody owns the seams between departments.

A GM with genuine end-to-end ownership operates differently:

• Daily operations briefing. A short, structured huddle (10-15 minutes) every morning where department heads or shift leads flag arrivals, departures, VIPs, maintenance issues, and F&B requirements for the day - so nothing surprises anyone by lunchtime.
• Cross-department visibility. Housekeeping should know the F&B forecast for the day; the kitchen should know occupancy and any dietary flags; the front desk should know which rooms had maintenance issues resolved overnight.
• Single point of escalation. Guests should never be bounced between departments to solve a problem. The GM builds a culture where any staff member can resolve a guest issue on the spot, with department heads as the only escalation layer above them.
• Walk-throughs, not just reports. Reports tell you what happened yesterday. A physical walk-through of the property - cottages, kitchen, gardens, back-of-house areas - tells you what is about to go wrong today. A GM who only manages from a desk is managing blind.

This is especially critical at boutique and hill-destination properties, where guest expectations are high relative to the intimacy of the setting, but the operational infrastructure (backup power, network connectivity, vendor access, spare parts) is often thinner than what a city-based five-star property can rely on. End-to-end ownership is not a management style choice here - it is survival.

3. SOP Development From the Ground Up

Standard Operating Procedures get a bad name because most people have only encountered the wrong kind: thick binders copied from a corporate chain's manual, written for a 200-room property with dedicated departments for everything, and dropped onto an 18-cottage boutique resort where one supervisor wears four hats.

Good SOPs for a smaller or independent property look nothing like that. They are built from the ground up, based on how the property actually runs, not how a textbook says it should run.

What makes an SOP actually usable

• Written for the staff who will use it. If your housekeeping team's strongest language is Hindi or a regional dialect, an SOP written entirely in formal corporate English will sit in a drawer unread. SOPs need to match the literacy level and language comfort of the team executing them - visual checklists often outperform paragraphs of text.
• Short enough to actually follow. A check-in SOP that takes three pages to read will never survive a Friday evening rush with four arrivals at once. The best SOPs fit on a single page, or even a laminated card at the workstation.
• Built around failure points, not ideal scenarios. A good SOP doesn't just describe the happy path ("guest arrives, checks in, is escorted to room"). It describes what to do when the room isn't ready, when the guest arrives four hours early, when the payment gateway is down, when there's a power cut mid-check-in. Properties that only document the ideal scenario get caught out by the predictable exceptions.

Priority SOP areas for any resort

1. Check-in / check-out procedures - including ID verification, early arrival/late departure handling, and payment reconciliation.
2. Food safety and kitchen hygiene - temperature logs, storage protocols, allergen handling, and pest control checklists. This is non-negotiable, both for guest safety and for liability protection.
3. Cost control procedures - purchase requisitions, store issue slips, daily consumption reconciliation against sales.
4. Vendor management - approved vendor lists, payment terms, quality-check protocols on delivery, and a clear escalation path when a vendor under-delivers.
5. Emergency and safety procedures - fire, medical emergencies, power outages, and (for hill properties especially) landslide or extreme weather protocols.
6. Guest complaint resolution - empowering staff to resolve issues up to a defined value/authority limit without needing GM sign-off for every minor compensation.

The discipline of writing these SOPs down - rather than keeping them as "tribal knowledge" in the GM's head or a long-serving supervisor's memory - is what allows a property to survive staff turnover without a drop in service quality. It is also what makes a property sellable or franchisable later, since buyers and brand partners want to see documented systems, not dependency on one irreplaceable individual.

4. Cost & Margin Control

Hospitality is a low-margin business even in the best of circumstances. At remote or hill-station properties, margins get squeezed further by logistics: vendors are fewer, delivery costs are higher, perishables spoil faster in transit, and bulk-buying leverage is harder to negotiate when order volumes are small.

A GM who does not actively manage cost and margin is, by default, allowing margin to leak. The leaks are rarely dramatic - they are usually small, repeated, and invisible until a monthly P&L review shows food cost running three points above where it should be.

Where the discipline needs to live

• F&B costing at the recipe level. Every dish on the menu should have a standardized recipe with portion sizes and a calculated cost. Without this, you cannot price intelligently, and you cannot detect when a kitchen team is over-portioning or wasting ingredients.
• Inventory discipline. Daily or weekly stock counts for high-value and high-spoilage items (meat, dairy, alcohol if licensed, imported goods). Variance between what should be in stock and what is actually in stock is one of the earliest warning signs of either waste or pilferage.
• Vendor negotiation suited to remote logistics. In hill or remote locations, it often makes more sense to consolidate orders with fewer, more reliable vendors who can guarantee delivery schedules, rather than chasing the lowest unit price from a vendor who may not show up during monsoon season. Reliability has a cost-saving value of its own, since stockouts and emergency local purchases at retail prices destroy margin fast.
• Energy and utility cost management. Many hill properties run on a mix of grid power, generators, and sometimes solar. A GM should track fuel consumption against occupancy, since generator running time that doesn't correlate with occupancy levels is usually a sign of equipment inefficiency or unauthorized usage.
• Labor cost against occupancy, not against a fixed headcount. Staffing models should flex - through cross-trained roles, contracted seasonal staff, or shift restructuring - rather than carrying a flat headcount through both peak and lean seasons.

None of this is about cutting corners on guest experience. It is about making sure the resort actually keeps the revenue it earns, instead of losing a chunk of it to inefficiency before it ever reaches the bottom line.

5. Team Performance and Training in High-Turnover Markets

Hill-destination and remote resort properties face a staffing reality that city hotels rarely deal with at the same intensity: high turnover, seasonal staffing swings, and a smaller local labor pool to draw from. A GM who designs training systems as if staff will stay for years is setting the property up to relearn the same lessons every season.

Principles that work for high-turnover environments

• Modular, fast-track onboarding. New hires should be operational within days, not weeks. This means breaking training into short, focused modules (a half-day on F&B service standards, a half-day on housekeeping protocols) rather than a long generic induction that delays productivity.
• Train for the role, not just the task. Staff who understand why a procedure exists - not just the mechanical steps - adapt better when a situation doesn't match the textbook scenario exactly. A waiter who understands the reasoning behind a food safety rule is more likely to catch a problem a checklist didn't anticipate.
• Cross-training as a retention and resilience tool. In a small property, a front office associate who can also run a basic F&B shift, or a kitchen helper who understands basic housekeeping standards, gives the GM flexibility when someone is sick, on leave, or has left without notice - which happens often in seasonal markets.
• Visible, fair performance feedback. Staff who feel invisible leave faster. Simple, regular recognition - even informal - for consistent guest-facing performance reduces churn more effectively than most formal incentive schemes.
• Local hiring and community relationships. Especially in hill and remote destinations, building a reputation as a fair, reliable employer within the local community creates a pipeline of returning seasonal staff and word-of-mouth referrals - which is far more reliable than repeated cold hiring through agencies.

The goal of a training system in a high-turnover environment is not to eliminate turnover - that is rarely fully possible - but to make sure guest-facing consistency does not collapse every time someone new joins.

6. Guest Experience, Reputation, and Experiential Value-Add

Operational excellence keeps a resort running. Guest experience is what gets the resort talked about, recommended, and rebooked.

Beyond the basics

Clean rooms, prompt service, and good food are the entry ticket, not the differentiator. What turns a guest into a repeat guest - or, more valuably, an organic promoter on review platforms and social media - is the layer above the basics:

• Experiential packages tied to the location. A hill resort sitting near trekking routes, viewpoints, or local nature attractions should be actively packaging those assets - guided nature walks, sunrise/sunset viewpoint trips, local village or market visits, bonfire evenings - rather than leaving guests to discover them on their own through a hand-drawn map at reception.
• Curated dining experiences. A breakfast served on a terrace with a view, a regional-cuisine dinner night, or a simple but well-presented outdoor barbecue evening costs little extra to execute but creates the kind of memory guests photograph and share - which is free, organic marketing.
• Reputation and review management as an active discipline, not an afterthought. This means monitoring review platforms consistently, responding to every review (positive and negative) professionally and promptly, and feeding recurring complaint themes back into operations as corrective action - not just apologizing publicly and moving on.
• Personalization at low cost. Remembering a returning guest's room preference, a small note for a birthday or anniversary stay, or simply training staff to use guest names naturally - these cost nothing but create disproportionate guest loyalty.

A GM who treats guest experience as the front desk's job alone is missing the point. Guest experience is shaped by housekeeping's attention to detail, the kitchen's consistency, the gardener's upkeep of the grounds, and the night security guard's courtesy - it is an output of the entire operation working in sync, which loops directly back to the "end-to-end ownership" principle covered earlier.

7. Multi-Unit Specific Responsibilities

When a GM's role expands beyond a single property, a new set of responsibilities layers on top of everything above.

• Standardization without losing local character. Brand consistency across properties matters for guest trust, but a hill resort and a beach resort under the same ownership should not feel identical. The multi-unit GM's job is to standardize the things guests expect to be reliable everywhere (booking process, service response times, hygiene standards) while allowing local teams to retain the character that makes each property distinct.
• Remote performance monitoring. Since physical presence at every property daily isn't possible, multi-unit GMs rely on structured reporting - daily flash reports, weekly department head calls, and periodic unannounced property visits - to maintain visibility without micromanaging.
• Resource sharing across properties. Shared vendor contracts, a central training calendar, and the ability to temporarily move staff between properties during peak season are tools available to multi-unit operations that a single-property GM does not have.
• Succession and bench strength. With multiple properties, building a bench of trained assistant managers or supervisors who can step up temporarily (or permanently) protects the business against the risk of losing a single-property GM unexpectedly.
• Capital allocation decisions. Deciding which property gets the next renovation budget, which one needs a marketing push, and which underperforming unit needs a deeper operational review - these are portfolio-level decisions a single-unit GM never has to make.

8. The 90-Day Operational Audit and Improvement Framework

Whether stepping into a single boutique resort or a small portfolio, the first 90 days set the tone for everything that follows. A structured audit approach - rather than reactive firefighting - is what separates a GM who stabilizes a property from one who simply survives it.

Days 1-30: Observe and Document

Full walk-through of every department, every shift pattern, and every existing SOP (or lack thereof). Review the last 6-12 months of financials, occupancy data, and guest reviews. Meet every staff member individually, even briefly. The goal in this phase is understanding, not changing anything yet - premature changes before understanding root causes often create new problems.

Days 31-60: Stabilize and Document SOPs

Address the most urgent, highest-risk gaps first - typically food safety, cash handling, and any guest-facing process actively causing complaints. Begin formal SOP documentation for the core operational areas. Start basic cost-tracking systems if none exist.

Days 61-90: Optimize and Build Forward

Introduce the experiential and guest-experience improvements. Launch a structured training calendar. Present ownership with a clear report: what was found, what was fixed, what is now in place, and a roadmap for the next two quarters with measurable targets - occupancy, average review rating, food cost percentage, and staff retention being the typical core metrics.

This phased approach gives ownership visibility and confidence early, rather than asking them to simply trust that "things are improving" without evidence.

Conclusion

The title "General Manager" covers a wide range of actual day-to-day realities, but the core of the job does not change: someone has to be accountable for turning separate departments into one coordinated guest experience, building systems that outlast any one individual, protecting margin without damaging quality, and keeping a team motivated even when the market makes retention difficult.

Whether the assignment is one boutique hillside resort or a small group of properties, the principles are the same. What changes is scale, delegation, and the tools used to maintain control without being everywhere at once.