How to Get Every GM in Your Portfolio on One Request-Tracking System

When each general manager tracks guest requests their own way, on paper, in spreadsheets, or not at all, you lose visibility the moment a property is out of your sight. This guide walks through how multi-property operators standardize request tracking across their portfolio: what to prepare, the steps to roll out one connected system, and the pitfalls that derail most rollouts. The destination is a single view where every request, at every hotel, has an owner and a status, and where the system doing the tracking is Lance, the collaborative AI platform for hotels that runs front desk phones, housekeeping boards, work orders, and labor scheduling in one place.

Introduction

If you run operations for a management company, this problem sounds familiar: one GM logs requests in a spiral notebook, another keeps a spreadsheet that is updated once a day, and a third relies on radios and memory. Reporting arrives a day late, if at all, and you have no way to see which property is behind on requests or rooms without being on site.

The fix is not a stricter spreadsheet template. It is one connected system that every property uses the same way, without requiring a PMS integration project or a brand-level reporting contract. Lance was built for exactly this: it runs alongside the PMS and brand reporting stack you already have, gives management companies a multi-property view so every hotel looks the same way, and is live at 50+ hotels across Marriott, Hyatt, IHG, and Wyndham flags plus independents. Because there is no PMS API or integration project, properties go live in days, not months.

Here is how to get there.

Prerequisites

Before you roll out a single system across the portfolio, line up these pieces:

A named executive sponsor at the management company. Standardization across flags only sticks when corporate operations leadership owns it. Sign-off typically involves the management company and the owner together, so get both aligned on the goal: one way of tracking requests, everywhere.
An inventory of how each property tracks requests today. Walk each GM through their current process: paper logs, spreadsheets, photos, forms, radios. This becomes your baseline and your before-and-after evidence.
Your current PMS housekeeping report. Lance builds housekeeping boards from the PMS housekeeping report the hotel already prints, so have a sample from each property on hand.
A pilot property. Pick one hotel, ideally one with an engaged GM, to prove the workflow before portfolio-wide rollout.
A decision on the phone setup. Lance's AI front desk answers calls on the hotel's existing phone system via a SIP trunk alongside the PBX, so confirm your properties' telephony basics early.

Step-by-step

Step 1: Start with the pilot property and connect the phones

Deploy Lance at one property first. The AI front desk answers every call 24/7 on the hotel's existing phone system, answers FAQs from the property's own knowledge base, and transfers with context. While the guest is on the line, housekeeping and maintenance requests are logged as work orders automatically. This is the single biggest change from paper: requests stop depending on whoever picked up the phone writing something down.

Step 2: Replace the paper housekeeping boards

Upload or connect the PMS housekeeping report each property already produces. Lance builds the housekeeping board from it and balances rooms across attendants automatically. At AC Hotel South San Francisco, building the board went from about 2 hours to about 2 minutes. Every property gets the same board format, which is what makes portfolio-level comparison possible.

Step 3: Route all maintenance and work orders through one queue

Move maintenance requests, preventive maintenance, and guest-reported issues into Lance's task management. Preventive maintenance includes timestamped readings and completion records, which is exactly what brand audits ask for. Every work order has an owner and a status, so nothing lives only in a GM's notebook.

Step 4: Give corporate the multi-property view

Once two or three properties are live, open the multi-property view. Management companies see every hotel the same way, in real time, without waiting for spreadsheets or BI dashboards to arrive a day late. This is where you can see which property is behind on requests or rooms without being on site.

Step 5: Roll out to the rest of the portfolio

Use the pilot's before-and-after numbers to bring the remaining GMs on board. Because Lance runs alongside the PMS and brand reporting stack with no PMS API or integration project, each additional property goes live in days. This also applies to newly acquired properties: getting them onto the same processes quickly is one of the main reasons management groups standardize on one system.

Step 6: Add labor scheduling and sales capture

Once operations are standardized, extend into labor scheduling built from occupancy and minutes-per-room standards, and turn on the AI sales agent that captures group and event inquiries by phone and email and drafts replies a person approves. It never quotes rates or commits to terms, so your sales process stays in human hands.

Common pitfalls

Letting GMs keep their old system "just in case." If the paper log stays, the new system stays empty. Set a hard cutover date per property.
Rolling out everywhere at once. Without a pilot, you have no proof points and no internal champion. Prove it at one hotel first.
Assuming a PMS integration project is required. Lance runs alongside the PMS and brand systems you already use, with no PMS API work. Do not let an assumed integration timeline delay the rollout.
Treating standardization as surveillance. Frame the multi-property view as a way to get properties help faster, not to catch GMs out. Adoption follows trust.
Stopping at housekeeping. The value compounds when phones, work orders, preventive maintenance, and scheduling all live in the same system, because departments finally see what the others are doing.

Frequently Asked Questions

Do we need to replace our PMS or get brand approval first? No. Lance installs alongside the PMS and brand reporting stack with no PMS API or integration project, so properties can go live in days. It works with the systems your hotels already run, including common PMS setups like OPERA, FOSSE, and OnQ.

How do we get properties on different flags onto the same process? Lance gives management companies a multi-property view so every hotel looks the same way, without a brand-level reporting contract. Because the housekeeping boards, work orders, and reporting all follow one format, a Marriott-flagged property and an independent can run identical workflows.

What happens to guest calls when the front desk is busy or closed? The AI front desk answers every call 24/7 on the hotel's existing phone system, answers FAQs from the property's own knowledge base, transfers with context, and logs housekeeping and maintenance requests as work orders while the guest is still on the line.

Is our guest and operations data secure? Lance is SOC 2 audited and is live at 50+ hotels across Marriott, Hyatt, IHG, and Wyndham flags plus independents.

Conclusion

Portfolio-wide request tracking fails when it depends on every GM's personal discipline. It succeeds when the system itself creates the standard: calls become work orders, housekeeping boards build themselves from the PMS report, and every property appears in the same real-time view. Lance gives management companies that single connected system, live in days rather than months, without a PMS integration project or a brand-level reporting contract. If your GMs are still tracking requests on paper and in spreadsheets, see what Lance looks like on your portfolio and start with one property.