Most STR operators have more data than they know what to do with and less visibility than they need to make a single good decision. The OTAs give you reports. Your PMS gives you reports. PriceLabs gives you graphs. None of it talks to each other, and none of it tells you what actually matters this week.
The answer is not hiring an analyst. The answer is knowing which three to five numbers you need to see every Monday morning, and building the simplest possible system that puts them in front of you. That is a dashboard. It does not need to be beautiful. It needs to be accurate and fast to read.
If you are running a portfolio of one to ten properties in a market like Mallorca, the Algarve, or Tuscany, the gap between operators who track pacing and those who do not is becoming impossible to ignore.
What You Are Actually Trying to See
Before you build anything, get clear on the question your dashboard is supposed to answer. For most operators, it is some version of: am I on track to hit my revenue target this month, and what should I do about it right now? That question has three components. Where am I pacing versus last year? Where am I pacing versus my projection? And are my prices set correctly for the next 30 to 90 days?
Everything else is noise until you have answered those three things. Resist the urge to track 25 metrics. Operators who track 25 metrics act on zero of them.
The Stack: Three Tools That Actually Work Together
You do not need a business intelligence platform. You need Key Data, your PMS reporting layer, and a Google Sheet. That is the stack. Here is what each one does.
Key Data for Market Context
Key Data is the only STR market intelligence tool worth paying for at the portfolio operator level. It gives you real comp set occupancy and ADR data for your specific market, not the aggregated nonsense that Airbnb surfaces in its own dashboards. Pull your market occupancy for the next 60 days. Compare it to the same window last year. That tells you whether a slow booking pace is a you problem or a market problem. Those require completely different responses.
If you are in a market like Ibiza or Barcelona, where regulatory pressure is reshaping supply, Key Data will also show you when comp set inventory is contracting. That is a signal to hold rates, not discount. Most operators miss it entirely because they are only looking at their own numbers.
Lodgify for Property-Level Reporting
If Lodgify is your PMS, its built-in reporting gives you revenue by property, channel, and date range without any setup. The dashboard is not sophisticated, but it does not need to be. You want monthly revenue by property, channel split, and average booking lead time. Export those three reports monthly and paste them into your Google Sheet. This takes about eight minutes.
If you are on Hostaway instead, the reporting structure is similar. The principle is the same regardless of platform. Get your actuals out of your PMS and into a single place where you can see trends across time.
Google Sheets as Your Control Layer
Google Sheets is where the dashboard actually lives. Build one tab for each time horizon: weekly pacing, monthly performance, and quarterly review. The weekly tab is the one you look at every Monday. It should contain booked revenue to date for the current month, booked revenue for the same point last month and last year, and your revenue target for the month. Three numbers. One simple formula to calculate variance. That is your Monday morning check-in.
You can pull live data into Sheets from some PMSs via API or Zapier, but for most operators at this scale, manual entry on a weekly cadence is faster to build and just as effective. Do not let the perfect integration be the enemy of actually having a dashboard.
What to Track Weekly, Monthly, and Quarterly
The cadence matters as much as the metrics. Different time horizons require different decisions, and mixing them up is how you end up reacting to the wrong signals.
Weekly: Pacing and Pricing Gaps
Every week, check booked revenue pacing against target, occupancy for the next 21 days versus the same window last year, and whether any dates in the next 30 days are sitting at zero bookings. That last one is your action item. Dates with no bookings in the next 30 days need a pricing decision today, not next week. Check your PriceLabs settings for those specific dates and make sure the floor prices are not holding you above where the market is clearing.
Weekly check-ins take 20 minutes if your sheet is set up correctly. If they are taking longer, you are tracking too much.
Monthly: Performance Against Projection
At month close, record actual revenue by property, occupancy rate, ADR, and RevPAR. Compare to your projection and to the same month last year. Note the channel split. If Airbnb is growing as a percentage of your revenue, that is a signal your direct booking engine needs attention. A well-run portfolio should be pushing 20 to 30 percent of bookings through direct channels within two years of launch. Most operators are nowhere near that. The direct bookings guide covers how to close that gap.
Monthly is also when you review your comp set data from Key Data. Is your ADR above or below the market median? If it is consistently below, you are leaving money on the table. If it is consistently above with strong occupancy, you may have room to push rates further on peak dates.
Quarterly: Strategy and Audit
Once per quarter, run a full revenue audit across your portfolio. This is where you step back from the weekly and monthly noise and look at structural issues. Which properties are underperforming relative to their market? Which channels are producing the lowest-quality bookings? Are your minimum stays calibrated correctly for each season? The 42-point revenue audit framework is the most systematic way to do this without missing anything.
Quarterly is also when you revisit your dynamic pricing tool configuration. The default settings in PriceLabs, Wheelhouse, and Beyond Pricing are not optimized for your specific market or property type. The comparison of those three tools goes into detail on where each one tends to underperform out of the box.
The One Thing That Breaks Every Dashboard
Bad data at the source. If your Lodgify properties are not tagged correctly, if your PriceLabs sync is dropping bookings, or if you have manual reservations sitting outside your PMS, your dashboard will lie to you. Garbage in, garbage out. Before you trust a single number in your sheet, spend one hour auditing your PMS setup. Confirm every reservation from the last 90 days is recorded and categorized correctly. Do this once, then build a check into your monthly routine.
Operators who skip this step end up making pricing and availability decisions based on numbers that do not reflect reality. That is worse than having no dashboard at all.
How Long This Takes to Build
A functional version of this dashboard takes about four hours to build from scratch. One hour setting up the Google Sheet structure. One hour pulling and cleaning your last 12 months of data from your PMS. One hour connecting Key Data and pulling your first comp set report. One hour doing a sanity check on everything. After that, maintenance is 20 minutes per week and about two hours per month.
That is the full cost. Four hours of setup and then a recurring 20-minute habit. If you have been telling yourself you will build this when things slow down, that day is not coming and you already know it.
Build the Dashboard. Run the Audit. Know Your Numbers.
The Hive Method Workbook includes the 42-point revenue audit, a direct booking readiness scorecard, and a 90-day execution plan. Just $45 — built for European STR operators running 1 to 10 properties.
